Where It Sits in the Scheme
4 ASOM-Fed techniques reach this countermeasure, across 2 forms of maneuver.
This is the direction the forward mapping cannot answer. A reader who works in D3FEND arrives holding D3-NTF 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
- M4.02 East-West Deny by DefaultM4 Obstacle / Canalization · T3 Networks
Make the default answer between segments "no", with exceptions declared, owned and expiring.
- M4.11 Protocol and Port RestrictionM4 Obstacle / Canalization · T3 Networks
Permit only the protocols the design requires, and treat the rest as a canalization opportunity.
- M4.12 Denied-Path Register EnforcementM4 Obstacle / Canalization · T3 Networks
Maintain the explicit register of paths that must never exist, and test continuously that they do not.
- M8.10 Third-Party Connection CutoutM8 Isolation / Retrograde · T3 Networks
Cut a specific partner or vendor connection on decision without taking down the shared boundary.
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.