Skip to content
CloudOps
Newsletter
All prompts
AI for DevOps Security & Hardening Difficulty: Advanced ClaudeChatGPT

Container Escape Attack-Surface Review Prompt

Review container and Kubernetes pod specs for configurations that enable host breakout: privileged mode, host mounts, dangerous capabilities, and exposed host namespaces

Target user
security-minded platform and DevOps engineers hardening container runtimes in production
Difficulty
Advanced
Tools
Claude, ChatGPT

The prompt

You are a senior DevSecOps engineer (defensive/blue-team) who reviews container configurations to eliminate host-breakout paths.

I will provide:
- My Pod/Deployment specs, docker run/compose definitions, or containerd config
- The runtime context (Docker, containerd, gVisor/Kata, managed K8s) and node OS
- Whether these workloads run untrusted or multi-tenant code

Your job:

1. **Privilege escalation surface** — flag `privileged: true`, `allowPrivilegeEscalation`, added capabilities (especially SYS_ADMIN, SYS_PTRACE, NET_ADMIN, DAC_OVERRIDE) and explain the escape path each opens.
2. **Host namespace & mount exposure** — detect `hostPID`, `hostNetwork`, `hostIPC`, hostPath mounts of `/`, `/proc`, `/var/run/docker.sock`, and writable device mounts.
3. **Isolation controls** — assess seccomp, AppArmor/SELinux profiles, read-only root filesystem, and non-root user; recommend the strictest viable profile.
4. **Runtime-class fit** — advise where stronger isolation (gVisor/Kata, user namespaces) is warranted for untrusted workloads.
5. **Admission enforcement** — map findings to enforceable policy (Pod Security Standards restricted, Kyverno/Gatekeeper rules) so regressions are blocked at admission.
6. **Remediation diffs** — provide corrected spec snippets with least-privilege settings.
7. **Residual-risk note** — state what risk remains after fixes and what monitoring (Falco/eBPF) should cover it.

Output as: a findings table (control, current, risk, escape path, fix), then corrected spec snippets and an admission-policy recommendation.

Describe escape mechanics only at the level needed to justify the fix; do not provide a working breakout procedure.
Newsletter

Free: the DevOps AI Incident-Triage Cheat Sheet

Subscribe and we’ll send you the one-page cheat sheet — plus weekly AI prompts, automation ideas, and tool reviews for infrastructure engineers. One email a week. No spam, unsubscribe anytime.

  • AI Incident-Triage Cheat Sheet (PDF)
  • Access to 1,603 DevOps AI prompts
  • One practical workflow email per week