BaffledJimmy 799ea20a95 Amend regkey path for Macro security level (#1515)
* Amend regkey path for Macro security level

As shown in this image - https://www.mdsec.co.uk/wp-content/uploads/2020/11/image-2-768x191.png.webp - the correct regkey is \Level\. The existing ```reg add``` syntax will not create a Level value with a DWORD of 4 (disable all).  Also changed the regkey to 1 (enable all macros without notif).

```
4 = Disable all macros without notification
3 = Notifications for digitally signed macros, all other macros disabled
2 = Notifications for all macros
1 = Enable all Macros
```

* Update T1137.yaml

* Update T1137.md
2021-06-15 22:39:17 -06:00
2020-07-16 09:10:35 -06:00
2021-06-04 14:30:15 -07:00
2021-04-01 10:50:37 -06:00
2021-03-12 10:02:09 -08:00
2018-06-13 19:33:59 -06:00
2018-06-13 19:33:59 -06:00
2021-03-11 15:15:00 -08: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%