Kubernetes and Cloud Native Associate (KCNA)Cloud Native SecurityMedium
A security auditor is reviewing the access controls for a Kubernetes cluster. They notice that a developer's Kubernetes `Role` grants `create` and `delete` permissions on `Pods` and `Deployments` across all namespaces. This broad access is a violation of which fundamental security principle?
- ADefense in depth
- BSeparation of duties
- CPrinciple of least privilege
- DSecurity by obscurity
Show answer & explanationAnswer & explanation
Correct answer: C. Principle of least privilege
Granting broad `create` and `delete` permissions on `Pods` and `Deployments` across all namespaces to a developer violates the Principle of Least Privilege. This principle dictates that users and services should only be granted the minimum permissions necessary to perform their legitimate functions.
Why the other options are wrong
- A. Defense in depth involves multiple layers of security, which is a broader strategy, not directly violated by a single overly permissive role.
- B. Separation of duties involves dividing critical tasks among different individuals, which is related but the core issue here is the *amount* of privilege, not its distribution.
- D. Security by obscurity relies on hiding information, which is not relevant to explicit access control settings.
Principle of Least Privilege
A security best practice that dictates that users, processes, and programs should be granted only the minimum necessary permissions to perform their authorized functions, and no more.
- Minimizes the potential impact of a compromise.
- Reduces the attack surface.
- Applies to user accounts, service accounts, and system components.
- Crucial for Role-Based Access Control (RBAC) in Kubernetes.
Memory trick: Least Privilege: only what's needed.