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

Supply Chain Lesson Propagation

What It Does

Feed what a supplier incident taught you back into acquisition and into the terrain register, so the next contract starts from it.

Observable indicator. Supplier incidents change the acquisition record, not only the ticket.

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 layerT9 Supply ChainThe lines of communication. Key terrain: Suppliers with production access, component provenance, the update path into the estate.
  • Position in the form7 of 7M10 carries 7 cataloged techniques; this is the 7th 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.

  • LC-1 Supplier Terrain RegisterLines of Communication — To make third parties positional, so that supplier risk is assessed against what a supplier can reach rather than against what they were contracted to do.
  • CG-5 Control Inheritance MappingCommand and Governance — To keep the framework additive, so that adopting it adds assessment effort only where it adds assessable content.
  • 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.

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.