container-security
Skill11 starsChanged 3 months agoApache-2.0View on GitHub
Container and Kubernetes security assessment — image vulnerability scanning, SBOM diff analysis, K8s cluster auditing, RBAC privilege mapping, NetworkPolicy review, container escape testing, and runtime monitoring (Falco/Tetragon). Use when scanning Docker/OCI images, auditing K8s clusters, reviewing Dockerfiles, diffing SBOMs across releases, analyzing RBAC, or assessing container runtime posture. Triggers on requests involving Trivy, Grype, Syft, Kubescape, kube-bench, Falco, container escapes, or CIS Docker/K8s benchmarks.
- Installs packages
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 70
Run concurrently (no shared state, no rate conflicts):
- Very specific: line 126
All findings MUST conform to schemas/finding.json.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Container Security
Thin router for container and Kubernetes security assessments. Load the reference, workflow, or payload file you need — do not read all of them.
When to Use
- Scanning Docker/OCI images for CVEs (single image or pipeline)
- Generating or attesting SBOMs (Syft / CycloneDX / SPDX)
- Diffing SBOMs across releases to flag newly-introduced CVEs
- Auditing a live Kubernetes cluster (CIS / NSA / MITRE)
- Mapping K8s RBAC and finding privilege-escalation paths
- Reviewing NetworkPolicy coverage
- Authoring Falco / Tetragon runtime rules
- Analyzing or testing container escape vectors (authorized only)
- Docker daemon / host hardening review
Trigger Phrases
"scan this image", "trivy / grype / syft", "audit k8s cluster", "kube-bench", "kubescape", "run CIS benchmark", "check RBAC", "networkpolicy coverage", "falco rule", "container escape", "SBOM diff", "new CVEs since last release".
When NOT to Use This Skill
| Request | Use instead |
| Static scan of K8s YAML / Helm / Kustomize before deploy | iac-security |
| Terraform / CloudFormation / Pulumi misconfig | iac-security |
| EKS / GKE / AKS control-plane or managed-service misconfig | exploiting-cloud-platforms |
| Cloud IAM misconfiguration (beyond K8s RBAC) | exploiting-cloud-platforms |
| Application-code vulns inside the container | auditing-code-for-vulnerabilities |
| Third-party library CVEs at source-code level | auditing-supply-chain |
| API endpoints exposed by containerized services | testing-apis |
Rule of thumb: pre-deployment YAML → iac-security; running cluster or built image → this skill.
Decision Tree
Target?
|
|-- Built/registry image ----------> workflows/image_scan.md
| \-- two images to compare? --> workflows/sbom_diff.md (FLAGSHIP)
|
|-- Dockerfile source -------------> examples/vulnerable_dockerfile.md
| + hadolint (references/image_scanning.md)
|
|-- Live K8s cluster --------------> workflows/cluster_audit.md
| |-- RBAC deep-dive ----------> workflows/rbac_analysis.md
| |-- Network policy gap ------> workflows/network_policy_review.md
| \-- CIS benchmark only ------> references/kubernetes_hardening.md
|
|-- Runtime monitoring ------------> references/runtime_security.md
| + examples/falco_custom_rule.yaml
|
\-- Escape testing (authorized) --> references/container_escape.md
+ payloads/container_escape_poc.mdParallelism Hints
Run concurrently (no shared state, no rate conflicts):
- Trivy + Grype + Syft + Hadolint on the same image — always parallel
- Scanners across multiple image tags — one sub-agent per tag
- kube-bench across nodes — deploy as DaemonSet, collect in parallel
- Kubescape frameworks (nsa, mitre, cis) — parallel invocations
- RBAC object fetches (
clusterroles,roles, bindings) — parallel - SBOM diff Grype scans (prior vs current) — parallel
- Per-principal RBAC graph expansion — parallel (stateless)
Sequential only:
- Cosign attestation (needs SBOM first)
- Cross-scanner CVE consensus merge (needs all scanner outputs)
- Finding emission (needs evaluated data)
Sub-Agent Delegation
- Multi-image pipeline: spawn one sub-agent per image; each runs
workflows/image_scan.mdand returns finding records. Parent merges. - Multi-cluster environment: one sub-agent per cluster; each runs
workflows/cluster_audit.mdwith its own kubecontext. - Cluster audit fan-out: parent runs inventory, then spawns sub-agents
for
rbac_analysis,network_policy_review, and runtime log triage in parallel. - SBOM diff per service: one sub-agent per service in a monorepo release; parent aggregates the "newly-introduced CVEs" roll-up.
Reasoning Budget
| Task | Budget |
| Running a scanner and capturing output | Minimal |
| Applying CIS checks, filling checklists | Minimal |
| SBOM canonicalization and package diff | Minimal |
| Cross-scanner CVE consensus | Moderate |
| RBAC privilege-graph traversal (principal -> cluster-admin) | Extended |
| Container escape chain composition | Extended |
| SBOM diff CVE exposure scoring + waiver decision | Extended |
| Runtime alert triage (chaining Falco events to intent) | Moderate |
Extended thinking pays off where the answer requires composing many small facts into an attack path or risk decision; it does not help when running a scanner and reporting output verbatim.
Multimodal Hooks
- Image layer histograms — attach Syft/Dive output screenshots to evidence for bloat/secret-layer findings.
- RBAC graphs —
rbac-tool vizproduces graphviz; render as PNG and embed in report for stakeholder clarity. - Falco/Tetragon alert screenshots — useful for runtime-detection evidence bundles.
Structured Output
All findings MUST conform to schemas/finding.json.
Container-security-specific fields: affected.image_digest,
affected.image_tag, affected.cluster_name, affected.namespace,
affected.resource_kind, affected.service_account, cve, cvss,
fixed_version, cis_control, and the sbom_diff block for diff
findings.
Workflow Index
| Workflow | Purpose |
workflows/image_scan.md | Build-time / registry image vuln scan with consensus merge |
workflows/sbom_diff.md | Flagship. Compare prior vs current SBOM; flag new CVEs |
workflows/cluster_audit.md | Live K8s cluster assessment (CIS / NSA / MITRE) |
workflows/rbac_analysis.md | RBAC privilege mapping and attack-path search |
workflows/network_policy_review.md | NetworkPolicy coverage + enforcement validation |
Payloads Index
| Payload | Purpose |
payloads/container_escape_poc.md | Documented escape PoCs (authorized testing only) |
References Index
| Reference | Purpose |
references/image_scanning.md | Trivy, Grype, Syft, Clair, Snyk, Hadolint commands |
references/kubernetes_hardening.md | kube-bench, Kubescape, CIS K8s mapping, PSS |
references/container_escape.md | Escape vectors, capabilities, runtime CVEs |
references/runtime_security.md | Falco, Tetragon, eBPF, rule authoring |
references/bounty_patterns_2024_2026.md | Post-2023 bounty TTPs (CVE-2024-21626 runC, CVE-2025-23266 NVIDIA, SA token theft, RoleBinding privesc) |
Examples Index
| Example | Purpose |
examples/falco_custom_rule.yaml | Ready-to-load Falco rule pack |
examples/vulnerable_dockerfile.md | Common Dockerfile anti-patterns + fixes |
Templates Index
| Template | Purpose |
templates/assessment_report_template.md | End-of-engagement deliverable skeleton |
Tools
| Tool | Purpose | Install |
| Trivy | Image / FS vuln + SBOM + IaC | brew install trivy |
| Grype | Image / SBOM vuln | brew install grype |
| Syft | SBOM generator | brew install syft |
| Hadolint | Dockerfile lint | brew install hadolint |
| Kubescape | K8s security platform | curl -s https://raw.githubusercontent.com/kubescape/kubescape/master/install.sh | /bin/bash |
| kube-bench | CIS K8s benchmark | brew install kube-bench |
| kube-hunter | K8s pentest recon | pip install kube-hunter |
| Falco | Runtime security (eBPF) | Helm chart falcosecurity/falco |
| Tetragon | eBPF detection + enforcement | Helm chart cilium/tetragon |
| Docker Bench | Docker CIS benchmark | git clone https://github.com/docker/docker-bench-security.git |
| Cosign | Sign / attest images + SBOMs | brew install cosign |
| Crane | Registry ops (resolve digest) | brew install crane |
| rbac-tool | RBAC graph visualization | brew install insights-engineering/tap/rbac-tool |
Last Validated
2026-04. Minimum tool versions: Trivy 0.59, Grype 0.87, Syft 1.18, Kubescape 3.0, kube-bench 0.10 (CIS K8s v1.9), Falco 0.38, Tetragon 1.2, Hadolint 2.12, Cosign 2.4.
Other versions5 projects use a version of this.
Word for word · 1
- EvilFreelancer/secs★ 11100% same
Edited · 1
- hardw00t/ai-security-arsenal★ 10197% same
Wrote their own version · 3
- kyleoliveiro/sg-gov-skills★ 17same name
- Adarshukumar/skills★ 1same name
- vbrevik/claude_code_skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- analyzing-binariesSkill
- analyzing-malwareSkill
- analyzing-memory-imagesSkill
- analyzing-network-trafficSkill
- analyzing-phishing-emailsSkill
- attacking-active-directorySkill
- attacking-wireless-networksSkill
- auditing-code-for-vulnerabilitiesSkill
- auditing-mcp-serversSkill
- auditing-supply-chainSkill
- cracking-passwordsSkill
- engineering-detectionsSkill
- enumerating-network-servicesSkill
- escalating-linux-privilegesSkill
- escalating-windows-privilegesSkill
- establishing-persistenceSkill
- exploiting-cloud-platformsSkill
- hardening-cloud-postureSkill
- hunting-threatsSkill
- hunting-web-backdoorsSkill
- iac-securitySkill
- investigating-aws-incidentsSkill
- investigating-azure-incidentsSkill
- investigating-gcp-incidentsSkill
- investigating-m365-entraSkill
- investigating-windows-endpointsSkill
- maintaining-engagement-stateSkill
- managing-vulnerabilitiesSkill
- mapping-attack-techniquesSkill
- orchestrating-vulnerability-researchSkill
- performing-reconnaissanceSkill
- performing-social-engineeringSkill
- producing-threat-intelligenceSkill
- recognizing-deceptionSkill
- reporting-security-findingsSkill
- responding-to-incidentsSkill
- reviewing-cryptographySkill
- securing-ai-systemsSkill
- testing-apisSkill
- testing-ics-ot-protocolsSkill
- testing-mobile-applicationsSkill
- testing-web-applicationsSkill
- threat-modelingSkill
- transferring-filesSkill
- triaging-security-alertsSkill
- vetting-agent-extensionsSkill
- writing-sigma-rulesSkill
- writing-yara-rulesSkill
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
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.

