|Finding ID||Version||Rule ID||IA Controls||Severity|
|When Kubernetes is started, components and user services are started. For auditing startup events, and events for components and services, it is important that auditing begin on startup. Within Kubernetes, audit data for all components is generated by the API server. To enable auditing to begin, an audit policy must be defined for the events and the information to be stored with each event. It is also necessary to give a secure location where the audit logs are to be stored. If an audit log path is not specified, all audit data is sent to studio.|
|Kubernetes Security Technical Implementation Guide||2022-12-02|
|Check Text ( C-45676r863801_chk )|
| Change to the /etc/kubernetes/manifests directory on the Kubernetes Control Plane. Run the command: |
grep -i audit-policy-file *
If the audit-policy-file is not set, this is a finding.
|Fix Text (F-45634r863802_fix)|
| Edit the Kubernetes API Server manifest and set "--audit-policy-file" to the audit policy file. |
Note: If the API server is running as a Pod, then the manifest will also need to be updated to mount the host system filesystem where the audit policy file resides.