ASOM-Fedv6.1Open the explorer
M5.09 · M5 Ambush · 9 of 13

Deception Alert Routing

What It Does

Route deception alerts on a separate, high-trust path that bypasses ordinary triage queues.

Observable indicator. Deception alerts reach a decision-maker without queueing.

Where It Sits

A technique is chosen from inside a form and emplaced on one layer. Both are the catalog’s own declarations; the position is counted in catalog order.

  • Form of maneuverM5 AmbushTrade space for information and time, and impose cost.
  • Terrain layerTX Cross-CuttingThe enablers of movement. Key terrain: The telemetry pipeline, the orchestration layer, the rules of engagement.
  • Position in the form9 of 13M5 carries 13 cataloged techniques; this is the 9th in catalog order.

Phases It Is Employed In

Employed in 2 of the campaign’s six phases. A phase named here means at least this technique is live in it — not that the form it belongs to is the main effort.

  • Phase IDeterVisible hardening, a deception grid, and a stated attribution posture.
  • Phase IIIDominateHunt, contain, evict.

Controls That Assess It

The controls the catalog names against this technique. They are what an assessor would test to establish that it is emplaced and working — the indicator above is what shows it is working, which is a different question.

  • CE-3 Fusion and ConfidenceCycle Execution and Assurance — To distinguish assessment from assertion, so that decisions taken on analytic conclusions carry the uncertainty of those conclusions with them.
  • TA-4 Pre-authorized ResponseTempo and Temporal Advantage — To remove authority latency from the decision loop, so that the segment most programs cannot shorten with tooling is shortened by governance.
  • SM-7 Deception EmplacementScheme of Maneuver — To obtain detection with no false-positive budget, and to ensure that signal is acted on rather than queued.
  • EN-1 Event Declaration and TriageEngagement and Pursuit — To convert raw events into a decided position quickly, since this is the segment of the decision loop that most often binds.

In MITRE D3FEND

What this technique is called in MITRE’s countermeasure ontology. The join runs technique-to-technique: D3FEND catalogs countermeasures, and the thing with a countermeasure’s shape here is the technique, not the control.

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.

Related Techniques

The catalog declares no relation for this entry, and no other entry names it — the inverse is derived here, so an incoming edge would show up even though this one never declared it. The techniques below share its assessment surface, which is the nearest adjacency the data supports.

Assessed Alongside

Not a declared relation: these are the techniques whose assessing controls overlap this one’s, ranked by how much of the two assessment surfaces coincide. Showing 6 of 34 that share at least one control.