How do I install the Cis Ocp V170 5.3.2 skill?

Run npx skillmds@latest add cyberstrikeus/cis-ocp-v170-5-3-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.3.2 skill do?

Ensure all Namespaces have Network Policies defined (Manual) It is listed under DevOps & Infra on SkillMD.

Is Cis Ocp V170 5.3.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.3.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.3.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.3.2?

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

Cis Ocp V170 5.3.2 by cyberstrikeus

Name: Cis Ocp V170 5.3.2
Author: cyberstrikeus

File contents

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

Profile Applicability

Level: 2

Description

Use network policies to isolate traffic in your cluster network.

Rationale

Running different applications on the same Kubernetes cluster creates a risk of one compromised application attacking a neighboring application. Network segmentation is important to ensure that containers can communicate only with those they are supposed to. A network policy is a specification of how selections of pods are allowed to communicate with each other and other network endpoints.

Once there is any Network Policy in a namespace selecting a particular pod, that pod will reject any connections that are not allowed by any Network Policy. Other pods in the namespace that are not selected by any Network Policy will continue to accept all traffic.

Impact

Audit Procedure

The OpenShift 4 CNI plugin uses network policies and by default all Pods in a project are accessible from other Pods and network endpoints. To isolate one or more Pods in a project, you create NetworkPolicy objects in that project to indicate the allowed incoming connections. Project administrators can create and delete NetworkPolicy objects within their own project. For more information see:

Run the following command and review the NetworkPolicy objects created in the cluster.

oc -n all get networkpolicy

Ensure that each namespace defined in the cluster has at least one Network Policy.

Remediation

Follow the documentation and create NetworkPolicy objects as you need them.

Default Value

By default, all Pods in a project are accessible from other Pods and network endpoints; network policies are not created.

References

CIS Controls

Controls Version	Control	IG 1	IG 2	IG 3
v8	4.4 Implement and Manage a Firewall on Servers	*	*	*
v7	14.2 Enable Firewall Filtering Between VLANs		*	*

MITRE ATT&CK Mappings

Techniques / Sub-techniques	Tactics	Mitigations
T1046	TA0007	M1030, M1042

Profile

Level 2 (Manual)

---name: cis-ocp-v170-5-3-2description: Ensure all Namespaces have Network Policies defined (Manual)---# CIS Red Hat OpenShift Container Platform Benchmark v1.7.0 - Control 5.3.2## Profile Applicability- **Level:** 2## DescriptionUse network policies to isolate traffic in your cluster network.## RationaleRunning different applications on the same Kubernetes cluster creates a risk of one compromised application attacking a neighboring application. Network segmentation is important to ensure that containers can communicate only with those they are supposed to. A network policy is a specification of how selections of pods are allowed to communicate with each other and other network endpoints.Once there is any Network Policy in a namespace selecting a particular pod, that pod will reject any connections that are not allowed by any Network Policy. Other pods in the namespace that are not selected by any Network Policy will continue to accept all traffic.## ImpactOnce there is any Network Policy in a namespace selecting a particular pod, that pod will reject any connections that are not allowed by any Network Policy. Other pods in the namespace that are not selected by any Network Policy will continue to accept all traffic.## Audit ProcedureThe OpenShift 4 CNI plugin uses network policies and by default all Pods in a project are accessible from other Pods and network endpoints. To isolate one or more Pods in a project, you create NetworkPolicy objects in that project to indicate the allowed incoming connections. Project administrators can create and delete NetworkPolicy objects within their own project. For more information see:Run the following command and review the `NetworkPolicy` objects created in the cluster.```bashoc -n all get networkpolicy```Ensure that each namespace defined in the cluster has at least one Network Policy.## RemediationFollow the documentation and create `NetworkPolicy` objects as you need them.## Default ValueBy default, all Pods in a project are accessible from other Pods and network endpoints; network policies are not created.## References1. https://docs.openshift.com/container-platform/latest/networking/network_policy/about-network-policy.html2. https://docs.openshift.com/container-platform/latest/networking/network_policy/creating-network-policy.html3. https://docs.openshift.com/container-platform/latest/networking/network_policy/multitenant-network-policy.html4. https://docs.openshift.com/container-platform/latest/networking/network_policy/default-network-policy.html5. https://kubernetes.io/docs/concepts/services-networking/network-policies/6. https://octetz.com/docs/2019/2019-04-22-netpol-api-k8s/7. https://kubernetes.io/docs/tasks/administer-cluster/declare-network-policy/## CIS Controls| Controls Version | Control | IG 1 | IG 2 | IG 3 || ---------------- | ---------------------------------------------- | ---- | ---- | ---- || v8 | 4.4 Implement and Manage a Firewall on Servers | \* | \* | \* || v7 | 14.2 Enable Firewall Filtering Between VLANs | | \* | \* |## MITRE ATT&CK Mappings| Techniques / Sub-techniques | Tactics | Mitigations || --------------------------- | ------- | ------------ || T1046 | TA0007 | M1030, M1042 |## Profile**Level 2** (Manual)

Frequently asked questions

Cis Ocp V170 5.3.2