operationalizing-a-hunt-into-a-detection
Converts a successful threat hunt into a durable detection by extracting the
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/operationalizing-a-hunt-into-a-detectionWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packagedffb7022…7a49137e
dffb7022d16a…449c7a49137e4 files · 3.0 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/operationalizing-a-hunt-into-a-detection@da7600a
On this page
When to Use
- A hunt surfaced malicious activity and you want to convert the discriminating logic into a repeatable detection (Sigma) with data sources, thresholds, and a tuning plan.
- You are closing the hunt→detect loop so the finding is caught automatically next time.
Do not use this to ship a rule without a false-positive review — operationalization includes tuning. The script generates rule scaffolding, not a deployment.
Prerequisites
- The hunt's discriminating fields/values, the data source/log channel, and the mapped ATT&CK technique.
Workflow
Step 1: Specify the detection
Define the logsource (category/product), the selection (field→value(s) that discriminated true positives), optional filters, the condition, and the ATT&CK technique.
Step 2: Generate the Sigma rule
python scripts/analyst.py generate --spec detection.json --out rule.ymlEmits a valid Sigma rule (title, status, logsource, detection, condition, level, tags) from the spec.
Step 3: Plan testing and tuning
Define how to validate (replay a known-true pcap/log, atomic test) and what benign sources may cause false positives.
Step 4: Document and stage
Record the rule's intent, expected FPs, and tuning levers; stage through your detection pipeline.
Validation
- The generated rule has logsource, detection, and condition keys.
- The selection encodes the fields/values that discriminated the hunt's true positives.
- The rule is tagged with the relevant ATT&CK technique.
Pitfalls
- Encoding incidental artifacts (one host's path) instead of generalizable logic.
- Omitting filters for known-benign sources, guaranteeing alert fatigue.
- No test plan, so regressions go unnoticed.
References
- See
references/api-reference.mdfor the rule generator. - Sigma specification and ATT&CK hunting resources (linked in frontmatter).
Files in this version
references/11.3 KB
- api-reference.md1.3 KB
scripts/12.7 KB
- analyst.py2.7 KB
- LICENSE340 B
- SKILL.md2.8 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumFile · Executable script shipped with the skillscripts/analyst.py
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v1.0.0 | Nov 13, 2026 | da7600a | dffb7022 | Signed | – |
More from meltedinhex
All from this publisher- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
More in DFIR and threat hunting
See the category- hunting-for-command-and-control-beaconingmukul975/hunting-for-command-and-control-beaconing5
- audit-context-buildingtrailofbits/audit-context-building4
- incident-response-forensicssecurityskills/incident-response-forensics3
- extracting-credentials-from-memory-dumpmukul975/extracting-credentials-from-memory-dump3
- analyzing-browser-forensics-with-hindsightmukul975/analyzing-browser-forensics-with-hindsight3
- forensics-ctfaeondave/forensics-ctf3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login