Menu
Configure Image Provenance using image controller configuration parameters (Manual)
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-ocp-v160-5-5-1The command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
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
Based on SOC occupation classification
Showing SKILL.md
| name | cis-ocp-v160-5.5.1 |
| description | Configure Image Provenance using image controller configuration parameters (Manual) |
| category | cis-openshift |
| version | 1.6.0 |
| author | cyberstrike-official |
| tags | ["cis","openshift","kubernetes","redhat","policies","admission-control"] |
| cis_id | 5.5.1 |
| cis_benchmark | CIS Red Hat OpenShift Container Platform Benchmark v1.6.0 |
| tech_stack | ["kubernetes","openshift","redhat"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
Configure Image Provenance for your deployment.
Kubernetes supports plugging in provenance rules to accept or reject the images in your deployments. You could configure such rules to ensure that only approved images are deployed in the cluster.
You can control which images can be imported, tagged, and run in a cluster using the image controller. For additional information on the image controller, see Image configuration resources.
You need to regularly maintain your provenance configuration based on container image updates.
Review the image controller parameters in your cluster and verify that image provenance is configured as appropriate.
Run the following command to return all registry sources:
oc get image.config.openshift.io/cluster -o json | jq .spec.registrySources
If nothing is returned, this is a finding and you should refer to the OpenShift image guide for configuring trusted registries.
Follow the OpenShift documentation: Image configuration resources.
By default, image provenance is not set.
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 4.1 Establish and Maintain a Secure Configuration Process | * | * | * |
| v7 | 5.4 Deploy System Configuration Management Tools | * | * |
| Techniques / Sub-techniques | Tactics | Mitigations |
|---|
| T1133, T1195 | TA0001, TA0003 | M1016, M1042 |
Level 2 (Manual)