Back to catalog
Static reviewDevelopment

Skill dossier

detecting-privilege-escalation-in-kubernetes-pods

Source declaration

Detects and prevents privilege escalation inside Kubernetes pods by combining admission control (OPA policies), runtime monitoring (Falco), and audit log analysis of security contexts, Linux capabilities, and syscall patterns. Use when investigating a pod running as root or privileged, hardening workloads against in-pod escalation, or hunting for containers exceeding their intended scope. Keywords: allowPrivilegeEscalation, runAsRoot, capabilities, securityContext, OPA, Falco, audit log. Do not use for escalation through RBAC and service-account permissions - use auditing-kubernetes-rbac-privilege-escalation.

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

Detects and prevents privilege escalation inside Kubernetes pods by combining admission control (OPA policies), runtime monitoring (Falco), and audit log analysis of security contexts, Linux capabilities, and syscall patterns. Use when investigating a pod running as root or privileged, hardening workloads against in-pod escalation, or hunting for containers exceeding their intended scope. Keywords: allowPrivilegeEscalation, runAsRoot, capabilities, securityContext, OPA, Falco, audit log. Do not use for escalation through RBAC and service-account permissions - use auditing-kubernetes-rbac-privilege-escalation.

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 and prevents privilege escalation inside Kubernetes pods by combining admission control (OPA policies), runtime monitoring (Falco), and audit log analysis of security contexts, Linux capabilities, and syscall patterns. Use when investigating a pod running as root or privileged, hardening workloads against in-pod escalation, or hunting for containers exceeding their intended scope. Keywords: allowPrivilegeEscalation, runAsRoot, capabilities, securityContext, OPA, Falco, audit log. Do not use for escalation through RBAC and service-account permissions - use auditing-kubernetes-rbac-privilege-escalation. 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

  • Source-declared purpose: Detects and prevents privilege escalation inside Kubernetes pods by combining admission control (OPA policies), runtime monitoring (Falco), and audit log analysis of security contexts, Linux capabilities, and syscall patterns. Use when investigating a pod running as root or privileged, hardening workloads against in-pod escalation, or hunting for containers exceeding their intended scope. Keywords: allowPrivilegeEscalation, runAsRoot, capabilities, securityContext, OPA, Falco, audit log. Do not use for escalation through RBAC and service-account permissions - use auditing-kubernetes-rbac-privilege-escalation. [Evidence: skills/detecting-privilege-escalation-in-kubernetes-pods/SKILL.md:L1-L40]
  • Provisional classification: category and tags are inferred from names, descriptions, and file paths, not verified outcomes. [Evidence: skills/detecting-privilege-escalation-in-kubernetes-pods/SKILL.md:L1-L40]

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-privilege-escalation-in-kubernetes-pods/SKILL.md:L1-L40]

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
34.1 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/detecting-privilege-escalation-in-kubernetes-pods/assets/template.mdReference1 KB
skills/detecting-privilege-escalation-in-kubernetes-pods/LICENSEOther11 KB
skills/detecting-privilege-escalation-in-kubernetes-pods/references/api-reference.mdReference1.2 KB
skills/detecting-privilege-escalation-in-kubernetes-pods/references/standards.mdReference1 KB
skills/detecting-privilege-escalation-in-kubernetes-pods/references/workflows.mdReference1.2 KB
skills/detecting-privilege-escalation-in-kubernetes-pods/scripts/agent.pyScript4.2 KB
skills/detecting-privilege-escalation-in-kubernetes-pods/scripts/process.pyScript5.3 KB
skills/detecting-privilege-escalation-in-kubernetes-pods/SKILL.mdInstruction9.2 KB

SKILL.md frontmatter

{
  "name": "detecting-privilege-escalation-in-kubernetes-pods",
  "description": "Detects and prevents privilege escalation inside Kubernetes pods by combining admission control (OPA policies), runtime monitoring (Falco), and audit log analysis of security contexts, Linux capabilities, and syscall patterns. Use when investigating a pod running as root or privileged, hardening workloads against in-pod escalation, or hunting for containers exceeding their intended scope. Keywords: allowPrivilegeEscalation, runAsRoot, capabilities, securityContext, OPA, Falco, audit log. Do not use for escalation through RBAC and service-account permissions - use auditing-kubernetes-rbac-privilege-escalation.",
  "domain": "cybersecurity",
  "subdomain": "container-security",
  "tags": [
    "kubernetes",
    "privilege-escalation",
    "security-context",
    "capabilities",
    "detection",
    "pod-security"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "d3fend_techniques": [
    "Executable Denylisting",
    "Execution Isolation",
    "File Metadata Consistency Validation",
    "Restore Access",
    "Password Authentication"
  ],
  "nist_csf": [
    "PR.PS-01",
    "PR.IR-01",
    "ID.AM-08",
    "DE.CM-01"
  ],
  "mitre_attack": [
    "T1610",
    "T1611",
    "T1609",
    "T1525",
    "T1068"
  ]
}

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

    Privilege Escalation Vectors in Kubernetes

    Source-described action candidate under “Privilege Escalation Vectors in Kubernetes”; not verified execution.

  4. 04
    Action

    Detection with Admission Control

    Source-described action candidate under “Detection with Admission Control”; not verified execution.

  5. 05
    Action

    Runtime Detection with Falco

    Source-described action candidate under “Runtime Detection with Falco”; not verified execution.

  6. 06
    Action

    Kubernetes Audit Log Detection

    Source-described action candidate under “Kubernetes Audit Log Detection”; not verified execution.

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

    Investigation Playbook

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

  2. 08
    Action

    Best Practices

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

  3. 09
    Action

    Enable Pod Security Admission at `restricted` level for production namespaces

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

  4. 10
    Action

    Drop ALL capabilities and add back only what is needed

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

  5. 11
    Action

    Set allowPrivilegeEscalation: false on all containers

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

  6. 12
    Action

    Run as non-root (runAsNonRoot: true, runAsUser > 0)

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

  7. 13
    Action

    Disable automountServiceAccountToken unless API access is needed

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

  8. 14
    Action

    Monitor with Falco for runtime privilege escalation attempts

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

  9. 15
    Action

    Audit RBAC changes with Kubernetes audit logging

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

  10. 16
    Action

    Use seccomp profiles to restrict syscalls

    Source-described action candidate under “Best Practices”; 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

12 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

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

Note

File modification is described or implemented

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

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 1 location(s) in the collected text; 1 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-privilege-escalation-in-kubernetes-pods/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-privilege-escalation-in-kubernetes-pods/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-privilege-escalation-in-kubernetes-pods
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.