Michael Haag 5832c65cb2 T1014 - Driver Rootkit Test Update (#1303)
* T1014 - Driver rootkit test

Fixed Test 3 per issue #1153 .
- Added pre-req
- New comments for additional info on retrieving the capcom driver
- Added elevation required
- Added new input argument for puppetstrings.exe

Confirmed operational on win10.

* Generate docs from job=validate_atomics_generate_docs branch=T1014

* Fixed GUID

* Generate docs from job=validate_atomics_generate_docs branch=T1014

* Update used_guids.txt

Co-authored-by: CircleCI Atomic Red Team doc generator <email>
2020-11-30 14:34:25 -07:00
2020-05-08 00:35:40 -06:00
2020-07-16 09:10:35 -06:00
2020-10-24 08:39:37 -06:00
2018-06-13 19:33:59 -06:00
2018-06-13 19:33:59 -06:00
2020-11-30 09:18:32 -07:00

Atomic Red Team

CircleCI

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 dont 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 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, which makes the community working together essential to making us all better.

See: https://atomicredteam.io

Having trouble?

Join the community on Slack at https://atomicredteam.slack.com

Getting Started

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.

S
Description
Atomic Red Team test automation and mapping
Readme 563 MiB
Languages
C 38.7%
PowerShell 13.3%
Go 11.4%
Java 7.8%
C# 6.8%
Other 21.7%