ASOM-Fedv6.1Open the explorer
M10.03 · M10 Exploitation & Pursuit · 3 of 7

Terrain Overlay Update

What It Does

Update the terrain overlay with what contact revealed, including everything the map got wrong.

Observable indicator. The overlay reflects the estate as contact proved it to be.

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 maneuverM10 Exploitation & PursuitConvert contact into durable advantage rather than closing the ticket.
  • Terrain layerTX Cross-CuttingThe enablers of movement. Key terrain: The telemetry pipeline, the orchestration layer, the rules of engagement.
  • Position in the form3 of 7M10 carries 7 cataloged techniques; this is the 3rd in catalog order.

Phases It Is Employed In

Employed in one phase of the campaign. 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 VEnable / RestoreRecover, harden, and update the doctrine and the intelligence requirements.

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.

  • TM-1 Terrain Inventory and OverlayTerrain Management — To establish one authoritative positional picture of the estate, so that every later judgment about priority, reachability and risk is made against the same ground.
  • TM-6 Terrain CurrencyTerrain Management — To keep the overlay current against both the clock and the change, so that planning is conducted against ground as it currently is.
  • EN-2 Engagement ReconstructionEngagement and Pursuit — To establish what actually happened, since every consolidation activity depends on a reconstruction and none of them can be performed without one.

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