Skip to main content
Back
DemonstrationMicrosoft Entra
2 min read

Azure AD password checks exposed a gap in sign-in visibility

Environment
Azure AD Seamless SSO research demonstration by Secureworks CTU
When
Secureworks discovered the issue in late June 2021.Disclosed Sep 29, 2021
Entry
Secureworks observes password validation before the user reaches multifactor authentication.

Secureworks showed that Microsoft’s Azure AD sign-in service could reveal whether a password was valid before multifactor authentication. The researchers initially saw attempts missing from sign-in logs. They later confirmed that the logs recorded successes and failures and that smart lockout limited repeated guesses. The test did not establish that anyone obtained a production user’s session.

What the demonstration did

Research team
Secureworks CTU
Internet
Microsoft Entra ID
Password check
Sign-in events

Research demonstration / Secureworks CTU

  1. 1

    Password validation

    June–September 2021

    Secureworks observes password validation before the user reaches multifactor authentication.

  2. 2

    Sign-in visibility

    June–September 2021

    Secureworks initially sees missing sign-in events and later confirms that successes and failures are logged.

Impact

Researchers could distinguish a valid password at a stage before multifactor authentication. The September update documented improved visibility. The research did not establish issuance of a session for a production user.

Would the controls have stopped it?

Limit repeated guesses and watch for attempts across accounts

Microsoft Entra smart lockout limits repeated bad passwords for one account. Secureworks confirmed that the endpoint began logging attempts. Individual account lockouts can still miss attempts spread across many accounts.

Incident control assessments

0
Prevented
1
Contained
1
Not covered

How it could have been prevented

The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.

Research team
Secureworks CTU
Internet
Microsoft Entra ID
Password check
Sign-in events

Research demonstration / Secureworks CTU

1 · Password validation

1 Contained

2 · Sign-in visibility

1 Not covered

Key facts

  • Secureworks reported the password-validation and sign-in logging behavior to Microsoft.
  • Microsoft confirmed the behavior on July 21 and initially described it as by design.
  • Secureworks published its initial analysis on September 29.
  • In an update, Secureworks confirmed that successful and failed attempts appeared in sign-in logs and that smart lockout limited repeated guesses.

Sources

Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.

  1. 1.
    Undetected Azure Active Directory Brute-Force AttacksSecureworks Counter Threat Unit (now Sophos) · Sep 29, 2021 · ResearchResearchers could distinguish a valid password at a stage before multifactor authentication. The September update documented improved visibility. The research did not establish issuance of a session for a production user.
  2. 2.
    Protect user accounts from attacks with Microsoft Entra smart lockoutMicrosoft · undated · Vendor reportMicrosoft documents smart lockout thresholds, duration and differences between familiar and unfamiliar locations.

The estate in the replay follows the researchers' description of their own test environment. Verdicts describe what a control does when it is in place before the run. They are not an assessment of any company's security program.

More cloud attack breakdowns

All breakdowns