What It Does
Bind every privileged account to a named, current, cleared human, so an orphaned credential has nowhere to hide.
Observable indicator. No privileged account exists without a named accountable holder.
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 layerT7 WorkforceTerrain that is also the force. Key terrain: Privileged humans, the roles that can approve a change, the separation pipeline.
- Position in the form19 of 20M3 carries 20 cataloged techniques; this is the 19th 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.
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-2 Privileged Human RegisterWorkforce Terrain — To ensure privilege is held by accountable people, so that every privileged action has a person behind it.
- WF-5 Separation and Revocation TempoWorkforce Terrain — To close the window between a person ceasing to be trusted and their access ceasing to work.
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.
- D3-DAM Domain Account MonitoringDetect tactic
- D3-LAM Local Account MonitoringDetect tactic
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.
- 1 shared controlM2.16 Role-Based Privilege MinimizationM2 Defense in Depth · T7 Workforce
- WF-2
- 1 shared controlM3.20 Supplier Identity FederationM3 Envelopment · T9 Supply Chain
- WF-2
- 1 shared controlM1.12 Workforce Credential Exposure MonitoringM1 Screen / Guard · T7 Workforce
- WF-2
- 1 shared controlM8.14 Rapid Offboarding and RevocationM8 Isolation / Retrograde · T7 Workforce
- WF-5
- 1 shared controlM8.17 Device Decommissioning and SanitizationM8 Isolation / Retrograde · T2 Devices
- WF-5