ASOM-Fedv6.1Open the explorer
M11.11 · M11 Reconstitution · 11 of 11

Mailbox and Message Restoration

What It Does

Restore mailboxes and messages removed during eviction or lost in the incident, verified against an integrity record, before returning the service to use.

Observable indicator. Legitimate messages removed during response are restored and verified.

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 maneuverM11 ReconstitutionRestore the mission on evidence, not on hope — and prove it before you need it.
  • Terrain layerT4 Applications and WorkloadsThe urban terrain. Key terrain: The public service portal, the case processing system, public APIs.
  • Position in the form11 of 11M11 carries 11 cataloged techniques; this is the 11th 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 IVStabilizeEradicate, verify, and preserve availability through the recovery.
  • Phase VEnable / RestoreRecover, harden, and update the doctrine and the intelligence requirements.

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.

  • RC-4 Recovery Integrity VerificationReconstitution and Recovery — To ensure restoration returns the mission to a known-good state rather than reinstating the compromise.
  • EN-5 Eradication and Transition to RecoveryEngagement and Pursuit — To ensure the adversary is actually gone before the mission is restored, and that the transition is a decision rather than a drift.
  • RC-3 Trusted Rebuild PathReconstitution and Recovery — To ensure that what must not be lost can be rebuilt, from a source the adversary did not touch, inside the time the mission requires.

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