mcpField
B
building-threat-hunt-hypothesis-framework

building-threat-hunt-hypothesis-framework

github.com/mukul975Security35.2k174 installsUpdated 8w ago
Repository

About building-threat-hunt-hypothesis-framework

A security skill for planning and conducting threat hunts from a testable hypothesis through evidence review and reporting. It is intended for analysts using SIEM and endpoint telemetry in threat-informed hunts, incident response, and security assessments.

Key features

  1. 01Formulate testable hunt hypotheses
  2. 02Identify required logs and telemetry
  3. 03Query SIEM and EDR data
  4. 04Correlate findings across sources
  5. 05Document evidence and response actions

Use cases

  1. 01Investigate campaigns described in threat intelligence
  2. 02Address gaps in ATT&CK coverage
  3. 03Examine anomalies raised by UEBA alerts
  4. 04Scope suspected compromise during incident response

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mukul975/anthropic-cybersecurity-skills --skill building-threat-hunt-hypothesis-framework

After installing, type/building-threat-hunt-hypothesis-frameworkin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

LICENSE
assets/
template.md
references/
api-reference.md
standards.md
workflows.md
scripts/
agent.py
process.py

Details

From the project README

Building Threat Hunt Hypothesis Framework

When to Use

  • When proactively hunting for indicators of building threat hunt hypothesis framework in the environment
  • After threat intelligence indicates active campaigns using these techniques
  • During incident response to scope compromise related to these techniques
  • When EDR or SIEM alerts trigger on related indicators
  • During periodic security assessments and purple team exercises

Prerequisites

  • EDR platform with process and network telemetry (CrowdStrike, MDE, SentinelOne)
  • SIEM with relevant log data ingested (Splunk, Elastic, Sentinel)
  • Sysmon deployed with comprehensive configuration
  • Windows Security Event Log forwarding enabled
  • Threat intelligence feeds for IOC correlation

Workflow

  1. Formulate Hypothesis: Define a testable hypothesis based on threat intelligence or ATT&CK gap analysis.
  2. Identify Data Sources: Determine which logs and telemetry are needed to validate or refute the hypothesis.
  3. Execute Queries: Run detection queries against SIEM and EDR platforms to collect relevant events.
  4. Analyze Results: Examine query results for anomalies, correlating across multiple data sources.
  5. Validate Findings: Distinguish true positives from false positives through contextual analysis.
  6. Correlate Activity: Link findings to broader attack chains and threat actor TTPs.
  7. Document and Report: Record findings, update detection rules, and recommend response actions.

Key Concepts

ConceptDescription
TA0001Initial Access
TA0003Persistence
TA0008Lateral Movement
TA0010Exfiltration

Tools & Systems

ToolPurpose
CrowdStrike FalconEDR telemetry and threat detection
Microsoft Defender for EndpointAdvanced hunting with KQL
Splunk EnterpriseSIEM log analysis with SPL queries
Elastic SecurityDetection rules and investigation timeline
SysmonDetailed Windows event monitoring
VelociraptorEndpoint artifact collection and hunting
Sigma RulesCross-platform detection rule format

Common Scenarios

  1. Scenario 1: Intelligence-driven hunt based on APT campaign report
  2. Scenario 2: ATT&CK coverage gap analysis driving hypothesis creation
  3. Scenario 3: Anomaly-driven hypothesis from UEBA alert investigation
  4. Scenario 4: Situational awareness hunt based on industry sector threats

Output Format

Hunt ID: TH-BUILDI-[DATE]-[SEQ]
Technique: TA0001
Host: [Hostname]
User: [Account context]
Evidence: [Log entries, process trees, network data]
Risk Level: [Critical/High/Medium/Low]
Confidence: [High/Medium/Low]
Recommended Action: [Containment, investigation, monitoring]

Comments

Markdown supported