Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
The Kubernetes API Server must be set to audit log max size.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-242462 | CNTR-K8-003290 | SV-242462r712742_rule | Medium |
| Description |
|---|
| The Kubernetes API Server must be set for enough storage to retain log information over the period required. When audit logs are large in size, the monitoring service for events becomes degraded. The function of the maximum log file size is to set these limits. |
| STIG | Date |
|---|---|
| Kubernetes Security Technical Implementation Guide | 2021-06-17 |
Details
| Check Text ( C-45737r712740_chk ) |
|---|
| Change to the /etc/kubernetes/manifests/ directory on the Kubernetes Master Node. Run the command: grep -i audit-log-maxsize * If the setting "audit-log-maxsize" is not set in the Kubernetes API Server manifest file or it is set to less than "100", this is a finding. |
| Fix Text (F-45695r712741_fix) |
|---|
| Edit the Kubernetes API Server manifest file in the /etc/kubernetes/manifests directory on the Kubernetes Master Node. Set the value of –"--audit-log-maxsize" to a minimum of "100". |