ASOM-Fedv6.1Open the explorer
M3.20 · M3 Envelopment · 20 of 20

Supplier Identity Federation

What It Does

Bring supplier access under the agency's own identity plane rather than standing local accounts the agency cannot see or revoke.

Observable indicator. Supplier access is revocable by the agency in one action.

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 maneuverM3 EnvelopmentMake identity, not network location, the decisive plane — surround the adversary with policy.
  • Terrain layerT9 Supply ChainThe lines of communication. Key terrain: Suppliers with production access, component provenance, the update path into the estate.
  • Position in the form20 of 20M3 carries 20 cataloged techniques; this is the 20th 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.

  • LC-3 Supplier Access ConstraintLines of Communication — To keep supplier access scoped, observable, and revocable by the agency rather than by the supplier.
  • WF-2 Privileged Human RegisterWorkforce Terrain — To ensure privilege is held by accountable people, so that every privileged action has a person behind it.

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