agentleFS
Sign inStart free
MasriyanMasriyan/gemini-security-skills/kubernetes-security/SKILL.md

kubernetes-security

Skill4 starsChanged 5 months agoMITView on GitHub

Kubernetes and container security skill for cluster hardening, RBAC review, admission control (OPA Gatekeeper, Kyverno), Pod Security Standards, network policies, secrets management, runtime defense (Falco, Tetragon), image supply chain (cosign, SLSA, in-toto), and CIS benchmark compliance. Use to assess and harden clusters you operate.

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Avoid disruptive runtime probes on production.

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Kubernetes Security

Authorization Boundary

  • Require cluster context, namespace scope, and read-only kubeconfig before live queries.
  • Avoid disruptive runtime probes on production; prefer staging or ephemeral clusters.

Hardening Workflow

  1. Inventory: API server flags, node OS, CNI, CSI, ingress, service mesh, admission plugins, controllers.
  2. Scan: kube-bench, kubescape, trivy k8s, polaris, kubeaudit, popeye.
  3. RBAC: enumerate ClusterRole/RoleBinding; flag wildcard verbs, system:masters, escalate, bind, impersonate, secret reads from broad subjects.
  4. Workloads: enforce Pod Security restricted, drop capabilities, read-only rootfs, non-root UID, seccomp RuntimeDefault, no hostPath/hostNetwork/hostPID.
  5. Network: default-deny NetworkPolicy; explicit egress to known services; mTLS via mesh where applicable.
  6. Supply chain: signed images (cosign verify), provenance attestations (SLSA), admission policy that blocks unsigned.
  7. Runtime: Falco/Tetragon rules for exec-in-container, reverse shells, crypto miners, sensitive mounts.

Multi-Tenant Patterns

  • Namespace-per-tenant with quotas, limit ranges, and NetworkPolicy isolation.
  • Separate node pools for untrusted workloads; gVisor or Kata for sandboxing.
  • Per-tenant audit log filters; secrets via external KMS, never inline.

Output Contract

  • inventory.yaml, findings.csv, policies/ (Gatekeeper/Kyverno), netpol/, runtime/falco-rules.yaml.
  • runbook.md: incident response for compromised pod, leaked token, miner detection.
  • gap.md: missing telemetry and proposed fixes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free