ASOM-Fedv6.1Open the explorer
M6.10 · M6 Delay · 10 of 10

Update Staging and Soak

What It Does

Hold vendor updates in a staging ring long enough to observe them, trading a little currency for the ability to not deploy a compromised build estate-wide.

Observable indicator. No supplier update reaches the whole estate without a stated soak period.

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 maneuverM6 DelayBuy decision time and prevent the adversary culminating on the objective.
  • Terrain layerT9 Supply ChainThe lines of communication. Key terrain: Suppliers with production access, component provenance, the update path into the estate.
  • Position in the form10 of 10M6 carries 10 cataloged techniques; this is the 10th 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.

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-4 Update Integrity and StagingLines of Communication — To limit the blast radius of a compromised trusted update, so that supply chain compromise reaches a ring rather than the estate.
  • LC-2 Component ProvenanceLines of Communication — To know where deployed components came from and what is inside them, so that a compromise disclosed anywhere can be located here.

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