What It Does
Sever the control network to a defined safe state that preserves the physical process, rather than a network state that abandons it.
Observable indicator. Isolation leaves the process safe, not merely disconnected.
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 layerT6 Operational TechnologyGround you cannot maneuver freely on. Key terrain: Building control systems, laboratory and facility instrumentation, engineering workstations.
- Position in the form13 of 17M8 carries 17 cataloged techniques; this is the 13th 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 IIIDominateHunt, contain, evict.
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.
- SM-5 Branches and SequelsScheme of Maneuver — To decide contingency responses before contact, so that the decision loop under pressure is a selection rather than a design exercise.
- FO-4 Operational Technology TerrainFederal Obligations — To stop operational technology being scored as though it were a server estate, and to make the connections between the two declarable.
- RC-1 Recovery ObjectivesReconstitution and Recovery — To establish what recovery must achieve, so that restoration can succeed or fail rather than simply take however long it takes.
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.
- D3-OMM Operating Mode MonitoringDetect tactic
- D3-OPR Operating Mode RestrictionIsolate tactic
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 19 that share at least one control.
- 1 shared controlM2.13 Backup Isolation and ImmutabilityM2 Defense in Depth · T5 Data
- SM-5
- 1 shared controlM2.15 Safety Instrumented Layer IntegrityM2 Defense in Depth · T6 Operational Technology
- FO-4
- 1 shared controlM4.14 Control Protocol ConstraintM4 Obstacle / Canalization · T6 Operational Technology
- FO-4
- 1 shared controlM7.05 Credential Reset SweepM7 Counterattack · T1 Identity
- SM-5
- 1 shared controlM7.14 Process Anomaly HuntingM7 Counterattack · T6 Operational Technology
- FO-4
- 1 shared controlM8.03 Read-Only Service DegradationM8 Isolation / Retrograde · T4 Applications and Workloads
- SM-5