OpenParable
Skip to content
← Back to skills

Cis Aks V180 4.1.4

DevOps & Security
cis-aks-v180-4.1.4

Cis Aks V180 4.1.4 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Minimize access to create pods (Manual)

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Server_Software/Kubernetes/CIS_Azure_Kubernetes_Service_AKS_Benchmark_v1.8.0/cis-aks-v180-4.1.4/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-aks-v180-4-1-4, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

4.1.4 Minimize access to create pods (Manual)

Profile Applicability

  • Level 1

Description

The ability to create pods in a namespace can provide a number of opportunities for privilege escalation, such as assigning privileged service accounts to these pods or mounting hostPaths with access to sensitive data (unless Pod Security Policies are implemented to restrict this access).

As such, access to create new pods should be restricted to the smallest possible group of users.

Rationale

The ability to create pods in a cluster opens up possibilities for privilege escalation and should be restricted, where possible.

Impact

Care should be taken not to remove access to pods to system components which require this for their operation.

Audit

Review the users who have create access to pod objects in the Kubernetes API.

Remediation

Where possible, remove create access to pod objects in the cluster.

Default Value

By default, the following list of principals have create privileges on pod objects:

CLUSTERROLEBINDINGSUBJECT
cluster-admin (Group)system:masters
system:controller:clusterrole-aggregation-controller (ServiceAccount kube-system)clusterrole-aggregation-controller
system:controller:daemon-set-controller (ServiceAccount kube-system)daemon-set-controller
system:controller:job-controller (ServiceAccount kube-system)job-controller
system:controller:persistent-volume-binder (ServiceAccount kube-system)persistent-volume-binder
system:controller:replicaset-controller (ServiceAccount kube-system)replicaset-controller
system:controller:replication-controller (ServiceAccount kube-system)replication-controller
system:controller:statefulset-controller (ServiceAccount kube-system)statefulset-controller

References

  1. https://docs.microsoft.com/security/benchmark/azure/security-controls-v2-privileged-access#pa-7-follow-just-enough-administration-least-privilege-principle

CIS Controls

Controls VersionControlIG 1IG 2IG 3
v84.1 Establish and Maintain a Secure Configuration Processxxx
v75.2 Maintain Secure Imagesxx