Where It Sits in the Scheme
4 ASOM-Fed techniques reach this countermeasure, across 3 forms of maneuver.
This is the direction the forward mapping cannot answer. A reader who works in D3FEND arrives holding D3-BDI 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
- M2.01 Trust Zone ArchitectureM2 Defense in Depth · T3 Networks
Define trust zones that reflect real boundaries and assurance differences, and record which elements sit in which.
- M4.01 MicrosegmentationM4 Obstacle / Canalization · T3 Networks
Reduce reachability between workloads to what is declared, so lateral movement requires defeating policy rather than finding a route.
- M4.13 Operational Technology SegregationM4 Obstacle / Canalization · T6 Operational Technology
Separate control-system networks from the enterprise with an enforced, inspectable boundary rather than a documented intention.
- M8.01 Automated Segment SeveringM8 Isolation / Retrograde · T3 Networks
Hold a tested capability to sever a segment or zone on decision, without an unplanned outage of everything else.
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.
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.