kubernetes_compliance

Kubernetes Compliance

Administrators should use a default policy selecting all Pods to deny all ingress and egress traffic and ensure any unselected Pods are isolated. An 'allow all' policy would override this default and should not be used.  Instead, use specific  policies to relax these restrictions only for permissible connections. 

network_policy_default_dont_allow_ingress

cis_kube_v120_v100_5_3_2

5.3.2 Ensure that all Namespaces have Network Policies defined

cis_v170_5_3_2

all_controls_network_policy

Network Policy

nsa_cisa_v1_network_hardening_default_deny_network_policy

Network policy should have a default policy to deny all ingress and egress traffic

Network policies should not have a default policy to allow all ingress traffic

kubernetes

Run individual controls or full compliance benchmarks for CIS, NSA CISA Kubernetes Hardening Guidance across all of your Kubernetes clusters using Powerpipe and Steampipe.

Apache License 2.0

steampipe-mod-kubernetes-compliance

Control: Network policies should not have a default policy to allow all ingress traffic

Description

Usage

SQL

Tags