security

Audit Kubernetes and OpenShift clusters for RBAC, NetworkPolicy, pod security, and compliance gaps.

5|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/kcns008/clusterclaw --skill security-kcns008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/kcns008/clusterclaw/tree/main/.claude/skills/security
Command: npx skills add https://github.com/kcns008/clusterclaw --skill security-kcns008

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, kube-bench, trivy, grype, kubectl, oc, and includes scripts (resource) components.

What problem does it solve?

This Skill helps platform teams find and fix Kubernetes and OpenShift security risks before they become incidents, reducing exposure from weak RBAC, missing NetworkPolicies, unsafe pod settings, and noncompliant workloads.

Core Features & Use Cases

  • Security Posture Audits: Reviews clusters for privileged containers, root execution, host namespace usage, service account risks, and missing Pod Security Admission labels.
  • Policy and Access Hardening: Checks RBAC for wildcards and overly broad bindings, and helps enforce zero-trust controls with NetworkPolicies, Kyverno, and OPA Gatekeeper.
  • Compliance and Supply Chain Safety: Supports CIS benchmark checks, image vulnerability scanning, secret management workflows, and image signature verification.
  • Use Case: A platform engineer can run a cluster-wide review to quickly identify namespaces without default deny policies, risky workloads, and compliance gaps, then prioritize remediation.

Quick Start

Ask the security skill to audit my Kubernetes or OpenShift cluster for RBAC, NetworkPolicy, pod security, and compliance issues.

Frequently Asked Questions about security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my Kubernetes cluster for RBAC and pod security risks?

Run a cluster-wide security posture audit to detect privileged containers, root execution, host namespace usage, and service account risks. It reviews RBAC for overly broad bindings and checks for missing Pod Security Admission labels to harden Kubernetes and OpenShift environments.

What is the best way to check Kubernetes NetworkPolicy coverage and enforce zero-trust controls?

Review namespaces for missing default deny policies and identify risky workloads. This skill checks NetworkPolicy coverage and helps enforce zero-trust controls using Kyverno and OPA Gatekeeper to restrict cluster traffic.

Can I use Trivy and kube-bench to scan OpenShift workloads for CIS compliance drift?

Yes, this skill leverages Trivy and kube-bench with oc CLI access to support CIS benchmark checks and image vulnerability scanning. It detects compliance drift and identifies supply chain risks in OpenShift environments.

Do I need kubectl or oc installed to review Kubernetes secrets management and image signing?

Yes, kubectl or oc CLI access is required to review secrets management workflows and image signature verification. The skill uses JSON-aware parsing with jq and integrates with tools like Vault to assess cluster security.

How do I find namespaces without default deny policies and prioritize remediation?

Execute a cluster-wide review to detect namespaces lacking default deny NetworkPolicies, risky workloads, and compliance gaps. This allows platform engineers to prioritize remediation of security issues before they become incidents.

What are the limitations of automated Kubernetes security posture auditing?

Auditing requires CLI access to kubectl or oc and depends on tools like Trivy, grype, and kube-bench. While it detects policy gaps and compliance drift, remediation of risky workloads, RBAC wildcards, and unsafe pod settings requires manual intervention.