|Finding ID||Version||Rule ID||IA Controls||Severity|
|Protecting the audit data from change or deletion is important when an attack occurs. One way an attacker can cover their tracks is to change or delete audit records. This will either make the attack unnoticeable or make it more difficult to investigate how the attack took place and what changes were made. The audit data can be protected through audit log file protections and user authorization. One way for an attacker to thwart these measures is to send the audit logs to another source and filter the audited results before sending them on to the original target. This can be done in Kubernetes through the configuration of dynamic audit webhooks through the DynamicAuditing flag.|
|Kubernetes Security Technical Implementation Guide||2022-12-02|
|Check Text ( C-45673r863794_chk )|
| On the Control Plane, change to the manifests' directory at /etc/kubernetes/manifests and run the command: |
grep -i feature-gates *
Review the feature-gates setting, if one is returned.
If the feature-gates setting is available and contains the DynamicAuditing flag set to "true", this is a finding.
Change to the directory /etc/sysconfig on the Control Plane and each Worker Node and execute the command:
grep -i feature-gates kubelet
Review every feature-gates setting that is returned.
If any feature-gates setting is available and contains the "DynamicAuditing" flag set to "true", this is a finding.
|Fix Text (F-45631r717018_fix)|
|Edit any manifest files or kubelet config files that contain the feature-gates setting with DynamicAuditing set to "true". Set the flag to "false" or remove the "DynamicAuditing" setting completely. Restart the kubelet service if the kubelet config file if the kubelet config file is changed.|