cyberstrikeus CIS Red Hat OpenShift Container Platform Benchmark v1.6.0 - Control 5.4.2
Profile Applicability
- Level: 2
Description
Consider the use of an external secrets storage and management system, instead of using Kubernetes Secrets directly, if you have more complex secret management needs. Ensure the solution requires authentication to access secrets, has auditing of access to and use of secrets, and encrypts secrets. Some solutions also make it easier to rotate secrets.
Rationale
Kubernetes supports secrets as first-class objects, but care needs to be taken to ensure that access to secrets is carefully limited. Using an external secrets provider can ease the management of access to secrets, especially where secrets are used across both Kubernetes and non-Kubernetes environments.
Impact
None
Audit Procedure
OpenShift supports a broad ecosystem of security partners many of whom provide integration with enterprise secret vaults. Review your secrets management implementation.
Remediation
Refer to the secrets management options offered by your cloud provider or a third-party secrets management solution.
Default Value
By default, no external secret management is configured.
References
None
CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 3.12 Segment Data Processing and Storage Based on Sensitivity | * | * | |
| v7 | 14.6 Protect Information through Access Control Lists | * | * | * |
MITRE ATT&CK Mappings
| Techniques / Sub-techniques | Tactics | Mitigations |
|---|---|---|
| T1552 | TA0006 | M1026 |
Profile
Level 2 (Manual)