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

Automated Segment Severing

What It Does

Hold a tested capability to sever a segment or zone on decision, without an unplanned outage of everything else.

Observable indicator. A zone can be severed inside the interval the plan assumes.

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 layerT3 NetworksThe corridors. Key terrain: TIC 3.0 access points, segment boundaries, cloud VPC peering.
  • Position in the form1 of 17M8 carries 17 cataloged techniques; this is the 1st 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.

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.
  • 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.
  • EN-4 Escalation and Engagement AuthorityEngagement and Pursuit — To remove the search for a decision-maker from the decision loop, which is where the decide segment is usually spent.

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