# Cis Oke V150 4.1.2

> Minimize access to secrets (Automated)

- Skill: `cyberstrikeus/cis-oke-v150-4-1-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add cyberstrikeus/cis-oke-v150-4-1-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/cyberstrikeus/cis-oke-v150-4-1-2/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: cyberstrikeus (https://skillmd.com/u/cyberstrikeus)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/cyberstrikeus/cis-oke-v150-4-1-2

---


# 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 Procedure

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

Run the following command to list all the users who have access to secrets objects in the Kubernetes API:

```bash
kubectl auth can-i get,list,watch secrets --all-namespaces --as=system:authenticated
```

This command checks if the system:authenticated group (which includes all authenticated users) has the get, list, or watch permissions for secrets objects in all namespaces. The output will display either yes or no for each user.

Note: If you want to check for specific namespaces, replace --all-namespaces with the desired namespace(s) separated by commas.

## 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:

```
CLUSTERROLEBINDING                                          SUBJECT
TYPE              SA-NAMESPACE
cluster-admin                                               system:masters
Group
system:controller:clusterrole-aggregation-controller        clusterrole-
aggregation-controller  ServiceAccount  kube-system
system:controller:expand-controller                         expand-controller
ServiceAccount    kube-system
system:controller:generic-garbage-collector                 generic-garbage-
collector              ServiceAccount  kube-system
system:controller:namespace-controller                      namespace-controller
ServiceAccount    kube-system
system:controller:persistent-volume-binder                  persistent-volume-
binder                 ServiceAccount  kube-system
system:kube-controller-manager                              system:kube-controller-
manager                User
```

## References

1. [https://docs.cloud.oracle.com/en-us/iaas/Content/ContEng/Concepts/contengoverview.htm](https://docs.cloud.oracle.com/en-us/iaas/Content/ContEng/Concepts/contengoverview.htm)

## CIS Controls

| Controls Version | Control                                                   | IG 1 | IG 2 | IG 3 |
| ---------------- | --------------------------------------------------------- | ---- | ---- | ---- |
| v8               | 4.1 Establish and Maintain a Secure Configuration Process | X    | X    | X    |

## MITRE ATT&CK Mappings

| Techniques / Sub-techniques | Tactics | Mitigations |
| --------------------------- | ------- | ----------- |
| T1552                       | TA0006  | M1026       |

---

**Profile:** Level 1