Limit Kubernetes API reachability to explicitly approved networks and private management paths to reduce administrative exposure.
Restrict Kubernetes API Network Access
CCC.K8S.CN01 · 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.Core.CP14 | API Access | The service exposes a port enabling external actors to interact programmatically with the service and its resources using HTTP protocol methods such as GET, POST, PUT, and DELETE. |
| CCC.K8S.CP01 | Managed Kubernetes Control Plane | The service supplies a Kubernetes-conformant control plane whose foundational components, health, and availability are automatically maintained by the provider. |
| 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.Core.CP23 | Network Access Rules | The service restricts access to child or networked resources based on user-defined network parameters such as IP address, protocol, port, or source. |
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.Core.TH15 | Automated Enumeration and Reconnaissance by Non-human Entities | Automated processes may be used to gather details about service and child resource elements such as APIs, file systems, or directories. This information can reveal vulnerabilities, misconfigurations, and the network topology, which can be used to plan an attack against the system, the service, or its child resources. |
| CCC.Core.TH17 | Responses are Generated for Unauthorized Requests | The service may generate responses to requests from unauthorized entities. This could lead to the exposure of system details, which may be used to plan an attack against the service, system, or network. Additionally, allocating resources to service the request could lead to a denial of service for legitimate users, leading to a loss of availability anywhere in the system. |
| CCC.K8S.TH01 | Kubernetes API is Exposed to Untrusted Networks | An API endpoint without network restrictions may be reached from untrusted networks. Cluster resources and configuration can then be enumerated or modified through exposed administrative interfaces. Cluster data may be disclosed, configuration integrity may be lost, and workloads may be disrupted. |
Assessment Requirements
| ID | Text | Applicability |
|---|---|---|
| CCC.K8S.CN01.AR01 | When a Kubernetes API endpoint is active, its network access configuration MUST restrict inbound traffic to explicitly approved private networks or source address ranges. | tlp-clear, tlp-green, tlp-amber, tlp-red |
| CCC.K8S.CN01.AR02 | When a Kubernetes API endpoint is active, public network access to that endpoint MUST be disabled. | tlp-amber, tlp-red |