Where It Sits in the Scheme
2 ASOM-Fed techniques reach this countermeasure, across 1 form of maneuver.
This is the direction the forward mapping cannot answer. A reader who works in D3FEND arrives holding D3-RC and needs to know where it is employed in a scheme of maneuver — not which of MITRE's tactics it belongs to, which they already know.
Reached By
- M11.06 Service Restoration SequencingM11 Reconstitution · T4 Applications and Workloads
Restore in a declared order that respects dependency and statutory priority, so the first service back is the one that must be.
- M11.09 Alternate Facility ActivationM11 Reconstitution · T8 Facilities
Be able to run the mission from somewhere else, and prove it by doing so rather than by documenting it.
Forms That Arrive Here
A countermeasure reached from more than one form is employed more than one way. D3FEND has no notion of a form, so this join exists only here.
- M11 ReconstitutionThe formRestore the mission on evidence, not on hope — and prove it before you need it.
What This Does Not Claim
That a technique reaches a D3FEND countermeasure says the two describe the same defensive act. It does not say the countermeasure is deployed, configured, or working — that is an assessment finding about your estate, not a property of the framework.
MITRE's own entry for this technique is at d3fend.mitre.org, and it is the authority on what the countermeasure is. This page is the authority only on where it sits in ASOM-Fed. D3FEND™ and ATT&CK® are trademarks of The MITRE Corporation. This mapping is published by threatDefendr and is neither produced nor endorsed by MITRE.