How do I install the Cis Ocp V170 5.1.2 skill?

Run npx skillmds@latest add cyberstrikeus/cis-ocp-v170-5-1-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Cis Ocp V170 5.1.2 skill do?

Minimize access to secrets (Manual) It is listed under DevOps & Infra on SkillMD.

Is Cis Ocp V170 5.1.2 safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cis Ocp V170 5.1.2?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cis Ocp V170 5.1.2 free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cis Ocp V170 5.1.2?

cyberstrikeus (@cyberstrikeus) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cis Ocp V170 5.1.2 by cyberstrikeus

Name: Cis Ocp V170 5.1.2
Author: cyberstrikeus

File contents

CIS Red Hat OpenShift Container Platform Benchmark v1.7.0 - Control 5.1.2

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. Executing the command below will return a list of users and groups who are allowed to get secrets:

oc adm policy who-can get secrets

The following command returns the users and groups who are allowed to list secrets:

oc adm policy who-can list secrets

The following command returns the users and groups who are allowed to watch secrets:

oc adm policy who-can watch secrets

Remediation

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

Default Value

By default in a OpenShift cluster the following list of principals have get privileges on secret objects:

# The following default cluster roles have get privileges on secret objects
admin
cloud-credential-operator-role
cluster-admin
cluster-image-registry-operator
cluster-monitoring-operator
cluster-node-tuning-operator
edit
kube-state-metrics
machine-config-controller
marketplace-operator
openshift-ingress-operator
prometheus-operator
registry-admin
registry-editor
system:aggregate-to-edit
system:controller:expand-controller
system:controller:generic-garbage-collector
system:controller:namespace-controller
system:controller:operator-lifecycle-manager
system:controller:persistent-volume-binder
system:kube-controller-manager
system:master
system:node
system:openshift:controller:build-controller
system:openshift:controller:cluster-quota-reconciliation-controller
system:openshift:controller:ingress-to-route-controller
system:openshift:controller:service-ca
system:openshift:controller:service-serving-cert-controller
system:openshift:controller:serviceaccount-pull-secrets-controller
system:openshift:controller:template-service-broker

References

https://kubernetes.io/docs/concepts/configuration/secret/#using-secrets

CIS Controls

Controls Version	Control	IG 1	IG 2	IG 3
v8	3.12 Segment Data Processing and Storage Based on Sensitivity		*	*
v7	13.4 Only Allow Access to Authorized Cloud Storage or Email Providers		*	*

MITRE ATT&CK Mappings

Techniques / Sub-techniques	Tactics	Mitigations
T1552	TA0006	M1026

Profile

Level 1 (Manual)

---name: cis-ocp-v170-5-1-2description: Minimize access to secrets (Manual)---# CIS Red Hat OpenShift Container Platform Benchmark v1.7.0 - Control 5.1.2## Profile Applicability- **Level:** 1## DescriptionThe 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.## RationaleInappropriate 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.## ImpactCare should be taken not to remove access to secrets to system components which require this for their operation.## Audit ProcedureReview the users who have `get`, `list` or `watch` access to `secrets` objects in the Kubernetes API. Executing the command below will return a list of users and groups who are allowed to get secrets:```bashoc adm policy who-can get secrets```The following command returns the users and groups who are allowed to list secrets:```bashoc adm policy who-can list secrets```The following command returns the users and groups who are allowed to watch secrets:```bashoc adm policy who-can watch secrets```## RemediationWhere possible, remove `get`, `list` and `watch` access to `secret` objects in the cluster.## Default ValueBy default in a OpenShift cluster the following list of principals have get privileges on secret objects:```# The following default cluster roles have get privileges on secret objectsadmincloud-credential-operator-rolecluster-admincluster-image-registry-operatorcluster-monitoring-operatorcluster-node-tuning-operatoreditkube-state-metricsmachine-config-controllermarketplace-operatoropenshift-ingress-operatorprometheus-operatorregistry-adminregistry-editorsystem:aggregate-to-editsystem:controller:expand-controllersystem:controller:generic-garbage-collectorsystem:controller:namespace-controllersystem:controller:operator-lifecycle-managersystem:controller:persistent-volume-bindersystem:kube-controller-managersystem:mastersystem:nodesystem:openshift:controller:build-controllersystem:openshift:controller:cluster-quota-reconciliation-controllersystem:openshift:controller:ingress-to-route-controllersystem:openshift:controller:service-casystem:openshift:controller:service-serving-cert-controllersystem:openshift:controller:serviceaccount-pull-secrets-controllersystem:openshift:controller:template-service-broker```## References1. https://kubernetes.io/docs/concepts/configuration/secret/#using-secrets## CIS Controls| Controls Version | Control | IG 1 | IG 2 | IG 3 || ---------------- | --------------------------------------------------------------------- | ---- | ---- | ---- || v8 | 3.12 Segment Data Processing and Storage Based on Sensitivity | | \* | \* || v7 | 13.4 Only Allow Access to Authorized Cloud Storage or Email Providers | | \* | \* |## MITRE ATT&CK Mappings| Techniques / Sub-techniques | Tactics | Mitigations || --------------------------- | ------- | ----------- || T1552 | TA0006 | M1026 |## Profile**Level 1** (Manual)

Frequently asked questions

Cis Ocp V170 5.1.2