Infrastructure and Kubernetes security audit
Review provided infrastructure templates and Kubernetes manifests for policy gaps.
Customize the recipe
0/1500 characters
Prompt preview
# Infrastructure and Kubernetes security audit Review provided infrastructure templates and Kubernetes manifests for policy gaps. ## Read-only scope Review only the authorized app, site, server, or local source named or supplied by the user. Work from provided code, configuration, redacted exports, and completed test results. Use URLs and hostnames as scope identifiers. Request the missing artifacts if evidence is insufficient. Use existing offline, read-only analysis on those artifacts. Exclude live probing, vulnerability reproduction, exploit payloads, credential testing, new load generation, and changes to the target or its files. ## Tools and setup · Universal Use the linked resources as references for interpreting the supplied material. Follow the read-only scope when a linked workflow describes other actions. - [Security Threat Model](https://github.com/openai/skills/blob/main/skills/.curated/security-threat-model/SKILL.md) (Skill) — Map assets, access boundaries, and risk from supplied architecture and source evidence. - [Checkov](https://github.com/bridgecrewio/checkov) (Repository) — Use static infrastructure policy guidance to interpret local manifest findings. - [KubeLinter](https://github.com/stackrox/kube-linter) (Repository) — Review local Kubernetes manifests for insecure workload defaults and missing protections. ## Workflow Review supplied IaC templates, manifests, policy exports, and existing lint results. Examine least privilege, network isolation, workload security, and storage settings with particular attention to environment-specific overrides. ## Deliverable An infrastructure policy findings report indexed by resource, namespace, or environment. - Minimalism: Apply this style to report presentation only. Plain Markdown is sufficient. ## Acceptance checks - [ ] Each finding cites the specific configuration resource and property. - [ ] Separate confirmed manifest defaults from assumed live cloud or cluster state. - [ ] Give each finding a severity, confidence, affected component, evidence reference, impact, and recommended mitigation. Explicitly list unverified controls and gaps. - [ ] Redact credentials, tokens, personal data, and sensitive values in the report.
Recipe resources
Source, setup, and compatibility details.
Security Threat Model
Map assets, access boundaries, and risk from supplied architecture and source evidence.
Upstream documents Codex.
28.9K GitHub stars on the source repository
Checkov
Use static infrastructure policy guidance to interpret local manifest findings.
License · Apache-2.0
9.2K GitHub stars
KubeLinter
Review local Kubernetes manifests for insecure workload defaults and missing protections.
License · Apache-2.0
3.5K GitHub stars