ASOM-Fedv6.1Open the explorer
M1.10 · M1 Screen / Guard · 10 of 15

Named-Campaign Indicator Watch

What It Does

Maintain standing collection against the specific campaigns the intelligence requirements name, not against indicators in general.

Observable indicator. Every priority intelligence requirement has live collection against it.

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 maneuverM1 Screen / GuardGain early warning and buy reaction time before the adversary touches key terrain.
  • Terrain layerTX Cross-CuttingThe enablers of movement. Key terrain: The telemetry pipeline, the orchestration layer, the rules of engagement.
  • Position in the form10 of 15M1 carries 15 cataloged techniques; this is the 10th 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 IDeterVisible hardening, a deception grid, and a stated attribution posture.

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-2 Priority Intelligence RequirementsCycle Execution and Assurance — To direct analytic effort at named questions, so that collection and hunting answer what the accountable authority needs rather than processing what arrives.
  • CE-3 Fusion and ConfidenceCycle Execution and Assurance — To distinguish assessment from assertion, so that decisions taken on analytic conclusions carry the uncertainty of those conclusions with them.

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