What It Does
Sever a host from the network on confirmed compromise while preserving it for analysis.
Observable indicator. Confirmed hosts are isolated inside the stated interval.
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 maneuverM7 CounterattackSeize the initiative and evict before the adversary reaches the objective.
- Terrain layerT2 DevicesThe entry fords. Key terrain: Mission-staff laptops, contractor devices, the server and VM fleet.
- Position in the form4 of 17M7 carries 17 cataloged techniques; this is the 4th 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.
- TA-4 Pre-authorized ResponseTempo and Temporal Advantage — To remove authority latency from the decision loop, so that the segment most programs cannot shorten with tooling is shortened by governance.
- TA-1 Decision Loop MeasurementTempo and Temporal Advantage — To make the defender's tempo a measured quantity rather than an impression, so that the numerator of temporal advantage exists at all.
- SM-4 Main Effort DesignationScheme of Maneuver — To concentrate defensive priority at a declared point, so that subordinate decisions follow from it without referral.
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-NI Network IsolationIsolate tactic
- D3-HS Host ShutdownEvict tactic
- D3-HR Host RebootEvict 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 23 that share at least one control.
- 2 shared controlsM3.11 Session and Token Revocation PathM3 Envelopment · T1 Identity
- TA-1
- TA-4
- 1 shared controlM1.05 Authentication Geography BaselineM1 Screen / Guard · T1 Identity
- TA-1
- 1 shared controlM1.06 Credential Exposure MonitoringM1 Screen / Guard · T1 Identity
- TA-4
- 1 shared controlM6.06 Tarpitting and Response DelayM6 Delay · T3 Networks
- TA-1
- 1 shared controlM7.05 Credential Reset SweepM7 Counterattack · T1 Identity
- TA-4
- 1 shared controlM8.05 Federation Trust SuspensionM8 Isolation / Retrograde · T1 Identity
- TA-4