validating-detections-with-atomic-tests
Validates detection coverage by mapping Atomic Red Team tests to ATT&CK techniques,
v1.0.04 installs+4 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/validating-detections-with-atomic-testsWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packagece2407c2…a1e90d72
ce2407c288e0…dc39a1e90d724 files · 2.7 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/validating-detections-with-atomic-tests@da7600a
On this page
When to Use
- You want to validate that your detections fire for specific ATT&CK techniques by correlating Atomic Red Team test definitions with your detection inventory.
- You are measuring coverage and identifying gaps before or after running atomics.
Do not use the atomics themselves on production systems without authorization and isolation — they execute adversary behaviors. This skill performs mapping/coverage analysis offline.
Prerequisites
- An export of Atomic test→technique mappings (CSV/JSON) and your detection inventory mapped to ATT&CK techniques.
Workflow
Step 1: Compute coverage
python scripts/analyst.py coverage --atomics atomics.json --detections detections.jsonJoins atomic-tested techniques with your detections' covered techniques and reports covered vs uncovered techniques.
Step 2: Prioritize gaps
Rank uncovered techniques by the number of atomic tests (more atomics → more validated adversary behavior you currently miss).
Step 3: Validate live (authorized/isolated)
For covered techniques, run the corresponding atomic in an isolated range and confirm the detection fires; record results.
Step 4: Close gaps
Author detections for high-priority uncovered techniques and re-run coverage.
Validation
- Coverage join keys on ATT&CK technique IDs (including sub-techniques).
- Covered and uncovered technique lists are complete and disjoint.
- Gap prioritization reflects atomic-test counts.
Pitfalls
- Sub-technique vs parent-technique mismatch (T1059 vs T1059.001) skewing coverage.
- Claiming coverage from a rule that exists but is disabled/untuned.
- Running atomics outside an isolated, authorized range.
References
- See
references/api-reference.mdfor the coverage tool. - Atomic Red Team and ATT&CK references (linked in frontmatter).
Files in this version
references/11.2 KB
- api-reference.md1.2 KB
scripts/12.5 KB
- analyst.py2.5 KB
- LICENSE340 B
- SKILL.md2.7 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 | ce2407c2 | Signed | – |
More from meltedinhex
All from this publisher- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
- writing-a-malware-analysis-reportmeltedinhex/writing-a-malware-analysis-report3
More in Reporting and compliance
See the category- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
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