[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFG8WD4DS37QHZ81VWVZKV":3,"skill-same:01M6AFG8WD4DS37QHZ81VWVZKV":146},{"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":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":75,"commitSha":76,"skillDirectory":77,"forksCount":78,"repositoryHtmlUrl":79,"repositoryHomepageUrl":80,"ownerHtmlUrl":81,"ownerBlogUrl":82,"ownerDescription":83,"updatedAt":84,"install":85,"resources":98},"01M6AFG8WD4DS37QHZ81VWVZKV","integrating-dast-with-owasp-zap-in-pipeline",null,"Integrates OWASP ZAP (Zed Attack Proxy) into GitHub Actions and GitLab CI pipelines, covering baseline, full, and API scan configuration against running applications, ZAP finding interpretation, scan policy tuning, and DAST quality gates. Use when testing running web apps or REST\u002FGraphQL APIs for XSS, SQLi, CSRF, and auth\u002Fauthz flaws, or when SAST alone is insufficient and runtime DAST is required for compliance or release gating.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",36078,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"integrating dast with owasp zap in pipeline","owasp","dast","pipeline","github actions","owasp-zap","tuning","t1195","xss","sqli","testing","ci","actions","release","gitlab","interpretation","secure","auth","cybersecurity","devsecops","2026-11-10 10:12:30",false,"---\nname: integrating-dast-with-owasp-zap-in-pipeline\ndescription: Integrates OWASP ZAP (Zed Attack Proxy) into GitHub Actions and GitLab CI pipelines, covering baseline, full, and API scan configuration against running applications, ZAP finding interpretation, scan policy tuning, and DAST quality gates. Use when testing running web apps or REST\u002FGraphQL APIs for XSS, SQLi, CSRF, and auth\u002Fauthz flaws, or when SAST alone is insufficient and runtime DAST is required for compliance or release gating.\ndomain: cybersecurity\nsubdomain: devsecops\ntags:\n- devsecops\n- cicd\n- dast\n- owasp-zap\n- dynamic-testing\n- secure-sdlc\nversion: 1.0.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# Integrating DAST with OWASP ZAP in Pipeline\n\n## When to Use\n\n- When testing running web applications for vulnerabilities like XSS, SQLi, CSRF, and misconfigurations\n- When SAST alone is insufficient and runtime behavior testing is required\n- When compliance mandates dynamic security testing of web applications before production\n- When testing APIs (REST\u002FGraphQL) for authentication, authorization, and injection flaws\n- When establishing continuous DAST scanning in staging environments before production deployment\n\n**Do not use** for scanning source code (use SAST), for scanning dependencies (use SCA), or for infrastructure configuration scanning (use IaC scanning tools).\n\n## Prerequisites\n\n- OWASP ZAP Docker image or installed locally (zaproxy\u002Fzap-stable or zaproxy\u002Faction-*)\n- Running target application accessible from the CI\u002FCD runner (staging URL or Docker service)\n- ZAP scan rules configuration (optional, for tuning)\n- OpenAPI\u002FSwagger specification for API scanning (optional)\n\n## Workflow\n\n### Step 1: Configure ZAP Baseline Scan in GitHub Actions\n\n```yaml\n# .github\u002Fworkflows\u002Fdast-scan.yml\nname: DAST Security Scan\n\non:\n  deployment_status:\n  workflow_dispatch:\n    inputs:\n      target_url:\n        description: 'Target URL to scan'\n        required: true\n\njobs:\n  zap-baseline:\n    name: ZAP Baseline Scan\n    runs-on: ubuntu-latest\n    services:\n      webapp:\n        image: ${{ github.repository }}:${{ github.sha }}\n        ports:\n          - 8080:8080\n        options: --health-cmd=\"curl -f http:\u002F\u002Flocalhost:8080\u002Fhealth\" --health-interval=10s --health-timeout=5s --health-retries=5\n\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: ZAP Baseline Scan\n        uses: zaproxy\u002Faction-baseline@v0.12.0\n        with:\n          target: 'http:\u002F\u002Fwebapp:8080'\n          rules_file_name: '.zap\u002Frules.tsv'\n          cmd_options: '-a -j'\n          allow_issue_writing: false\n\n      - name: Upload ZAP Report\n        if: always()\n        uses: actions\u002Fupload-artifact@v4\n        with:\n          name: zap-baseline-report\n          path: report_html.html\n```\n\n### Step 2: Configure ZAP Full Scan for Comprehensive Testing\n\n```yaml\n  zap-full-scan:\n    name: ZAP Full Scan\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: ZAP Full Scan\n        uses: zaproxy\u002Faction-full-scan@v0.12.0\n        with:\n          target: ${{ github.event.inputs.target_url || 'https:\u002F\u002Fstaging.example.com' }}\n          rules_file_name: '.zap\u002Frules.tsv'\n          cmd_options: '-a -j -T 60'\n\n      - name: Upload Reports\n        if: always()\n        uses: actions\u002Fupload-artifact@v4\n        with:\n          name: zap-full-report\n          path: |\n            report_html.html\n            report_json.json\n```\n\n### Step 3: Configure API Scan with OpenAPI Specification\n\n```yaml\n  zap-api-scan:\n    name: ZAP API Scan\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: ZAP API Scan\n        uses: zaproxy\u002Faction-api-scan@v0.12.0\n        with:\n          target: 'https:\u002F\u002Fstaging.example.com\u002Fapi\u002Fopenapi.json'\n          format: openapi\n          rules_file_name: '.zap\u002Fapi-rules.tsv'\n          cmd_options: '-a -j'\n```\n\n### Step 4: Configure ZAP Scan Rules\n\n```tsv\n# .zap\u002Frules.tsv\n# Rule ID\tAction (IGNORE\u002FWARN\u002FFAIL)\tDescription\n10003\tIGNORE\t# Vulnerable JS Library (handled by SCA)\n10015\tWARN\t# Incomplete or No Cache-control Header\n10021\tFAIL\t# X-Content-Type-Options Missing\n10035\tFAIL\t# Strict-Transport-Security Missing\n10038\tFAIL\t# Content Security Policy Missing\n10098\tIGNORE\t# Cross-Domain Misconfiguration (CDN)\n40012\tFAIL\t# Cross Site Scripting (Reflected)\n40014\tFAIL\t# Cross Site Scripting (Persistent)\n40018\tFAIL\t# SQL Injection\n40019\tFAIL\t# SQL Injection (MySQL)\n40032\tFAIL\t# .htaccess Information Leak\n90033\tFAIL\t# Loosely Scoped Cookie\n```\n\n### Step 5: Run ZAP with Docker Compose for Local Testing\n\n```yaml\n# docker-compose.zap.yml\nversion: '3.8'\nservices:\n  webapp:\n    build: .\n    ports:\n      - \"8080:8080\"\n    healthcheck:\n      test: [\"CMD\", \"curl\", \"-f\", \"http:\u002F\u002Flocalhost:8080\u002Fhealth\"]\n      interval: 10s\n      retries: 5\n\n  zap:\n    image: zaproxy\u002Fzap-stable:latest\n    depends_on:\n      webapp:\n        condition: service_healthy\n    command: >\n      zap-baseline.py\n        -t http:\u002F\u002Fwebapp:8080\n        -r \u002Fzap\u002Fwrk\u002Freport.html\n        -J \u002Fzap\u002Fwrk\u002Freport.json\n        -c \u002Fzap\u002Fwrk\u002Frules.tsv\n        -I\n    volumes:\n      - .\u002Fzap-reports:\u002Fzap\u002Fwrk\n      - .\u002F.zap\u002Frules.tsv:\u002Fzap\u002Fwrk\u002Frules.tsv\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| DAST | Dynamic Application Security Testing — tests running applications by sending requests and analyzing responses |\n| Baseline Scan | Quick passive scan that spiders the application without active attacks, suitable for CI\u002FCD |\n| Full Scan | Active scan including attack payloads for XSS, SQLi, and other injection vulnerabilities |\n| API Scan | Targeted scan using OpenAPI\u002FSwagger specs to test all documented API endpoints |\n| Spider | ZAP's crawler that discovers application pages and endpoints by following links |\n| Active Scan | Phase where ZAP sends attack payloads to discovered endpoints to find exploitable vulnerabilities |\n| Passive Scan | Analysis of HTTP responses for security headers, cookies, and information disclosure without sending attacks |\n| Scan Policy | Configuration defining which attack types to enable and their intensity levels |\n\n## Tools & Systems\n\n- **OWASP ZAP**: Open-source web application security scanner for DAST testing\n- **zaproxy\u002Faction-baseline**: GitHub Action for ZAP passive baseline scanning\n- **zaproxy\u002Faction-full-scan**: GitHub Action for ZAP active full scanning\n- **zaproxy\u002Faction-api-scan**: GitHub Action for API-focused scanning with OpenAPI support\n- **Nuclei**: Alternative vulnerability scanner with template-based detection for CI\u002FCD integration\n\n## Common Scenarios\n\n### Scenario: Integrating DAST into a Staging Deployment Pipeline\n\n**Context**: A team deploys to staging before production and needs automated DAST scanning between stages to catch runtime vulnerabilities.\n\n**Approach**:\n1. Add a DAST job in the pipeline that triggers after successful staging deployment\n2. Run ZAP baseline scan first for quick passive feedback (2-5 minutes)\n3. Follow with a targeted API scan using the application's OpenAPI specification\n4. Configure rules.tsv to FAIL on critical findings (XSS, SQLi) and WARN on headers\u002Fcookies\n5. Upload ZAP reports as pipeline artifacts for review\n6. Block production deployment if any FAIL-level findings are detected\n7. Schedule weekly full scans against staging for deeper coverage\n\n**Pitfalls**: ZAP full scans can take 30+ minutes and may overwhelm staging servers with attack traffic. Use baseline scans in CI and full scans on schedule. Running DAST against production without coordination can trigger WAF blocks and incident alerts.\n\n## Output Format\n\n```\nZAP DAST Scan Report\n======================\nTarget: https:\u002F\u002Fstaging.example.com\nScan Type: Baseline + API\nDate: 2026-02-23\nDuration: 4m 32s\n\nFINDINGS:\n  FAIL: 3\n  WARN: 7\n  INFO: 12\n  PASS: 45\n\nFAILING ALERTS:\n  [HIGH] 40012 - Cross Site Scripting (Reflected)\n    URL: https:\u002F\u002Fstaging.example.com\u002Fsearch?q=\u003Cscript>\n    Method: GET\n    Evidence: \u003Cscript>alert(1)\u003C\u002Fscript>\n\n  [MEDIUM] 10021 - X-Content-Type-Options Missing\n    URL: https:\u002F\u002Fstaging.example.com\u002Fapi\u002Fv1\u002F*\n    Evidence: Response header missing\n\n  [MEDIUM] 10035 - Strict-Transport-Security Missing\n    URL: https:\u002F\u002Fstaging.example.com\u002F\n    Evidence: HSTS header not present\n\nQUALITY GATE: FAILED (1 HIGH, 2 MEDIUM findings)\n```\n","# Integrating DAST with OWASP ZAP in Pipeline\n\n## When to Use\n\n- When testing running web applications for vulnerabilities like XSS, SQLi, CSRF, and misconfigurations\n- When SAST alone is insufficient and runtime behavior testing is required\n- When compliance mandates dynamic security testing of web applications before production\n- When testing APIs (REST\u002FGraphQL) for authentication, authorization, and injection flaws\n- When establishing continuous DAST scanning in staging environments before production deployment\n\n**Do not use** for scanning source code (use SAST), for scanning dependencies (use SCA), or for infrastructure configuration scanning (use IaC scanning tools).\n\n## Prerequisites\n\n- OWASP ZAP Docker image or installed locally (zaproxy\u002Fzap-stable or zaproxy\u002Faction-*)\n- Running target application accessible from the CI\u002FCD runner (staging URL or Docker service)\n- ZAP scan rules configuration (optional, for tuning)\n- OpenAPI\u002FSwagger specification for API scanning (optional)\n\n## Workflow\n\n### Step 1: Configure ZAP Baseline Scan in GitHub Actions\n\n```yaml\n# .github\u002Fworkflows\u002Fdast-scan.yml\nname: DAST Security Scan\n\non:\n  deployment_status:\n  workflow_dispatch:\n    inputs:\n      target_url:\n        description: 'Target URL to scan'\n        required: true\n\njobs:\n  zap-baseline:\n    name: ZAP Baseline Scan\n    runs-on: ubuntu-latest\n    services:\n      webapp:\n        image: ${{ github.repository }}:${{ github.sha }}\n        ports:\n          - 8080:8080\n        options: --health-cmd=\"curl -f http:\u002F\u002Flocalhost:8080\u002Fhealth\" --health-interval=10s --health-timeout=5s --health-retries=5\n\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: ZAP Baseline Scan\n        uses: zaproxy\u002Faction-baseline@v0.12.0\n        with:\n          target: 'http:\u002F\u002Fwebapp:8080'\n          rules_file_name: '.zap\u002Frules.tsv'\n          cmd_options: '-a -j'\n          allow_issue_writing: false\n\n      - name: Upload ZAP Report\n        if: always()\n        uses: actions\u002Fupload-artifact@v4\n        with:\n          name: zap-baseline-report\n          path: report_html.html\n```\n\n### Step 2: Configure ZAP Full Scan for Comprehensive Testing\n\n```yaml\n  zap-full-scan:\n    name: ZAP Full Scan\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: ZAP Full Scan\n        uses: zaproxy\u002Faction-full-scan@v0.12.0\n        with:\n          target: ${{ github.event.inputs.target_url || 'https:\u002F\u002Fstaging.example.com' }}\n          rules_file_name: '.zap\u002Frules.tsv'\n          cmd_options: '-a -j -T 60'\n\n      - name: Upload Reports\n        if: always()\n        uses: actions\u002Fupload-artifact@v4\n        with:\n          name: zap-full-report\n          path: |\n            report_html.html\n            report_json.json\n```\n\n### Step 3: Configure API Scan with OpenAPI Specification\n\n```yaml\n  zap-api-scan:\n    name: ZAP API Scan\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: ZAP API Scan\n        uses: zaproxy\u002Faction-api-scan@v0.12.0\n        with:\n          target: 'https:\u002F\u002Fstaging.example.com\u002Fapi\u002Fopenapi.json'\n          format: openapi\n          rules_file_name: '.zap\u002Fapi-rules.tsv'\n          cmd_options: '-a -j'\n```\n\n### Step 4: Configure ZAP Scan Rules\n\n```tsv\n# .zap\u002Frules.tsv\n# Rule ID\tAction (IGNORE\u002FWARN\u002FFAIL)\tDescription\n10003\tIGNORE\t# Vulnerable JS Library (handled by SCA)\n10015\tWARN\t# Incomplete or No Cache-control Header\n10021\tFAIL\t# X-Content-Type-Options Missing\n10035\tFAIL\t# Strict-Transport-Security Missing\n10038\tFAIL\t# Content Security Policy Missing\n10098\tIGNORE\t# Cross-Domain Misconfiguration (CDN)\n40012\tFAIL\t# Cross Site Scripting (Reflected)\n40014\tFAIL\t# Cross Site Scripting (Persistent)\n40018\tFAIL\t# SQL Injection\n40019\tFAIL\t# SQL Injection (MySQL)\n40032\tFAIL\t# .htaccess Information Leak\n90033\tFAIL\t# Loosely Scoped Cookie\n```\n\n### Step 5: Run ZAP with Docker Compose for Local Testing\n\n```yaml\n# docker-compose.zap.yml\nversion: '3.8'\nservices:\n  webapp:\n    build: .\n    ports:\n      - \"8080:8080\"\n    healthcheck:\n      test: [\"CMD\", \"curl\", \"-f\", \"http:\u002F\u002Flocalhost:8080\u002Fhealth\"]\n      interval: 10s\n      retries: 5\n\n  zap:\n    image: zaproxy\u002Fzap-stable:latest\n    depends_on:\n      webapp:\n        condition: service_healthy\n    command: >\n      zap-baseline.py\n        -t http:\u002F\u002Fwebapp:8080\n        -r \u002Fzap\u002Fwrk\u002Freport.html\n        -J \u002Fzap\u002Fwrk\u002Freport.json\n        -c \u002Fzap\u002Fwrk\u002Frules.tsv\n        -I\n    volumes:\n      - .\u002Fzap-reports:\u002Fzap\u002Fwrk\n      - .\u002F.zap\u002Frules.tsv:\u002Fzap\u002Fwrk\u002Frules.tsv\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| DAST | Dynamic Application Security Testing — tests running applications by sending requests and analyzing responses |\n| Baseline Scan | Quick passive scan that spiders the application without active attacks, suitable for CI\u002FCD |\n| Full Scan | Active scan including attack payloads for XSS, SQLi, and other injection vulnerabilities |\n| API Scan | Targeted scan using OpenAPI\u002FSwagger specs to test all documented API endpoints |\n| Spider | ZAP's crawler that discovers application pages and endpoints by following links |\n| Active Scan | Phase where ZAP sends attack payloads to discovered endpoints to find exploitable vulnerabilities |\n| Passive Scan | Analysis of HTTP responses for security headers, cookies, and information disclosure without sending attacks |\n| Scan Policy | Configuration defining which attack types to enable and their intensity levels |\n\n## Tools & Systems\n\n- **OWASP ZAP**: Open-source web application security scanner for DAST testing\n- **zaproxy\u002Faction-baseline**: GitHub Action for ZAP passive baseline scanning\n- **zaproxy\u002Faction-full-scan**: GitHub Action for ZAP active full scanning\n- **zaproxy\u002Faction-api-scan**: GitHub Action for API-focused scanning with OpenAPI support\n- **Nuclei**: Alternative vulnerability scanner with template-based detection for CI\u002FCD integration\n\n## Common Scenarios\n\n### Scenario: Integrating DAST into a Staging Deployment Pipeline\n\n**Context**: A team deploys to staging before production and needs automated DAST scanning between stages to catch runtime vulnerabilities.\n\n**Approach**:\n1. Add a DAST job in the pipeline that triggers after successful staging deployment\n2. Run ZAP baseline scan first for quick passive feedback (2-5 minutes)\n3. Follow with a targeted API scan using the application's OpenAPI specification\n4. Configure rules.tsv to FAIL on critical findings (XSS, SQLi) and WARN on headers\u002Fcookies\n5. Upload ZAP reports as pipeline artifacts for review\n6. Block production deployment if any FAIL-level findings are detected\n7. Schedule weekly full scans against staging for deeper coverage\n\n**Pitfalls**: ZAP full scans can take 30+ minutes and may overwhelm staging servers with attack traffic. Use baseline scans in CI and full scans on schedule. Running DAST against production without coordination can trigger WAF blocks and incident alerts.\n\n## Output Format\n\n```\nZAP DAST Scan Report\n======================\nTarget: https:\u002F\u002Fstaging.example.com\nScan Type: Baseline + API\nDate: 2026-02-23\nDuration: 4m 32s\n\nFINDINGS:\n  FAIL: 3\n  WARN: 7\n  INFO: 12\n  PASS: 45\n\nFAILING ALERTS:\n  [HIGH] 40012 - Cross Site Scripting (Reflected)\n    URL: https:\u002F\u002Fstaging.example.com\u002Fsearch?q=\u003Cscript>\n    Method: GET\n    Evidence: \u003Cscript>alert(1)\u003C\u002Fscript>\n\n  [MEDIUM] 10021 - X-Content-Type-Options Missing\n    URL: https:\u002F\u002Fstaging.example.com\u002Fapi\u002Fv1\u002F*\n    Evidence: Response header missing\n\n  [MEDIUM] 10035 - Strict-Transport-Security Missing\n    URL: https:\u002F\u002Fstaging.example.com\u002F\n    Evidence: HSTS header not present\n\nQUALITY GATE: FAILED (1 HIGH, 2 MEDIUM findings)\n```\n",{"name":5,"tags":60,"author":64,"domain":53,"license":15,"version":65,"nist_csf":66,"subdomain":54,"description":7,"mitre_attack":71},[54,61,37,40,62,63],"cicd","dynamic-testing","secure-sdlc","mahipal","1.0.0",[67,68,69,70],"PR.PS-01","GV.SC-07","ID.IM-04","PR.PS-04",[72,73,74],"T1195","T1554","T1059.004","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fintegrating-dast-with-owasp-zap-in-pipeline",4414,"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":86,"prompt":96,"zipAvailable":97},[87,90,93],{"tool":88,"command":89},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill integrating-dast-with-owasp-zap-in-pipeline",{"tool":91,"command":92},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill integrating-dast-with-owasp-zap-in-pipeline",{"tool":94,"command":95},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill integrating-dast-with-owasp-zap-in-pipeline","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002FSKILL.md",true,[99,105,111,115,119,124,128,132,136,142],{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"assets\u002Ftemplate.md","ASSET","资产文件",2410,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002Fassets\u002Ftemplate.md",{"path":106,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":109,"sourceHtmlUrl":110},"checklists\u002Faccessibility-checklist.md","REFERENCE","参考文档",5874,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Frsmdt-the-startup\u002Fplugins\u002Fteam\u002Fskills\u002Fcross-cutting\u002Fcoding-conventions\u002Fchecklists\u002Faccessibility-checklist.md",{"path":112,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":113,"sourceHtmlUrl":114},"checklists\u002Fperformance-checklist.md",5034,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Frsmdt-the-startup\u002Fplugins\u002Fteam\u002Fskills\u002Fcross-cutting\u002Fcoding-conventions\u002Fchecklists\u002Fperformance-checklist.md",{"path":116,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":117,"sourceHtmlUrl":118},"checklists\u002Fsecurity-checklist.md",5149,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Frsmdt-the-startup\u002Fplugins\u002Fteam\u002Fskills\u002Fcross-cutting\u002Fcoding-conventions\u002Fchecklists\u002Fsecurity-checklist.md",{"path":120,"resourceType":120,"resourceTypeDesc":121,"sizeBytes":122,"sourceHtmlUrl":123},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002FLICENSE",{"path":125,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":126,"sourceHtmlUrl":127},"references\u002Fapi-reference.md",1496,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002Freferences\u002Fapi-reference.md",{"path":129,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":130,"sourceHtmlUrl":131},"references\u002Fstandards.md",1412,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002Freferences\u002Fstandards.md",{"path":133,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":134,"sourceHtmlUrl":135},"references\u002Fworkflows.md",2443,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002Freferences\u002Fworkflows.md",{"path":137,"resourceType":138,"resourceTypeDesc":139,"sizeBytes":140,"sourceHtmlUrl":141},"scripts\u002Fagent.py","SCRIPT","脚本",6106,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002Fscripts\u002Fagent.py",{"path":143,"resourceType":138,"resourceTypeDesc":139,"sizeBytes":144,"sourceHtmlUrl":145},"scripts\u002Fprocess.py",8058,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fintegrating-dast-with-owasp-zap-in-pipeline\u002Fscripts\u002Fprocess.py",[147,171,195,220,246,273],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":154,"publishedAt":55},"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",[153],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[155,156,157,158,159,53,160,161,162,163,164,46,165,38,166,42,167,168,169,170],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","security","incident response","identity","pr","code","artifacts","supply-chain","supply-chain-security","attestation","code-signing","cosign","keyless",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":178,"publishedAt":55},"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",[177],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[179,167,180,181,159,182,53,162,183,184,185,186,187,188,189,190,191,192,193,194],"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":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":203,"publishedAt":55},"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",[201,202],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[189,204,205,206,45,53,207,208,183,209,210,211,212,213,214,215,216,217,218,219],"backup","recovery","validating backup integrity for recovery","infrastructure","validation","compliance","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":224,"categories":225,"keywords":227,"publishedAt":55},"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",[226],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[228,229,230,53,231,232,233,234,235,236,237,238,239,240,241,242,186,243,244,245],"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":247,"name":248,"nameZh":6,"description":249,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":250,"categories":251,"keywords":253,"publishedAt":55},"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",[252],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[254,255,256,53,257,258,259,260,261,262,263,264,265,266,267,268,269,270,271,272],"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":274,"name":275,"nameZh":6,"description":276,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":277,"categories":278,"keywords":280,"publishedAt":55},"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",[279],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[159,281,53,282,283,284,285,286,287,288,289,215,290,216,291,292,293,294,295,296],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]