validating-detections-with-atomic-tests
Validates detection coverage by mapping Atomic Red Team tests to ATT&CK techniques,
v1.0.04 installazioni+4 in 7 giorni24 StelleApache-2.0sincronizzato 10 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/validating-detections-with-atomic-testsScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchettoce2407c2…a1e90d72
ce2407c288e0…dc39a1e90d724 file · 2.7 KBScansioneMedio2 segnalazioni
- Script eseguibile incluso nella skillscripts/analyst.py
- Link a domini esterni
Sorgentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/validating-detections-with-atomic-tests@da7600a
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
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).
File di questa versione
references/11.2 KB
- api-reference.md1.2 KB
scripts/12.5 KB
- analyst.py2.5 KB
- LICENSE340 B
- SKILL.md2.7 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | Sì | Sì |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- MediaFile · Script eseguibile incluso nella skillscripts/analyst.py
- InfoLink · Link a domini esterni
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v1.0.0 | 13 nov 2026 | da7600a | ce2407c2 | Firmata | – |
Altro da meltedinhex
Tutto da questo editore- 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
Altro in Report e compliance
Vai alla categoria- 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
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login