Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/mapping-hunts-to-mitre-attackReporting and compliance

mapping-hunts-to-mitre-attack

⁨Maps hunts and detections to MITRE ATT&CK for coverage analysis: tagging hypotheses⁩

v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/mapping-hunts-to-mitre-attack

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
DDiX4rOy1H…NIgzLgBA==The CLI checks the SHA-256 and the signature before it writes a file.
Package433e87ba…957a3e14
433e87bafa56…af96957a3e144 files · ⁦3.1 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/mapping-hunts-to-mitre-attack@da7600a

When to Use

  • You have a backlog of hunts/detections and want a coverage view by technique.
  • You need to prioritize the next hunt by mapping current coverage against relevant adversary TTPs (e.g., from a threat profile).
  • You want to produce an ATT&CK Navigator layer to visualize coverage and gaps.

Do not use technique counts as a quality metric — broad shallow coverage can hide weak detections; pair the map with detection confidence.

Prerequisites

  • An inventory of hunts/detections with the data sources each uses.
  • The ATT&CK enterprise matrix (technique IDs and tactics) for reference.

Workflow

Step 1: Tag each hunt with techniques

Annotate every hunt/detection with the ATT&CK technique(s) it covers and a confidence score (e.g., high/medium/low based on telemetry quality and FP rate).

Step 2: Build the coverage matrix

Aggregate tags into a technique → coverage map. Group by tactic to see where the kill chain is strong or thin.

bash
python scripts/analyst.py coverage hunts.json --out layer.json

Step 3: Overlay your threat model

Weight techniques by relevance (actors targeting your sector, observed in incidents). A gap on a high-relevance technique outranks a gap on an unlikely one.

Step 4: Identify and prioritize gaps

Surface techniques with no coverage or low confidence; rank by threat relevance and data availability to pick the next hunt.

Step 5: Visualize and share

Emit an ATT&CK Navigator layer (scores/colors) for stakeholders and to track progress over time.

Validation

  • Every hunt maps to at least one valid technique ID (^T\d{4}(\.\d{3})?$).
  • Coverage reflects confidence, not just presence/absence.
  • The Navigator layer loads and renders the intended scores.

Pitfalls

  • Counting a low-confidence hunt as full coverage.
  • Mapping to overly broad parent techniques when a sub-technique is more accurate.
  • Ignoring data-source feasibility when prioritizing gaps.

References

  • See references/api-reference.md for the coverage/layer generator.
  • ATT&CK Navigator and enterprise techniques (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600a433e87baSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login