[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFAVB9CD5EYHGSS076DSQ8":3,"skill-same:01M6AFAVB9CD5EYHGSS076DSQ8":121},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":67,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6AFAVB9CD5EYHGSS076DSQ8","implementing-pod-security-admission-controller",null,"Configures and operates the Kubernetes Pod Security Admission (PSA) controller that enforces Pod Security Standards: namespace enforce\u002Faudit\u002Fwarn 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.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",35925,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"security","controller","implementing pod security admission controller","kubernetes","cybersecurity","workload","pr","debugging","audit","container-security","pod-security","security-standards","PSA","pod-security-admission","pod-security-standards","admission-controller","2026-11-10 10:12:30",false,"---\nname: implementing-pod-security-admission-controller\ndescription: >-\n  Configures and operates the Kubernetes Pod Security Admission (PSA) controller\n  that enforces Pod Security Standards: namespace enforce\u002Faudit\u002Fwarn labels,\n  cluster-wide defaults via AdmissionConfiguration, exemptions for usernames,\n  runtime classes and namespaces, version pinning, and troubleshooting pods the\n  controller rejected. Use when wiring PSA up on a cluster, setting cluster-wide\n  default enforcement, exempting system namespaces, debugging why a pod was\n  rejected or why enforcement is not firing, or reading PSA audit and warning\n  output. Keywords: Pod Security Admission, PSA, admission controller,\n  AdmissionConfiguration, pod-security.kubernetes.io labels, enforce audit warn,\n  exemptions, kube-apiserver. Do not use for choosing which security profile a\n  workload needs - use implementing-kubernetes-pod-security-standards.\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- kubernetes\n- pod-security-admission\n- psa\n- pod-security-standards\n- admission-controller\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- PR.IR-01\n- ID.AM-08\n- DE.CM-01\nmitre_attack:\n- T1610\n- T1611\n- T1609\n- T1525\n---\n\n# Implementing Pod Security Admission Controller\n\n## Overview\n\nPod Security Admission (PSA) is a built-in Kubernetes admission controller (stable since v1.25) that enforces Pod Security Standards at the namespace level. It replaces the deprecated PodSecurityPolicy (PSP) and provides three security profiles: Privileged, Baseline, and Restricted, with three enforcement modes: enforce, audit, and warn.\n\n\n## When to Use\n\n- Wiring PSA up on a cluster for the first time\n- Setting cluster-wide default enforcement via `AdmissionConfiguration`\n- Exempting system namespaces, service accounts, or runtime classes from enforcement\n- Debugging why a pod was rejected, or why enforcement is silently not firing\n- Staging a safe rollout: `warn` and `audit` first, `enforce` once violations reach zero\n- Pulling PSA violations out of the kube-apiserver audit log\n\n**Not this skill:** deciding which profile a workload should run under, or what\n`securityContext` changes Restricted demands. Use\n`implementing-kubernetes-pod-security-standards`.\n\n## Prerequisites\n\n- Kubernetes v1.25+ (PSA is stable\u002FGA)\n- kubectl with cluster-admin access\n- No dependency on external tools - PSA is built into kube-apiserver\n\n## Pod Security Standards\n\n### Privileged Profile\n- **Unrestricted** - No restrictions applied\n- Use case: System-level pods (kube-system, monitoring)\n\n### Baseline Profile\n- **Minimally restrictive** - Prevents known privilege escalation\n- Blocks: privileged containers, hostPID, hostIPC, hostNetwork, hostPorts, certain volume types, adding capabilities beyond runtime defaults\n\n### Restricted Profile\n- **Heavily restricted** - Follows security best practices\n- Requires: non-root, drop ALL capabilities, seccomp RuntimeDefault, read-only root filesystem considerations\n- Blocks: Everything in Baseline plus running as root, privilege escalation, non-approved volume types\n\n## Enforcement Modes\n\n| Mode | Behavior | Use Case |\n|------|----------|----------|\n| enforce | Reject pods violating policy | Production enforcement |\n| audit | Log violations to audit log | Pre-enforcement assessment |\n| warn | Show warnings to user | Developer feedback |\n\n## Implementation\n\n### Apply to Namespace via Labels\n\n```yaml\n# Restricted enforcement with audit and warn\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: production\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: restricted\n    pod-security.kubernetes.io\u002Fenforce-version: v1.28\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: v1.28\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: v1.28\n```\n\n```yaml\n# Baseline enforcement for staging\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: staging\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: baseline\n    pod-security.kubernetes.io\u002Fenforce-version: v1.28\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: v1.28\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: v1.28\n```\n\n```yaml\n# Privileged for system namespaces\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: kube-system\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: privileged\n```\n\n### Apply Labels with kubectl\n\n```bash\n# Set restricted enforcement\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Fenforce=restricted \\\n  pod-security.kubernetes.io\u002Fenforce-version=v1.28 \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted\n\n# Set baseline enforcement\nkubectl label namespace staging \\\n  pod-security.kubernetes.io\u002Fenforce=baseline \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted\n\n# Check current labels\nkubectl get namespace production -o jsonpath='{.metadata.labels}' | jq .\n```\n\n## Dry-Run Testing\n\n```bash\n# Test what would happen with restricted policy on a namespace\nkubectl label --dry-run=server --overwrite namespace staging \\\n  pod-security.kubernetes.io\u002Fenforce=restricted\n\n# Output shows existing pods that would violate the policy\n# Warning: existing pods in namespace \"staging\" violate the new PodSecurity enforce level \"restricted:latest\"\n```\n\n## Cluster-Wide Defaults (AdmissionConfiguration)\n\n```yaml\n# \u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\napiVersion: apiserver.config.k8s.io\u002Fv1\nkind: AdmissionConfiguration\nplugins:\n  - name: PodSecurity\n    configuration:\n      apiVersion: pod-security.admission.config.k8s.io\u002Fv1\n      kind: PodSecurityConfiguration\n      defaults:\n        enforce: baseline\n        enforce-version: latest\n        audit: restricted\n        audit-version: latest\n        warn: restricted\n        warn-version: latest\n      exemptions:\n        usernames: []\n        runtimeClasses: []\n        namespaces:\n          - kube-system\n          - kube-public\n          - kube-node-lease\n          - calico-system\n          - gatekeeper-system\n          - monitoring\n          - falco\n```\n\n### Apply to API Server\n\n```bash\n# Add to kube-apiserver manifests\n# \u002Fetc\u002Fkubernetes\u002Fmanifests\u002Fkube-apiserver.yaml\nspec:\n  containers:\n  - command:\n    - kube-apiserver\n    - --admission-control-config-file=\u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\n    volumeMounts:\n    - name: psa-config\n      mountPath: \u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\n      readOnly: true\n  volumes:\n  - name: psa-config\n    hostPath:\n      path: \u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\n      type: File\n```\n\n## Compliant Pod Examples\n\n### Restricted-Compliant Pod\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: restricted-pod\n  namespace: production\nspec:\n  securityContext:\n    runAsNonRoot: true\n    runAsUser: 1000\n    runAsGroup: 3000\n    fsGroup: 2000\n    seccompProfile:\n      type: RuntimeDefault\n  automountServiceAccountToken: false\n  containers:\n    - name: app\n      image: myregistry\u002Fmyapp:v1.0.0\n      securityContext:\n        allowPrivilegeEscalation: false\n        readOnlyRootFilesystem: true\n        capabilities:\n          drop:\n            - ALL\n      resources:\n        limits:\n          cpu: 500m\n          memory: 256Mi\n        requests:\n          cpu: 100m\n          memory: 128Mi\n      volumeMounts:\n        - name: tmp\n          mountPath: \u002Ftmp\n  volumes:\n    - name: tmp\n      emptyDir: {}\n```\n\n### Baseline-Compliant Pod\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: baseline-pod\n  namespace: staging\nspec:\n  containers:\n    - name: app\n      image: myregistry\u002Fmyapp:v1.0.0\n      securityContext:\n        allowPrivilegeEscalation: false\n      resources:\n        limits:\n          cpu: 500m\n          memory: 256Mi\n```\n\n## Migration from PodSecurityPolicy\n\n### Step 1: Audit Current State\n```bash\n# Check existing PSPs\nkubectl get psp\n\n# Check which service accounts use which PSP\nkubectl get clusterrolebinding -o json | \\\n  jq '.items[] | select(.roleRef.name | startswith(\"psp-\")) | {name: .metadata.name, subjects: .subjects}'\n```\n\n### Step 2: Map PSP to PSA Profiles\n```bash\n# For each namespace, determine required PSA level\nfor ns in $(kubectl get ns -o jsonpath='{.items[*].metadata.name}'); do\n  echo \"Namespace: $ns\"\n  kubectl label --dry-run=server namespace $ns \\\n    pod-security.kubernetes.io\u002Fenforce=restricted 2>&1 | head -5\ndone\n```\n\n### Step 3: Apply PSA Labels (Audit First)\n```bash\n# Start with audit mode\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted\n```\n\n### Step 4: Review and Fix Violations\n```bash\n# Check audit logs for violations\nkubectl get events --field-selector reason=FailedCreate -A\n```\n\n### Step 5: Enable Enforcement\n```bash\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Fenforce=restricted\n```\n\n## Monitoring\n\n```bash\n# Check PSA violations in events\nkubectl get events --all-namespaces --field-selector reason=FailedCreate\n\n# Check audit logs\nkubectl logs -n kube-system kube-apiserver-* | grep \"pod-security.kubernetes.io\"\n\n# List namespace PSA labels\nkubectl get namespaces -L pod-security.kubernetes.io\u002Fenforce\n```\n\n## Best Practices\n\n1. **Start with audit+warn** before enforce to assess impact\n2. **Use dry-run** to test enforcement before applying\n3. **Exempt system namespaces** (kube-system, monitoring) in cluster defaults\n4. **Pin version** (enforce-version) for predictable behavior across upgrades\n5. **Set cluster-wide baseline** as default, then restrict specific namespaces\n6. **Combine with Gatekeeper** for additional custom policies beyond PSA\n7. **Use restricted profile** for all production workloads\n8. **Document exemptions** with clear justification\n","# Implementing Pod Security Admission Controller\n\n## Overview\n\nPod Security Admission (PSA) is a built-in Kubernetes admission controller (stable since v1.25) that enforces Pod Security Standards at the namespace level. It replaces the deprecated PodSecurityPolicy (PSP) and provides three security profiles: Privileged, Baseline, and Restricted, with three enforcement modes: enforce, audit, and warn.\n\n\n## When to Use\n\n- Wiring PSA up on a cluster for the first time\n- Setting cluster-wide default enforcement via `AdmissionConfiguration`\n- Exempting system namespaces, service accounts, or runtime classes from enforcement\n- Debugging why a pod was rejected, or why enforcement is silently not firing\n- Staging a safe rollout: `warn` and `audit` first, `enforce` once violations reach zero\n- Pulling PSA violations out of the kube-apiserver audit log\n\n**Not this skill:** deciding which profile a workload should run under, or what\n`securityContext` changes Restricted demands. Use\n`implementing-kubernetes-pod-security-standards`.\n\n## Prerequisites\n\n- Kubernetes v1.25+ (PSA is stable\u002FGA)\n- kubectl with cluster-admin access\n- No dependency on external tools - PSA is built into kube-apiserver\n\n## Pod Security Standards\n\n### Privileged Profile\n- **Unrestricted** - No restrictions applied\n- Use case: System-level pods (kube-system, monitoring)\n\n### Baseline Profile\n- **Minimally restrictive** - Prevents known privilege escalation\n- Blocks: privileged containers, hostPID, hostIPC, hostNetwork, hostPorts, certain volume types, adding capabilities beyond runtime defaults\n\n### Restricted Profile\n- **Heavily restricted** - Follows security best practices\n- Requires: non-root, drop ALL capabilities, seccomp RuntimeDefault, read-only root filesystem considerations\n- Blocks: Everything in Baseline plus running as root, privilege escalation, non-approved volume types\n\n## Enforcement Modes\n\n| Mode | Behavior | Use Case |\n|------|----------|----------|\n| enforce | Reject pods violating policy | Production enforcement |\n| audit | Log violations to audit log | Pre-enforcement assessment |\n| warn | Show warnings to user | Developer feedback |\n\n## Implementation\n\n### Apply to Namespace via Labels\n\n```yaml\n# Restricted enforcement with audit and warn\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: production\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: restricted\n    pod-security.kubernetes.io\u002Fenforce-version: v1.28\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: v1.28\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: v1.28\n```\n\n```yaml\n# Baseline enforcement for staging\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: staging\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: baseline\n    pod-security.kubernetes.io\u002Fenforce-version: v1.28\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: v1.28\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: v1.28\n```\n\n```yaml\n# Privileged for system namespaces\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: kube-system\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: privileged\n```\n\n### Apply Labels with kubectl\n\n```bash\n# Set restricted enforcement\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Fenforce=restricted \\\n  pod-security.kubernetes.io\u002Fenforce-version=v1.28 \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted\n\n# Set baseline enforcement\nkubectl label namespace staging \\\n  pod-security.kubernetes.io\u002Fenforce=baseline \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted\n\n# Check current labels\nkubectl get namespace production -o jsonpath='{.metadata.labels}' | jq .\n```\n\n## Dry-Run Testing\n\n```bash\n# Test what would happen with restricted policy on a namespace\nkubectl label --dry-run=server --overwrite namespace staging \\\n  pod-security.kubernetes.io\u002Fenforce=restricted\n\n# Output shows existing pods that would violate the policy\n# Warning: existing pods in namespace \"staging\" violate the new PodSecurity enforce level \"restricted:latest\"\n```\n\n## Cluster-Wide Defaults (AdmissionConfiguration)\n\n```yaml\n# \u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\napiVersion: apiserver.config.k8s.io\u002Fv1\nkind: AdmissionConfiguration\nplugins:\n  - name: PodSecurity\n    configuration:\n      apiVersion: pod-security.admission.config.k8s.io\u002Fv1\n      kind: PodSecurityConfiguration\n      defaults:\n        enforce: baseline\n        enforce-version: latest\n        audit: restricted\n        audit-version: latest\n        warn: restricted\n        warn-version: latest\n      exemptions:\n        usernames: []\n        runtimeClasses: []\n        namespaces:\n          - kube-system\n          - kube-public\n          - kube-node-lease\n          - calico-system\n          - gatekeeper-system\n          - monitoring\n          - falco\n```\n\n### Apply to API Server\n\n```bash\n# Add to kube-apiserver manifests\n# \u002Fetc\u002Fkubernetes\u002Fmanifests\u002Fkube-apiserver.yaml\nspec:\n  containers:\n  - command:\n    - kube-apiserver\n    - --admission-control-config-file=\u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\n    volumeMounts:\n    - name: psa-config\n      mountPath: \u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\n      readOnly: true\n  volumes:\n  - name: psa-config\n    hostPath:\n      path: \u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\n      type: File\n```\n\n## Compliant Pod Examples\n\n### Restricted-Compliant Pod\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: restricted-pod\n  namespace: production\nspec:\n  securityContext:\n    runAsNonRoot: true\n    runAsUser: 1000\n    runAsGroup: 3000\n    fsGroup: 2000\n    seccompProfile:\n      type: RuntimeDefault\n  automountServiceAccountToken: false\n  containers:\n    - name: app\n      image: myregistry\u002Fmyapp:v1.0.0\n      securityContext:\n        allowPrivilegeEscalation: false\n        readOnlyRootFilesystem: true\n        capabilities:\n          drop:\n            - ALL\n      resources:\n        limits:\n          cpu: 500m\n          memory: 256Mi\n        requests:\n          cpu: 100m\n          memory: 128Mi\n      volumeMounts:\n        - name: tmp\n          mountPath: \u002Ftmp\n  volumes:\n    - name: tmp\n      emptyDir: {}\n```\n\n### Baseline-Compliant Pod\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: baseline-pod\n  namespace: staging\nspec:\n  containers:\n    - name: app\n      image: myregistry\u002Fmyapp:v1.0.0\n      securityContext:\n        allowPrivilegeEscalation: false\n      resources:\n        limits:\n          cpu: 500m\n          memory: 256Mi\n```\n\n## Migration from PodSecurityPolicy\n\n### Step 1: Audit Current State\n```bash\n# Check existing PSPs\nkubectl get psp\n\n# Check which service accounts use which PSP\nkubectl get clusterrolebinding -o json | \\\n  jq '.items[] | select(.roleRef.name | startswith(\"psp-\")) | {name: .metadata.name, subjects: .subjects}'\n```\n\n### Step 2: Map PSP to PSA Profiles\n```bash\n# For each namespace, determine required PSA level\nfor ns in $(kubectl get ns -o jsonpath='{.items[*].metadata.name}'); do\n  echo \"Namespace: $ns\"\n  kubectl label --dry-run=server namespace $ns \\\n    pod-security.kubernetes.io\u002Fenforce=restricted 2>&1 | head -5\ndone\n```\n\n### Step 3: Apply PSA Labels (Audit First)\n```bash\n# Start with audit mode\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted\n```\n\n### Step 4: Review and Fix Violations\n```bash\n# Check audit logs for violations\nkubectl get events --field-selector reason=FailedCreate -A\n```\n\n### Step 5: Enable Enforcement\n```bash\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Fenforce=restricted\n```\n\n## Monitoring\n\n```bash\n# Check PSA violations in events\nkubectl get events --all-namespaces --field-selector reason=FailedCreate\n\n# Check audit logs\nkubectl logs -n kube-system kube-apiserver-* | grep \"pod-security.kubernetes.io\"\n\n# List namespace PSA labels\nkubectl get namespaces -L pod-security.kubernetes.io\u002Fenforce\n```\n\n## Best Practices\n\n1. **Start with audit+warn** before enforce to assess impact\n2. **Use dry-run** to test enforcement before applying\n3. **Exempt system namespaces** (kube-system, monitoring) in cluster defaults\n4. **Pin version** (enforce-version) for predictable behavior across upgrades\n5. **Set cluster-wide baseline** as default, then restrict specific namespaces\n6. **Combine with Gatekeeper** for additional custom policies beyond PSA\n7. **Use restricted profile** for all production workloads\n8. **Document exemptions** with clear justification\n",{"name":5,"tags":48,"author":50,"domain":31,"license":15,"version":51,"nist_csf":52,"subdomain":36,"description":7,"mitre_attack":57},[30,40,49,41,42],"psa","mahipal","1.0",[53,54,55,56],"PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01",[58,59,60,61],"T1610","T1611","T1609","T1525","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fimplementing-pod-security-admission-controller",4384,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","https:\u002F\u002Fmahipal.engineer\u002FAnthropic-Cybersecurity-Skills\u002F","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-08-31 12:32:44",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-pod-security-admission-controller",{"tool":78,"command":79},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-pod-security-admission-controller",{"tool":81,"command":82},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-pod-security-admission-controller","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002FSKILL.md",true,[86,92,97,103,107,111,117],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"assets\u002Ftemplate.md","ASSET","资产文件",1290,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002Fassets\u002Ftemplate.md",{"path":93,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002FLICENSE",{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fapi-reference.md","REFERENCE","参考文档",5229,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002Freferences\u002Fapi-reference.md",{"path":104,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fstandards.md",1099,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002Freferences\u002Fstandards.md",{"path":108,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fworkflows.md",1066,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002Freferences\u002Fworkflows.md",{"path":112,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":115,"sourceHtmlUrl":116},"scripts\u002Fagent.py","SCRIPT","脚本",11706,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002Fscripts\u002Fagent.py",{"path":118,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":119,"sourceHtmlUrl":120},"scripts\u002Fprocess.py",5185,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002Fscripts\u002Fprocess.py",[122,149,173,199,225,252],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":131,"publishedAt":43},"01M6AGDM3HJXTKXX15ZZ0ZVCJ3","verifying-build-provenance-with-slsa-sigstore","Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI\u002FCD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fverifying-build-provenance-with-slsa-sigstore\u002FSKILL.md",[128],{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[132,133,134,135,27,31,136,137,33,138,139,140,141,142,143,144,145,146,147,148],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","incident response","identity","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":156,"publishedAt":43},"01M6AGDGBPWYVZ2F11GFKJ4HZ9","validating-tpm-measured-boot-attestation","Verifies TPM 2.0 measured-boot integrity and remote attestation with tpm2-tools -- reading PCRs (tpm2_pcrread), replaying the boot event log, generating and checking signed quotes (tpm2_quote\u002Ftpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware\u002Fkernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-tpm-measured-boot-attestation\u002FSKILL.md",[155],{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},[157,145,158,159,27,160,31,33,161,162,163,164,165,166,167,168,169,170,171,172],"boot","TPM","validating tpm measured boot attestation","policy","verification","ZeRO","firmware","Tools","measured-boot","PCR","integrity","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":181,"publishedAt":43},"01M6AGDCW0Y4FXZ3362GT1941M","validating-backup-integrity-for-recovery","Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped backups for silent corruption or tampering.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[179,180],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},[167,182,183,184,185,31,186,187,161,188,189,190,191,192,193,194,195,196,197,198],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","compliance","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":206,"publishedAt":43},"01M6AGD9GBG2KZ336AE763J3WH","triaging-windows-with-kape","Runs KAPE (Kroll Artifact Parser and Extractor) to collect targeted forensic artifacts (registry hives, $MFT, event logs, prefetch, browser data) via Targets and parse them with Modules wrapping Eric Zimmerman's EZ Tools (PECmd, MFTECmd, RECmd). Use during early incident containment\u002Ftriage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-windows-with-kape\u002FSKILL.md",[205],{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},[207,208,209,31,210,211,212,213,214,215,216,217,218,219,220,221,164,222,223,224],"windows","kape","triaging windows with kape","registry","browser","logs","windows-forensics","dfir","mft","mftecmd","data","prefetch","eric-zimmerman","digital-forensics","SET","collection","pecmd","artifact-collection",{"skillNo":226,"name":227,"nameZh":6,"description":228,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":229,"categories":230,"keywords":232,"publishedAt":43},"01M6AGD5PW5J4EVZM958WD74ZQ","triaging-vulnerabilities-with-ssvc-framework","Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS API), technical impact, automatability, and mission prevalence to output Track\u002FTrack*\u002FAttend\u002FAct decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[231],{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},[233,234,235,31,236,237,238,239,240,241,242,243,244,245,246,247,248,249,250,251],"vulnerabilities","framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","vulnerability-management","risk-management","nessus","qualys","openvas","cvss","remediation","risk","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":253,"name":254,"nameZh":6,"description":255,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":256,"categories":257,"keywords":259,"publishedAt":43},"01M6AGD24TTQQM4CXG69E3B9TJ","triaging-security-incident","Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM\u002FEDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-security-incident\u002FSKILL.md",[258],{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},[27,260,31,261,262,263,264,265,266,267,268,194,269,195,270,271,272,273,274,275],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]