[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE129KNVPH1M44SDP473R2":3,"skill-same:01M6AE129KNVPH1M44SDP473R2":138},{"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":37,"publishedAt":56,"linkOnly":57,"markdownContent":58,"markdownBody":59,"frontMatter":60,"refName":73,"commitSha":74,"skillDirectory":75,"forksCount":76,"repositoryHtmlUrl":77,"repositoryHomepageUrl":78,"ownerHtmlUrl":79,"ownerBlogUrl":80,"ownerDescription":81,"updatedAt":82,"install":83,"resources":96},"01M6AE129KNVPH1M44SDP473R2","building-vulnerability-dashboard-with-defectdojo",null,"Deploy DefectDojo as a centralized vulnerability management dashboard that ingests findings from 200+ security scanners, deduplicates results, tracks remediation metrics, and integrates with CI\u002FCD, Jira ticketing, and Slack notifications via its REST API. Use when consolidating scanner output into one dashboard or automating vulnerability ticketing and executive reporting.","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\u002Fbuilding-vulnerability-dashboard-with-defectdojo\u002FSKILL.md",[18,23,26,29,34],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":35,"categoryName":36,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000033","数据分析师",[38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55],"building vulnerability dashboard with defectdojo","dashboard","integration","scanner-integration","deduplication","defectdojo","vulnerability-management","reporting","ci","notifications","slack","vulnerability management","metrics","jira","deploy","cybersecurity","security","devsecops","2026-11-10 10:12:30",false,"---\nname: building-vulnerability-dashboard-with-defectdojo\ndescription: Deploy DefectDojo as a centralized vulnerability management dashboard that ingests findings from 200+ security scanners, deduplicates results, tracks remediation metrics, and integrates with CI\u002FCD, Jira ticketing, and Slack notifications via its REST API. Use when consolidating scanner output into one dashboard or automating vulnerability ticketing and executive reporting.\ndomain: cybersecurity\nsubdomain: vulnerability-management\ntags:\n- defectdojo\n- vulnerability-management\n- dashboard\n- deduplication\n- scanner-integration\n- devsecops\n- jira\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- ID.RA-01\n- ID.RA-02\n- ID.IM-02\n- ID.RA-06\nmitre_attack:\n- T1190\n- T1203\n- T1068\n---\n\n# Building Vulnerability Dashboard with DefectDojo\n\n## Overview\n\nDefectDojo is an open-source application vulnerability management platform that aggregates findings from 200+ security tools, deduplicates results, tracks remediation progress, and provides executive dashboards. It serves as a central hub for vulnerability management, integrating with CI\u002FCD pipelines, Jira for ticketing, and Slack for notifications. DefectDojo supports OWASP-based categorization and provides REST API for automation.\n\n\n## When to Use\n\n- When deploying or configuring building vulnerability dashboard with defectdojo 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- Docker and Docker Compose\n- 4GB+ RAM, 2+ CPU cores, 20GB+ disk\n- PostgreSQL 12+ (included in Docker deployment)\n- Python 3.9+ for API integration scripts\n- Jira instance (optional, for ticket integration)\n\n## Deployment\n\n### Docker Compose Deployment\n```bash\n# Clone DefectDojo repository\ngit clone https:\u002F\u002Fgithub.com\u002FDefectDojo\u002Fdjango-DefectDojo.git\ncd django-DefectDojo\n\n# Start with Docker Compose (production mode)\n.\u002Fdc-up-d.sh\n\n# Alternative: manual Docker Compose\ndocker compose up -d\n\n# Check service status\ndocker compose ps\n\n# View initial admin credentials\ndocker compose logs initializer 2>&1 | grep \"Admin password\"\n\n# Access DefectDojo at http:\u002F\u002Flocalhost:8080\n```\n\n### Environment Configuration\n```bash\n# Key environment variables in docker-compose.yml\nDD_DATABASE_ENGINE=django.db.backends.postgresql\nDD_DATABASE_HOST=postgres\nDD_DATABASE_PORT=5432\nDD_DATABASE_NAME=defectdojo\nDD_DATABASE_USER=defectdojo\nDD_DATABASE_PASSWORD=\u003Csecure_password>\nDD_ALLOWED_HOSTS=*\nDD_SECRET_KEY=\u003Crandom_64_char_key>\nDD_CREDENTIAL_AES_256_KEY=\u003Crandom_128_bit_key>\nDD_SOCIAL_AUTH_GOOGLE_OAUTH2_ENABLED=True\n```\n\n## Organizational Structure\n\n### Hierarchy\n```\nProduct Type (Business Unit)\n  └── Product (Application\u002FService)\n       └── Engagement (Assessment\u002FSprint)\n            └── Test (Scanner Run)\n                 └── Finding (Individual Vulnerability)\n```\n\n### Setup via API\n```python\nimport requests\n\nDD_URL = \"http:\u002F\u002Flocalhost:8080\u002Fapi\u002Fv2\"\nAPI_KEY = \"your_api_key_here\"\nHEADERS = {\"Authorization\": f\"Token {API_KEY}\", \"Content-Type\": \"application\u002Fjson\"}\n\n# Create Product Type\nresp = requests.post(f\"{DD_URL}\u002Fproduct_types\u002F\", headers=HEADERS, json={\n    \"name\": \"Web Applications\",\n    \"description\": \"Customer-facing web application portfolio\"\n})\nproduct_type_id = resp.json()[\"id\"]\n\n# Create Product\nresp = requests.post(f\"{DD_URL}\u002Fproducts\u002F\", headers=HEADERS, json={\n    \"name\": \"Customer Portal\",\n    \"description\": \"Main customer-facing web application\",\n    \"prod_type\": product_type_id,\n    \"sla_configuration\": 1,\n})\nproduct_id = resp.json()[\"id\"]\n\n# Create Engagement\nresp = requests.post(f\"{DD_URL}\u002Fengagements\u002F\", headers=HEADERS, json={\n    \"name\": \"Q1 2024 Security Assessment\",\n    \"product\": product_id,\n    \"target_start\": \"2024-01-01\",\n    \"target_end\": \"2024-03-31\",\n    \"engagement_type\": \"CI\u002FCD\",\n    \"status\": \"In Progress\",\n})\nengagement_id = resp.json()[\"id\"]\n```\n\n## Scanner Integration\n\n### Import Scan Results via API\n```bash\n# Upload Nessus scan results\ncurl -X POST \"${DD_URL}\u002Freimport-scan\u002F\" \\\n  -H \"Authorization: Token ${API_KEY}\" \\\n  -F \"scan_type=Nessus Scan\" \\\n  -F \"file=@nessus_report.csv\" \\\n  -F \"product_name=Customer Portal\" \\\n  -F \"engagement_name=Q1 2024 Security Assessment\" \\\n  -F \"auto_create_context=true\" \\\n  -F \"deduplication_on_engagement=true\"\n\n# Upload OWASP ZAP results\ncurl -X POST \"${DD_URL}\u002Freimport-scan\u002F\" \\\n  -H \"Authorization: Token ${API_KEY}\" \\\n  -F \"scan_type=ZAP Scan\" \\\n  -F \"file=@zap_report.xml\" \\\n  -F \"product_name=Customer Portal\" \\\n  -F \"engagement_name=Q1 2024 Security Assessment\" \\\n  -F \"auto_create_context=true\"\n\n# Upload Trivy container scan\ncurl -X POST \"${DD_URL}\u002Freimport-scan\u002F\" \\\n  -H \"Authorization: Token ${API_KEY}\" \\\n  -F \"scan_type=Trivy Scan\" \\\n  -F \"file=@trivy_results.json\" \\\n  -F \"product_name=Customer Portal\" \\\n  -F \"engagement_name=Q1 2024 Security Assessment\" \\\n  -F \"auto_create_context=true\"\n```\n\n### Supported Scanner Types (Partial List)\n| Scanner | Type String | Format |\n|---------|------------|--------|\n| Nessus | Nessus Scan | CSV\u002FXML |\n| OpenVAS | OpenVAS CSV | CSV |\n| Qualys | Qualys Scan | XML |\n| OWASP ZAP | ZAP Scan | XML\u002FJSON |\n| Burp Suite | Burp XML | XML |\n| Trivy | Trivy Scan | JSON |\n| Semgrep | Semgrep JSON Report | JSON |\n| Snyk | Snyk Scan | JSON |\n| SonarQube | SonarQube Scan | JSON |\n| Checkov | Checkov Scan | JSON |\n\n### CI\u002FCD Integration (GitHub Actions)\n```yaml\n# .github\u002Fworkflows\u002Fsecurity-scan.yml\nname: Security Scan\non: [push]\njobs:\n  scan:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - name: Run Semgrep\n        run: |\n          pip install semgrep\n          semgrep --config auto --json -o semgrep_results.json .\n      - name: Upload to DefectDojo\n        run: |\n          curl -X POST \"${{ secrets.DD_URL }}\u002Fapi\u002Fv2\u002Freimport-scan\u002F\" \\\n            -H \"Authorization: Token ${{ secrets.DD_API_KEY }}\" \\\n            -F \"scan_type=Semgrep JSON Report\" \\\n            -F \"file=@semgrep_results.json\" \\\n            -F \"product_name=${{ github.event.repository.name }}\" \\\n            -F \"engagement_name=CI\u002FCD\" \\\n            -F \"auto_create_context=true\"\n```\n\n## Jira Integration\n\n```python\n# Configure Jira integration in DefectDojo settings\njira_config = {\n    \"url\": \"https:\u002F\u002Fcompany.atlassian.net\",\n    \"username\": \"jira-bot@company.com\",\n    \"password\": \"jira_api_token\",\n    \"default_issue_type\": \"Bug\",\n    \"critical_mapping_severity\": \"Blocker\",\n    \"high_mapping_severity\": \"Critical\",\n    \"medium_mapping_severity\": \"Major\",\n    \"low_mapping_severity\": \"Minor\",\n    \"finding_text\": \"**Vulnerability**: {{ finding.title }}\\n**Severity**: {{ finding.severity }}\\n**CVE**: {{ finding.cve }}\\n**Description**: {{ finding.description }}\",\n    \"accepted_mapping_resolution\": \"Done\",\n    \"close_status_key\": 6,\n}\n```\n\n## Metrics and Dashboards\n\n### Key Metrics API Queries\n```python\n# Get finding counts by severity\nresp = requests.get(f\"{DD_URL}\u002Ffindings\u002F?limit=0&active=true\",\n                    headers=HEADERS)\nfindings = resp.json()\n\n# Get SLA breach counts\nresp = requests.get(f\"{DD_URL}\u002Ffindings\u002F?limit=0&active=true&sla_breached=true\",\n                    headers=HEADERS)\n\n# Get product-level metrics\nresp = requests.get(f\"{DD_URL}\u002Fproducts\u002F{product_id}\u002F\",\n                    headers=HEADERS)\nproduct_data = resp.json()\n```\n\n## References\n\n- [DefectDojo GitHub](https:\u002F\u002Fgithub.com\u002FDefectDojo\u002Fdjango-DefectDojo)\n- [DefectDojo Documentation](https:\u002F\u002Fdefectdojo.github.io\u002Fdjango-DefectDojo\u002F)\n- [DefectDojo REST API](https:\u002F\u002Fdefectdojo.github.io\u002Fdjango-DefectDojo\u002Fintegrations\u002Fapi-v2-docs\u002F)\n- [OWASP DefectDojo Project](https:\u002F\u002Fowasp.org\u002Fwww-project-defectdojo\u002F)\n- [DefectDojo Integrations](https:\u002F\u002Fdefectdojo.com\u002Fintegrations)\n","# Building Vulnerability Dashboard with DefectDojo\n\n## Overview\n\nDefectDojo is an open-source application vulnerability management platform that aggregates findings from 200+ security tools, deduplicates results, tracks remediation progress, and provides executive dashboards. It serves as a central hub for vulnerability management, integrating with CI\u002FCD pipelines, Jira for ticketing, and Slack for notifications. DefectDojo supports OWASP-based categorization and provides REST API for automation.\n\n\n## When to Use\n\n- When deploying or configuring building vulnerability dashboard with defectdojo 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- Docker and Docker Compose\n- 4GB+ RAM, 2+ CPU cores, 20GB+ disk\n- PostgreSQL 12+ (included in Docker deployment)\n- Python 3.9+ for API integration scripts\n- Jira instance (optional, for ticket integration)\n\n## Deployment\n\n### Docker Compose Deployment\n```bash\n# Clone DefectDojo repository\ngit clone https:\u002F\u002Fgithub.com\u002FDefectDojo\u002Fdjango-DefectDojo.git\ncd django-DefectDojo\n\n# Start with Docker Compose (production mode)\n.\u002Fdc-up-d.sh\n\n# Alternative: manual Docker Compose\ndocker compose up -d\n\n# Check service status\ndocker compose ps\n\n# View initial admin credentials\ndocker compose logs initializer 2>&1 | grep \"Admin password\"\n\n# Access DefectDojo at http:\u002F\u002Flocalhost:8080\n```\n\n### Environment Configuration\n```bash\n# Key environment variables in docker-compose.yml\nDD_DATABASE_ENGINE=django.db.backends.postgresql\nDD_DATABASE_HOST=postgres\nDD_DATABASE_PORT=5432\nDD_DATABASE_NAME=defectdojo\nDD_DATABASE_USER=defectdojo\nDD_DATABASE_PASSWORD=\u003Csecure_password>\nDD_ALLOWED_HOSTS=*\nDD_SECRET_KEY=\u003Crandom_64_char_key>\nDD_CREDENTIAL_AES_256_KEY=\u003Crandom_128_bit_key>\nDD_SOCIAL_AUTH_GOOGLE_OAUTH2_ENABLED=True\n```\n\n## Organizational Structure\n\n### Hierarchy\n```\nProduct Type (Business Unit)\n  └── Product (Application\u002FService)\n       └── Engagement (Assessment\u002FSprint)\n            └── Test (Scanner Run)\n                 └── Finding (Individual Vulnerability)\n```\n\n### Setup via API\n```python\nimport requests\n\nDD_URL = \"http:\u002F\u002Flocalhost:8080\u002Fapi\u002Fv2\"\nAPI_KEY = \"your_api_key_here\"\nHEADERS = {\"Authorization\": f\"Token {API_KEY}\", \"Content-Type\": \"application\u002Fjson\"}\n\n# Create Product Type\nresp = requests.post(f\"{DD_URL}\u002Fproduct_types\u002F\", headers=HEADERS, json={\n    \"name\": \"Web Applications\",\n    \"description\": \"Customer-facing web application portfolio\"\n})\nproduct_type_id = resp.json()[\"id\"]\n\n# Create Product\nresp = requests.post(f\"{DD_URL}\u002Fproducts\u002F\", headers=HEADERS, json={\n    \"name\": \"Customer Portal\",\n    \"description\": \"Main customer-facing web application\",\n    \"prod_type\": product_type_id,\n    \"sla_configuration\": 1,\n})\nproduct_id = resp.json()[\"id\"]\n\n# Create Engagement\nresp = requests.post(f\"{DD_URL}\u002Fengagements\u002F\", headers=HEADERS, json={\n    \"name\": \"Q1 2024 Security Assessment\",\n    \"product\": product_id,\n    \"target_start\": \"2024-01-01\",\n    \"target_end\": \"2024-03-31\",\n    \"engagement_type\": \"CI\u002FCD\",\n    \"status\": \"In Progress\",\n})\nengagement_id = resp.json()[\"id\"]\n```\n\n## Scanner Integration\n\n### Import Scan Results via API\n```bash\n# Upload Nessus scan results\ncurl -X POST \"${DD_URL}\u002Freimport-scan\u002F\" \\\n  -H \"Authorization: Token ${API_KEY}\" \\\n  -F \"scan_type=Nessus Scan\" \\\n  -F \"file=@nessus_report.csv\" \\\n  -F \"product_name=Customer Portal\" \\\n  -F \"engagement_name=Q1 2024 Security Assessment\" \\\n  -F \"auto_create_context=true\" \\\n  -F \"deduplication_on_engagement=true\"\n\n# Upload OWASP ZAP results\ncurl -X POST \"${DD_URL}\u002Freimport-scan\u002F\" \\\n  -H \"Authorization: Token ${API_KEY}\" \\\n  -F \"scan_type=ZAP Scan\" \\\n  -F \"file=@zap_report.xml\" \\\n  -F \"product_name=Customer Portal\" \\\n  -F \"engagement_name=Q1 2024 Security Assessment\" \\\n  -F \"auto_create_context=true\"\n\n# Upload Trivy container scan\ncurl -X POST \"${DD_URL}\u002Freimport-scan\u002F\" \\\n  -H \"Authorization: Token ${API_KEY}\" \\\n  -F \"scan_type=Trivy Scan\" \\\n  -F \"file=@trivy_results.json\" \\\n  -F \"product_name=Customer Portal\" \\\n  -F \"engagement_name=Q1 2024 Security Assessment\" \\\n  -F \"auto_create_context=true\"\n```\n\n### Supported Scanner Types (Partial List)\n| Scanner | Type String | Format |\n|---------|------------|--------|\n| Nessus | Nessus Scan | CSV\u002FXML |\n| OpenVAS | OpenVAS CSV | CSV |\n| Qualys | Qualys Scan | XML |\n| OWASP ZAP | ZAP Scan | XML\u002FJSON |\n| Burp Suite | Burp XML | XML |\n| Trivy | Trivy Scan | JSON |\n| Semgrep | Semgrep JSON Report | JSON |\n| Snyk | Snyk Scan | JSON |\n| SonarQube | SonarQube Scan | JSON |\n| Checkov | Checkov Scan | JSON |\n\n### CI\u002FCD Integration (GitHub Actions)\n```yaml\n# .github\u002Fworkflows\u002Fsecurity-scan.yml\nname: Security Scan\non: [push]\njobs:\n  scan:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - name: Run Semgrep\n        run: |\n          pip install semgrep\n          semgrep --config auto --json -o semgrep_results.json .\n      - name: Upload to DefectDojo\n        run: |\n          curl -X POST \"${{ secrets.DD_URL }}\u002Fapi\u002Fv2\u002Freimport-scan\u002F\" \\\n            -H \"Authorization: Token ${{ secrets.DD_API_KEY }}\" \\\n            -F \"scan_type=Semgrep JSON Report\" \\\n            -F \"file=@semgrep_results.json\" \\\n            -F \"product_name=${{ github.event.repository.name }}\" \\\n            -F \"engagement_name=CI\u002FCD\" \\\n            -F \"auto_create_context=true\"\n```\n\n## Jira Integration\n\n```python\n# Configure Jira integration in DefectDojo settings\njira_config = {\n    \"url\": \"https:\u002F\u002Fcompany.atlassian.net\",\n    \"username\": \"jira-bot@company.com\",\n    \"password\": \"jira_api_token\",\n    \"default_issue_type\": \"Bug\",\n    \"critical_mapping_severity\": \"Blocker\",\n    \"high_mapping_severity\": \"Critical\",\n    \"medium_mapping_severity\": \"Major\",\n    \"low_mapping_severity\": \"Minor\",\n    \"finding_text\": \"**Vulnerability**: {{ finding.title }}\\n**Severity**: {{ finding.severity }}\\n**CVE**: {{ finding.cve }}\\n**Description**: {{ finding.description }}\",\n    \"accepted_mapping_resolution\": \"Done\",\n    \"close_status_key\": 6,\n}\n```\n\n## Metrics and Dashboards\n\n### Key Metrics API Queries\n```python\n# Get finding counts by severity\nresp = requests.get(f\"{DD_URL}\u002Ffindings\u002F?limit=0&active=true\",\n                    headers=HEADERS)\nfindings = resp.json()\n\n# Get SLA breach counts\nresp = requests.get(f\"{DD_URL}\u002Ffindings\u002F?limit=0&active=true&sla_breached=true\",\n                    headers=HEADERS)\n\n# Get product-level metrics\nresp = requests.get(f\"{DD_URL}\u002Fproducts\u002F{product_id}\u002F\",\n                    headers=HEADERS)\nproduct_data = resp.json()\n```\n\n## References\n\n- [DefectDojo GitHub](https:\u002F\u002Fgithub.com\u002FDefectDojo\u002Fdjango-DefectDojo)\n- [DefectDojo Documentation](https:\u002F\u002Fdefectdojo.github.io\u002Fdjango-DefectDojo\u002F)\n- [DefectDojo REST API](https:\u002F\u002Fdefectdojo.github.io\u002Fdjango-DefectDojo\u002Fintegrations\u002Fapi-v2-docs\u002F)\n- [OWASP DefectDojo Project](https:\u002F\u002Fowasp.org\u002Fwww-project-defectdojo\u002F)\n- [DefectDojo Integrations](https:\u002F\u002Fdefectdojo.com\u002Fintegrations)\n",{"name":5,"tags":61,"author":62,"domain":53,"license":15,"version":63,"nist_csf":64,"subdomain":44,"description":7,"mitre_attack":69},[43,44,39,42,41,55,51],"mahipal","1.0",[65,66,67,68],"ID.RA-01","ID.RA-02","ID.IM-02","ID.RA-06",[70,71,72],"T1190","T1203","T1068","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fbuilding-vulnerability-dashboard-with-defectdojo",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":84,"prompt":94,"zipAvailable":95},[85,88,91],{"tool":86,"command":87},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill building-vulnerability-dashboard-with-defectdojo",{"tool":89,"command":90},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill building-vulnerability-dashboard-with-defectdojo",{"tool":92,"command":93},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill building-vulnerability-dashboard-with-defectdojo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-vulnerability-dashboard-with-defectdojo\u002FSKILL.md",true,[97,103,108,114,118,122,128,132],{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"assets\u002Ftemplate.md","ASSET","资产文件",1878,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-vulnerability-dashboard-with-defectdojo\u002Fassets\u002Ftemplate.md",{"path":104,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":106,"sourceHtmlUrl":107},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-vulnerability-dashboard-with-defectdojo\u002FLICENSE",{"path":109,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fapi-reference.md","REFERENCE","参考文档",2017,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-vulnerability-dashboard-with-defectdojo\u002Freferences\u002Fapi-reference.md",{"path":115,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Fstandards.md",1428,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-vulnerability-dashboard-with-defectdojo\u002Freferences\u002Fstandards.md",{"path":119,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fworkflows.md",1729,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-vulnerability-dashboard-with-defectdojo\u002Freferences\u002Fworkflows.md",{"path":123,"resourceType":124,"resourceTypeDesc":125,"sizeBytes":126,"sourceHtmlUrl":127},"scripts\u002Fagent.py","SCRIPT","脚本",6860,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-vulnerability-dashboard-with-defectdojo\u002Fscripts\u002Fagent.py",{"path":129,"resourceType":124,"resourceTypeDesc":125,"sizeBytes":130,"sourceHtmlUrl":131},"scripts\u002Fprocess.py",7481,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-vulnerability-dashboard-with-defectdojo\u002Fscripts\u002Fprocess.py",{"path":133,"resourceType":134,"resourceTypeDesc":135,"sizeBytes":136,"sourceHtmlUrl":137},"SKILL.md.tmpl","OTHER","其他",48624,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fland-and-deploy\u002FSKILL.md.tmpl",[139,166,190,218,244,270],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":148,"publishedAt":56},"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",[145],{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[149,150,151,152,54,53,153,154,155,156,157,46,158,159,160,161,162,163,164,165],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","incident response","identity","pr","code","artifacts","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":173,"publishedAt":56},"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",[172],{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},[174,162,175,176,54,177,53,155,178,179,180,181,182,183,184,185,186,187,188,189],"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":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":200,"publishedAt":56},"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",[196,199],{"categoryNo":197,"categoryName":198,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},[184,201,202,203,204,53,205,206,178,207,208,209,210,211,212,213,214,215,216,217],"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":219,"name":220,"nameZh":6,"description":221,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":222,"categories":223,"keywords":225,"publishedAt":56},"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",[224],{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},[226,227,228,53,229,230,231,232,233,234,235,236,237,238,239,240,181,241,242,243],"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":245,"name":246,"nameZh":6,"description":247,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":248,"categories":249,"keywords":251,"publishedAt":56},"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",[250],{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},[252,253,254,53,255,256,257,44,258,259,260,261,262,263,264,265,266,267,268,269],"vulnerabilities","framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","risk-management","nessus","qualys","openvas","cvss","remediation","risk","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":271,"name":272,"nameZh":6,"description":273,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":274,"categories":275,"keywords":277,"publishedAt":56},"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",[276],{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},[54,278,53,279,280,281,282,283,284,285,286,213,287,214,288,289,290,291,292,293],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]