redcanaryco/atomic-red-team

Small and highly portable detection tests based on MITRE's ATT&CK.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 21 minutes ago
Added to GitGenius on September 4th, 2026
Created on October 11th, 2017
Open Issues & Pull Requests: 31 (+0)
GitHub issues: Enabled
Number of forks: 3,206
Total Stargazers: 12,495 (+0)
Total Subscribers: 370 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.3 days
Mean response time: 14.4 days
90th percentile: 31.1 days
Tracked items: 43

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 16% of issues opened in the past year have been closed. Three people close 67% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 47 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Stale (41)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Atomic Red Team is a library of portable detection tests mapped to the MITRE ATT&CK framework that security teams use to validate their defensive capabilities.

The tool addresses the challenge of testing whether security controls can detect known adversarial techniques. It provides small, self-contained tests that simulate tactics and procedures from the ATT&CK framework, allowing teams to execute them directly from the command line without installation and verify that their detection systems respond appropriately. Tests are organized by ATT&CK technique, making it straightforward to map coverage gaps to the framework.

Security teams should adopt this tool if they need to validate detection coverage across their environment in a reproducible, portable manner. It suits organizations that want to move beyond theoretical security assessments and run actual simulated attacks to confirm their monitoring and alerting work. The project acknowledges that for more sophisticated testing workflows, users may want to layer an execution framework like Invoke-Atomic on top of the atomic tests themselves.

The project maintains an active validation pipeline that checks atomics for correctness. Community contribution is actively encouraged through a dedicated Slack workspace, a structured contribution guide, and support for contributors working through GitHub Codespaces. The tool is open source and community developed, with a clear code of conduct and established processes for reporting issues and submitting new tests.