Bind human access to the Kubernetes API and cluster resources to identities that can be centrally governed, monitored, and revoked.
Enforce Managed Cluster Authentication
CCC.K8S.CN16 · Access
Related Capabilities
| ID | Title | Description |
|---|---|---|
| CCC.Core.CP06 | Access Control | The service automatically enforces user configurations to restrict or allow access to a specific component or a child resource based on factors such as user identities, roles, groups, or attributes. |
| CCC.Core.CP29 | Active Ingestion | While running, the service itself can fetch or reach out to some other service or external source to get data, inputs or commands for the service to process or operate on. |
| CCC.K8S.CP10 | Cloud Identity Integration | The service can authenticate cloud identities and authorize their access to cluster resources through Kubernetes and provider-native access controls. |
Related Threats
| ID | Title | Description |
|---|---|---|
| CCC.Core.TH01 | Access is Granted to Unauthorized Users | Logic designed to give different permissions to different entities may be misconfigured or manipulated, allowing unauthorized entities to access restricted parts of the service, its data, or its child resources. This could result in a loss of data confidentiality or tolerance of unauthorized actions which impact the integrity and availability of resources and data. |
| CCC.K8S.TH16 | Unmanaged Credentials Bypass Cluster Identity Controls | Locally managed accounts, static administrative credentials, or legacy authentication methods may remain valid after the associated identity should lose access. Requests authenticated by these mechanisms can bypass centrally managed identity lifecycle and revocation controls. Cluster data may be disclosed, cluster state may be changed, and workloads may be disrupted through unauthorized administrative access. |
Assessment Requirements
| ID | Text | Applicability |
|---|---|---|
| CCC.K8S.CN16.AR01 | When a human accesses the Kubernetes API or cluster resources, authentication MUST use an identity from a centrally managed identity provider or cloud identity service AND that access MUST be revocable independently of the cluster. | tlp-clear, tlp-green, tlp-amber, tlp-red |
| CCC.K8S.CN16.AR02 | Unmanaged local accounts, static human credentials, and legacy authentication methods MUST NOT provide human access to the Kubernetes API or cluster resources. | tlp-clear, tlp-green, tlp-amber, tlp-red |