Sensitive information must be stored using Kubernetes Secrets or an external Secret store provider.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-274883 | CNTR-K8-001161 | SV-274883r1107230_rule | CCI-004062 | high |
| Description | ||||
| Sensitive information, such as passwords, keys, and tokens must not be stored in application code. Kubernetes offers a resource called Secrets that are designed for storing sensitive information for use by applications. Secrets are created and managed separately from application code. Additionally, they can be encrypted at rest and access to the secrets can be controlled via RBAC. | ||||
| STIG | Date | |||
| Kubernetes Security Technical Implementation Guide | 2025-05-16 | |||
Details
Check Text (C-274883r1107230_chk)
On the Kubernetes Master node, run the following command:
kubectl get all,cm -A -o yaml
Manually review the output for sensitive information.
If any sensitive information is found, this is a finding.
Fix Text (F-78889r1107229_fix)
Any sensitive information found must be stored in an approved external Secret store provider or use Kubernetes Secrets (attached on an as-needed basis to pods).