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-CRO 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.12 Secrets ManagementM2 Defense in Depth · T4 Applications and Workloads
Remove long-lived secrets from code, images and configuration into brokered, rotated, audited storage.
- M3.04 Just-in-Time PrivilegeM3 Envelopment · T1 Identity
Grant privilege for a bounded task and window, with the grant itself recorded as an event.
- M3.06 Machine and Service Identity GovernanceM3 Envelopment · T1 Identity
Give non-human identities owners, expiry and scope on the same terms as human ones.
- M7.05 Credential Reset SweepM7 Counterattack · T1 Identity
Execute a scoped, ordered reset of credentials and tokens across the compromised blast radius.
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.