What It Does
Baseline where, when and from what the population legitimately authenticates, so deviation is measurable rather than anecdotal.
Observable indicator. Account-takeover precursors are detected on deviation, not on damage.
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 layerT1 IdentityThe high ground. Key terrain: The ICAM policy decision point, privileged accounts, external-user and mission-staff identities.
- Position in the form5 of 15M1 carries 15 cataloged techniques; this is the 5th 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 IISeize InitiativeDetect early, canalize movement, and buy decision time.
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.
- CE-2 Priority Intelligence RequirementsCycle Execution and Assurance — To direct analytic effort at named questions, so that collection and hunting answer what the accountable authority needs rather than processing what arrives.
- TA-1 Decision Loop MeasurementTempo and Temporal Advantage — To make the defender's tempo a measured quantity rather than an impression, so that the numerator of temporal advantage exists at all.
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-ID Identifier AnalysisDetect tactic
- D3-IAA Identifier Activity AnalysisDetect tactic
- D3-UBA User Behavior AnalysisDetect tactic
- D3-UGLPA User Geolocation Logon Pattern AnalysisDetect 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 6 of 32 that share at least one control.
- 2 shared controlsM1.08 Public Service Abuse TelemetryM1 Screen / Guard · T4 Applications and Workloads
- CE-2
- TA-1
- 2 shared controlsM5.02 Honeytokens in Document StoresM5 Ambush · T5 Data
- CE-2
- TA-1
- 2 shared controlsM5.05 Canary Files on EndpointsM5 Ambush · T2 Devices
- CE-2
- TA-1
- 1 shared controlM1.04 Perimeter Canary TokensM1 Screen / Guard · T5 Data
- CE-2
- 1 shared controlM1.06 Credential Exposure MonitoringM1 Screen / Guard · T1 Identity
- CE-2
- 1 shared controlM1.07 Partner and Advisory IntakeM1 Screen / Guard · TX Cross-Cutting
- CE-2