[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HCM481E3D97NGEQB14JHVG":3,"skill-same:01M6HCM481E3D97NGEQB14JHVG":126},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":69,"commitSha":70,"skillDirectory":71,"forksCount":72,"repositoryHtmlUrl":73,"repositoryHomepageUrl":6,"ownerHtmlUrl":74,"ownerBlogUrl":6,"ownerDescription":75,"updatedAt":76,"install":77,"resources":90},"01M6HCM481E3D97NGEQB14JHVG","building-vulnerability-dashboard-with-defectdojo",null,"Deploy DefectDojo as a centralized vulnerability management dashboard with scanner integrations, deduplication, metrics tracking, and Jira ticketing workflows.","HenriqueMC17\u002Fagente-core","HenriqueMC17","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206460478?v=4","01M6HB63HBBF18AC4H09XTB549","Henrique Monteiro Cardoso","01M6HB63NGSQXWKWCFWW2B20W0",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-vulnerability-dashboard-with-defectdojo\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"with","dashboard","vulnerability","defectdojo","building vulnerability dashboard with defectdojo","deduplication","id","as","scanner","integrations","ticketing","scanner-integration","devsecops","vulnerability-management","integration","vulnerability management","metrics","jira","workflows","cybersecurity","2026-11-10 10:12:30",false,"---\nname: building-vulnerability-dashboard-with-defectdojo\ndescription: Deploy DefectDojo as a centralized vulnerability management dashboard with scanner integrations, deduplication, metrics tracking, and Jira ticketing workflows.\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\ncategory: building-vulnerability-dashboard-with-defectdojo\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":57,"author":58,"domain":51,"license":15,"version":59,"category":5,"nist_csf":60,"subdomain":45,"description":7,"mitre_attack":65},[35,45,33,37,43,44,49],"mahipal","1.0",[61,62,63,64],"ID.RA-01","ID.RA-02","ID.IM-02","ID.RA-06",[66,67,68],"T1190","T1203","T1068","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fbuilding-vulnerability-dashboard-with-defectdojo",0,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core","https:\u002F\u002Fgithub.com\u002FHenriqueMC17","Qualquer tecnologia suficientemente avançada é indistinguível da mágica.","2026-09-28 22:40:38",{"source":8,"skillName":5,"commands":78,"prompt":88,"zipAvailable":89},[79,82,85],{"tool":80,"command":81},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill building-vulnerability-dashboard-with-defectdojo",{"tool":83,"command":84},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill building-vulnerability-dashboard-with-defectdojo",{"tool":86,"command":87},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill building-vulnerability-dashboard-with-defectdojo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-vulnerability-dashboard-with-defectdojo\u002FSKILL.md",true,[91,97,102,108,112,116,122],{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"assets\u002Ftemplate.md","ASSET","资产文件",1878,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-vulnerability-dashboard-with-defectdojo\u002Fassets\u002Ftemplate.md",{"path":98,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-vulnerability-dashboard-with-defectdojo\u002FLICENSE",{"path":103,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fapi-reference.md","REFERENCE","参考文档",2017,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-vulnerability-dashboard-with-defectdojo\u002Freferences\u002Fapi-reference.md",{"path":109,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fstandards.md",1428,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-vulnerability-dashboard-with-defectdojo\u002Freferences\u002Fstandards.md",{"path":113,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":114,"sourceHtmlUrl":115},"references\u002Fworkflows.md",1729,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-vulnerability-dashboard-with-defectdojo\u002Freferences\u002Fworkflows.md",{"path":117,"resourceType":118,"resourceTypeDesc":119,"sizeBytes":120,"sourceHtmlUrl":121},"scripts\u002Fagent.py","SCRIPT","脚本",6860,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-vulnerability-dashboard-with-defectdojo\u002Fscripts\u002Fagent.py",{"path":123,"resourceType":118,"resourceTypeDesc":119,"sizeBytes":124,"sourceHtmlUrl":125},"scripts\u002Fprocess.py",7481,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-vulnerability-dashboard-with-defectdojo\u002Fscripts\u002Fprocess.py",[127,156,179,202,218,238],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":136,"publishedAt":52},"01M6HPFF0RCN0X6WT5EBSV71GY","validating-backup-integrity-for-recovery","Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[133],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[137,138,139,140,141,142,51,143,144,145,146,147,148,149,150,151,152,153,154,155],"integrity","backup","recovery","validating backup integrity for recovery","for","testing","validate","verification","hash-verification","incident-response","ransomware","detection","t1078","t1490","disaster-recovery","restore","incident","disaster recovery","ransomware response",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":52},"01M6HPFAWJVFK25Q33K3T7WQ8G","triaging-vulnerabilities-with-ssvc-framework","Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[],[163,164,165,166,32,51,167,168,45,169,170,171,34,172,173,174,175,176,177,178],"vulnerabilities","framework","ssvc","triaging vulnerabilities with ssvc framework","triage and prioritize","CISA","risk-management","cvss","remediation","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":52},"01M6HPF6JS9X72WP59094H3ASQ","triaging-security-incident","Performs initial triage of security incidents to determine severity, scope, and required response actions using the NIST SP 800-61r3 and SANS PICERL frameworks. Classifies incidents by type, assigns priority based on business impact, and routes...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident\u002FSKILL.md",[],[186,187,153,51,188,189,190,149,150,191,192,193,194,195,196,197,198,199,200,201],"security","triaging security incident","actions","soc","NIST","analysis","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","isolation","scope","impact","consistency",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":208,"publishedAt":52},"01M6HPF2EX6ZYNYYHKBRJN7GEF","triaging-security-incident-with-ir-playbook","Classify and prioritize security incidents using structured IR playbooks to determine severity, assign response teams, and initiate appropriate response procedures.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",[],[186,209,210,187,153,32,51,211,189,146,212,213,149,150,214,192,174,215,216,217],"playbook","triaging security incident with ir playbook","teams","IR-playbook","severity","classification","classify","incidents","initiate",{"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":224,"publishedAt":52},"01M6HPEY9XPGE7X95AG4XJFQAW","triaging-security-alerts-in-splunk","Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-alerts-in-splunk\u002FSKILL.md",[],[186,225,226,227,228,229,51,230,33,231,189,232,149,233,234,235,195,236,153,237],"security alerts","splunk","triaging security alerts in splunk","alerts","review","siem","search","correlation-search","t1566","notable-events","incident-review","cm","de",{"skillNo":239,"name":240,"nameZh":6,"description":241,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":242,"categories":243,"keywords":244,"publishedAt":52},"01M6HPET6XGEPEJPN7V032JGZ0","tracking-threat-actor-infrastructure","Threat actor infrastructure tracking involves monitoring and mapping adversary-controlled assets including command-and-control (C2) servers, phishing domains, exploit kit hosts, bulletproof hosting, a","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftracking-threat-actor-infrastructure\u002FSKILL.md",[],[245,246,247,248,51,249,250,251,252,253,254,233,255,256,236,257,237,258,259,260],"infrastructure","tracking threat actor infrastructure","tracking","threat","monitoring","mitre-attack","threat-actor","threat-intelligence","command-and-control","dns","command","exploit","intelligence","domains","kit","hosts"]