Back to catalog
Static reviewDevelopment

Skill dossier

detecting-container-runtime-threats-with-falco

Source declaration

Deploys and operates Falco with the modern eBPF driver in Kubernetes and Docker, covering driver selection, Helm installation, output channels, and the built-in ruleset that detects container escape, namespace abuse, privileged mounts, and anomalous syscalls. Use when standing Falco up on a cluster, choosing between the eBPF and kernel-module drivers, routing Falco alerts into a SIEM or Falcosidekick, or upgrading an existing deployment. Keywords: Falco, modern_ebpf, kernel module, Helm, Falcosidekick, runtime security, syscall. Do not use for authoring individual escape rules - use detecting-container-escape-with-falco-rules.

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

Deploys and operates Falco with the modern eBPF driver in Kubernetes and Docker, covering driver selection, Helm installation, output channels, and the built-in ruleset that detects container escape, namespace abuse, privileged mounts, and anomalous syscalls. Use when standing Falco up on a cluster, choosing between the eBPF and kernel-module drivers, routing Falco alerts into a SIEM or Falcosidekick, or upgrading an existing deployment. Keywords: Falco, modern_ebpf, kernel module, Helm, Falcosidekick, runtime security, syscall. Do not use for authoring individual escape rules - use detecting-container-escape-with-falco-rules.

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.

Deploys and operates Falco with the modern eBPF driver in Kubernetes and Docker, covering driver selection, Helm installation, output channels, and the built-in ruleset that detects container escape, namespace abuse, privileged mounts, and anomalous syscalls. Use when standing Falco up on a cluster, choosing between the eBPF and kernel-module drivers, routing Falco alerts into a SIEM or Falcosidekick, or upgrading an existing deployment. Keywords: Falco, modern_ebpf, kernel module, Helm, Falcosidekick, runtime security, syscall. Do not use for authoring individual escape rules - use detecting-container-escape-with-falco-rules. 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-runtime-threats-with-falco/SKILL.md:L91]
  • Step 1: Install Falco and Confirm the Driver [Source statement; provisional, not tested. Evidence: skills/detecting-container-runtime-threats-with-falco/SKILL.md:L93]
  • Step 2: Learn the Rule, Macro, and List Schema [Source statement; provisional, not tested. Evidence: skills/detecting-container-runtime-threats-with-falco/SKILL.md:L106]
  • Step 3: Write a Container-Escape Detection Rule (releaseagent / cgroup) [Source statement; provisional, not tested. Evidence: skills/detecting-container-runtime-threats-with-falco/SKILL.md:L122]
  • Step 4: Detect Namespace Breakout (setns / nsenter) [Source statement; provisional, not tested. Evidence: skills/detecting-container-runtime-threats-with-falco/SKILL.md:L144]
  • Step 5: Detect Privileged Mount and Docker Socket Abuse [Source statement; provisional, not tested. Evidence: skills/detecting-container-runtime-threats-with-falco/SKILL.md:L163]
  • Step 6: Detect Reverse Shells and Sensitive File Reads [Source statement; provisional, not tested. Evidence: skills/detecting-container-runtime-threats-with-falco/SKILL.md:L192]
  • Step 7: Validate Rule Syntax and Load [Source statement; provisional, not tested. Evidence: skills/detecting-container-runtime-threats-with-falco/SKILL.md:L223]
  • Step 8: Trigger and Confirm (Purple-Team) [Source statement; provisional, not tested. Evidence: skills/detecting-container-runtime-threats-with-falco/SKILL.md:L237]
  • Step 9: Forward Alerts to a SIEM [Source statement; provisional, not tested. Evidence: skills/detecting-container-runtime-threats-with-falco/SKILL.md:L250]

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-runtime-threats-with-falco/SKILL.md:L1-L29]

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
5
Markdown files
3
scripts
1
references
2
Size
32.1 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/detecting-container-runtime-threats-with-falco/LICENSEOther11 KB
skills/detecting-container-runtime-threats-with-falco/references/api-reference.mdReference2.6 KB
skills/detecting-container-runtime-threats-with-falco/references/standards.mdReference1.8 KB
skills/detecting-container-runtime-threats-with-falco/scripts/agent.pyScript5.1 KB
skills/detecting-container-runtime-threats-with-falco/SKILL.mdInstruction11.6 KB

