Operational Dependency Mapping

Where It Sits in the Scheme

2 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-ODM 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

• M1.09 Supply Chain and Vendor WatchM1 Screen / Guard · TX Cross-Cutting

  Track the security posture and incident disclosures of vendors and integrators whose products sit on key terrain.

• M11.01 Recovery Objective DeclarationM11 Reconstitution · T4 Applications and Workloads

  Declare, per mission service, how quickly it must return and how much data loss is survivable — before an incident forces the answer.

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.

• M1 Screen / GuardThe formGain early warning and buy reaction time before the adversary touches key terrain.
• 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.