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

Workforce Credential Exposure Monitoring

What It Does

Watch the outside world for agency credentials and staff identities appearing where they should not, on the same cadence you watch the network perimeter.

Observable indicator. Exposed staff credentials are found and revoked before they are used.

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 layerT7 WorkforceTerrain that is also the force. Key terrain: Privileged humans, the roles that can approve a change, the separation pipeline.
  • Position in the form12 of 15M1 carries 15 cataloged techniques; this is the 12th 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.

  • WF-1 Workforce Terrain IdentificationWorkforce Terrain — To make the workforce positional, so that defensive effort concentrates on the roles an adversary would actually target.
  • WF-2 Privileged Human RegisterWorkforce Terrain — To ensure privilege is held by accountable people, so that every privileged action has a person behind it.
  • TM-6 Terrain CurrencyTerrain Management — To keep the overlay current against both the clock and the change, so that planning is conducted against ground as it currently is.

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