Skip to content
Back to skills

Cis K8s V1111 5.2.1

ASecurity

Ensure that the cluster has at least one active policy control mechanism in place (Manual)

  • 3,518 stars
  • 0 votes
  • 0 copies
  • 5 views
  • Added September 3, 2026
securitygonodekubernetessecurity

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add CyberStrikeus/CyberStrike --skill cis-k8s-v1111-5.2.1 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cis K8s V1111 5.2.1?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cis K8s V1111 5.2.1
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cyberstrikeus-cis-k8s-v1111-5-2-1/badge)](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-k8s-v1111-5-2-1)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: cis-k8s-v1111-5.2.1
description: "Ensure that the cluster has at least one active policy control mechanism in place (Manual)"
category: cis-k8s
version: "1.11.1"
author: cyberstrike-official
tags: [cis, kubernetes, policies, pod-security, pod-security-standards]
cis_id: "5.2.1"
cis_benchmark: "CIS Kubernetes Benchmark v1.11.1"
tech_stack: [kubernetes]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---

# 5.2.1 Ensure that the cluster has at least one active policy control mechanism in place (Manual)

## Profile Applicability

- Level 1 - Master Node

## Description

Every Kubernetes cluster should have at least one policy control mechanism in place to enforce the other requirements in this section. This could be the in-built Pod Security Admission controller, or a third party policy control system.

## Rationale

Without an active policy control mechanism, it is not possible to limit the use of containers with access to underlying cluster nodes, via mechanisms like privileged containers, or the use of hostPath volume mounts.

## Impact

Where policy control systems are in place, there is a risk that workloads required for the operation of the cluster may be stopped from running. Care is required when implementing admission control policies to ensure that this does not occur.

## Audit

Review the workloads deployed to the cluster to understand if Pod Security Admission or external admission control systems are in place.

## Remediation

Ensure that either Pod Security Admission or an external policy control system is in place for every namespace which contains user workloads.

## Default Value

By default, Pod Security Admission is enabled but no policies are in place.

## References

1. https://kubernetes.io/docs/concepts/security/pod-security-admission

## CIS Controls

| Controls Version | Control                                                 | IG 1 | IG 2 | IG 3 |
| ---------------- | ------------------------------------------------------- | ---- | ---- | ---- |
| v8               | 13.4 Perform Traffic Filtering Between Network Segments |      | X    | X    |
| v8               | 13.10 Perform Application Layer Filtering               |      |      | X    |
| v7               | 4.7 Limit Access to Script Tools                        |      | X    | X    |
| v7               | 9.4 Apply Host-based Firewalls or Port Filtering        | X    | X    | X    |

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in security →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.