Read-Only Service Degradation

What It Does

Degrade mission services to read-only or queued operation rather than exposing or losing the corpus.

Observable indicator. Service degrades gracefully instead of failing open or dark.

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 form3 of 17M8 carries 17 cataloged techniques; this is the 3rd 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 IIIDominateHunt, contain, evict.
• Phase IVStabilizeEradicate, verify, and preserve availability through the recovery.

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.
• TA-5 Tempo Degradation TriggerTempo and Temporal Advantage — To plan for the periods in which tempo predictably falls, so that the measured advantage is not a statement about the organization's best hours only.

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-OPR Operating Mode RestrictionIsolate tactic
• D3-PS Process SuspensionEvict tactic
• D3-PT Process TerminationEvict 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 16 that share at least one control.

• 1 shared controlM2.13 Backup Isolation and ImmutabilityM2 Defense in Depth · T5 Data
  • SM-5
• 1 shared controlM6.01 Adaptive Rate LimitingM6 Delay · T4 Applications and Workloads
  • TA-5
• 1 shared controlM6.03 Bulk Export ThrottlingM6 Delay · T5 Data
  • TA-5
• 1 shared controlM6.06 Tarpitting and Response DelayM6 Delay · T3 Networks
  • TA-5
• 1 shared controlM6.07 Progressive LockoutM6 Delay · T1 Identity
  • TA-5
• 1 shared controlM6.08 Change and Deploy Freeze Under ContactM6 Delay · T4 Applications and Workloads
  • TA-5