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/validating-detections-with-atomic-testsReporting and compliance

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-tests

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

SignatureSigned, ed25519
Fg9AYMezsA…B61xdLAg==The CLI checks the SHA-256 and the signature before it writes a file.
Packagece2407c2…a1e90d72
ce2407c288e0…dc39a1e90d724 files · ⁦2.7 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/validating-detections-with-atomic-tests@da7600a

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

bash
python scripts/analyst.py coverage --atomics atomics.json --detections detections.json

Joins 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.md for the coverage tool.
  • Atomic Red Team and ATT&CK references (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, 2026da7600ace2407c2Signed–

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