ASOM-Fedv6.1Open the explorer
D3-IOPR · Isolate tactic · MITRE D3FEND v1.5.0

IO Port Restriction

Where It Sits in the Scheme

2 ASOM-Fed techniques reach this countermeasure, across 1 form of maneuver.

This is the direction the forward mapping cannot answer. A reader who works in D3FEND arrives holding D3-IOPR 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.09 Removable Media ControlM4 Obstacle / Canalization · T2 Devices

    Constrain and log removable media on endpoints holding or reaching decisive data.

  • M4.16 Maintenance Access ConstraintM4 Obstacle / Canalization · T8 Facilities

    Force vendor and remote maintenance onto a supervised, time-boxed path instead of standing access into the estate.

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.

  • 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.