-
Notifications
You must be signed in to change notification settings - Fork 825
CMP-4434: Add manual rule kubevirt-use-multi-network-policies CIS OCP-Virt 4.3 #14928
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
yuumasato
merged 2 commits into
ComplianceAsCode:master
from
taimurhafeez:CMP-4434-Add-rule-use-multi-network-policies-CIS-OCP-Virt-4.3
Aug 12, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
32 changes: 32 additions & 0 deletions
32
applications/openshift-virtualization/kubevirt-use-multi-network-policies/rule.yml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,32 @@ | ||
| documentation_complete: true | ||
|
|
||
| title: 'Use Multi-Network Policies' | ||
|
|
||
| description: |- | ||
| Because the required multi-network policy configuration is specific | ||
| to each cluster's secondary network topology, this rule cannot be | ||
| evaluated automatically and always reports a manual status. | ||
| Organizations that use secondary networks should consider creating | ||
| a CustomRule with a CEL expression that verifies | ||
| <tt>MultiNetworkPolicy</tt> resources exist in the namespaces where | ||
| <tt>NetworkAttachmentDefinition</tt> objects are deployed. | ||
|
|
||
| rationale: |- | ||
| Secondary networks configured through Multus bypass the default | ||
| Kubernetes network policy enforcement. If multi-network policies are | ||
| not applied, workloads on those networks have unrestricted | ||
| connectivity, increasing the risk of lateral movement and | ||
| unauthorized access between virtual machines. Deploying | ||
| <tt>MultiNetworkPolicy</tt> resources ensures that traffic on | ||
| secondary networks is subject to the same segmentation controls | ||
| as the primary cluster network. | ||
|
|
||
| severity: medium | ||
|
|
||
| ocil_clause: 'multi-network policies are not in use' | ||
|
|
||
| ocil: |- | ||
| Run the following command to check for multi-network policies: | ||
| <pre>$ oc get multi-networkpolicies -A</pre> | ||
| Verify that multi-network policies exist and are configured for | ||
| namespaces that use secondary networks. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After reading these manual rule
descriptionsa few times, I think they are a bit backwards.First thing in the description should be what the rule is or should be checking for, then we can say we cannot automate the rule, then suggest how they can do it themselves.
Additionally, it looks like the rule description is a bit misaligned.
For example:
Then, ideally have an example CEL expression that users an use as a base to write their own expression.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can do this improvement in a follow up PR.