Ensure that the AdvancedAuditing argument is not set to false (API Server)

Do not disable advanced auditing. AdvancedAuditing enables a much more general API auditing pipeline, which includes support for pluggable output backends and an audit policy specifying how different requests should be audited. Additionally, this enables auditing of failed authentication, authorization and login attempts which could prove crucial for protecting your production clusters. It is thus recommended not to disable advanced auditing.

Suggest Edits

Risk Level: Low
Cloud Entity: Pods
CloudGuard Rule ID: D9.K8S.LOG.05
Covered by Spectral: Yes
Category: Compute

GSL LOGIC

KubernetesPod where labels contain [value='kube-apiserver'] and namespace = 'kube-system' should have spec.containers with [(parsedArgs contain [key like 'feature-gates' and value unlike '%AdvancedAuditing=false%']) or (parsedArgs contain-none [key like 'feature-gates'])]

REMEDIATION

Follow the Kubernetes documentation and set the desired audit policy in the
/etc/kubernetes/audit-policy.yaml file. Then, edit the API server pod specification file $apiserverconf
and set the below parameters.
--audit-policy-file=/etc/kubernetes/audit-policy.yaml

Pods

Pods are the smallest deployable units of computing that can be created and managed in Kubernetes.A Pod is a group of one or more containers (such as Docker containers), with shared storage/network, and a specification for how to run the containers.

Compliance Frameworks

CIS Kubernetes Benchmark v1.4.0
Kubernetes NIST.SP.800-190
Kubernetes v.1.13 CloudGuard Best Practices
Kubernetes v.1.14 CloudGuard Best Practices

Updated about 1 year ago