How do I install the Cis Ocp V160 5.3.1 skill?

Run npx skillmds@latest add cyberstrikeus/cis-ocp-v160-5-3-1 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 V160 5.3.1 skill do?

Ensure that the CNI in use supports Network Policies (Manual) It is listed under DevOps & Infra on SkillMD.

Is Cis Ocp V160 5.3.1 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 V160 5.3.1?

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 V160 5.3.1 free to use?

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

Who published Cis Ocp V160 5.3.1?

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

Cis Ocp V160 5.3.1 by cyberstrikeus

Name: Cis Ocp V160 5.3.1
Author: cyberstrikeus

File contents

CIS Red Hat OpenShift Container Platform Benchmark v1.6.0 - Control 5.3.1

Profile Applicability

Level: 1

Description

There are a variety of CNI plugins available for Kubernetes. If the CNI in use does not support Network Policies it may not be possible to effectively restrict traffic in the cluster.

Rationale

Kubernetes network policies are enforced by the CNI plugin in use. As such it is important to ensure that the CNI plugin supports both Ingress and Egress network policies.

Impact

None

Audit Procedure

Review the documentation of the CNI plugin (OpenShift SDN or OVN-Kubernetes) in use by the cluster, and confirm that it supports ingress and egress network policies.

OpenShift Container Platform uses a software-defined networking (SDN) approach to offer a unified cluster network that enables communication between Pods across the OpenShift Container Platform cluster. This Pod network can be established and maintained by either the OpenShift SDN plugin, which configures an overlay network using Open vSwitch (OVS), or by the OVN-Kubernetes plugin.

OVN-Kubernetes, based on Open Virtual Network (OVN), offers an overlay-based networking implementation. A cluster using the OVN-Kubernetes plugin also runs Open vSwitch (OVS) on each node. OVN configures OVS on each node to implement the declared network configuration.

As of OpenShift 4.10, both these plugins provide all Kubernetes Network Policy features, including ingress, egress, and ipBlock. OpenShift provides several options for controlling the traffic leaving the cluster, the supporting matrix can be found at. Please refer to the OpenShift documentation for a complete list of features available for securing cluster networks.

Remediation

None required.

Default Value

This will depend on the CNI plugin in use.

References

CIS Controls

Controls Version	Control	IG 1	IG 2	IG 3
v8	4.4 Implement and Manage a Firewall on Servers	*	*	*
v7	9.5 Implement Application Firewalls			*

MITRE ATT&CK Mappings

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

Profile

Level 1 (Manual)

---name: cis-ocp-v160-5-3-1description: Ensure that the CNI in use supports Network Policies (Manual)---# CIS Red Hat OpenShift Container Platform Benchmark v1.6.0 - Control 5.3.1## Profile Applicability- **Level:** 1## DescriptionThere are a variety of CNI plugins available for Kubernetes. If the CNI in use does not support Network Policies it may not be possible to effectively restrict traffic in the cluster.## RationaleKubernetes network policies are enforced by the CNI plugin in use. As such it is important to ensure that the CNI plugin supports both Ingress and Egress network policies.## ImpactNone## Audit ProcedureReview the documentation of the CNI plugin (OpenShift SDN or OVN-Kubernetes) in use by the cluster, and confirm that it supports ingress and egress network policies.OpenShift Container Platform uses a software-defined networking (SDN) approach to offer a unified cluster network that enables communication between Pods across the OpenShift Container Platform cluster. This Pod network can be established and maintained by either the OpenShift SDN plugin, which configures an overlay network using Open vSwitch (OVS), or by the OVN-Kubernetes plugin.OVN-Kubernetes, based on Open Virtual Network (OVN), offers an overlay-based networking implementation. A cluster using the OVN-Kubernetes plugin also runs Open vSwitch (OVS) on each node. OVN configures OVS on each node to implement the declared network configuration.As of OpenShift 4.10, both these plugins provide all Kubernetes Network Policy features, including ingress, egress, and `ipBlock`. OpenShift provides several options for controlling the traffic leaving the cluster, the supporting matrix can be found at. Please refer to the OpenShift documentation for a complete list of features available for securing cluster networks.## RemediationNone required.## Default ValueThis will depend on the CNI plugin in use.## References1. https://docs.openshift.com/container-platform/4.5/networking/openshift-sdn/about-openshift-sdn.html2. https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/## CIS Controls| Controls Version | Control | IG 1 | IG 2 | IG 3 || ---------------- | ---------------------------------------------- | ---- | ---- | ---- || v8 | 4.4 Implement and Manage a Firewall on Servers | \* | \* | \* || v7 | 9.5 Implement Application Firewalls | | | \* |## MITRE ATT&CK Mappings| Techniques / Sub-techniques | Tactics | Mitigations || --------------------------- | ------- | ------------ || T1046 | TA0007 | M1030, M1042 |## Profile**Level 1** (Manual)

Frequently asked questions

Cis Ocp V160 5.3.1