Matt Graeber
d0687be58c
* Refactoring and adding test cases for T1118 Developed a new test harness for InstallUtil variant execution and built many new tests around it. * T1118 test refactoring and documentation * All installer assemblies now output to %TEMP% by default so as to not pollute an atomics directory. * Get-CommandLineArgument and Invoke-BuildAndInvokeInstallUtilAssembly are now fully documented. * Cleanup commands added * Any mention of payload was removed. This isn't offensive code and we should give that impression. * Removed Rollback and Commit methods from the installer source code. I do not see it as a necessity to test this functionality. Co-authored-by: Matt Graeber <mattifestation@users.noreply.github.com> Co-authored-by: Carrie Roberts <clr2of8@gmail.com>
Atomic Red Team
Atomic Red Team allows every security team to test their controls by executing simple "atomic tests" that exercise the same techniques used by adversaries (all mapped to Mitre's ATT&CK).
Philosophy
Atomic Red Team is a library of simple tests that every security team can execute to test their controls. Tests are focused, have few dependencies, and are defined in a structured format that be used by automation frameworks.
Three key beliefs made up the Atomic Red Team charter:
-
Teams need to be able to test everything from specific technical controls to outcomes. 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 don’t have to detect every adversary, but we do believe in knowing our blind spots.
-
We should be able to run a test in less than five minutes. 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 run in a few minutes.
The best test is the one you actually run.
-
We need to keep learning how adversaries are operating. Most security teams don’t 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, which makes the community working together essential to making us all better.
Having trouble?
Join the community on Slack at https://atomicredteam.slack.com
Getting Started
- Getting Started With Atomic Tests
- Automated Test Execution with the Execution Frameworks
- Peruse the Complete list of Atomic Tests and the ATT&CK Matrix
- Using ATT&CK Navigator? Check out our coverage layer
- Fork and Contribute your own modifications
- Have questions? Join the community on Slack at https://atomicredteam.slack.com
- Need a Slack invitation? Grab one at https://slack.atomicredteam.io/
Code of Conduct
In order to have a more open and welcoming community, Atomic Red Team adheres to a code of conduct.
License
See the LICENSE file.