基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-ocp-v170-5-2-6命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
macOS post-exploitation for credential harvesting, DTrace monitoring, TCC bypass, and stealth operations via native tools
Windows userland post-exploitation for credential harvesting, monitoring, AMSI/ETW bypass, and stealth operations
Kubernetes post-exploitation for container escape, secret extraction, RBAC abuse, and cluster persistence
| name | cis-ocp-v170-5.2.6 |
| description | Minimize admission of root containers (Manual) |
| category | cis-openshift |
| version | 1.7.0 |
| author | cyberstrike-official |
| tags | ["cis","openshift","kubernetes","redhat","policies","security-context-constraints"] |
| cis_id | 5.2.6 |
| cis_benchmark | CIS Red Hat OpenShift Container Platform Benchmark v1.7.0 |
| tech_stack | ["kubernetes","openshift","redhat"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
Do not generally permit containers to be run as the root user.
Containers may run as any Linux user. Containers which run as the root user, whilst constrained by Container Runtime security features still have an escalated likelihood of container breakout.
Ideally, all containers should run as a defined non-UID 0 user.
There should be at least one Security Context Constraint (SCC) defined which does not permit root users in a container.
If you need to run root containers, this should be defined in a separate SCC and you should carefully check RBAC controls to ensure that only limited service accounts and users are given permission to access that SCC.
Pods with containers which run as the root user will not be permitted.
Use the following command to list all SCCs that restrict the ability to run the container as root:
oc get scc -A -o json | jq '.items[] | select(.runAsUser["type"] ==
"MustRunAsNonRoot") | .metadata.name'
Verify at least one SCC is returned.
You can perform additional validation by using the following command to list the UID range for each SCC:
for i in `oc get scc --template '{{range
.items}}{{.metadata.name}}{{"\n"}}{{end}}'`; do echo "$i"; oc describe scc $i
| grep "\sUID"; done
Verify there is at least one SCC that doesn't contain 0 in the UID range.
None required. By default, OpenShift includes the nonroot and nonroot-v2 SCCs that restrict the ability to run as nonroot. If additional SCCs are appropriate, follow the OpenShift documentation to create custom SCCs.
By default, the following SCCs restrict the ability to run as non-root:
"nonroot"
"nonroot-v2"
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts | * | * | * |
| v8 | 12.8 Establish and Maintain Dedicated Computing Resources for All Administrative Work | * | ||
| v7 | 4.3 Ensure the Use of Dedicated Administrative Accounts | * | * | * |
| Techniques / Sub-techniques | Tactics | Mitigations |
|---|---|---|
| T1098 | TA0003 | M1026 |
Level 2 (Manual)