OpenParable
Skip to content
← Back to skills

Cis Aks V170 4.1.2

DevOps & Security
cis-aks-v170-4.1.2

Cis Aks V170 4.1.2 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 secrets (Automated)

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.7.0/cis-aks-v170-4.1.2/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-aks-v170-4-1-2, 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.2 Minimize access to secrets (Automated)

Profile Applicability

  • Level 1

Description

The Kubernetes API stores secrets, which may be service account tokens for the Kubernetes API or credentials used by workloads in the cluster. Access to these secrets should be restricted to the smallest possible group of users to reduce the risk of privilege escalation.

Rationale

Inappropriate access to secrets stored within the Kubernetes cluster can allow for an attacker to gain additional access to the Kubernetes cluster or external resources whose credentials are stored as secrets.

Impact

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

Audit

Review the users who have get, list or watch access to secrets objects in the Kubernetes API.

Remediation

Where possible, remove get, list and watch access to secret objects in the cluster.

Default Value

By default, the following list of principals have get privileges on secret objects:

CLUSTERROLEBINDINGSUBJECT
cluster-admin (Group)system:masters
system:controller:clusterrole-aggregation-controller (ServiceAccount kube-system)clusterrole-aggregation-controller
system:controller:expand-controller (ServiceAccount kube-system)expand-controller
system:controller:generic-garbage-collector (ServiceAccount kube-system)generic-garbage-collector
system:controller:namespace-controller (ServiceAccount kube-system)namespace-controller
system:controller:persistent-volume-binder (ServiceAccount kube-system)persistent-volume-binder
system:kube-controller-manager (User)system:kube-controller-manager

References

  1. https://docs.microsoft.com/security/benchmark/azure/security-controls-v2-identity-management#im-7-eliminate-unintended-credential-exposure

CIS Controls

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