Back to catalog
Static reviewDevelopment

Skill dossier

implementing-pod-security-admission-controller

Source declaration

Configures and operates the Kubernetes Pod Security Admission (PSA) controller that enforces Pod Security Standards: namespace enforce/audit/warn labels, cluster-wide defaults via AdmissionConfiguration, exemptions for usernames, runtime classes and namespaces, version pinning, and troubleshooting pods the controller rejected. Use when wiring PSA up on a cluster, setting cluster-wide default enforcement, exempting system namespaces, debugging why a pod was rejected or why enforcement is not firing, or reading PSA audit and warning output. Keywords: Pod Security Admission, PSA, admission controller, AdmissionConfiguration, pod-security.kubernetes.io labels, enforce audit warn, exemptions, kube-apiserver. Do not use for choosing which security profile a workload needs - use implementing-kubernetes-pod-security-standards.

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

Configures and operates the Kubernetes Pod Security Admission (PSA) controller that enforces Pod Security Standards: namespace enforce/audit/warn labels, cluster-wide defaults via AdmissionConfiguration, exemptions for usernames, runtime classes and namespaces, version pinning, and troubleshooting pods the controller rejected. Use when wiring PSA up on a cluster, setting cluster-wide default enforcement, exempting system namespaces, debugging why a pod was rejected or why enforcement is not firing, or reading PSA audit and warning output. Keywords: Pod Security Admission, PSA, admission controller, AdmissionConfiguration, pod-security.kubernetes.io labels, enforce audit warn, exemptions, kube-apiserver. Do not use for choosing which security profile a workload needs - use implementing-kubernetes-pod-security-standards.

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.

Configures and operates the Kubernetes Pod Security Admission (PSA) controller that enforces Pod Security Standards: namespace enforce/audit/warn labels, cluster-wide defaults via AdmissionConfiguration, exemptions for usernames, runtime classes and namespaces, version pinning, and troubleshooting pods the controller rejected. Use when wiring PSA up on a cluster, setting cluster-wide default enforcement, exempting system namespaces, debugging why a pod was rejected or why enforcement is not firing, or reading PSA audit and warning output. Keywords: Pod Security Admission, PSA, admission controller, AdmissionConfiguration, pod-security.kubernetes.io labels, enforce audit warn, exemptions, kube-apiserver. Do not use for choosing which security profile a workload needs - use implementing-kubernetes-pod-security-standards. 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

  • Step 1: Audit Current State [Source statement; provisional, not tested. Evidence: skills/implementing-pod-security-admission-controller/SKILL.md:L279]
  • Step 2: Map PSP to PSA Profiles [Source statement; provisional, not tested. Evidence: skills/implementing-pod-security-admission-controller/SKILL.md:L289]
  • Step 3: Apply PSA Labels (Audit First) [Source statement; provisional, not tested. Evidence: skills/implementing-pod-security-admission-controller/SKILL.md:L299]
  • Step 4: Review and Fix Violations [Source statement; provisional, not tested. Evidence: skills/implementing-pod-security-admission-controller/SKILL.md:L307]
  • Step 5: Enable Enforcement [Source statement; provisional, not tested. Evidence: skills/implementing-pod-security-admission-controller/SKILL.md:L313]

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/implementing-pod-security-admission-controller/SKILL.md:L1-L36]

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

File inventory

PathTypeBytes
skills/implementing-pod-security-admission-controller/assets/template.mdReference1.3 KB
skills/implementing-pod-security-admission-controller/LICENSEOther11 KB
skills/implementing-pod-security-admission-controller/references/api-reference.mdReference5.1 KB
skills/implementing-pod-security-admission-controller/references/standards.mdReference1.1 KB
skills/implementing-pod-security-admission-controller/references/workflows.mdReference1 KB
skills/implementing-pod-security-admission-controller/scripts/agent.pyScript11.4 KB
skills/implementing-pod-security-admission-controller/scripts/process.pyScript5.1 KB
skills/implementing-pod-security-admission-controller/SKILL.mdInstruction9.6 KB

SKILL.md frontmatter

{
  "name": "implementing-pod-security-admission-controller",
  "description": "Configures and operates the Kubernetes Pod Security Admission (PSA) controller that enforces Pod Security Standards: namespace enforce/audit/warn labels, cluster-wide defaults via AdmissionConfiguration, exemptions for usernames, runtime classes and namespaces, version pinning, and troubleshooting pods the controller rejected. Use when wiring PSA up on a cluster, setting cluster-wide default enforcement, exempting system namespaces, debugging why a pod was rejected or why enforcement is not firing, or reading PSA audit and warning output. Keywords: Pod Security Admission, PSA, admission controller, AdmissionConfiguration, pod-security.kubernetes.io labels, enforce audit warn, exemptions, kube-apiserver. Do not use for choosing which security profile a workload needs - use implementing-kubernetes-pod-security-standards.",
  "domain": "cybersecurity",
  "subdomain": "container-security",
  "tags": [
    "kubernetes",
    "pod-security-admission",
    "psa",
    "pod-security-standards",
    "admission-controller"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "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

    Pod Security Standards

    Source-described action candidate under “Pod Security Standards”; not verified execution.

  4. 04
    Action

    Enforcement Modes

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

  5. 05
    Action

    Implementation

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

  6. 06
    Action

    Dry-Run Testing

    Source-described action candidate under “Dry-Run Testing”; not verified execution.

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

    Cluster-Wide Defaults (AdmissionConfiguration)

    Source-described action candidate under “Cluster-Wide Defaults (AdmissionConfiguration)”; not verified execution.

  2. 08
    Action

    Migration from PodSecurityPolicy

    Source-described action candidate under “Migration from PodSecurityPolicy”; not verified execution.

  3. 09
    Action

    Step 1: Audit Current State

    Source-described action candidate under “Step 1: Audit Current State”; not verified execution.

  4. 10
    Action

    Step 2: Map PSP to PSA Profiles

    Source-described action candidate under “Step 2: Map PSP to PSA Profiles”; not verified execution.

  5. 11
    Action

    Step 3: Apply PSA Labels (Audit First)

    Source-described action candidate under “Step 3: Apply PSA Labels (Audit First)”; not verified execution.

  6. 12
    Action

    Step 4: Review and Fix Violations

    Source-described action candidate under “Step 4: Review and Fix Violations”; not verified execution.

  7. 13
    Action

    Step 5: Enable Enforcement

    Source-described action candidate under “Step 5: Enable Enforcement”; not verified execution.

  8. 14
    Action

    Monitoring

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

  9. 15
    Action

    Best Practices

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

  10. 16
    Action

    Start with audit+warn before enforce to assess impact

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

  11. 17
    Action

    Use dry-run to test enforcement before applying

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

  12. 18
    Action

    Exempt system namespaces (kube-system, monitoring) in cluster defaults

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

  13. 19
    Action

    Pin version (enforce-version) for predictable behavior across upgrades

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

  14. 20
    Action

    Set cluster-wide baseline as default, then restrict specific namespaces

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

  15. 21
    Action

    Combine with Gatekeeper for additional custom policies beyond PSA

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

  16. 22
    Action

    Use restricted profile for all production workloads

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

  17. 23
    Action

    Document exemptions with clear justification

    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.

Items warrant review

14 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

12 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 12 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/implementing-pod-security-admission-controller/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/implementing-pod-security-admission-controller/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/implementing-pod-security-admission-controller
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.