ASOM-Fedv6.1Open the explorer
M9.04 · M9 Spoiling Attack · 4 of 9

Sector Intelligence Exchange

What It Does

Contribute and consume in the sector and federal exchanges so pre-emption is possible at all.

Observable indicator. The agency both receives and contributes actionable reporting.

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 maneuverM9 Spoiling AttackDisrupt adversary staging before the attack is launched.
  • Terrain layerTX Cross-CuttingThe enablers of movement. Key terrain: The telemetry pipeline, the orchestration layer, the rules of engagement.
  • Position in the form4 of 9M9 carries 9 cataloged techniques; this is the 4th 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 0ShapeContinuous terrain preparation, zero-trust hardening, partnerships, threat intelligence.
  • 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.

  • CE-7 Brief Generation and DistributionCycle Execution and Assurance — To produce one document per cycle that an Authorizing Official can decide from, rather than a dashboard nobody decides from.
  • CG-5 Control Inheritance MappingCommand and Governance — To keep the framework additive, so that adopting it adds assessment effort only where it adds assessable content.
  • EN-6 Engagement CommunicationEngagement and Pursuit — To ensure the people who must know, do — inside the agency, across the federal community, and among those the mission serves.

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