Identity-and-Access - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/tags/identity-and-access/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioThu, 10 Sep 2026 18:47:58 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgEntra ID Windows Hello for Business Credential Registration Persistencehttps://feed.craftedsignal.io/briefs/2026-09-entra-id-whfb-persistence/Thu, 10 Sep 2026 18:47:58 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-09-entra-id-whfb-persistence/Adversaries can establish durable, phishing-resistant persistence in Microsoft Entra ID by registering unauthorized Windows Hello for Business (WHfB) credentials to survive password resets and session revocations.This threat involves the abuse of the Windows Hello for Business (WHfB) credential registration process within Microsoft Entra ID. While WHfB is a standard onboarding and passwordless authentication feature, it can be repurposed by adversaries for persistent access. Attackers who have successfully compromised a valid user account, specifically one with existing WHfB or passkey access, can leverage that access to satisfy multi-factor authentication (MFA) requirements for registering a new, attacker-controlled credential. This credential becomes a permanent fixture of the account, remaining valid even if the user resets their password or if existing browser sessions are revoked. This technique provides a robust mechanism for long-term access that is resistant to standard remediation efforts, necessitating careful monitoring of new credential registration patterns across a tenant.

Impact

Successful exploitation allows an adversary to maintain long-term, persistent access to a compromised account within the target's Entra ID environment. Because the registered credential is device-bound and satisfies MFA requirements, the persistence survives common incident response actions such as password resets and session token invalidation. This poses a high risk for continued unauthorized access, data exfiltration, and lateral movement within the cloud identity perimeter.

Recommendation

  • Deploy detection logic to identify first-seen WHfB credential registrations correlated with new or anomalous source Autonomous System Numbers (ASN) within the tenant environment.
  • Review the sign-in history immediately preceding any detected WHfB registration for signs of deviceless authentication, device-code flow abuse, or anomalous geographic activity.
  • If unauthorized registration is confirmed, delete the malicious WHfB credential via the Entra portal or Microsoft Graph API, revoke all active sessions, and force a credential re-enrollment from a trusted, physical device.
]]>lowadvisorypersistencecloud-securityentra-ididentity-and-access