Files
atomic-red-team/README.md
T

60 lines
4.3 KiB
Markdown
Raw Normal View History

2018-05-23 17:34:41 -06:00
<p><img src="https://redcanary.com/wp-content/uploads/Atomic-Red-Team-Logo.png" width="150px" /></p>
2017-10-19 13:27:16 -07:00
# Atomic Red Team
2018-05-10 13:25:40 -06:00
[![CircleCI](https://circleci.com/gh/redcanaryco/atomic-red-team.svg?style=svg)](https://circleci.com/gh/redcanaryco/atomic-red-team)
2017-10-19 13:27:16 -07:00
2018-06-13 19:33:59 -06:00
Atomic Red Team allows every security team to test their controls by executing simple
2018-06-21 08:54:17 -06:00
"atomic tests" that exercise the same techniques used by adversaries (all mapped to
[Mitre's ATT&CK](https://attack.mitre.org)).
2018-02-20 16:31:29 -05:00
2018-06-13 19:33:59 -06:00
## Philosophy
2017-10-19 13:32:26 -07:00
2018-06-13 19:33:59 -06:00
Atomic Red Team is a library of simple tests that every security team can execute to test their controls. Tests are
2020-08-11 13:35:09 -06:00
focused, have few dependencies, and are defined in a structured format that can be used by automation frameworks.
2017-10-19 13:32:26 -07:00
2018-06-13 19:33:59 -06:00
Three key beliefs made up the Atomic Red Team charter:
- **Teams need to be able to test everything from specific technical controls to outcomes.**
2018-06-21 08:54:17 -06:00
Our security teams do not want to operate with a “hopes and prayers” attitude toward detection. We need to know
what our controls and program can detect, and what it cannot. We dont have to detect every adversary, but we
2018-06-13 19:33:59 -06:00
do believe in knowing our blind spots.
2017-10-19 13:32:26 -07:00
2018-06-13 19:33:59 -06:00
- **We should be able to run a test in less than five minutes.**
2018-06-21 08:54:17 -06:00
Most security tests and automation tools take a tremendous amount of time to install, configure, and execute.
We coined the term "atomic tests" because we felt there was a simple way to decompose tests so most could be
2018-06-13 19:33:59 -06:00
run in a few minutes.
2017-10-19 13:32:26 -07:00
2018-06-13 19:33:59 -06:00
The best test is the one you actually run.
2017-10-19 13:32:26 -07:00
2018-06-13 19:33:59 -06:00
- **We need to keep learning how adversaries are operating.**
2018-06-21 08:54:17 -06:00
Most security teams dont have the benefit of seeing a wide variety of adversary types and techniques crossing
their desk every day. Even we at Red Canary only come across a fraction of the possible techniques being used,
2018-06-13 19:33:59 -06:00
which makes the community working together essential to making us all better.
2017-10-19 13:27:16 -07:00
2018-06-21 08:54:17 -06:00
See: https://atomicredteam.io
2017-10-19 13:27:16 -07:00
2018-06-13 19:33:59 -06:00
## Having trouble?
2017-10-19 13:27:16 -07:00
Join the community on Slack at [https://atomicredteam.slack.com](https://atomicredteam.slack.com) ([Request Invite](https://docs.google.com/forms/d/e/1FAIpQLSc3oMtugGy--6kcYiY52ZJQQ-iOaEy-UpxfSA37IlA5wCMV0A/viewform?usp=sf_link))
2017-10-19 13:27:16 -07:00
2018-06-13 19:33:59 -06:00
## Getting Started
2017-10-19 13:27:16 -07:00
* [Getting Started With Atomic Red Team](https://github.com/redcanaryco/atomic-red-team/wiki/About-Atomic-Red-Team)
2020-11-30 11:18:32 -05:00
* Automated Test Execution with the [Execution Frameworks](https://github.com/redcanaryco/atomic-red-team/wiki/Executing-Atomic-Tests#execute-an-atomic-test-with-an-execution-framework)
2020-08-19 09:29:26 -06:00
* Peruse the Complete list of Atomic Tests ([md](atomics/Indexes/Indexes-Markdown/index.md), [csv](atomics/Indexes/Indexes-CSV/index.csv)) and the [ATT&CK Matrix](atomics/Indexes/Matrices/matrix.md)
2020-04-03 11:36:55 -06:00
- Windows [Matrix](atomics/Indexes/Matrices/windows-matrix.md) and tests by tactic ([md](atomics/Indexes/Indexes-Markdown/windows-index.md), [csv](atomics/Indexes/Indexes-CSV/windows-index.csv))
- MacOS [Matrix](atomics/Indexes/Matrices/macos-matrix.md) and tests by tactic ([md](atomics/Indexes/Indexes-Markdown/macos-index.md), [csv](atomics/Indexes/Indexes-CSV/macos-index.csv))
- Linux [Matrix](atomics/Indexes/Matrices/linux-matrix.md) and tests by tactic ([md](atomics/Indexes/Indexes-Markdown/linux-index.md), [csv](atomics/Indexes/Indexes-CSV/linux-index.csv))
* Using [ATT&CK Navigator](https://github.com/mitre-attack/attack-navigator)? Check out our coverage layers ([All](atomics/Indexes/Attack-Navigator-Layers/art-navigator-layer.json), [Windows](atomics/Indexes/Attack-Navigator-Layers/art-navigator-layer-windows.json), [MacOS](atomics/Indexes/Attack-Navigator-Layers/art-navigator-layer-macos.json), [Linux](atomics/Indexes/Attack-Navigator-Layers/art-navigator-layer-linux.json))
* [Fork](https://github.com/redcanaryco/atomic-red-team/fork) and [Contribute](https://github.com/redcanaryco/atomic-red-team/wiki/Contributing) your own modifications
2018-06-13 19:33:59 -06:00
* Have questions? Join the community on Slack at [https://atomicredteam.slack.com](https://atomicredteam.slack.com)
2021-03-11 15:15:00 -08:00
* Need a Slack invitation? Submit an invite request via this [Google Form](https://docs.google.com/forms/d/e/1FAIpQLSc3oMtugGy--6kcYiY52ZJQQ-iOaEy-UpxfSA37IlA5wCMV0A/viewform?usp=sf_link)
2017-10-19 13:27:16 -07:00
2018-06-13 19:33:59 -06:00
## Code of Conduct
2017-10-19 13:27:16 -07:00
2018-06-13 19:33:59 -06:00
In order to have a more open and welcoming community, Atomic Red Team adheres to a
[code of conduct](CODE_OF_CONDUCT.md).
2017-10-19 13:27:16 -07:00
2018-06-13 19:33:59 -06:00
## License
2017-10-19 13:27:16 -07:00
2018-06-21 08:54:17 -06:00
See the [LICENSE](https://github.com/redcanaryco/atomic-red-team/blob/master/LICENSE.txt) file.