Back to catalog
Static reviewDevelopment

Skill dossier

detecting-container-escape-attempts

Source declaration

Detects container escape at runtime across tooling - namespace manipulation, capability abuse, kernel exploits, sensitive host mounts, and anomalous syscalls - and explains which signals matter regardless of whether Falco, Sysdig, auditd, or an EDR is doing the collection. Use when deciding what breakout behaviour to monitor, investigating a suspected Docker or Kubernetes breakout, or comparing escape coverage across runtime sensors. Keywords: container escape, breakout, namespaces, CAP_SYS_ADMIN, privileged, hostPath, kernel exploit, syscall. Do not use for Falco rule syntax itself - use detecting-container-escape-with-falco-rules; for a static configuration sweep use performing-container-escape-detection.

The author's original description, preserved in English. It describes intent, not verified performance.

Detects container escape at runtime across tooling - namespace manipulation, capability abuse, kernel exploits, sensitive host mounts, and anomalous syscalls - and explains which signals matter regardless of whether Falco, Sysdig, auditd, or an EDR is doing the collection. Use when deciding what breakout behaviour to monitor, investigating a suspected Docker or Kubernetes breakout, or comparing escape coverage across runtime sensors. Keywords: container escape, breakout, namespaces, CAP_SYS_ADMIN, privileged, hostPath, kernel exploit, syscall. Do not use for Falco rule syntax itself - use detecting-container-escape-with-falco-rules; for a static configuration sweep use performing-container-escape-detection.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Detects container escape at runtime across tooling - namespace manipulation, capability abuse, kernel exploits, sensitive host mounts, and anomalous syscalls - and explains which signals matter regardless of whether Falco, Sysdig, auditd, or an EDR is doing the collection. Use when deciding what breakout behaviour to monitor, investigating a suspected Docker or Kubernetes breakout, or comparing escape coverage across runtime sensors. Keywords: container escape, breakout, namespaces, CAP_SYS_ADMIN, privileged, hostPath, kernel exploit, syscall. Do not use for Falco rule syntax itself - use detecting-container-escape-with-falco-rules; for a static configuration sweep use performing-container-escape-detection. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/detecting-container-escape-attempts/SKILL.md:L86]
  • Step 1: Deploy Falco for Runtime Detection [Source statement; provisional, not tested. Evidence: skills/detecting-container-escape-attempts/SKILL.md:L88]
  • Step 2: Custom Falco Rules for Escape Detection [Source statement; provisional, not tested. Evidence: skills/detecting-container-escape-attempts/SKILL.md:L117]
  • Step 3: Configure Seccomp Profile for Escape Prevention [Source statement; provisional, not tested. Evidence: skills/detecting-container-escape-attempts/SKILL.md:L222]
  • Step 4: Audit Rules for Container Escape [Source statement; provisional, not tested. Evidence: skills/detecting-container-escape-attempts/SKILL.md:L263]
  • Step 5: Real-Time Alert Pipeline [Source statement; provisional, not tested. Evidence: skills/detecting-container-escape-attempts/SKILL.md:L285]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/detecting-container-escape-attempts/SKILL.md:L1-L41]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
50 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/detecting-container-escape-attempts/assets/template.mdReference1.3 KB
skills/detecting-container-escape-attempts/LICENSEOther11 KB
skills/detecting-container-escape-attempts/references/api-reference.mdReference2.2 KB
skills/detecting-container-escape-attempts/references/standards.mdReference2.3 KB
skills/detecting-container-escape-attempts/references/workflows.mdReference3 KB
skills/detecting-container-escape-attempts/scripts/agent.pyScript6.6 KB
skills/detecting-container-escape-attempts/scripts/process.pyScript12.2 KB
skills/detecting-container-escape-attempts/SKILL.mdInstruction11.3 KB

SKILL.md frontmatter

{
  "name": "detecting-container-escape-attempts",
  "description": "Detects container escape at runtime across tooling - namespace manipulation, capability abuse, kernel exploits, sensitive host mounts, and anomalous syscalls - and explains which signals matter regardless of whether Falco, Sysdig, auditd, or an EDR is doing the collection. Use when deciding what breakout behaviour to monitor, investigating a suspected Docker or Kubernetes breakout, or comparing escape coverage across runtime sensors. Keywords: container escape, breakout, namespaces, CAP_SYS_ADMIN, privileged, hostPath, kernel exploit, syscall. Do not use for Falco rule syntax itself - use detecting-container-escape-with-falco-rules; for a static configuration sweep use performing-container-escape-detection.",
  "domain": "cybersecurity",
  "subdomain": "container-security",
  "tags": [
    "containers",
    "kubernetes",
    "docker",
    "security",
    "runtime-security",
    "escape-detection"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "d3fend_techniques": [
    "Platform Monitoring",
    "Process Code Segment Verification",
    "Stack Frame Canary Validation",
    "Segment Address Offset Randomization",
    "Process Analysis"
  ],
  "nist_csf": [
    "PR.PS-01",
    "PR.IR-01",
    "ID.AM-08",
    "DE.CM-01"
  ],
  "mitre_attack": [
    "T1610",
    "T1611",
    "T1609",
    "T1525"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Core Concepts

    Source-described action candidate under “Core Concepts”; not verified execution.

  4. 04
    Action

    Syscall monitoring - eBPF/kernel module captures syscalls in real-time

    Source-described action candidate under “Detection Layers”; not verified execution.

  5. 05
    Action

    File integrity - Detect modification of escape-enabling paths

    Source-described action candidate under “Detection Layers”; not verified execution.

  6. 06
    Action

    Process monitoring - Track process creation, namespace changes

    Source-described action candidate under “Detection Layers”; not verified execution.

Inspect all extracted workflow candidates (16 candidate steps)
  1. 07
    Action

    Network monitoring - Detect container-to-host connections

    Source-described action candidate under “Detection Layers”; not verified execution.

  2. 08
    Action

    Audit logging - Linux auditd for capability and mount operations

    Source-described action candidate under “Detection Layers”; not verified execution.

  3. 09
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  4. 10
    Action

    Step 1: Deploy Falco for Runtime Detection

    Source-described action candidate under “Step 1: Deploy Falco for Runtime Detection”; not verified execution.

  5. 11
    Action

    Step 2: Custom Falco Rules for Escape Detection

    Source-described action candidate under “Step 2: Custom Falco Rules for Escape Detection”; not verified execution.

  6. 12
    Action

    Step 3: Configure Seccomp Profile for Escape Prevention

    Source-described action candidate under “Step 3: Configure Seccomp Profile for Escape Prevention”; not verified execution.

  7. 13
    Action

    Step 4: Audit Rules for Container Escape

    Source-described action candidate under “Step 4: Audit Rules for Container Escape”; not verified execution.

  8. 14
    Action

    Step 5: Real-Time Alert Pipeline

    Source-described action candidate under “Step 5: Real-Time Alert Pipeline”; not verified execution.

  9. 15
    Action

    Validation Commands

    Source-described action candidate under “Validation Commands”; not verified execution.

  10. 16
    Action

    References

    Source-described action candidate under “References”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

36 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

10 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 10 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

26 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 26 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/detecting-container-escape-attempts/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/detecting-container-escape-attempts/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/detecting-container-escape-attempts
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.