Inbound Traffic Filtering

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-ITF 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.07 Web Application ProtectionM2 Defense in Depth · T4 Applications and Workloads

  Front public applications with request-level inspection tuned to the application, not to a generic ruleset.

• M4.11 Protocol and Port RestrictionM4 Obstacle / Canalization · T3 Networks

  Permit only the protocols the design requires, and treat the rest as a canalization opportunity.

• M6.01 Adaptive Rate LimitingM6 Delay · T4 Applications and Workloads

  Slow request rates as risk rises, so automation loses its advantage while humans keep service.

• M6.06 Tarpitting and Response DelayM6 Delay · T3 Networks

  Introduce deliberate latency on suspicious paths, so an adversary spends time you are spending on decision.

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.

• M2 Defense in DepthThe formEnsure no single failure is decisive.
• M4 Obstacle / CanalizationThe formForce the adversary onto ground you own and watch.
• M6 DelayThe formBuy decision time and prevent the adversary culminating on the objective.

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.