ASOM-Fedv6.1Open the explorer
M4.14 · M4 Obstacle / Canalization · 14 of 17

Control Protocol Constraint

What It Does

Permit only the industrial protocols and function codes the process requires, and deny engineering commands from outside the corridor.

Observable indicator. Write and program commands originate only from declared engineering stations.

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 maneuverM4 Obstacle / CanalizationForce the adversary onto ground you own and watch.
  • Terrain layerT6 Operational TechnologyGround you cannot maneuver freely on. Key terrain: Building control systems, laboratory and facility instrumentation, engineering workstations.
  • Position in the form14 of 17M4 carries 17 cataloged techniques; this is the 14th 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.

  • KT-5 Barrier SufficiencyKey Terrain and Decisive Points — To make the barriers on which negative reachability results depend into named, owned, monitored controls, so that the assurance KT-4 provides cannot be silently withdrawn.
  • FO-4 Operational Technology TerrainFederal Obligations — To stop operational technology being scored as though it were a server estate, and to make the connections between the two declarable.

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