Skip to content
Back to skills

Cis K8s V1120 3.2.2

ASecurity

Ensure that the audit policy covers key security concerns (Manual)

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

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add CyberStrikeus/CyberStrike --skill cis-k8s-v1120-3.2.2 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cis K8s V1120 3.2.2?

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

Security grade badge for Cis K8s V1120 3.2.2
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cyberstrikeus-cis-k8s-v1120-3-2-2/badge)](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-k8s-v1120-3-2-2)

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-v1120-3.2.2
description: "Ensure that the audit policy covers key security concerns (Manual)"
category: cis-k8s
version: "1.12.0"
author: cyberstrike-official
tags: [cis, kubernetes, control-plane-config, logging]
cis_id: "3.2.2"
cis_benchmark: "CIS Kubernetes Benchmark v1.12.0"
tech_stack: [kubernetes]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---

# CIS Kubernetes Benchmark v1.12.0 - Control 3.2.2

## Profile Applicability

- **Level:** 2 - Master Node

## Description

Ensure that the audit policy created for the cluster covers key security concerns.

## Rationale

Security audit logs should cover access and modification of key resources in the cluster, to enable them to form an effective part of a security environment.

## Impact

Increasing audit logging will consume resources on the nodes or other log destination.

## Audit Procedure

Review the audit policy provided for the cluster and ensure that it covers at least the following areas:

- Access to Secrets managed by the cluster. Care should be taken to only log Metadata for requests to Secrets, ConfigMaps, and TokenReviews, in order to avoid the risk of logging sensitive data.
- Modification of `pod` and `deployment` objects.
- Use of `pods/exec`, `pods/portforward`, `pods/proxy` and `services/proxy`.

For most requests, minimally logging at the Metadata level is recommended (the most basic level of logging).

## Remediation

Consider modification of the audit policy in use on the cluster to include these items, at a minimum.

## Default Value

By default Kubernetes clusters do not log audit information.

## References

1. https://github.com/k8scop/k8s-security-dashboard/blob/master/configs/kubernetes/adv-audit.yaml
2. https://kubernetes.io/docs/tasks/debug-application-cluster/audit/#audit-policy
3. https://github.com/kubernetes/kubernetes/blob/master/cluster/gce/gci/configure-helper.sh#L735

## CIS Controls

| Controls Version | Control                                                             | IG 1 | IG 2 | IG 3 |
| ---------------- | ------------------------------------------------------------------- | ---- | ---- | ---- |
| v8               | 8.5 Collect Detailed Audit Logs                                     |      |      |      |
| v7               | 14.9 Enforce Detail Logging for Access or Changes to Sensitive Data |      |      |      |

## Profile

**Level 2 - Master Node** (Manual)

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.