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

Phishing Deception and Reporting

What It Does

Exercise the workforce against realistic lures and treat the reporting rate, not the click rate, as the measure that matters.

Observable indicator. Reporting rate exceeds click rate and the first report arrives within minutes.

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 layerT7 WorkforceTerrain that is also the force. Key terrain: Privileged humans, the roles that can approve a change, the separation pipeline.
  • Position in the form12 of 13M5 carries 13 cataloged techniques; this is the 12th 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 0ShapeContinuous terrain preparation, zero-trust hardening, partnerships, threat intelligence.
  • Phase IDeterVisible hardening, a deception grid, and a stated attribution posture.

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.

  • WF-3 Role-Based ReadinessWorkforce Terrain — To prepare people for the attacks their role attracts, and to know whether the preparation worked.
  • CE-2 Priority Intelligence RequirementsCycle Execution and Assurance — To direct analytic effort at named questions, so that collection and hunting answer what the accountable authority needs rather than processing what arrives.
  • 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.

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 32 that share at least one control.