diff --git a/applications/openshift/networking/configure_appropriate_network_policies/ocp4/e2e.yml b/applications/openshift/networking/configure_appropriate_network_policies/ocp4/e2e.yml new file mode 100644 index 00000000000..69a7d085eb4 --- /dev/null +++ b/applications/openshift/networking/configure_appropriate_network_policies/ocp4/e2e.yml @@ -0,0 +1,2 @@ +--- +default_result: MANUAL diff --git a/applications/openshift/networking/configure_appropriate_network_policies/rule.yml b/applications/openshift/networking/configure_appropriate_network_policies/rule.yml new file mode 100644 index 00000000000..1d94cb55641 --- /dev/null +++ b/applications/openshift/networking/configure_appropriate_network_policies/rule.yml @@ -0,0 +1,43 @@ +documentation_complete: true + +title: 'Ensure appropriate Network Policies are configured' + +description: |- + Configure Network Policies in any application namespace in an approrpriate way, so that + only the required communications are allowed. The Network Policies should precisely define + source and target using label selectors and ports. + +rationale: |- + By default, all pod to pod traffic within a cluster is allowed. Network + Policy creates a pod- level firewall that can be used to restrict traffic + between sources. Pod traffic is restricted by having a Network Policy that + selects it (through the use of labels). 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. + + Implementing Kubernetes Network Policies with minimal allowed communication enhances security + by reducing entry points and limiting attacker movement within the cluster. It ensures pods and + services communicate only with necessary entities, reducing unauthorized access risks. In case + of a breach, these policies contain compromised pods, preventing widespread malicious activity. + Additionally, they enhance monitoring and detection of anomalous network activities. + +severity: medium + +identifiers: {} + +references: + bsi: APP.4.4.A19 + +ocil_clause: 'Network Policies need to be evaluated if they are appropriate' + +ocil: |- + For each non-default namespace in the cluster, review the configured Network Policies + and ensure that they only allow the necessary network network connections. They should should + precisely define source and target using label selectors and ports. + + 1. Get a list of existing projects(namespaces), exclude default, kube-*, openshift-* + 
$ oc get namespaces -ojson | jq -r '[.items[] | select((.metadata.name | startswith("openshift") | not) and (.metadata.name | startswith("kube-") | not) and .metadata.name != "default") | .metadata.name]'
+ + 2. For each of these namespaces, review the network policies: + 
$ oc get networkpolicies -n $namespace -o yaml
diff --git a/controls/bsi_app_4_4.yml b/controls/bsi_app_4_4.yml index 76144bb12c6..460498ad4cd 100644 --- a/controls/bsi_app_4_4.yml +++ b/controls/bsi_app_4_4.yml @@ -433,27 +433,28 @@ controls: rules SHOULD precisely define the source and destination of the allowed connections using at least one of the following criteria: service name, metadata (“labels”), Kubernetes service accounts, or certificate-based authentication. - (4) All the criteria used as labels for a connection SHOULD be secured in such a way that they + (4) All the criteria used as labels for a connection SHOULD be secured in such a way that they can only be changed by authorised persons and management services. notes: >- - In a cluster using a network plugin that supports Kubernetes network policy, network isolation + In a cluster using a network plugin that supports Kubernetes network policy, network isolation is controlled entirely by NetworkPolicy objects. In OpenShift, the default plugins (OpenShift SDN, OVN Kubernetes) supports using network policy. Support for NetworkPolicy objects is verified using rules. - - Section 1-3: 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 need to create NetworkPolicy objects in that project - to indicate the allowed incoming connections. If a pod is matched by selectors in one or more - NetworkPolicy objects, then the pod will accept only connections that are allowed by at least - one of those NetworkPolicy objects. A pod that is not selected by any NetworkPolicy objects - is fully accessible. + Section 1-3: 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 need to create NetworkPolicy objects in that project + to indicate the allowed incoming connections. If a pod is matched by selectors in one or more + NetworkPolicy objects, then the pod will accept only connections that are allowed by at least + one of those NetworkPolicy objects. A pod that is not selected by any NetworkPolicy objects + is fully accessible. + It is useful to create default policies for each application namespace e.g. to deny all ingress traffic by default. The existance of at least one network policy and the automatic creation - as part of a namespace template is checked using rules. The creation of suitable NetworkPolicy - objects that satisfy the requirements from sections 1 to 3, however, needs to be ensured by the - application owner. - + as part of a namespace template is checked using rules. + + The creation of suitable NetworkPolicy objects that satisfy the requirements from sections 1 to 3, + however, needs to be ensured by the application owner. A manual rule is provided for that. + Section 4: It needs to be ensured organizationally, that only required subjects are granted RBAC to change the relevant Kubernetes objects. status: partial @@ -463,6 +464,8 @@ controls: # Section 1-2 - configure_network_policies_namespaces - project_config_and_template_network_policy + # Section 3 + - configure_appropriate_network_policies - id: APP.4.4.A19 title: High Availability of Kubernetes