[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71CKV0A0EKB2BY4ZXQBBSNC":3,"skill-same:01M71CKV0A0EKB2BY4ZXQBBSNC":99},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":72,"commitSha":73,"skillDirectory":74,"forksCount":14,"repositoryHtmlUrl":75,"repositoryHomepageUrl":6,"ownerHtmlUrl":76,"ownerBlogUrl":6,"ownerDescription":77,"updatedAt":78,"install":79,"resources":92},"01M71CKV0A0EKB2BY4ZXQBBSNC","kubernetes-hardening-kubesecmanifest-detect",null,"Perform security risk analysis on Kubernetes resource manifests using Kubesec to identify misconfigurations, privilege escalation risks, and deviations from security best practices.","DCx7C5\u002Fai-marketplace","DCx7C5","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42419559?v=4","01M71C01G2AZV3NTNGWAWSHJPP","DC","01M71C01GQW6G50S2BYMS7PP3E",0,"MIT","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fkubernetes\u002Fhardening\u002Fkubesecmanifest\u002Fdetect\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"kubernetes","detect","kubernetes hardening kubesecmanifest detect","hardening","kubernetes hardening","security","devsecops","read","privilege escalation","scanning","container-security","de","analysis","Bash","manifests","cybersecurity","ci","static","cm","static-analysis","2026-11-10 10:12:30",false,"---\nname: kubernetes-hardening-kubesecmanifest-detect\ndescription: Perform security risk analysis on Kubernetes resource manifests using Kubesec to identify misconfigurations, privilege escalation risks, and deviations from security best practices.\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- kubesec\n- kubernetes\n- manifest-scanning\n- security-scanning\n- devsecops\n- misconfiguration\n- static-analysis\n- ci-cd\nnist_csf:\n- PR.PS-01\n- PR.IR-01\n- ID.AM-08\n- DE.CM-01\nmodel: sonnet\nmaxTurns: 20\ntools: [Read, Bash, Glob, Grep]\nmitre_attack:\n- T1046\n- T1610\ncwe:\n- CWE-16\ncapec: []\n---\n\n# Scanning Kubernetes Manifests with Kubesec\n\n## Overview\n\nKubesec is an open-source security risk analysis tool developed by ControlPlane that inspects Kubernetes resource manifests for common exploitable risks such as privilege escalation, writable host mounts, and excessive capabilities. It assigns a numerical security score to each resource and provides actionable recommendations for hardening. Kubesec can be used as a CLI binary, Docker container, kubectl plugin, admission webhook, or REST API endpoint.\n\n\n## When to Use\n\n- When conducting security assessments that involve scanning kubernetes manifests with kubesec\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Kubernetes manifest files (YAML\u002FJSON) for Deployments, Pods, DaemonSets, StatefulSets\n- Docker or Go runtime for local installation\n- kubectl access for scanning live cluster resources\n- CI\u002FCD pipeline access for automated scanning integration\n\n## Core Concepts\n\n### Security Scoring System\n\nKubesec assigns a score to each Kubernetes resource based on security checks:\n\n- **Positive scores**: Awarded for security-enhancing configurations (readOnlyRootFilesystem, runAsNonRoot)\n- **Zero or negative scores**: Indicate missing security controls or dangerous configurations\n- **Critical advisories**: Flagged configurations that represent immediate security risks\n\n### Check Categories\n\n1. **Privilege Controls**: Checks for privileged containers, host PID\u002Fnetwork access, root execution\n2. **Capabilities**: Identifies excessive Linux capabilities (SYS_ADMIN, NET_RAW)\n3. **Volume Mounts**: Detects dangerous host path mounts and writable sensitive paths\n4. **Resource Limits**: Validates presence of CPU\u002Fmemory resource constraints\n5. **Security Context**: Verifies seccomp profiles, AppArmor annotations, SELinux contexts\n\n## Installation\n\n### Binary Installation\n\n```bash\n# Linux\u002FmacOS\ncurl -sSL https:\u002F\u002Fgithub.com\u002Fcontrolplaneio\u002Fkubesec\u002Freleases\u002Flatest\u002Fdownload\u002Fkubesec_linux_amd64.tar.gz | \\\n  tar xz -C \u002Fusr\u002Flocal\u002Fbin\u002F kubesec\n\n# Verify installation\nkubesec version\n```\n\n### Docker Installation\n\n```bash\ndocker pull kubesec\u002Fkubesec:v2\n\n# Scan a manifest file\ndocker run -i kubesec\u002Fkubesec:v2 scan \u002Fdev\u002Fstdin \u003C deployment.yaml\n```\n\n### kubectl Plugin\n\n```bash\nkubectl krew install kubesec-scan\nkubectl kubesec-scan pod mypod -n default\n```\n\n## Practical Scanning\n\n### Scanning a Single Manifest\n\n```bash\n# Scan a deployment manifest\nkubesec scan deployment.yaml\n\n# Scan with JSON output\nkubesec scan -o json deployment.yaml\n\n# Scan from stdin\ncat pod.yaml | kubesec scan -\n```\n\n### Sample Output\n\n```json\n[\n  {\n    \"object\": \"Pod\u002Fweb-app.default\",\n    \"valid\": true,\n    \"fileName\": \"pod.yaml\",\n    \"message\": \"Passed with a score of 3 points\",\n    \"score\": 3,\n    \"scoring\": {\n      \"passed\": [\n        {\n          \"id\": \"ReadOnlyRootFilesystem\",\n          \"selector\": \"containers[] .securityContext .readOnlyRootFilesystem == true\",\n          \"reason\": \"An immutable root filesystem prevents applications from writing to their local disk\",\n          \"points\": 1\n        },\n        {\n          \"id\": \"RunAsNonRoot\",\n          \"selector\": \"containers[] .securityContext .runAsNonRoot == true\",\n          \"reason\": \"Force the running image to run as a non-root user\",\n          \"points\": 1\n        },\n        {\n          \"id\": \"LimitsCPU\",\n          \"selector\": \"containers[] .resources .limits .cpu\",\n          \"reason\": \"Enforcing CPU limits prevents DOS via resource exhaustion\",\n          \"points\": 1\n        }\n      ],\n      \"advise\": [\n        {\n          \"id\": \"ApparmorAny\",\n          \"selector\": \"metadata .annotations .\\\"container.apparmor.security.beta.kubernetes.io\u002Fnginx\\\"\",\n          \"reason\": \"Well defined AppArmor policies reduce the attack surface of the container\",\n          \"points\": 3\n        },\n        {\n          \"id\": \"ServiceAccountName\",\n          \"selector\": \".spec .serviceAccountName\",\n          \"reason\": \"Service accounts restrict Kubernetes API access and should be configured\",\n          \"points\": 3\n        }\n      ]\n    }\n  }\n]\n```\n\n### Scanning Multiple Resources\n\n```bash\n# Scan all YAML files in a directory\nfor file in manifests\u002F*.yaml; do\n  echo \"=== Scanning $file ===\"\n  kubesec scan \"$file\"\ndone\n\n# Scan multi-document YAML\nkubesec scan multi-resource.yaml\n```\n\n### Using the HTTP API\n\n```bash\n# Scan via the public API\ncurl -sSX POST --data-binary @deployment.yaml \\\n  https:\u002F\u002Fv2.kubesec.io\u002Fscan\n\n# Run a local API server\nkubesec http --port 8080 &\n\n# Scan against local server\ncurl -sSX POST --data-binary @deployment.yaml \\\n  http:\u002F\u002Flocalhost:8080\u002Fscan\n```\n\n## CI\u002FCD Integration\n\n### GitHub Actions\n\n```yaml\nname: kubernetes-hardening-kubesecmanifest\non: [pull_request]\njobs:\n  kubesec:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - name: Install Kubesec\n        run: |\n          curl -sSL https:\u002F\u002Fgithub.com\u002Fcontrolplaneio\u002Fkubesec\u002Freleases\u002Flatest\u002Fdownload\u002Fkubesec_linux_amd64.tar.gz | \\\n            tar xz -C \u002Fusr\u002Flocal\u002Fbin\u002F kubesec\n      - name: Scan Manifests\n        run: |\n          FAIL=0\n          for file in k8s\u002F*.yaml; do\n            SCORE=$(kubesec scan \"$file\" | jq '.[0].score')\n            echo \"$file: score=$SCORE\"\n            if [ \"$SCORE\" -lt 0 ]; then\n              echo \"FAIL: $file has critical issues (score: $SCORE)\"\n              FAIL=1\n            fi\n          done\n          exit $FAIL\n```\n\n### GitLab CI\n\n```yaml\nkubesec-scan:\n  stage: security\n  image: kubesec\u002Fkubesec:v2\n  script:\n    - |\n      for file in k8s\u002F*.yaml; do\n        kubesec scan \"$file\" > \u002Ftmp\u002Fresult.json\n        SCORE=$(cat \u002Ftmp\u002Fresult.json | jq '.[0].score')\n        if [ \"$SCORE\" -lt 0 ]; then\n          echo \"CRITICAL: $file scored $SCORE\"\n          cat \u002Ftmp\u002Fresult.json | jq '.[0].scoring.critical'\n          exit 1\n        fi\n      done\n  artifacts:\n    paths:\n      - kubesec-results\u002F\n```\n\n### Admission Webhook\n\nDeploy Kubesec as a ValidatingWebhookConfiguration to reject insecure manifests at deploy time:\n\n```yaml\napiVersion: admissionregistration.k8s.io\u002Fv1\nkind: ValidatingWebhookConfiguration\nmetadata:\n  name: kubesec-webhook\nwebhooks:\n  - name: kubesec.controlplane.io\n    rules:\n      - apiGroups: [\"\"]\n        apiVersions: [\"v1\"]\n        operations: [\"CREATE\", \"UPDATE\"]\n        resources: [\"pods\"]\n      - apiGroups: [\"apps\"]\n        apiVersions: [\"v1\"]\n        operations: [\"CREATE\", \"UPDATE\"]\n        resources: [\"deployments\", \"daemonsets\", \"statefulsets\"]\n    clientConfig:\n      service:\n        name: kubesec-webhook\n        namespace: kube-system\n        path: \u002Fscan\n    failurePolicy: Fail\n    sideEffects: None\n    admissionReviewVersions: [\"v1\"]\n```\n\n## Security Checks Reference\n\n### Critical Checks (Negative Score)\n\n| Check | Selector | Risk |\n|-------|----------|------|\n| Privileged | `securityContext.privileged == true` | Full host access |\n| HostPID | `spec.hostPID == true` | Process namespace escape |\n| HostNetwork | `spec.hostNetwork == true` | Network namespace escape |\n| SYS_ADMIN | `capabilities.add contains SYS_ADMIN` | Near-root capability |\n\n### Best Practice Checks (Positive Score)\n\n| Check | Points | Description |\n|-------|--------|-------------|\n| ReadOnlyRootFilesystem | +1 | Prevents filesystem writes |\n| RunAsNonRoot | +1 | Non-root process execution |\n| RunAsUser > 10000 | +1 | High UID reduces collision risk |\n| LimitsCPU | +1 | Prevents CPU resource exhaustion |\n| LimitsMemory | +1 | Prevents memory resource exhaustion |\n| RequestsCPU | +1 | Ensures scheduler resource awareness |\n| ServiceAccountName | +3 | Explicit service account |\n| AppArmor annotation | +3 | Kernel-level MAC enforcement |\n| Seccomp profile | +4 | Syscall filtering |\n\n## References\n\n- [Kubesec GitHub Repository](https:\u002F\u002Fgithub.com\u002Fcontrolplaneio\u002Fkubesec)\n- [Kubesec Online Scanner](https:\u002F\u002Fkubesec.io\u002F)\n- [ControlPlane Security Tools](https:\u002F\u002Fcontrolplane.io\u002F)\n- [CIS Kubernetes Benchmark](https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fkubernetes)\n- [Kubernetes Pod Security Standards](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Fconcepts\u002Fsecurity\u002Fpod-security-standards\u002F)\n","# Scanning Kubernetes Manifests with Kubesec\n\n## Overview\n\nKubesec is an open-source security risk analysis tool developed by ControlPlane that inspects Kubernetes resource manifests for common exploitable risks such as privilege escalation, writable host mounts, and excessive capabilities. It assigns a numerical security score to each resource and provides actionable recommendations for hardening. Kubesec can be used as a CLI binary, Docker container, kubectl plugin, admission webhook, or REST API endpoint.\n\n\n## When to Use\n\n- When conducting security assessments that involve scanning kubernetes manifests with kubesec\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Kubernetes manifest files (YAML\u002FJSON) for Deployments, Pods, DaemonSets, StatefulSets\n- Docker or Go runtime for local installation\n- kubectl access for scanning live cluster resources\n- CI\u002FCD pipeline access for automated scanning integration\n\n## Core Concepts\n\n### Security Scoring System\n\nKubesec assigns a score to each Kubernetes resource based on security checks:\n\n- **Positive scores**: Awarded for security-enhancing configurations (readOnlyRootFilesystem, runAsNonRoot)\n- **Zero or negative scores**: Indicate missing security controls or dangerous configurations\n- **Critical advisories**: Flagged configurations that represent immediate security risks\n\n### Check Categories\n\n1. **Privilege Controls**: Checks for privileged containers, host PID\u002Fnetwork access, root execution\n2. **Capabilities**: Identifies excessive Linux capabilities (SYS_ADMIN, NET_RAW)\n3. **Volume Mounts**: Detects dangerous host path mounts and writable sensitive paths\n4. **Resource Limits**: Validates presence of CPU\u002Fmemory resource constraints\n5. **Security Context**: Verifies seccomp profiles, AppArmor annotations, SELinux contexts\n\n## Installation\n\n### Binary Installation\n\n```bash\n# Linux\u002FmacOS\ncurl -sSL https:\u002F\u002Fgithub.com\u002Fcontrolplaneio\u002Fkubesec\u002Freleases\u002Flatest\u002Fdownload\u002Fkubesec_linux_amd64.tar.gz | \\\n  tar xz -C \u002Fusr\u002Flocal\u002Fbin\u002F kubesec\n\n# Verify installation\nkubesec version\n```\n\n### Docker Installation\n\n```bash\ndocker pull kubesec\u002Fkubesec:v2\n\n# Scan a manifest file\ndocker run -i kubesec\u002Fkubesec:v2 scan \u002Fdev\u002Fstdin \u003C deployment.yaml\n```\n\n### kubectl Plugin\n\n```bash\nkubectl krew install kubesec-scan\nkubectl kubesec-scan pod mypod -n default\n```\n\n## Practical Scanning\n\n### Scanning a Single Manifest\n\n```bash\n# Scan a deployment manifest\nkubesec scan deployment.yaml\n\n# Scan with JSON output\nkubesec scan -o json deployment.yaml\n\n# Scan from stdin\ncat pod.yaml | kubesec scan -\n```\n\n### Sample Output\n\n```json\n[\n  {\n    \"object\": \"Pod\u002Fweb-app.default\",\n    \"valid\": true,\n    \"fileName\": \"pod.yaml\",\n    \"message\": \"Passed with a score of 3 points\",\n    \"score\": 3,\n    \"scoring\": {\n      \"passed\": [\n        {\n          \"id\": \"ReadOnlyRootFilesystem\",\n          \"selector\": \"containers[] .securityContext .readOnlyRootFilesystem == true\",\n          \"reason\": \"An immutable root filesystem prevents applications from writing to their local disk\",\n          \"points\": 1\n        },\n        {\n          \"id\": \"RunAsNonRoot\",\n          \"selector\": \"containers[] .securityContext .runAsNonRoot == true\",\n          \"reason\": \"Force the running image to run as a non-root user\",\n          \"points\": 1\n        },\n        {\n          \"id\": \"LimitsCPU\",\n          \"selector\": \"containers[] .resources .limits .cpu\",\n          \"reason\": \"Enforcing CPU limits prevents DOS via resource exhaustion\",\n          \"points\": 1\n        }\n      ],\n      \"advise\": [\n        {\n          \"id\": \"ApparmorAny\",\n          \"selector\": \"metadata .annotations .\\\"container.apparmor.security.beta.kubernetes.io\u002Fnginx\\\"\",\n          \"reason\": \"Well defined AppArmor policies reduce the attack surface of the container\",\n          \"points\": 3\n        },\n        {\n          \"id\": \"ServiceAccountName\",\n          \"selector\": \".spec .serviceAccountName\",\n          \"reason\": \"Service accounts restrict Kubernetes API access and should be configured\",\n          \"points\": 3\n        }\n      ]\n    }\n  }\n]\n```\n\n### Scanning Multiple Resources\n\n```bash\n# Scan all YAML files in a directory\nfor file in manifests\u002F*.yaml; do\n  echo \"=== Scanning $file ===\"\n  kubesec scan \"$file\"\ndone\n\n# Scan multi-document YAML\nkubesec scan multi-resource.yaml\n```\n\n### Using the HTTP API\n\n```bash\n# Scan via the public API\ncurl -sSX POST --data-binary @deployment.yaml \\\n  https:\u002F\u002Fv2.kubesec.io\u002Fscan\n\n# Run a local API server\nkubesec http --port 8080 &\n\n# Scan against local server\ncurl -sSX POST --data-binary @deployment.yaml \\\n  http:\u002F\u002Flocalhost:8080\u002Fscan\n```\n\n## CI\u002FCD Integration\n\n### GitHub Actions\n\n```yaml\nname: kubernetes-hardening-kubesecmanifest\non: [pull_request]\njobs:\n  kubesec:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - name: Install Kubesec\n        run: |\n          curl -sSL https:\u002F\u002Fgithub.com\u002Fcontrolplaneio\u002Fkubesec\u002Freleases\u002Flatest\u002Fdownload\u002Fkubesec_linux_amd64.tar.gz | \\\n            tar xz -C \u002Fusr\u002Flocal\u002Fbin\u002F kubesec\n      - name: Scan Manifests\n        run: |\n          FAIL=0\n          for file in k8s\u002F*.yaml; do\n            SCORE=$(kubesec scan \"$file\" | jq '.[0].score')\n            echo \"$file: score=$SCORE\"\n            if [ \"$SCORE\" -lt 0 ]; then\n              echo \"FAIL: $file has critical issues (score: $SCORE)\"\n              FAIL=1\n            fi\n          done\n          exit $FAIL\n```\n\n### GitLab CI\n\n```yaml\nkubesec-scan:\n  stage: security\n  image: kubesec\u002Fkubesec:v2\n  script:\n    - |\n      for file in k8s\u002F*.yaml; do\n        kubesec scan \"$file\" > \u002Ftmp\u002Fresult.json\n        SCORE=$(cat \u002Ftmp\u002Fresult.json | jq '.[0].score')\n        if [ \"$SCORE\" -lt 0 ]; then\n          echo \"CRITICAL: $file scored $SCORE\"\n          cat \u002Ftmp\u002Fresult.json | jq '.[0].scoring.critical'\n          exit 1\n        fi\n      done\n  artifacts:\n    paths:\n      - kubesec-results\u002F\n```\n\n### Admission Webhook\n\nDeploy Kubesec as a ValidatingWebhookConfiguration to reject insecure manifests at deploy time:\n\n```yaml\napiVersion: admissionregistration.k8s.io\u002Fv1\nkind: ValidatingWebhookConfiguration\nmetadata:\n  name: kubesec-webhook\nwebhooks:\n  - name: kubesec.controlplane.io\n    rules:\n      - apiGroups: [\"\"]\n        apiVersions: [\"v1\"]\n        operations: [\"CREATE\", \"UPDATE\"]\n        resources: [\"pods\"]\n      - apiGroups: [\"apps\"]\n        apiVersions: [\"v1\"]\n        operations: [\"CREATE\", \"UPDATE\"]\n        resources: [\"deployments\", \"daemonsets\", \"statefulsets\"]\n    clientConfig:\n      service:\n        name: kubesec-webhook\n        namespace: kube-system\n        path: \u002Fscan\n    failurePolicy: Fail\n    sideEffects: None\n    admissionReviewVersions: [\"v1\"]\n```\n\n## Security Checks Reference\n\n### Critical Checks (Negative Score)\n\n| Check | Selector | Risk |\n|-------|----------|------|\n| Privileged | `securityContext.privileged == true` | Full host access |\n| HostPID | `spec.hostPID == true` | Process namespace escape |\n| HostNetwork | `spec.hostNetwork == true` | Network namespace escape |\n| SYS_ADMIN | `capabilities.add contains SYS_ADMIN` | Near-root capability |\n\n### Best Practice Checks (Positive Score)\n\n| Check | Points | Description |\n|-------|--------|-------------|\n| ReadOnlyRootFilesystem | +1 | Prevents filesystem writes |\n| RunAsNonRoot | +1 | Non-root process execution |\n| RunAsUser > 10000 | +1 | High UID reduces collision risk |\n| LimitsCPU | +1 | Prevents CPU resource exhaustion |\n| LimitsMemory | +1 | Prevents memory resource exhaustion |\n| RequestsCPU | +1 | Ensures scheduler resource awareness |\n| ServiceAccountName | +3 | Explicit service account |\n| AppArmor annotation | +3 | Kernel-level MAC enforcement |\n| Seccomp profile | +4 | Syscall filtering |\n\n## References\n\n- [Kubesec GitHub Repository](https:\u002F\u002Fgithub.com\u002Fcontrolplaneio\u002Fkubesec)\n- [Kubesec Online Scanner](https:\u002F\u002Fkubesec.io\u002F)\n- [ControlPlane Security Tools](https:\u002F\u002Fcontrolplane.io\u002F)\n- [CIS Kubernetes Benchmark](https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fkubernetes)\n- [Kubernetes Pod Security Standards](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Fconcepts\u002Fsecurity\u002Fpod-security-standards\u002F)\n",{"cwe":49,"name":5,"tags":51,"capec":57,"model":58,"tools":59,"domain":39,"maxTurns":63,"nist_csf":64,"subdomain":34,"description":7,"mitre_attack":69},[50],"CWE-16",[52,24,53,54,30,55,43,56],"kubesec","manifest-scanning","security-scanning","misconfiguration","ci-cd",[],"sonnet",[60,37,61,62],"Read","Glob","Grep",20,[65,66,67,68],"PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01",[70,71],"T1046","T1610","main","a91f1293287ffa9f4f1b8f486cd6e835a1568c84","skills\u002Fcloud\u002Fkubernetes\u002Fhardening\u002Fkubesecmanifest\u002Fdetect","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace","https:\u002F\u002Fgithub.com\u002FDCx7C5","#Python","2026-09-01 11:21:00",{"source":8,"skillName":5,"commands":80,"prompt":90,"zipAvailable":91},[81,84,87],{"tool":82,"command":83},"npx","npx skills add DCx7C5\u002Fai-marketplace --skill kubernetes-hardening-kubesecmanifest-detect",{"tool":85,"command":86},"bunx","bunx skills add DCx7C5\u002Fai-marketplace --skill kubernetes-hardening-kubesecmanifest-detect",{"tool":88,"command":89},"pnpm","pnpm dlx skills add DCx7C5\u002Fai-marketplace --skill kubernetes-hardening-kubesecmanifest-detect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fkubernetes\u002Fhardening\u002Fkubesecmanifest\u002Fdetect\u002FSKILL.md",true,[93],{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"index.json","REFERENCE","参考文档",721,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fkubernetes\u002Fhardening\u002Fkubesecmanifest\u002Fdetect\u002Findex.json",[100,110,132,152,173,195],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":104,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":109},"01M73MDK3NT5XHNYTQ5P5172V9","devel-jb-algorithmic-art","- Embed algorithms inline in the HTML artifact (don't create separate .","Apache-2.0","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fdevel-jb-algorithmic-art\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fdevel-jb-algorithmic-art\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":44},"01M71HAPZ01KQ30RKTB0FFSQ05","services-wmi-persistence-detect","Detect WMI event subscription persistence by enumerating ActiveScriptEventConsumer, CommandLineEventConsumer, and permanent subscriptions in the WMI repository.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fpersistence\u002Fdetect\u002FSKILL.md",[],[117,25,118,119,120,121,122,39,123,124,125,126,127,128,129,130,131,42,35],"services","services wmi persistence detect","wmi","persistence","process-forensics","process","forensics","t1546.003","event-subscription","subscription","repository","commandline-consumer","subscriptions","event","activescript",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":44},"01M71HAK6JTTTS229T17WJMMCG","services-wmi-exec-exploit","Perform lateral movement across Windows networks using WMI-based remote execution techniques including Impacket wmiexec.py, CrackMapExec, and native WMI commands for stealthy post-exploitation during red team engagements.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fexec\u002Fexploit\u002FSKILL.md",[],[139,119,140,117,141,142,37,36,143,39,144,145,146,147,148,31,149,150,35,151],"exec","services wmi exec exploit","exploit","across","team","traffic","remote","crackmapexec","Impacket","lateral-movement","lateral movement","command","native",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":44},"01M71HAG6MHKNQV8KDZKMT4886","registry-artifact-extract","Extract and analyze Windows Registry hives to uncover user activity, installed software, autostart entries, and evidence of system compromise.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fregistry\u002Fartifact\u002Fextract\u002FSKILL.md",[],[159,160,161,162,163,58,164,165,166,167,31,35,168,169,36,170,37,39,171,172],"extract","registry artifact extract","registry","artifact","digital-forensics","regripper","windows-registry","evidence-collection","software","uncover","analyze","collection","artifact-analysis","activity",{"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":179,"publishedAt":44},"01M71HACR4A8XTWTTSXK4124AA","processes-token-impersonate-detect","Detect Windows token impersonation and privilege abuse including SeImpersonatePrivilege exploitation via Potato attacks and token stealing techniques.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Ftoken\u002Fimpersonate\u002Fdetect\u002FSKILL.md",[],[180,181,182,25,39,183,42,184,185,186,121,35,187,188,189,190,191,192,193,194],"processes","token","processes token impersonate detect","techniques","escalation","windows","attacks","via","impersonation","potato","exploitation","printspoofer","token-impersonation","seimpersonate","privilege-escalation",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":201,"publishedAt":44},"01M71HAABSB4Z6QFSXEG00R4RK","processes-thread-injection-detect","Detect Windows thread injection techniques including CreateRemoteThread, QueueUserAPC, NtCreateThreadEx, and thread hijacking via process memory analysis.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fthread\u002Finjection\u002Fdetect\u002FSKILL.md",[],[202,180,203,25,204,205,122,35,187,206,207,208,36,121,39,183,209,42,210,185],"thread","injection","processes thread injection detect","thread-injection","nt-api","apc-injection","api","process-injection","memory"]