ASOM-Fedv6.1Open the explorer
M8.17 · M8 Isolation / Retrograde · 17 of 17

Device Decommissioning and Sanitization

What It Does

Remove a retired, lost or reassigned device from the estate's trust and sanitize its media within a period derived from what its retained trust could do.

Observable indicator. No device holds estate trust without a current accountable holder.

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 maneuverM8 Isolation / RetrogradeGive ground deliberately to preserve the force. Degrade gracefully; never fail open.
  • Terrain layerT2 DevicesThe entry fords. Key terrain: Mission-staff laptops, contractor devices, the server and VM fleet.
  • Position in the form17 of 17M8 carries 17 cataloged techniques; this is the 17th 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 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.

  • DV-5 Device Lifecycle and SanitizationDevices Terrain — To close the ends of the device lifecycle — the point of entry and the point of exit — where trust is granted and where it is most often left behind.
  • WF-5 Separation and Revocation TempoWorkforce Terrain — To close the window between a person ceasing to be trusted and their access ceasing to work.
  • TM-7 Terrain OwnershipTerrain Management — To attach every element to a person who can be asked to act, so that findings convert into work rather than accumulating.

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