Apply least privilege across cloud and Kubernetes authorization so identities receive only the permissions required for their cluster responsibilities.
Enforce Least-Privilege Cluster Authorization
CCC.K8S.CN02 · 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. |
| CCC.K8S.CP11 | Workload Identity Federation | The service may be configured to exchange Kubernetes service-account identity for short-lived cloud credentials without placing long-lived credentials in workloads. |
| CCC.K8S.CP06 | Declarative Workload Orchestration | The service automatically reconciles Kubernetes workload resources toward their user-declared state by scheduling, restarting, and replacing containers as needed. |
| CCC.K8S.CP14 | Managed Cluster Extensions | The service can manage the installation and lifecycle of supported extensions for networking, storage, policy, observability, and workload management. |
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.TH02 | Workload Identity Grants Excessive Cloud Access | A Kubernetes service account bound to an overprivileged cloud identity may give its workloads permissions beyond their operational needs. Cloud resources can then be accessed or modified outside the workload's intended boundary, exposing protected data and allowing unauthorized changes to cloud state. |
| CCC.K8S.TH13 | Controllers Reconcile Unauthorized Cluster State | A controller or scheduled workload granted excessive scope may repeatedly create or restore unauthorized resources and configuration through its reconciliation loop. Manual remediation can then be overwritten, restoring unsafe cluster state that exposes workload data or interferes with service availability. |
Assessment Requirements
| ID | Text | Applicability |
|---|---|---|
| CCC.K8S.CN02.AR01 | When a user or group is granted cluster access, each cloud access binding and Kubernetes role binding MUST grant only an approved role required by that identity's documented responsibilities. | tlp-clear, tlp-green, tlp-amber, tlp-red |
| CCC.K8S.CN02.AR02 | When a non-system Kubernetes role is defined, it MUST NOT grant wildcard verbs or wildcard resources AND any access to secrets, role bindings, admission configuration, or node proxy functions MUST enumerate the required verbs and resource names. | tlp-clear, tlp-green, tlp-amber, tlp-red |