What It Does
Quarantine a cloud account or subscription — revoking roles and cutting peering — as one rehearsed action.
Observable indicator. A cloud account is 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 maneuverM8 Isolation / RetrogradeGive ground deliberately to preserve the force. Degrade gracefully; never fail open.
- Terrain layerT4 Applications and WorkloadsThe urban terrain. Key terrain: The public service portal, the case processing system, public APIs.
- Position in the form6 of 17M8 carries 17 cataloged techniques; this is the 6th 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.
- TM-4 Trust Zone DefinitionTerrain Management — To establish boundaries that something enforces, so that reachability and denied-path analysis rest on configuration rather than on design intent.
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-UAP User Account PermissionsIsolate tactic
- D3-AL Account LockingEvict 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 22 that share at least one control.
- 1 shared controlM1.06 Credential Exposure MonitoringM1 Screen / Guard · T1 Identity
- TA-4
- 1 shared controlM2.01 Trust Zone ArchitectureM2 Defense in Depth · T3 Networks
- TM-4
- 1 shared controlM4.01 MicrosegmentationM4 Obstacle / Canalization · T3 Networks
- TM-4
- 1 shared controlM4.07 Cloud Boundary EnforcementM4 Obstacle / Canalization · T3 Networks
- TM-4
- 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