Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
securityskills/kubernetes-security-auditLinux, cloud and containers

kubernetes-security-audit

⁨Audit Kubernetes clusters for RBAC excesses, pod security gaps, network policy holes, and supply-chain risks. Use when reviewing cluster configuration or hardening deployments.⁩

v2026.8.26-b2b6b522 installs+2 in 7 days0 Starssynced 19 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install securityskills/kubernetes-security-audit

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
7Ejo+1tHke…TzuemXCg==The CLI checks the SHA-256 and the signature before it writes a file.
Package30c5eb3d…25b07dfe
30c5eb3d9ea0…21c025b07dfe1 file · ⁦1.1 KB⁩
ScanMedium1 finding
  • No license found
See the full scan
Sourcegithub.com/securityskills/skills/tree/main/container-security/kubernetes/kubernetes-security-audit@b2b6b52

Audit a cluster across four layers: workload, identity, network, supply chain.

Workload Security

  • Pod Security Standards: check namespace labels (pod-security.kubernetes.io/enforce)
  • Privileged pods, hostPID/hostNetwork/hostPath usage — each needs justification
  • Containers running as root; allowPrivilegeEscalation: true; missing readOnlyRootFilesystem
  • securityContext set at pod and container level; capabilities dropped to minimum set

RBAC

  • Enumerate bindings; find cluster-admin subjects — minimize to a named list
  • Escalation paths: bind/escalate/impersonate verbs; create pods + node privileged, create pods/exec
  • Service accounts: default SA used by workloads? token automount disabled where unneeded?
  • Check for wildcard (*) verbs/resources in custom roles

Network

  • NetworkPolicy: default-deny ingress/egress per namespace as the baseline
  • Cross-namespace exposure: which namespaces can reach kube-system, ingress controllers, databases
  • Control plane exposure: API server on public IP? etcd reachable/authenticated?

Supply Chain

  • Image provenance: registry digests pinned (not :latest), signature verification (cosign)
  • Admission control: image policy, no privileged images from untrusted registries
  • Secrets: Kubernetes Secrets at rest (KMS encryption configured), not baked into images or env in manifests committed to git

Quick Checks

bash
kubectl get pods -A -o json | jq '[.items[] | select(.spec.containers[].securityContext.privileged==true)]'
kubectl get ns -l pod-security.kubernetes.io/enforce
kubectl auth can-i --list --as=system:serviceaccount:default:default
kubectl get networkpolicy -A

Output

Findings per layer with YAML evidence, risk, and hardening manifests for remediation.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumLicense · No license found

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.8.26-b2b6b52Nov 13, 2026b2b6b5230c5eb3dSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login