| name | performing-purple-team-atomic-testing |
| description | Use when executing Atomic Red Team tests mapped to MITRE ATT&CK techniques, performing coverage gap analysis across the ATT&CK matrix, and running detection validation loops to measure blue team visibility. Covers Invoke-AtomicRedTeam PowerShell execution, ATT&CK Navigator layer generation for heatmaps, Sigma rule correlation, and continuous atomic testing pipelines. |
| domain | cybersecurity |
| tags | ["purple-team","atomic-red-team","mitre-attack","detection-engineering","adversary-emulation"] |
| subdomain | purple-team |
| version | 1.0.0 |
| author | oyi77 |
| license | Apache-2.0 |
| nist_ai_rmf | ["MEASURE-2.7","MAP-5.1","MANAGE-2.4"] |
| atlas_techniques | ["AML.T0070","AML.T0066","AML.T0082"] |
| d3fend_techniques | ["Executable Denylisting","Execution Isolation","File Metadata Consistency Validation","Content Format Conversion","File Content Analysis"] |
| nist_csf | ["ID.RA-01","DE.AE-07","GV.OV-02"] |
Performing Purple Team Atomic Testing
Overview
Cybersecurity skill for performing purple team atomic testing. Follows industry best practices and security standards.
When to Use
Trigger phrases:
-
"performing purple team atomic testing"
-
"Use when working with performing purple team atomic testing"
-
Validating detection coverage against specific MITRE ATT&CK techniques
-
Running purple team exercises using Atomic Red Team test library
-
Performing ATT&CK coverage gap analysis to identify blind spots in SIEM/EDR
-
Building a detection validation loop: execute atomic test, check SIEM, tune rule, retest
-
Generating ATT&CK Navigator heatmap layers for executive reporting
-
Automating continuous atomic testing in CI/CD or scheduled pipelines
-
Mapping threat intelligence reports to executable atomic tests
Do not use for full-scope red team engagements requiring custom implants or live adversary simulation beyond atomic tests; use Caldera, SCYTHE, or Cobalt Strike for advanced adversary emulation.
DISCLAIMER: Atomic Red Team tests execute real attack techniques. Run only on systems you own or have explicit written authorization to test. Many tests modify system state, create artifacts, or trigger security alerts. Always execute cleanup commands after testing. Never run atomic tests in production without risk acceptance from stakeholders.
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- Windows host with PowerShell 5.1+ or PowerShell Core 7+ (Linux/macOS supported for cross-platform atomics)
- Invoke-AtomicRedTeam PowerShell module installed from PSGallery
- Atomic Red Team atomics repository cloned locally
- SIEM/EDR with log ingestion from test endpoints (Splunk, Elastic, Microsoft Sentinel, CrowdStrike)
- MITRE ATT&CK Navigator (web-based or local instance) for layer visualization
- Python 3.9+ with
mitreattack-python, pyyaml, and requests for automation scripts
- Sigma rules repository for detection correlation
- Administrative/root access on test endpoints
- Isolated test environment (lab, sandbox, or dedicated test range)
