[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HNH46QPMN2WZGWPFMBB0KH":3,"skill-same:01M6HNH46QPMN2WZGWPFMBB0KH":118},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":6,"ownerHtmlUrl":66,"ownerBlogUrl":6,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M6HNH46QPMN2WZGWPFMBB0KH","performing-subdomain-enumeration-with-subfinder",null,"Enumerate subdomains of target domains using ProjectDiscovery's Subfinder passive reconnaissance tool to map the attack surface during security assessments.","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\u002Fperforming-subdomain-enumeration-with-subfinder\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"subdomain","performing","with","performing subdomain enumeration with subfinder","subfinder","enumeration","web-application-security","t1505","subdomain-enumeration","passive-recon","security","cm","bug","007","map","de","domains","recon","attack-surface","cybersecurity","2026-11-10 10:12:30",false,"---\nname: performing-subdomain-enumeration-with-subfinder\ndescription: Enumerate subdomains of target domains using ProjectDiscovery's Subfinder passive reconnaissance tool to map the attack surface during security assessments.\ndomain: cybersecurity\nsubdomain: web-application-security\ntags:\n- subdomain-enumeration\n- reconnaissance\n- bug-bounty\n- attack-surface\n- subfinder\n- passive-recon\n- osint\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- ID.RA-01\n- PR.DS-10\n- DE.CM-01\nmitre_attack:\n- T1190\n- T1059.007\n- T1505.003\n- T1083\n- T1595\ncategory: performing-subdomain-enumeration-with-subfinder\n---\n# Performing Subdomain Enumeration with Subfinder\n\n## When to Use\n- During the reconnaissance phase of penetration testing or bug bounty hunting\n- When mapping the external attack surface of a target organization\n- Before performing vulnerability scanning on discovered subdomains\n- When building an asset inventory for continuous security monitoring\n- During red team engagements requiring passive information gathering\n\n## Prerequisites\n- Go 1.21+ installed for building from source\n- Subfinder v2 installed (`go install -v github.com\u002Fprojectdiscovery\u002Fsubfinder\u002Fv2\u002Fcmd\u002Fsubfinder@latest`)\n- API keys configured for passive sources (Shodan, Censys, VirusTotal, SecurityTrails, Chaos)\n- Provider configuration file at `$HOME\u002F.config\u002Fsubfinder\u002Fprovider-config.yaml`\n- Network access to passive DNS and certificate transparency sources\n- httpx or httprobe for validating discovered subdomains\n\n## Workflow\n\n### Step 1 — Install and Configure Subfinder\n```bash\n# Install subfinder\ngo install -v github.com\u002Fprojectdiscovery\u002Fsubfinder\u002Fv2\u002Fcmd\u002Fsubfinder@latest\n\n# Verify installation\nsubfinder -version\n\n# Configure API keys for enhanced results\nmkdir -p $HOME\u002F.config\u002Fsubfinder\ncat > $HOME\u002F.config\u002Fsubfinder\u002Fprovider-config.yaml \u003C\u003C 'EOF'\nshodan:\n  - YOUR_SHODAN_API_KEY\ncensys:\n  - YOUR_CENSYS_API_ID:YOUR_CENSYS_API_SECRET\nvirustotal:\n  - YOUR_VT_API_KEY\nsecuritytrails:\n  - YOUR_ST_API_KEY\nchaos:\n  - YOUR_CHAOS_API_KEY\nEOF\n```\n\n### Step 2 — Run Basic Subdomain Enumeration\n```bash\n# Single domain enumeration\nsubfinder -d example.com -o subdomains.txt\n\n# Multiple domains from a file\nsubfinder -dL domains.txt -o all_subdomains.txt\n\n# Use all passive sources (slower but more thorough)\nsubfinder -d example.com -all -o subdomains_all.txt\n\n# Silent mode for piping to other tools\nsubfinder -d example.com -silent | httpx -silent -status-code\n```\n\n### Step 3 — Filter and Customize Source Selection\n```bash\n# Use specific sources only\nsubfinder -d example.com -s crtsh,virustotal,shodan -o filtered.txt\n\n# Exclude specific sources\nsubfinder -d example.com -es github -o results.txt\n\n# Enable recursive subdomain enumeration\nsubfinder -d example.com -recursive -o recursive_subs.txt\n\n# Match specific patterns\nsubfinder -d example.com -m \"api,dev,staging\" -o matched.txt\n```\n\n### Step 4 — Control Rate Limiting and Output Format\n```bash\n# Rate limit to avoid API throttling\nsubfinder -d example.com -rate-limit 10 -t 5 -o rate_limited.txt\n\n# JSON output for programmatic processing\nsubfinder -d example.com -oJ -o subdomains.json\n\n# Output with source information\nsubfinder -d example.com -cs -o subdomains_with_sources.txt\n\n# Collect results in a directory per domain\nsubfinder -dL domains.txt -oD .\u002Fresults\u002F\n```\n\n### Step 5 — Validate Discovered Subdomains with httpx\n```bash\n# Pipe subfinder output to httpx for live validation\nsubfinder -d example.com -silent | httpx -silent -status-code -title -tech-detect -o live_hosts.txt\n\n# Check for specific ports\nsubfinder -d example.com -silent | httpx -ports 80,443,8080,8443 -o web_services.txt\n\n# Resolve IP addresses\nsubfinder -d example.com -silent | dnsx -a -resp -o resolved.txt\n```\n\n### Step 6 — Integrate with Broader Recon Pipeline\n```bash\n# Chain with nuclei for vulnerability scanning\nsubfinder -d example.com -silent | httpx -silent | nuclei -t cves\u002F -o vulns.txt\n\n# Combine with amass for comprehensive enumeration\nsubfinder -d example.com -o subfinder_results.txt\namass enum -passive -d example.com -o amass_results.txt\ncat subfinder_results.txt amass_results.txt | sort -u > combined_subdomains.txt\n\n# Screenshot discovered hosts\nsubfinder -d example.com -silent | httpx -silent | gowitness file -f - -P screenshots\u002F\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Passive Enumeration | Discovering subdomains without directly querying target DNS servers |\n| Certificate Transparency | Public logs of SSL\u002FTLS certificates revealing subdomain names |\n| DNS Aggregation | Collecting subdomain data from multiple passive DNS databases |\n| Recursive Enumeration | Discovering subdomains of subdomains for deeper coverage |\n| Source Providers | External APIs and databases queried for subdomain intelligence |\n| CNAME Records | Canonical name records that may reveal additional infrastructure |\n| Wildcard DNS | DNS configuration returning results for any subdomain query |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Subfinder | Primary passive subdomain enumeration engine |\n| httpx | HTTP probe tool for validating live subdomains |\n| dnsx | DNS resolution and validation toolkit |\n| Nuclei | Template-based vulnerability scanner for discovered hosts |\n| Amass | Complementary subdomain enumeration with active\u002Fpassive modes |\n| gowitness | Web screenshot utility for visual reconnaissance |\n| Shodan | Internet-wide scanning database for subdomain intelligence |\n| crt.sh | Certificate transparency log search engine |\n\n## Common Scenarios\n\n1. **Bug Bounty Reconnaissance** — Enumerate all subdomains of a target program scope to identify forgotten or misconfigured assets that may contain vulnerabilities\n2. **Attack Surface Mapping** — Build a comprehensive inventory of externally accessible subdomains for ongoing security monitoring and risk assessment\n3. **Cloud Asset Discovery** — Identify subdomains pointing to cloud services (AWS, Azure, GCP) that may be vulnerable to subdomain takeover\n4. **CI\u002FCD Integration** — Automate subdomain monitoring in pipelines to detect new subdomains and alert on changes to the attack surface\n5. **Merger & Acquisition Due Diligence** — Map the complete external footprint of an acquisition target during security assessment\n\n## Output Format\n\n```\n## Subdomain Enumeration Report\n- **Target Domain**: example.com\n- **Total Subdomains Found**: 247\n- **Live Hosts**: 183\n- **Unique IP Addresses**: 42\n- **Sources Used**: crt.sh, VirusTotal, Shodan, SecurityTrails, Censys\n\n### Discovered Subdomains\n| Subdomain | IP Address | Status Code | Technology |\n|-----------|-----------|-------------|------------|\n| api.example.com | 10.0.1.5 | 200 | Nginx, Node.js |\n| staging.example.com | 10.0.2.10 | 403 | Apache |\n| dev.example.com | 10.0.3.15 | 200 | Express |\n\n### Recommendations\n- Remove DNS records for decommissioned subdomains\n- Investigate subdomains with CNAME pointing to unclaimed services\n- Restrict access to development and staging environments\n```\n","# Performing Subdomain Enumeration with Subfinder\n\n## When to Use\n- During the reconnaissance phase of penetration testing or bug bounty hunting\n- When mapping the external attack surface of a target organization\n- Before performing vulnerability scanning on discovered subdomains\n- When building an asset inventory for continuous security monitoring\n- During red team engagements requiring passive information gathering\n\n## Prerequisites\n- Go 1.21+ installed for building from source\n- Subfinder v2 installed (`go install -v github.com\u002Fprojectdiscovery\u002Fsubfinder\u002Fv2\u002Fcmd\u002Fsubfinder@latest`)\n- API keys configured for passive sources (Shodan, Censys, VirusTotal, SecurityTrails, Chaos)\n- Provider configuration file at `$HOME\u002F.config\u002Fsubfinder\u002Fprovider-config.yaml`\n- Network access to passive DNS and certificate transparency sources\n- httpx or httprobe for validating discovered subdomains\n\n## Workflow\n\n### Step 1 — Install and Configure Subfinder\n```bash\n# Install subfinder\ngo install -v github.com\u002Fprojectdiscovery\u002Fsubfinder\u002Fv2\u002Fcmd\u002Fsubfinder@latest\n\n# Verify installation\nsubfinder -version\n\n# Configure API keys for enhanced results\nmkdir -p $HOME\u002F.config\u002Fsubfinder\ncat > $HOME\u002F.config\u002Fsubfinder\u002Fprovider-config.yaml \u003C\u003C 'EOF'\nshodan:\n  - YOUR_SHODAN_API_KEY\ncensys:\n  - YOUR_CENSYS_API_ID:YOUR_CENSYS_API_SECRET\nvirustotal:\n  - YOUR_VT_API_KEY\nsecuritytrails:\n  - YOUR_ST_API_KEY\nchaos:\n  - YOUR_CHAOS_API_KEY\nEOF\n```\n\n### Step 2 — Run Basic Subdomain Enumeration\n```bash\n# Single domain enumeration\nsubfinder -d example.com -o subdomains.txt\n\n# Multiple domains from a file\nsubfinder -dL domains.txt -o all_subdomains.txt\n\n# Use all passive sources (slower but more thorough)\nsubfinder -d example.com -all -o subdomains_all.txt\n\n# Silent mode for piping to other tools\nsubfinder -d example.com -silent | httpx -silent -status-code\n```\n\n### Step 3 — Filter and Customize Source Selection\n```bash\n# Use specific sources only\nsubfinder -d example.com -s crtsh,virustotal,shodan -o filtered.txt\n\n# Exclude specific sources\nsubfinder -d example.com -es github -o results.txt\n\n# Enable recursive subdomain enumeration\nsubfinder -d example.com -recursive -o recursive_subs.txt\n\n# Match specific patterns\nsubfinder -d example.com -m \"api,dev,staging\" -o matched.txt\n```\n\n### Step 4 — Control Rate Limiting and Output Format\n```bash\n# Rate limit to avoid API throttling\nsubfinder -d example.com -rate-limit 10 -t 5 -o rate_limited.txt\n\n# JSON output for programmatic processing\nsubfinder -d example.com -oJ -o subdomains.json\n\n# Output with source information\nsubfinder -d example.com -cs -o subdomains_with_sources.txt\n\n# Collect results in a directory per domain\nsubfinder -dL domains.txt -oD .\u002Fresults\u002F\n```\n\n### Step 5 — Validate Discovered Subdomains with httpx\n```bash\n# Pipe subfinder output to httpx for live validation\nsubfinder -d example.com -silent | httpx -silent -status-code -title -tech-detect -o live_hosts.txt\n\n# Check for specific ports\nsubfinder -d example.com -silent | httpx -ports 80,443,8080,8443 -o web_services.txt\n\n# Resolve IP addresses\nsubfinder -d example.com -silent | dnsx -a -resp -o resolved.txt\n```\n\n### Step 6 — Integrate with Broader Recon Pipeline\n```bash\n# Chain with nuclei for vulnerability scanning\nsubfinder -d example.com -silent | httpx -silent | nuclei -t cves\u002F -o vulns.txt\n\n# Combine with amass for comprehensive enumeration\nsubfinder -d example.com -o subfinder_results.txt\namass enum -passive -d example.com -o amass_results.txt\ncat subfinder_results.txt amass_results.txt | sort -u > combined_subdomains.txt\n\n# Screenshot discovered hosts\nsubfinder -d example.com -silent | httpx -silent | gowitness file -f - -P screenshots\u002F\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Passive Enumeration | Discovering subdomains without directly querying target DNS servers |\n| Certificate Transparency | Public logs of SSL\u002FTLS certificates revealing subdomain names |\n| DNS Aggregation | Collecting subdomain data from multiple passive DNS databases |\n| Recursive Enumeration | Discovering subdomains of subdomains for deeper coverage |\n| Source Providers | External APIs and databases queried for subdomain intelligence |\n| CNAME Records | Canonical name records that may reveal additional infrastructure |\n| Wildcard DNS | DNS configuration returning results for any subdomain query |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Subfinder | Primary passive subdomain enumeration engine |\n| httpx | HTTP probe tool for validating live subdomains |\n| dnsx | DNS resolution and validation toolkit |\n| Nuclei | Template-based vulnerability scanner for discovered hosts |\n| Amass | Complementary subdomain enumeration with active\u002Fpassive modes |\n| gowitness | Web screenshot utility for visual reconnaissance |\n| Shodan | Internet-wide scanning database for subdomain intelligence |\n| crt.sh | Certificate transparency log search engine |\n\n## Common Scenarios\n\n1. **Bug Bounty Reconnaissance** — Enumerate all subdomains of a target program scope to identify forgotten or misconfigured assets that may contain vulnerabilities\n2. **Attack Surface Mapping** — Build a comprehensive inventory of externally accessible subdomains for ongoing security monitoring and risk assessment\n3. **Cloud Asset Discovery** — Identify subdomains pointing to cloud services (AWS, Azure, GCP) that may be vulnerable to subdomain takeover\n4. **CI\u002FCD Integration** — Automate subdomain monitoring in pipelines to detect new subdomains and alert on changes to the attack surface\n5. **Merger & Acquisition Due Diligence** — Map the complete external footprint of an acquisition target during security assessment\n\n## Output Format\n\n```\n## Subdomain Enumeration Report\n- **Target Domain**: example.com\n- **Total Subdomains Found**: 247\n- **Live Hosts**: 183\n- **Unique IP Addresses**: 42\n- **Sources Used**: crt.sh, VirusTotal, Shodan, SecurityTrails, Censys\n\n### Discovered Subdomains\n| Subdomain | IP Address | Status Code | Technology |\n|-----------|-----------|-------------|------------|\n| api.example.com | 10.0.1.5 | 200 | Nginx, Node.js |\n| staging.example.com | 10.0.2.10 | 403 | Apache |\n| dev.example.com | 10.0.3.15 | 200 | Express |\n\n### Recommendations\n- Remove DNS records for decommissioned subdomains\n- Investigate subdomains with CNAME pointing to unclaimed services\n- Restrict access to development and staging environments\n```\n",{"name":5,"tags":44,"author":48,"domain":38,"license":15,"version":49,"category":5,"nist_csf":50,"subdomain":25,"description":7,"mitre_attack":55},[27,45,46,37,23,28,47],"reconnaissance","bug-bounty","osint","mahipal","1.0",[51,52,53,54],"PR.PS-01","ID.RA-01","PR.DS-10","DE.CM-01",[56,57,58,59,60],"T1190","T1059.007","T1505.003","T1083","T1595","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fperforming-subdomain-enumeration-with-subfinder",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":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill performing-subdomain-enumeration-with-subfinder",{"tool":75,"command":76},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill performing-subdomain-enumeration-with-subfinder",{"tool":78,"command":79},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill performing-subdomain-enumeration-with-subfinder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-subdomain-enumeration-with-subfinder\u002FSKILL.md",true,[83,89,94,100,104,108,114],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"assets\u002Ftemplate.md","ASSET","资产文件",1494,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-subdomain-enumeration-with-subfinder\u002Fassets\u002Ftemplate.md",{"path":90,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-subdomain-enumeration-with-subfinder\u002FLICENSE",{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fapi-reference.md","REFERENCE","参考文档",2097,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-subdomain-enumeration-with-subfinder\u002Freferences\u002Fapi-reference.md",{"path":101,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fstandards.md",1509,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-subdomain-enumeration-with-subfinder\u002Freferences\u002Fstandards.md",{"path":105,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fworkflows.md",1627,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-subdomain-enumeration-with-subfinder\u002Freferences\u002Fworkflows.md",{"path":109,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":112,"sourceHtmlUrl":113},"scripts\u002Fagent.py","SCRIPT","脚本",6602,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-subdomain-enumeration-with-subfinder\u002Fscripts\u002Fagent.py",{"path":115,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":116,"sourceHtmlUrl":117},"scripts\u002Fprocess.py",5827,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-subdomain-enumeration-with-subfinder\u002Fscripts\u002Fprocess.py",[119,150,175,197,213,232],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":130,"publishedAt":39},"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",[125],{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[131,132,133,134,135,136,38,137,138,139,140,141,142,143,144,145,146,147,148,149],"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":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":39},"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",[],[157,158,159,160,21,38,161,162,163,164,165,166,167,168,169,170,171,172,173,174],"vulnerabilities","framework","ssvc","triaging vulnerabilities with ssvc framework","triage and prioritize","CISA","vulnerability-management","risk-management","cvss","remediation","vulnerability","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":39},"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",[],[29,182,147,38,183,184,185,143,144,186,187,188,189,190,191,192,193,194,195,196],"triaging security incident","actions","soc","NIST","analysis","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","isolation","scope","impact","consistency",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":203,"publishedAt":39},"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",[],[29,204,205,182,147,21,38,206,184,140,207,208,143,144,209,187,170,210,211,212],"playbook","triaging security incident with ir playbook","teams","IR-playbook","severity","classification","classify","incidents","initiate",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":219,"publishedAt":39},"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",[],[29,220,221,222,223,224,38,225,226,227,184,228,143,229,230,231,190,30,147,34],"security alerts","splunk","triaging security alerts in splunk","alerts","review","siem","dashboard","search","correlation-search","t1566","notable-events","incident-review",{"skillNo":233,"name":234,"nameZh":6,"description":235,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":236,"categories":237,"keywords":238,"publishedAt":39},"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",[],[239,240,241,242,38,243,244,245,246,247,248,229,249,250,30,251,34,35,252,253],"infrastructure","tracking threat actor infrastructure","tracking","threat","monitoring","mitre-attack","threat-actor","threat-intelligence","command-and-control","dns","command","exploit","intelligence","kit","hosts"]