ASOM-Fedv6.1Open the explorer
M2.02 · M2 Defense in Depth · 2 of 18

Policy Enforcement Point Placement

What It Does

Place an enforcement point at every zone boundary so that crossing is a decision, not a route.

Observable indicator. No path reaches a higher-trust zone without transiting an enforcement point.

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 maneuverM2 Defense in DepthEnsure no single failure is decisive.
  • Terrain layerT3 NetworksThe corridors. Key terrain: TIC 3.0 access points, segment boundaries, cloud VPC peering.
  • Position in the form2 of 18M2 carries 18 cataloged techniques; this is the 2nd 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.

  • Phase 0ShapeContinuous terrain preparation, zero-trust hardening, partnerships, threat intelligence.

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.

  • TM-4 Trust Zone DefinitionTerrain Management — To establish boundaries that something enforces, so that reachability and denied-path analysis rest on configuration rather than on design intent.
  • KT-2 Decisive Point Protection FloorKey Terrain and Decisive Points — To ensure designation produces protection, so that identifying a decisive point is an act with consequences rather than an annotation.
  • ID-5 Authorization Decision IntegrityIdentity Terrain — To ensure the policy that governs movement is actually consulted and cannot be altered without trace.

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