SKILL.md frontmatter

{
  "name": "detecting-container-runtime-threats-with-falco",
  "description": "Deploys and operates Falco with the modern eBPF driver in Kubernetes and Docker, covering driver selection, Helm installation, output channels, and the built-in ruleset that detects container escape, namespace abuse, privileged mounts, and anomalous syscalls. Use when standing Falco up on a cluster, choosing between the eBPF and kernel-module drivers, routing Falco alerts into a SIEM or Falcosidekick, or upgrading an existing deployment. Keywords: Falco, modern_ebpf, kernel module, Helm, Falcosidekick, runtime security, syscall. Do not use for authoring individual escape rules - use detecting-container-escape-with-falco-rules.",
  "domain": "cybersecurity",
  "subdomain": "container-security",
  "tags": [
    "falco",
    "runtime-security",
    "ebpf",
    "container-escape",
    "syscall-monitoring",
    "detection-engineering",
    "kubernetes",
    "threat-detection"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "DE.CM-01"
  ],
  "mitre_attack": [
    "T1611"
  ]
}

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

    Objectives

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

  4. 04
    Action

    MITRE ATT&CK Mapping

    Source-described action candidate under “MITRE ATT&CK Mapping”; not verified execution.

  5. 05
    Action

    Workflow

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

  6. 06
    Action

    Step 1: Install Falco and Confirm the Driver

    Source-described action candidate under “Step 1: Install Falco and Confirm the Driver”; not verified execution.

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

    Step 2: Learn the Rule, Macro, and List Schema

    Source-described action candidate under “Step 2: Learn the Rule, Macro, and List Schema”; not verified execution.

  2. 08
    Output

    Step 3: Write a Container-Escape Detection Rule (releaseagent / cgroup)

    Source-described output candidate under “Step 3: Write a Container-Escape Detection Rule (release_agent / cgroup)”; not verified execution.

  3. 09
    Action

    Step 4: Detect Namespace Breakout (setns / nsenter)

    Source-described action candidate under “Step 4: Detect Namespace Breakout (setns / nsenter)”; not verified execution.

  4. 10
    Action

    Step 5: Detect Privileged Mount and Docker Socket Abuse

    Source-described action candidate under “Step 5: Detect Privileged Mount and Docker Socket Abuse”; not verified execution.

  5. 11
    Action

    Step 6: Detect Reverse Shells and Sensitive File Reads

    Source-described action candidate under “Step 6: Detect Reverse Shells and Sensitive File Reads”; not verified execution.

  6. 12
    Input

    Step 7: Validate Rule Syntax and Load

    Source-described input candidate under “Step 7: Validate Rule Syntax and Load”; not verified execution.

  7. 13
    Action

    Step 8: Trigger and Confirm (Purple-Team)

    Source-described action candidate under “Step 8: Trigger and Confirm (Purple-Team)”; not verified execution.

  8. 14
    Action

    Step 9: Forward Alerts to a SIEM

    Source-described action candidate under “Step 9: Forward Alerts to a SIEM”; not verified execution.

  9. 15
    Action

    Tools and Resources

    Source-described action candidate under “Tools and Resources”; not verified execution.

  10. 16
    Action

    Key Falco Filter Fields

    Source-described action candidate under “Key Falco Filter Fields”; not verified execution.

  11. 17
    Action

    Validation Criteria

    Source-described action candidate under “Validation Criteria”; 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.

Attention recommended

46 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

22 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 22 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

16 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 16 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Elevated privileges are referenced

8 occurrences

Privilege-elevation syntax is present. Confirm whether elevation is necessary and inspect every operation performed under it; static analysis cannot prove that elevation succeeded. This rule matched 8 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-runtime-threats-with-falco/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 5 collected file(s), 3 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/detecting-container-runtime-threats-with-falco/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-runtime-threats-with-falco
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.