[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFD3FS9RHV5GE81EFQ6PBY":3,"skill-same:01M6AFD3FS9RHV5GE81EFQ6PBY":106},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6AFD3FS9RHV5GE81EFQ6PBY","implementing-semgrep-for-custom-sast-rules",null,"Write custom Semgrep SAST rules in YAML to detect application-specific vulnerabilities, enforce coding standards, and integrate into CI\u002FCD pipelines.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",35884,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-semgrep-for-custom-sast-rules\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,43],"sast","implementing semgrep for custom sast rules","semgrep","cybersecurity","vulnerabilities","pr","code","coding standards","yaml","ci","static-analysis","t1059","t1195","security","custom-rules","code-security","devsecops","2026-11-10 10:12:30",false,"---\nname: implementing-semgrep-for-custom-sast-rules\ndescription: Write custom Semgrep SAST rules in YAML to detect application-specific\n  vulnerabilities, enforce coding standards, and integrate into CI\u002FCD pipelines.\ndomain: cybersecurity\nsubdomain: devsecops\ntags:\n- semgrep\n- sast\n- static-analysis\n- custom-rules\n- devsecops\n- code-security\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- GV.SC-07\n- ID.IM-04\n- PR.PS-04\nmitre_attack:\n- T1195\n- T1554\n- T1059.004\n---\n\n# Implementing Semgrep for Custom SAST Rules\n\n## Overview\n\nSemgrep is an open-source static analysis tool that uses pattern-matching to find bugs, enforce code standards, and detect security vulnerabilities. Custom rules are written in YAML using Semgrep's pattern syntax, making it accessible without requiring compiler knowledge. It supports 30+ languages including Python, JavaScript, Go, Java, and C.\n\n\n## When to Use\n\n- When deploying or configuring implementing semgrep for custom sast rules capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Python 3.8+ or Docker\n- Semgrep CLI installed\n- Target codebase in a supported language\n\n## Installation\n\n```bash\n# Install via pip\npip install semgrep\n\n# Install via Homebrew\nbrew install semgrep\n\n# Run via Docker\ndocker run -v \"${PWD}:\u002Fsrc\" returntocorp\u002Fsemgrep semgrep --config auto \u002Fsrc\n\n# Verify\nsemgrep --version\n```\n\n## Running Semgrep\n\n```bash\n# Auto-detect rules for your code\nsemgrep --config auto .\n\n# Use Semgrep registry rules\nsemgrep --config r\u002Fpython.lang.security\n\n# Use custom rule file\nsemgrep --config my-rules.yaml .\n\n# Use multiple configs\nsemgrep --config auto --config .\u002Fcustom-rules\u002F .\n\n# JSON output\nsemgrep --config auto --json . > results.json\n\n# SARIF output for GitHub\nsemgrep --config auto --sarif . > results.sarif\n\n# Filter by severity\nsemgrep --config auto --severity ERROR .\n```\n\n## Writing Custom Rules\n\n### Basic Pattern Matching\n\n```yaml\n# rules\u002Fsql-injection.yaml\nrules:\n  - id: sql-injection-string-format\n    languages: [python]\n    severity: ERROR\n    message: |\n      Potential SQL injection via string formatting.\n      Use parameterized queries instead.\n    pattern: |\n      cursor.execute(f\"...\" % ...)\n    metadata:\n      cwe: [\"CWE-89\"]\n      owasp: [\"A03:2021\"]\n      category: security\n    fix: |\n      cursor.execute(\"SELECT * FROM users WHERE id = %s\", (user_id,))\n```\n\n### Pattern Operators\n\n```yaml\nrules:\n  - id: hardcoded-secret-in-code\n    languages: [python, javascript, typescript]\n    severity: ERROR\n    message: Hardcoded secret detected in source code\n    patterns:\n      - pattern-either:\n          - pattern: $VAR = \"...\"\n          - pattern: $VAR = '...'\n      - metavariable-regex:\n          metavariable: $VAR\n          regex: (?i)(password|secret|api_key|token|aws_secret)\n      - pattern-not: $VAR = \"\"\n      - pattern-not: $VAR = \"changeme\"\n      - pattern-not: $VAR = \"PLACEHOLDER\"\n    metadata:\n      cwe: [\"CWE-798\"]\n      category: security\n```\n\n### Taint Analysis\n\n```yaml\nrules:\n  - id: xss-taint-tracking\n    languages: [python]\n    severity: ERROR\n    message: User input flows to HTML response without sanitization\n    mode: taint\n    pattern-sources:\n      - pattern: request.args.get(...)\n      - pattern: request.form.get(...)\n      - pattern: request.form[...]\n    pattern-sinks:\n      - pattern: return render_template_string(...)\n      - pattern: Markup(...)\n    pattern-sanitizers:\n      - pattern: bleach.clean(...)\n      - pattern: escape(...)\n    metadata:\n      cwe: [\"CWE-79\"]\n      owasp: [\"A03:2021\"]\n```\n\n### Multiple Language Rule\n\n```yaml\nrules:\n  - id: insecure-random\n    languages: [python, javascript, go, java]\n    severity: WARNING\n    message: |\n      Using insecure random number generator. Use cryptographically\n      secure alternatives for security-sensitive operations.\n    pattern-either:\n      # Python\n      - pattern: random.random()\n      - pattern: random.randint(...)\n      # JavaScript\n      - pattern: Math.random()\n      # Go\n      - pattern: math\u002Frand.Intn(...)\n      # Java\n      - pattern: new java.util.Random()\n    metadata:\n      cwe: [\"CWE-330\"]\n```\n\n### Enforce Coding Standards\n\n```yaml\nrules:\n  - id: require-error-handling\n    languages: [go]\n    severity: WARNING\n    message: Error return value not checked\n    pattern: |\n      $VAR, _ := $FUNC(...)\n    fix: |\n      $VAR, err := $FUNC(...)\n      if err != nil {\n        return fmt.Errorf(\"$FUNC failed: %w\", err)\n      }\n\n  - id: no-console-log-in-production\n    languages: [javascript, typescript]\n    severity: WARNING\n    message: Remove console.log before merging to production\n    pattern: console.log(...)\n    paths:\n      exclude:\n        - \"tests\u002F*\"\n        - \"*.test.*\"\n```\n\n### JWT Security Rules\n\n```yaml\nrules:\n  - id: jwt-none-algorithm\n    languages: [python]\n    severity: ERROR\n    message: JWT decoded without algorithm verification - allows token forgery\n    patterns:\n      - pattern: jwt.decode($TOKEN, ..., algorithms=[\"none\"], ...)\n    metadata:\n      cwe: [\"CWE-347\"]\n\n  - id: jwt-no-verification\n    languages: [python]\n    severity: ERROR\n    message: JWT decoded with verification disabled\n    patterns:\n      - pattern: jwt.decode($TOKEN, ..., options={\"verify_signature\": False}, ...)\n    metadata:\n      cwe: [\"CWE-345\"]\n```\n\n## Rule Testing\n\n```yaml\n# rules\u002Ftest-sql-injection.yaml\nrules:\n  - id: sql-injection-format-string\n    languages: [python]\n    severity: ERROR\n    message: SQL injection via format string\n    pattern: |\n      cursor.execute(f\"...{$VAR}...\")\n\n# Test annotation in test file:\n# test-sql-injection.py\ndef bad_query(user_id):\n    # ruleid: sql-injection-format-string\n    cursor.execute(f\"SELECT * FROM users WHERE id = {user_id}\")\n\ndef good_query(user_id):\n    # ok: sql-injection-format-string\n    cursor.execute(\"SELECT * FROM users WHERE id = %s\", (user_id,))\n```\n\n```bash\n# Run rule tests\nsemgrep --test rules\u002F\n\n# Test specific rule\nsemgrep --config rules\u002Fsql-injection.yaml --test\n```\n\n## CI\u002FCD Integration\n\n### GitHub Actions\n\n```yaml\nname: Semgrep SAST\non: [pull_request]\n\njobs:\n  semgrep:\n    runs-on: ubuntu-latest\n    container:\n      image: returntocorp\u002Fsemgrep\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: Run Semgrep\n        run: |\n          semgrep --config auto \\\n            --config .\u002Fcustom-rules\u002F \\\n            --sarif --output results.sarif \\\n            --severity ERROR \\\n            .\n\n      - name: Upload SARIF\n        uses: github\u002Fcodeql-action\u002Fupload-sarif@v3\n        with:\n          sarif_file: results.sarif\n```\n\n### GitLab CI\n\n```yaml\nsemgrep:\n  stage: test\n  image: returntocorp\u002Fsemgrep\n  script:\n    - semgrep --config auto --config .\u002Fcustom-rules\u002F --json --output semgrep.json .\n  artifacts:\n    reports:\n      sast: semgrep.json\n```\n\n## Configuration File\n\n```yaml\n# .semgrep.yaml\nrules:\n  - id: my-org-rules\n    # ... rules here\n\n# .semgrepignore\ntests\u002F\nnode_modules\u002F\nvendor\u002F\n*.min.js\n```\n\n## Best Practices\n\n1. **Start with auto config** then add custom rules for org-specific patterns\n2. **Test rules** with `# ruleid:` and `# ok:` annotations\n3. **Use taint mode** for data flow vulnerabilities (XSS, SQLi, SSRF)\n4. **Include metadata** (CWE, OWASP) for vulnerability classification\n5. **Provide fix suggestions** with the `fix` key where possible\n6. **Exclude test files** to reduce false positives\n7. **Version control rules** in a shared repository\n8. **Run in CI as a blocking check** for ERROR severity findings\n","# Implementing Semgrep for Custom SAST Rules\n\n## Overview\n\nSemgrep is an open-source static analysis tool that uses pattern-matching to find bugs, enforce code standards, and detect security vulnerabilities. Custom rules are written in YAML using Semgrep's pattern syntax, making it accessible without requiring compiler knowledge. It supports 30+ languages including Python, JavaScript, Go, Java, and C.\n\n\n## When to Use\n\n- When deploying or configuring implementing semgrep for custom sast rules capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Python 3.8+ or Docker\n- Semgrep CLI installed\n- Target codebase in a supported language\n\n## Installation\n\n```bash\n# Install via pip\npip install semgrep\n\n# Install via Homebrew\nbrew install semgrep\n\n# Run via Docker\ndocker run -v \"${PWD}:\u002Fsrc\" returntocorp\u002Fsemgrep semgrep --config auto \u002Fsrc\n\n# Verify\nsemgrep --version\n```\n\n## Running Semgrep\n\n```bash\n# Auto-detect rules for your code\nsemgrep --config auto .\n\n# Use Semgrep registry rules\nsemgrep --config r\u002Fpython.lang.security\n\n# Use custom rule file\nsemgrep --config my-rules.yaml .\n\n# Use multiple configs\nsemgrep --config auto --config .\u002Fcustom-rules\u002F .\n\n# JSON output\nsemgrep --config auto --json . > results.json\n\n# SARIF output for GitHub\nsemgrep --config auto --sarif . > results.sarif\n\n# Filter by severity\nsemgrep --config auto --severity ERROR .\n```\n\n## Writing Custom Rules\n\n### Basic Pattern Matching\n\n```yaml\n# rules\u002Fsql-injection.yaml\nrules:\n  - id: sql-injection-string-format\n    languages: [python]\n    severity: ERROR\n    message: |\n      Potential SQL injection via string formatting.\n      Use parameterized queries instead.\n    pattern: |\n      cursor.execute(f\"...\" % ...)\n    metadata:\n      cwe: [\"CWE-89\"]\n      owasp: [\"A03:2021\"]\n      category: security\n    fix: |\n      cursor.execute(\"SELECT * FROM users WHERE id = %s\", (user_id,))\n```\n\n### Pattern Operators\n\n```yaml\nrules:\n  - id: hardcoded-secret-in-code\n    languages: [python, javascript, typescript]\n    severity: ERROR\n    message: Hardcoded secret detected in source code\n    patterns:\n      - pattern-either:\n          - pattern: $VAR = \"...\"\n          - pattern: $VAR = '...'\n      - metavariable-regex:\n          metavariable: $VAR\n          regex: (?i)(password|secret|api_key|token|aws_secret)\n      - pattern-not: $VAR = \"\"\n      - pattern-not: $VAR = \"changeme\"\n      - pattern-not: $VAR = \"PLACEHOLDER\"\n    metadata:\n      cwe: [\"CWE-798\"]\n      category: security\n```\n\n### Taint Analysis\n\n```yaml\nrules:\n  - id: xss-taint-tracking\n    languages: [python]\n    severity: ERROR\n    message: User input flows to HTML response without sanitization\n    mode: taint\n    pattern-sources:\n      - pattern: request.args.get(...)\n      - pattern: request.form.get(...)\n      - pattern: request.form[...]\n    pattern-sinks:\n      - pattern: return render_template_string(...)\n      - pattern: Markup(...)\n    pattern-sanitizers:\n      - pattern: bleach.clean(...)\n      - pattern: escape(...)\n    metadata:\n      cwe: [\"CWE-79\"]\n      owasp: [\"A03:2021\"]\n```\n\n### Multiple Language Rule\n\n```yaml\nrules:\n  - id: insecure-random\n    languages: [python, javascript, go, java]\n    severity: WARNING\n    message: |\n      Using insecure random number generator. Use cryptographically\n      secure alternatives for security-sensitive operations.\n    pattern-either:\n      # Python\n      - pattern: random.random()\n      - pattern: random.randint(...)\n      # JavaScript\n      - pattern: Math.random()\n      # Go\n      - pattern: math\u002Frand.Intn(...)\n      # Java\n      - pattern: new java.util.Random()\n    metadata:\n      cwe: [\"CWE-330\"]\n```\n\n### Enforce Coding Standards\n\n```yaml\nrules:\n  - id: require-error-handling\n    languages: [go]\n    severity: WARNING\n    message: Error return value not checked\n    pattern: |\n      $VAR, _ := $FUNC(...)\n    fix: |\n      $VAR, err := $FUNC(...)\n      if err != nil {\n        return fmt.Errorf(\"$FUNC failed: %w\", err)\n      }\n\n  - id: no-console-log-in-production\n    languages: [javascript, typescript]\n    severity: WARNING\n    message: Remove console.log before merging to production\n    pattern: console.log(...)\n    paths:\n      exclude:\n        - \"tests\u002F*\"\n        - \"*.test.*\"\n```\n\n### JWT Security Rules\n\n```yaml\nrules:\n  - id: jwt-none-algorithm\n    languages: [python]\n    severity: ERROR\n    message: JWT decoded without algorithm verification - allows token forgery\n    patterns:\n      - pattern: jwt.decode($TOKEN, ..., algorithms=[\"none\"], ...)\n    metadata:\n      cwe: [\"CWE-347\"]\n\n  - id: jwt-no-verification\n    languages: [python]\n    severity: ERROR\n    message: JWT decoded with verification disabled\n    patterns:\n      - pattern: jwt.decode($TOKEN, ..., options={\"verify_signature\": False}, ...)\n    metadata:\n      cwe: [\"CWE-345\"]\n```\n\n## Rule Testing\n\n```yaml\n# rules\u002Ftest-sql-injection.yaml\nrules:\n  - id: sql-injection-format-string\n    languages: [python]\n    severity: ERROR\n    message: SQL injection via format string\n    pattern: |\n      cursor.execute(f\"...{$VAR}...\")\n\n# Test annotation in test file:\n# test-sql-injection.py\ndef bad_query(user_id):\n    # ruleid: sql-injection-format-string\n    cursor.execute(f\"SELECT * FROM users WHERE id = {user_id}\")\n\ndef good_query(user_id):\n    # ok: sql-injection-format-string\n    cursor.execute(\"SELECT * FROM users WHERE id = %s\", (user_id,))\n```\n\n```bash\n# Run rule tests\nsemgrep --test rules\u002F\n\n# Test specific rule\nsemgrep --config rules\u002Fsql-injection.yaml --test\n```\n\n## CI\u002FCD Integration\n\n### GitHub Actions\n\n```yaml\nname: Semgrep SAST\non: [pull_request]\n\njobs:\n  semgrep:\n    runs-on: ubuntu-latest\n    container:\n      image: returntocorp\u002Fsemgrep\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: Run Semgrep\n        run: |\n          semgrep --config auto \\\n            --config .\u002Fcustom-rules\u002F \\\n            --sarif --output results.sarif \\\n            --severity ERROR \\\n            .\n\n      - name: Upload SARIF\n        uses: github\u002Fcodeql-action\u002Fupload-sarif@v3\n        with:\n          sarif_file: results.sarif\n```\n\n### GitLab CI\n\n```yaml\nsemgrep:\n  stage: test\n  image: returntocorp\u002Fsemgrep\n  script:\n    - semgrep --config auto --config .\u002Fcustom-rules\u002F --json --output semgrep.json .\n  artifacts:\n    reports:\n      sast: semgrep.json\n```\n\n## Configuration File\n\n```yaml\n# .semgrep.yaml\nrules:\n  - id: my-org-rules\n    # ... rules here\n\n# .semgrepignore\ntests\u002F\nnode_modules\u002F\nvendor\u002F\n*.min.js\n```\n\n## Best Practices\n\n1. **Start with auto config** then add custom rules for org-specific patterns\n2. **Test rules** with `# ruleid:` and `# ok:` annotations\n3. **Use taint mode** for data flow vulnerabilities (XSS, SQLi, SSRF)\n4. **Include metadata** (CWE, OWASP) for vulnerability classification\n5. **Provide fix suggestions** with the `fix` key where possible\n6. **Exclude test files** to reduce false positives\n7. **Version control rules** in a shared repository\n8. **Run in CI as a blocking check** for ERROR severity findings\n",{"name":5,"tags":49,"author":50,"domain":30,"license":15,"version":51,"nist_csf":52,"subdomain":43,"description":7,"mitre_attack":57},[29,27,37,41,43,42],"mahipal","1.0",[53,54,55,56],"PR.PS-01","GV.SC-07","ID.IM-04","PR.PS-04",[58,59,60],"T1195","T1554","T1059.004","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fimplementing-semgrep-for-custom-sast-rules",4379,"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":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-semgrep-for-custom-sast-rules",{"tool":77,"command":78},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-semgrep-for-custom-sast-rules",{"tool":80,"command":81},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-semgrep-for-custom-sast-rules","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-semgrep-for-custom-sast-rules\u002FSKILL.md",true,[85,90,96,100],{"path":86,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-semgrep-for-custom-sast-rules\u002FLICENSE",{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fapi-reference.md","REFERENCE","参考文档",5264,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-semgrep-for-custom-sast-rules\u002Freferences\u002Fapi-reference.md",{"path":97,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fstandards.md",1162,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-semgrep-for-custom-sast-rules\u002Freferences\u002Fstandards.md",{"path":101,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Fagent.py","SCRIPT","脚本",7808,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-semgrep-for-custom-sast-rules\u002Fscripts\u002Fagent.py",[107,131,155,181,207,233],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":116,"publishedAt":44},"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",[113],{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[117,118,119,120,40,30,121,122,32,33,123,36,124,125,126,39,127,128,129,130],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","incident response","identity","artifacts","supply-chain","pipeline","supply-chain-security","attestation","code-signing","cosign","keyless",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":138,"publishedAt":44},"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",[137],{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},[139,127,140,141,40,142,30,32,143,144,145,146,147,148,149,150,151,152,153,154],"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":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":163,"publishedAt":44},"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",[161,162],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},[149,164,165,166,167,30,168,169,143,170,171,172,173,174,175,176,177,178,179,180],"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":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":188,"publishedAt":44},"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",[187],{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},[189,190,191,30,192,193,194,195,196,197,198,199,200,201,202,203,146,204,205,206],"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":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":214,"publishedAt":44},"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",[213],{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},[31,215,216,30,217,218,219,220,221,222,223,224,225,226,227,228,229,230,231,232],"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":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":237,"categories":238,"keywords":240,"publishedAt":44},"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",[239],{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},[40,241,30,242,243,244,245,246,247,248,249,176,250,177,251,252,253,254,255,256],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]