LoFP LoFP / a legitimate new or rare client (a new operating system, a newly adopted browser, a privacy-hardened or developer browser, or a corporate kiosk/appliance) produces a new browser/os combination the first time the user is seen on it. the device-trust filter already excludes the user's entra-joined and registered endpoints, so the residual false positives are first sign-ins from genuinely unmanaged personal devices (byod, a home laptop, a new phone). baseline the browser and os families that are normal for the user and add exceptions for sanctioned clients, and correlate the source ip, asn, and the authentication methods completed in the session before escalating.

Techniques

Sample rules

Entra ID Non-Passkey Sign-In with Unusual Browser and OS

Description

Identifies a successful Microsoft Entra ID sign-in from a browser and operating system combination not previously seen for the user, without a phishing-resistant method and not from an Entra-joined or registered device. Adversary-in-the-middle proxies often present a spoofed client fingerprint, including impossible pairings such as Safari on Windows, to suppress the passkey prompt and force a phishable fallback. A genuinely new client also triggers this rule, so corroborate with source and authentication context.

Detection logic

data_stream.dataset: "azure.signinlogs" and
    azure.signinlogs.category: "SignInLogs" and
    azure.signinlogs.properties.authentication_details.authentication_method: (* and not (
        "Passkey (synced)" or
        "Passkey (device-bound)" or
        "FIDO2 security key" or
        "Windows Hello for Business" or
        "Previously satisfied"
    )) and
    not azure.signinlogs.properties.device_detail.trust_type: * and
    user.name: * and user_agent.name: * and
    azure.signinlogs.properties.device_detail.operating_system: * and
    event.outcome: "success"