Colour theme
Book a consultation

Password spraying: checking your defences

Understand password spraying and review sign-in coverage, password controls, lockout behaviour, available alerts and incident response.

An illustration of a hand selecting a login button on a phone screen.

Password spraying uses a small set of likely passwords against many accounts. The attacker spreads the guesses across users, often slowly, to reduce the chance of reaching a single account’s lockout threshold.

It differs from repeatedly guessing many passwords for one user, and from credential stuffing, which reuses stolen username-and-password pairs. OWASP’s explanation describes that distinction. Spraying doesn’t require staff to share the same password; one account accepting a guess can be enough to create a problem.

Find the services that accept passwords

Ask IT which internet-facing services still accept password sign-ins. Include email, remote access, supplier portals and independent applications outside your main identity provider.

Identify dormant accounts, privileged accounts and any older authentication routes. Check whether effective MFA or another access restriction applies to each route. A policy for the main web login may not cover a separate application.

Use the MFA rollout guide to verify coverage. Passwordless access can reduce reliance on passwords, but review whether password-based fallback remains available.

Reduce predictable guesses

Support long, unique passwords and a business password manager. Review the provider’s blocklist for common or compromised values and any available protection against organization-specific guesses.

The password-policy guide explains current requirements without arbitrary rotation or mandatory character mixtures. Predictable seasonal changes can leave a password easy to guess.

Disable accounts that are no longer needed through your usual account-removal process. Review non-human accounts separately so a change doesn’t silently break an integration.

Review throttling without locking out the business

Ask how the service limits repeated attempts and how legitimate users recover access. Lockout slows guessing, but it can’t stop a spray that stays under each account’s threshold.

Microsoft Entra smart lockout is enabled with default settings for Entra customers. Customizing those settings requires the applicable licence. Microsoft also notes that genuine users can still be locked out.

Have IT check the relationship between cloud and on-premises controls in a hybrid environment. Don’t lower thresholds blindly or block a shared network address without assessing who else uses it.

Connect the available evidence

Look across accounts and over a suitable time period; one user’s failures won’t show a spray. An attacker can use several source addresses, while a stale application password can also cause repeated failures.

Ask the monitoring owner to review outcomes, affected users, applications, timing and subsequent activity. Confirm which logs exist, how long they’re retained and who receives an actionable alert.

Microsoft’s risk-investigation guidance says an Entra password-spray detection indicates successful credential validation during a spray attack. That deserves investigation even if MFA prevented the complete sign-in. It means more than failed guesses, but on its own it doesn’t show that the attacker reached business data.

Check the licence and detection coverage you have. If no alert arrives, an attempt may still have gone unnoticed.

Practise the response safely

Use a tabletop scenario, sample logs and designated test accounts to check the handoff. Don’t run password guesses across production users to see whether an alarm appears.

Agree who can restrict accounts, preserve logs and involve the incident-response team. For suspected successful access, follow the provider’s containment steps and review sessions, recovery methods and application permissions. A password reset alone may leave other access available.

Document findings, assign owners and repeat the relevant checks after changes. Contact us if you need help reviewing sign-in controls and the response to suspicious authentication activity.


Featured Image Credit