JB
1eaae6d3ce
* Create T1595.002.yaml * Added vbscript (griffon recon) for test 1 Script ref. (public gist) https://gist.githubusercontent.com/kirk-sayre-work/1a9476e7708ed650508f9fb5adfbad9d/raw/55ecbf8f83c36984371a335991f6cf4f2022319b/gistfile1.txt * added run as priv user n/a * removed guid accidentally put in * removed extra line * checking syntax final * remove dependency line * minor updates to invoke the build process again * removing elevation required thanks for that additional review, carrie * moving to T1082 per review * adding test 8 (griffon recon) * create griffon_recon.vbs for test 8 script used here was reduced by security researcher Kirk Sayre (github.com/kirk-sayre-work/1a9476e7708ed650508f9fb5adfbad9d), and it gives the exact same recon behavior, hash mentioned in the code, as the original (minus the C2 interaction). * moving vbs file to T1082 per review 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 can 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 Red Team
- Automated Test Execution with the Execution Frameworks
- Peruse the Complete list of Atomic Tests (md, csv) and the ATT&CK Matrix
- Using ATT&CK Navigator? Check out our coverage layers (All, Windows, MacOS, Linux)
- 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.