ISC · Security and Confidentiality and Privacy · 9 practice questions
Password Spraying vs Credential Stuffing: Distinguishing Signs
Password spraying tests a few common passwords across many accounts; credential stuffing tests previously exposed username-password pairs. Below, sort one company portal’s login patterns by the credentials attackers test.
Try one first
Hint
Focus on the attacker’s login pattern: many accounts with very few common-password attempts each is different from using known credential pairs or hammering one account repeatedly.
Answer D. Password spraying is characterized by attempting a small number of very common passwords across many accounts, often pacing attempts to avoid triggering lockout thresholds. The pattern here, thousands of valid usernames, only two common passwords tried per username, and no evidence of username-specific stolen password pairs, best matches password spraying. The mailbox forwarding rules are consistent with post-compromise activity but do not change the primary attack classification.
Why not A: Session hijacking involves stealing or reusing an active authenticated session token or cookie to assume an authenticated session without re-authenticating. The logs show authentication attempts rather than evidence of intercepted session tokens or reused sessions, so session hijacking is not supported by the recorded sign-in activity.
Why not B: Credential stuffing uses large lists of previously stolen username-password pairs and tests those matched pairs against a service. Although some employee credentials were breached previously, the logs show a small set of common passwords tried broadly across many usernames rather than testing unique breached username-password pairs, so credential stuffing is less supported by the facts.
Why not C: A classic brute-force attack focuses many password guesses against a single account or a small set of accounts until one succeeds. Here the attacker limited attempts to only two passwords per username while targeting thousands of different usernames, which aligns with password spraying rather than a brute-force approach.
Sort it
Does the attacker spread a few common password guesses across many usernames?
Does the attacker test matched username-password pairs exposed in another breach?
| Item | Goes to |
|---|---|
| At one company's portal, an attacker tries Welcome1! against 100 usernames, then Spring2026! against those same usernames. | Password sprayingThe usernames change while the same two common guesses repeat across accounts. |
| The portal receives one attempt for each of 100 accounts. Every attempted pair exactly matches an unrelated site's breach list. | Credential stuffingThe attacker tests exposed matched pairs, even with only one attempt per account. |
| Hundreds of rotating IP addresses each submit Welcome1! against different portal users. No user-specific breached pairs are tested. | Password sprayingThe same common guess spreads across users. Rotating IPs do not change that pattern. |
| One IP address tests 100 portal usernames with their corresponding passwords from an external breach. | Credential stuffingExposed matched pairs define stuffing. A single source IP does not make it spraying. |
| Some employees appeared in an earlier breach, but portal attempts use only two common guesses that do not match their exposed pairs. | Password sprayingThe tested credentials show broad common-password guessing. The earlier breach is a distraction. |
| Several portal accounts accept Welcome1!. Each had received only that common guess, also tried against many other accounts. | Password sprayingThe same common password was guessed across accounts; successful guesses do not establish use of breached pairs. |
| The portal locks accounts after five failures. An attacker tries two common passwords against each of 100 users. | Password sprayingThe two common guesses spread across users identify spraying; staying below the five-failure threshold explains why lockouts are not triggered. |
| Portal accounts receive one or two attempts each. The tested passwords vary by username and match exposed pairs from another site. | Credential stuffingThe exposed username-specific pairs identify stuffing despite the low attempt counts. |
| An attacker tries Welcome1! across 100 portal users. Two successful users also used that password on a breached consumer site. | Password sprayingThe observed method spreads one common guess across users. Incidental password reuse does not establish replay of breached pairs. |
| Rotating residential IPs submit user-specific pairs from an external breach to the portal, often succeeding on the first attempt. | Credential stuffingReusing exposed matched pairs identifies credential stuffing. |
| The attacker has employee usernames and uniquely salted hashes from another site's breach, but submits only two common guesses across portal accounts. | Password sprayingThe actual attempts spread common guesses across users. Possessing hashes does not establish testing of usable breached password pairs. |
| The portal accepts passwords from exposed matched pairs, but MFA prevents the attacker from completing those logins. | Credential stuffingTesting exposed matched pairs identifies credential stuffing even when MFA prevents completed logins. |
Key points
- Remember: Common guesses spread across users mean spraying; exposed matched pairs mean stuffing.
- Few attempts per account and rotating source IPs can occur in either attack.
- A prior breach alone does not establish stuffing; identify the credentials actually tested.
How the exam traps you
- Calling every low-attempt, many-account attack password spraying. Check whether the attacker tests common guesses or exposed matched pairs.
- Choosing credential stuffing just because employees appeared in a prior breach. The tested pairs must support credential reuse; unrelated breach history does not override a common-password pattern.
- Letting rotating IP addresses determine the classification. Source rotation describes delivery, not whether passwords were guessed or reused from exposed pairs.
Question 2
Hint
Focus on defenses that remain effective when attackers present valid, stolen credentials and that mitigate distributed, automated login attempts.
Answer D. The pattern of many login attempts using stolen username/password lists from many IPs that only succeed when users reused breached passwords is credential stuffing. MFA protects accounts even when attackers present valid credentials; credential-stuffing detection and application-layer rate-limiting slow and detect distributed automated attempts; and checking logins against breached-credential lists prevents reuse of known-compromised passwords. Together these controls provide immediate containment and longer-term prevention.
Why not A: Why tempting: Lockouts, IP blocking, and CAPTCHAs look like direct measures against repeated failed logins and basic bots. Why wrong: Credential stuffing is typically distributed across many IPs and uses low attempts per IP to avoid lockouts; strict lockouts and IP blocks can be evaded or abused to trigger denial-of-service for legitimate users, so they are insufficient alone.
Why not B: Why tempting: WAFs, bot management, and network filters target malicious automation and can reduce attack traffic. Why wrong: These network- and application-edge controls are useful but often reactive; botnets, proxy services, and rotated IPs commonly bypass IP/geo rules, and without account-level defenses like MFA and breached-credential checks they do not reliably prevent account takeover.
Why not C: Why tempting: Password resets and stronger policies directly address compromised credentials and encourage better hygiene. Why wrong: Mass resets are disruptive and, if users continue to reuse passwords or choose predictable replacements, attackers with stolen credentials may still succeed; these measures are longer-term hygiene steps and do not provide the immediate account-protection given by MFA and breached-credential blocking.
Question 3
Hint
Focus on how the attacker obtained or used the passwords: guessed them, reused stolen ones, or tricked users into giving them up.
Answer B. Credential stuffing is when an attacker takes username-password pairs stolen from one breach and tries them on other systems to gain access. The scenario states the attacker is using real credential pairs from an unrelated breach (not guessing or contacting users), which matches credential stuffing. That makes credential stuffing the best classification.
Why not A: This may seem plausible because there are many login attempts, but a brute-force attack involves systematically guessing passwords (trying many combinations) rather than reusing known username-password pairs stolen elsewhere.
Why not C: Password spraying involves trying a small set of common passwords across many accounts. In contrast, the attacker here is using actual credential pairs obtained from another breach, not a small list of guessed common passwords.
Why not D: Phishing is a common method to harvest credentials, but it involves tricking users into revealing them. The stem specifies the attacker already had credentials from an external breach and did not contact employees, so the active attack is credential stuffing, not phishing.
Question 4
Hint
Focus on what the login pattern says about the attacker’s method: many IPs, very few failed attempts, no endpoint malware evidence, and a clear difference between MFA and non-MFA users.
Answer A. The pattern (many accounts, many IPs, very few failures, and MFA users unaffected) is most consistent with credential stuffing or the use of previously compromised credentials rather than endpoint malware or a volumetric attack. Enforcing MFA and resetting exposed credentials directly addresses the attacker's effective vector while allowing the portal to remain available.
Why not B: Tightening lockout thresholds targets brute-force attacks against individual accounts, but here attackers appear to be testing known username/password pairs across many accounts (credential stuffing), often with only one failed attempt or none. Lockouts may disrupt legitimate users and will not fully stop attackers using valid stolen credentials or distributed attempts.
Why not C: Endpoint compromise is a plausible concern, but the scenario reports no malware indicators and shows MFA protected accounts, suggesting the primary weakness is credential reuse, not keyloggers on endpoints. Forensics can be done later, but it is not the fastest single control to stop ongoing unauthorized access.
Why not D: Many source IPs can accompany credential-stuffing campaigns, but the observable harm here is unauthorized account access and fraudulent payroll changes rather than service disruption. DDoS mitigations do not directly prevent use of stolen credentials to log in.
Question 5
Hint
Focus on a control that prevents access even when an attacker already knows valid usernames and passwords and can be applied promptly to remote logins.
Answer B. The attack combined phishing (stolen credentials) and credential-stuffing followed by a successful VPN login with valid credentials; MFA stops an attacker who only has passwords by requiring a second factor. MFA mitigates both stolen-credential attacks and automated login attempts and can typically be rolled out to remote access relatively quickly. Other controls have value but either do not reliably block access with valid credentials or are slower to implement as the primary immediate control.
Why not A: This is tempting because the SOC saw many failed logins and lockouts/IP blocks help against brute-force or credential-stuffing; however, they do not prevent access when an attacker uses legitimately stolen credentials, can be circumvented by distributed attempts, and aggressive lockouts risk denial-of-service to legitimate users.
Why not C: DLP addresses the data-exfiltration step seen in the incident and is an important control, but it does not prevent the initial account takeover that allowed the attacker to access and exfiltrate files; it is not the best immediate measure to reduce the risk of credential-based compromise.
Why not D: Device certificates and disabling split-tunneling can reduce risk by ensuring only managed devices connect, but provisioning certificates and device management is typically more complex and slower than deploying MFA. Also, certificates do not stop an attacker who gains access via a legitimately managed but compromised device, so they are not the fastest or most directly effective immediate control.
Question 6
Hint
Focus on what changes from attempt to attempt: the password, the user account, or the delivery method.
Answer D. Password spraying is characterized by trying a small number of common passwords across many user accounts. Attackers use this approach to avoid triggering account lockout thresholds that would occur if they repeatedly targeted a single account, which matches the pattern described.
Why not A: High-volume traffic aimed at disrupting availability indicates a denial-of-service attack. The key facts here concern authentication attempts and password reuse, not network-level availability attacks.
Why not B: This is tempting because both involve repeated login attempts, but attempting many passwords against a single account aligns with brute-force or targeted credential-guessing, not password spraying, which varies the target account while reusing common passwords.
Why not C: Phishing can lead to credential compromise and is a plausible distractor; however, the scenario describes automated sign-in attempts using the same password across many accounts rather than users voluntarily entering credentials via a fraudulent message or site.
Question 7
Hint
Focus on the login pattern attackers use when they want to guess passwords without causing many account lockouts.
Answer A. Password spraying involves trying a common password (or a small set of common passwords) across many accounts to avoid triggering account lockouts on any single account. A pattern showing many different accounts each with one or two failed attempts using the same password is the strongest indicator of a spraying attempt. By contrast, many failures against one account suggest a brute-force attack.
Why not B: This pattern indicates an attacker trying many different passwords against a single account (brute-force). It is malicious but does not match the cross-account, same-password pattern of password spraying.
Why not C: Phishing reset emails are credential-theft attempts and merit investigation, but they are not the authentication-log pattern that indicates password spraying. The question asks which login-attempt behavior points specifically to spraying.
Why not D: A website outage after a traffic surge describes a denial-of-service event affecting availability, not a pattern of failed logins across user accounts. It does not indicate password spraying.
Question 8
Hint
Focus on what the attacker already has: unknown passwords to guess, a few common passwords to reuse broadly, or matched username-password pairs from another breach.
Answer A. This activity is credential stuffing: the attacker is replaying known username-password pairs obtained from another breach. Tactics such as rotating IPs and low tries per account are evasive measures, but the defining fact is that the credentials were already compromised and are being reused rather than guessed.
Why not B: Password spraying spreads a small set of common passwords across many usernames and relies on users choosing weak passwords. It is incorrect here because the attempts use exact username-password pairs that match an external breach, not a short list of common passwords.
Why not C: A brute-force attack involves systematically guessing passwords that are not previously known. This scenario is different because the attacker is replaying exact credential pairs from a breach rather than trying to guess unknown passwords.
Why not D: Account enumeration probes which usernames exist but does not typically involve submitting full, valid username-password combinations from a separate breach. Here, the primary activity is replaying compromised credentials rather than merely identifying valid accounts.
Question 9
Hint
Focus on what inputs each attack requires and which attack is least constrained by a lockout that is measured per account rather than across the whole system.
Answer D. Password spraying best matches the attacker's available inputs and constraints. The attacker can enumerate valid usernames but does not have plaintext credential pairs, and the VPN enforces a per-account lockout after five failures; trying a small set of common passwords across many accounts keeps failed attempts per account low while exploiting the lack of MFA. Offline cracking of uniquely salted hashes or concentrated brute force against one account would be slower or likely trigger lockouts, and credential stuffing requires recovered plaintext passwords.
Why not A: Focusing on one account is appealing for high-value access, but the portal's per-account lockout after five failed attempts makes concentrated brute force likely to trigger a lockout and impede access. Distributing a few guesses across many accounts (spraying) better minimizes lockouts under these conditions.
Why not B: This is tempting because the item mentions a breach, but credential stuffing needs usable username/password pairs. The breach data here are uniquely salted hashes (no plaintext), so the attacker cannot immediately replay credentials against the VPN without time-consuming offline cracking.
Why not C: Hashes suggest offline recovery is possible, making this choice attractive, but uniquely salted hashes largely defeat rainbow-table efficiency and require substantial cracking effort. Even if some passwords might be recovered eventually, that approach is not the fastest practical path to immediate VPN access.
Common questions
What is the difference between password spraying and credential stuffing?
Spraying spreads a few common password guesses across many usernames. Stuffing tests matched username-password pairs exposed in another breach.
Can credential stuffing use only one or two attempts per account?
Yes. Low attempt counts do not make it spraying when the attacker is testing exposed matched pairs.
Is it still credential stuffing if MFA blocks the login?
Yes. Testing exposed matched pairs identifies credential stuffing even when MFA prevents completed logins.
Watch it solved
A full CPA ISC task-based simulation on Threats and attacks, worked step by step.
SIEM Attack Identification | CPA ISC Simulation (TBS) on YouTube
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Threats and attacks
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.