[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HCKFZXRPQJTK0290T7G2J9":3,"skill-same:01M6HCKFZXRPQJTK0290T7G2J9":115},{"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":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6HCKFZXRPQJTK0290T7G2J9","building-threat-hunt-hypothesis-framework",null,"Build a systematic threat hunt hypothesis framework that transforms threat intelligence, attack patterns, and environmental data into testable hunting hypotheses.","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-threat-hunt-hypothesis-framework\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"framework","hypothesis","building threat hunt hypothesis framework","threat","hunt","proactive","cybersecurity","hunting","transforms","de","id","systematic","build","cm","t1059","methodology","T1059.001","threat-hunting","threat-intelligence","threat intelligence","2026-11-10 10:12:30",false,"---\nname: building-threat-hunt-hypothesis-framework\ndescription: Build a systematic threat hunt hypothesis framework that transforms threat intelligence, attack patterns, and environmental data into testable hunting hypotheses.\ndomain: cybersecurity\nsubdomain: threat-hunting\ntags:\n- threat-hunting\n- methodology\n- hypothesis\n- threat-intelligence\n- hunting-framework\n- proactive-detection\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- DE.CM-01\n- DE.AE-02\n- DE.AE-07\n- ID.RA-05\nmitre_attack:\n- T1071\n- T1059.001\n- T1055\n- T1547\ncategory: building-threat-hunt-hypothesis-framework\n---\n# Building Threat Hunt Hypothesis Framework\n\n## When to Use\n\n- When proactively hunting for indicators of building threat hunt hypothesis framework in the environment\n- After threat intelligence indicates active campaigns using these techniques\n- During incident response to scope compromise related to these techniques\n- When EDR or SIEM alerts trigger on related indicators\n- During periodic security assessments and purple team exercises\n\n## Prerequisites\n\n- EDR platform with process and network telemetry (CrowdStrike, MDE, SentinelOne)\n- SIEM with relevant log data ingested (Splunk, Elastic, Sentinel)\n- Sysmon deployed with comprehensive configuration\n- Windows Security Event Log forwarding enabled\n- Threat intelligence feeds for IOC correlation\n\n## Workflow\n\n1. **Formulate Hypothesis**: Define a testable hypothesis based on threat intelligence or ATT&CK gap analysis.\n2. **Identify Data Sources**: Determine which logs and telemetry are needed to validate or refute the hypothesis.\n3. **Execute Queries**: Run detection queries against SIEM and EDR platforms to collect relevant events.\n4. **Analyze Results**: Examine query results for anomalies, correlating across multiple data sources.\n5. **Validate Findings**: Distinguish true positives from false positives through contextual analysis.\n6. **Correlate Activity**: Link findings to broader attack chains and threat actor TTPs.\n7. **Document and Report**: Record findings, update detection rules, and recommend response actions.\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| TA0001 | Initial Access |\n| TA0003 | Persistence |\n| TA0008 | Lateral Movement |\n| TA0010 | Exfiltration |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| CrowdStrike Falcon | EDR telemetry and threat detection |\n| Microsoft Defender for Endpoint | Advanced hunting with KQL |\n| Splunk Enterprise | SIEM log analysis with SPL queries |\n| Elastic Security | Detection rules and investigation timeline |\n| Sysmon | Detailed Windows event monitoring |\n| Velociraptor | Endpoint artifact collection and hunting |\n| Sigma Rules | Cross-platform detection rule format |\n\n## Common Scenarios\n\n1. **Scenario 1**: Intelligence-driven hunt based on APT campaign report\n2. **Scenario 2**: ATT&CK coverage gap analysis driving hypothesis creation\n3. **Scenario 3**: Anomaly-driven hypothesis from UEBA alert investigation\n4. **Scenario 4**: Situational awareness hunt based on industry sector threats\n\n## Output Format\n\n```\nHunt ID: TH-BUILDI-[DATE]-[SEQ]\nTechnique: TA0001\nHost: [Hostname]\nUser: [Account context]\nEvidence: [Log entries, process trees, network data]\nRisk Level: [Critical\u002FHigh\u002FMedium\u002FLow]\nConfidence: [High\u002FMedium\u002FLow]\nRecommended Action: [Containment, investigation, monitoring]\n```\n","# Building Threat Hunt Hypothesis Framework\n\n## When to Use\n\n- When proactively hunting for indicators of building threat hunt hypothesis framework in the environment\n- After threat intelligence indicates active campaigns using these techniques\n- During incident response to scope compromise related to these techniques\n- When EDR or SIEM alerts trigger on related indicators\n- During periodic security assessments and purple team exercises\n\n## Prerequisites\n\n- EDR platform with process and network telemetry (CrowdStrike, MDE, SentinelOne)\n- SIEM with relevant log data ingested (Splunk, Elastic, Sentinel)\n- Sysmon deployed with comprehensive configuration\n- Windows Security Event Log forwarding enabled\n- Threat intelligence feeds for IOC correlation\n\n## Workflow\n\n1. **Formulate Hypothesis**: Define a testable hypothesis based on threat intelligence or ATT&CK gap analysis.\n2. **Identify Data Sources**: Determine which logs and telemetry are needed to validate or refute the hypothesis.\n3. **Execute Queries**: Run detection queries against SIEM and EDR platforms to collect relevant events.\n4. **Analyze Results**: Examine query results for anomalies, correlating across multiple data sources.\n5. **Validate Findings**: Distinguish true positives from false positives through contextual analysis.\n6. **Correlate Activity**: Link findings to broader attack chains and threat actor TTPs.\n7. **Document and Report**: Record findings, update detection rules, and recommend response actions.\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| TA0001 | Initial Access |\n| TA0003 | Persistence |\n| TA0008 | Lateral Movement |\n| TA0010 | Exfiltration |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| CrowdStrike Falcon | EDR telemetry and threat detection |\n| Microsoft Defender for Endpoint | Advanced hunting with KQL |\n| Splunk Enterprise | SIEM log analysis with SPL queries |\n| Elastic Security | Detection rules and investigation timeline |\n| Sysmon | Detailed Windows event monitoring |\n| Velociraptor | Endpoint artifact collection and hunting |\n| Sigma Rules | Cross-platform detection rule format |\n\n## Common Scenarios\n\n1. **Scenario 1**: Intelligence-driven hunt based on APT campaign report\n2. **Scenario 2**: ATT&CK coverage gap analysis driving hypothesis creation\n3. **Scenario 3**: Anomaly-driven hypothesis from UEBA alert investigation\n4. **Scenario 4**: Situational awareness hunt based on industry sector threats\n\n## Output Format\n\n```\nHunt ID: TH-BUILDI-[DATE]-[SEQ]\nTechnique: TA0001\nHost: [Hostname]\nUser: [Account context]\nEvidence: [Log entries, process trees, network data]\nRisk Level: [Critical\u002FHigh\u002FMedium\u002FLow]\nConfidence: [High\u002FMedium\u002FLow]\nRecommended Action: [Containment, investigation, monitoring]\n```\n",{"name":5,"tags":44,"author":47,"domain":25,"license":15,"version":48,"category":5,"nist_csf":49,"subdomain":36,"description":7,"mitre_attack":54},[36,34,20,37,45,46],"hunting-framework","proactive-detection","mahipal","1.0",[50,51,52,53],"DE.CM-01","DE.AE-02","DE.AE-07","ID.RA-05",[55,35,56,57],"T1071","T1055","T1547","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fbuilding-threat-hunt-hypothesis-framework",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":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill building-threat-hunt-hypothesis-framework",{"tool":72,"command":73},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill building-threat-hunt-hypothesis-framework",{"tool":75,"command":76},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill building-threat-hunt-hypothesis-framework","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-threat-hunt-hypothesis-framework\u002FSKILL.md",true,[80,86,91,97,101,105,111],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"assets\u002Ftemplate.md","ASSET","资产文件",2664,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-threat-hunt-hypothesis-framework\u002Fassets\u002Ftemplate.md",{"path":87,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-threat-hunt-hypothesis-framework\u002FLICENSE",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fapi-reference.md","REFERENCE","参考文档",2199,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-threat-hunt-hypothesis-framework\u002Freferences\u002Fapi-reference.md",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fstandards.md",1629,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-threat-hunt-hypothesis-framework\u002Freferences\u002Fstandards.md",{"path":102,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fworkflows.md",3158,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-threat-hunt-hypothesis-framework\u002Freferences\u002Fworkflows.md",{"path":106,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":109,"sourceHtmlUrl":110},"scripts\u002Fagent.py","SCRIPT","脚本",6743,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-threat-hunt-hypothesis-framework\u002Fscripts\u002Fagent.py",{"path":112,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":113,"sourceHtmlUrl":114},"scripts\u002Fprocess.py",3584,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-threat-hunt-hypothesis-framework\u002Fscripts\u002Fprocess.py",[116,147,172,195,211,230],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":127,"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",[122],{"categoryNo":123,"categoryName":124,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[128,129,130,131,132,133,25,134,135,136,137,138,139,140,141,142,143,144,145,146],"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":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":153,"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",[],[154,19,155,156,157,25,158,159,160,161,162,163,164,165,166,167,168,169,170,171],"vulnerabilities","ssvc","triaging vulnerabilities with ssvc framework","with","triage and prioritize","CISA","vulnerability-management","risk-management","cvss","remediation","vulnerability","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"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",[],[179,180,144,25,181,182,183,140,141,184,185,186,187,188,189,190,191,192,193,194],"security","triaging security incident","actions","soc","NIST","analysis","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","isolation","scope","impact","consistency",{"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":201,"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",[],[179,202,203,180,144,157,25,204,182,137,205,206,140,141,207,185,167,208,209,210],"playbook","triaging security incident with ir playbook","teams","IR-playbook","severity","classification","classify","incidents","initiate",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":217,"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",[],[179,218,219,220,221,222,25,223,224,225,182,226,140,227,228,229,188,32,144,28],"security alerts","splunk","triaging security alerts in splunk","alerts","review","siem","dashboard","search","correlation-search","t1566","notable-events","incident-review",{"skillNo":231,"name":232,"nameZh":6,"description":233,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":234,"categories":235,"keywords":236,"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",[],[237,238,239,22,25,240,241,242,37,243,244,227,245,246,32,247,28,248,249,250],"infrastructure","tracking threat actor infrastructure","tracking","monitoring","mitre-attack","threat-actor","command-and-control","dns","command","exploit","intelligence","domains","kit","hosts"]