Adversary emulation
Adversary emulation is an authorized assessment that models documented attacker behavior to evaluate how defenses perform against selected threats.
Reproduce the behavior that matters
Adversary emulation starts with threat reporting and asks how to reproduce selected attacker behaviors in an authorized exercise. MITRE’s emulation plans allow different tools to exhibit the same behavior. The purpose is to test defenses against how an adversary operates, rather than only whether a known file or indicator gets flagged.
The choice of implementation still matters. If a substitute tool produces different events, a result may say more about that tool than the behavior you meant to examine. Describe the substitutions so defenders can interpret what they saw.
Separate reported activity from exercise assumptions
Public reporting rarely captures every step of an intrusion. MITRE acknowledges that limitation in its prototype plans. Keep the reported behaviors separate from the assumptions used to join them into a runnable exercise.
The UNC3944 recovery-abuse article is a useful starting point for thinking about a support-led entry route. An exercise limited to the recovery decision can examine verification and escalation; later access needs its own permitted steps.
An emulation need not recreate a whole campaign. MITRE’s library includes full plans and smaller micro emulations focused on selected behaviors. Choose the extent that answers the defensive question.
Where red teaming and BAS fit
A red team can use adversary emulation while pursuing an objective. Breach and attack simulation can automate repeatable scenarios. Emulation supplies the threat model for the activity; it does not prescribe one tool or engagement format.