Posture check · Entra ID and hybrid
Federated domain trusts the identity provider's multifactor check (T1556.007)
A federated domain accepts the multifactor check done by its identity provider, so Microsoft Entra skips its own.
Why it matters
An attacker who controls the federation server can issue tokens that claim multifactor was done, which defeats the requirement.
How GraphnAI finds it
It runs after every sync, on each connected domain or tenant on its own. It applies to Microsoft Entra ID.
It reads:
- 2 more GraphnAI analyses
Tiered Fidelity™ level: Theoretical
Every finding from this check carries the Theoretical level.
- TheoreticalThis checkConfigured in the directory. Nothing else checked.
- ConstrainedA constraint on it has been checked.
- ValidatedTelemetry has seen it in use.
Why there's no automatic fix
GraphnAI doesn't change federation settings yet.
How to fix it
Set the domain's multifactor behavior for the federated identity provider to "Always require Microsoft Entra multifactor". The federatedIdpMfaBehavior property of its federation configuration sets it through Microsoft Graph.
MITRE ATT&CK® technique names and MITRE D3FEND™ technique labels: © The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. ATT&CK® is a registered trademark and D3FEND™ a trademark of The MITRE Corporation.
See it on your own directory.
The Public Preview is free for 30 days from your first sync, on your own server.