Endpoint Health Beacon

Where It Sits in the Scheme

3 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-EHB 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.15 Device Estate DiscoveryM1 Screen / Guard · T2 Devices

  Discover devices reaching the estate from the identity plane outward rather than from the management console, because the console can only report what it already manages.

• M2.05 Endpoint Detection and Response CoverageM2 Defense in Depth · T2 Devices

  Achieve and prove sensor coverage across the managed fleet, with unmanaged devices treated as a measured gap rather than an assumption.

• M2.14 Control Failure DetectionM2 Defense in Depth · TX Cross-Cutting

  Detect when a control stops working — sensor silent, policy unapplied, agent removed — as a security event in its own right.

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.
• M2 Defense in DepthThe formEnsure no single failure is decisive.

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.