Credential Transmission Scoping

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-CTS 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

• M3.16 Token Replay ProtectionM3 Envelopment · T1 Identity

  Bind issued tokens to sender and context so a captured token cannot be replayed from elsewhere.

• M4.14 Control Protocol ConstraintM4 Obstacle / Canalization · T6 Operational Technology

  Permit only the industrial protocols and function codes the process requires, and deny engineering commands from outside the corridor.

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.

• M3 EnvelopmentThe formMake identity, not network location, the decisive plane — surround the adversary with policy.
• M4 Obstacle / CanalizationThe formForce the adversary onto ground you own and watch.

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.