Breach and attack simulation

Breach and attack simulation (BAS) uses repeatable, authorized attack scenarios to evaluate how security defenses respond to specified adversary behaviors.

Turn a control question into a repeatable test

A BAS exercise can test whether a simulated behavior is blocked or produces the expected alert in an agreed environment. Automation helps repeat the test. It does not, by itself, tell you which systems or techniques are covered.

MITRE’s Micro Emulation Plans illustrate smaller technique-focused scenarios that can run in compatible BAS or automated emulation tools. Compatibility depends on the plan and implementation.

Follow the test from execution to response

For an authorized endpoint simulation, first check that the scenario actually ran. Then check for the endpoint event, the expected alert, and the team’s response.

If the event arrives but no alert appears, investigate that detection path. It does not mean every attacker would go undetected. If the simulation never ran, the result is untested, not a prevention success.

Know what the exercise covers

A technical simulation does not automatically test a help-desk callback procedure. That needs an explicitly scoped social engineering assessment. A red team may pursue a broader objective across several systems and decisions.

Repeatability is useful after a detection rule or configuration changes: rerunning the same scenario gives you a comparison. Keep the test conditions with both results so a change in the scenario is not mistaken for a change in the defense. Security validation explains how to interpret that evidence.

Sources

See it in practice