Professor Franklin
Accessibility settings

Preferences are saved in this browser when storage is available.

Chapter 3 · Reading 4 of 5

Password Attacks

Security+ SY0-801 · Objectives 4.5

A student sees failed sign-ins on an account with a long password. A friend says to make the password longer. Before giving that advice, ask where the guesses occurred and whether the password had ever been used elsewhere. Length addresses only part of the problem.

Password attacks are malicious attempts to gain unauthorized access to systems, accounts, or data by cracking or bypassing password authentication mechanisms. While it may appear simple, there are various methods that this can be achieved:

  • Brute Force Attacks: Attackers use automated tools to try all possible combinations of characters until the correct password is found.This uses a program to try every possible combination of letters, numbers, and symbols until the correct password is guessed.
  • Dictionary Attacks: Attackers use a list of common passwords or dictionary words to guess the password. Trying passwords like "password123", "welcome", or "qwerty".
  • Credential Stuffing: Attackers use stolen username and password pairs from one breach to try and gain access to other accounts. Such as using credentials obtained from a breached website to attempt login on other websites.
  • Rainbow Table Attacks: Attackers use precomputed tables of hash values for common passwords to quickly find matches. This uses a rainbow table to find the original password from its hashed value.

Hardening the verifier

Store a distinct random salt with each password verifier and use a slow, purpose-built password hashing function. A password manager helps users avoid reuse across services. A passkey binds authentication to the service identity. Protect enrollment and recovery as carefully as routine sign-in and monitor for compromised credentials.

When a lockout becomes an availability problem

Imagine a student mistypes a new password several times on a phone that keeps trying to synchronize mail. A rigid lockout can interrupt the student's legitimate work. A campus policy needs a way to slow suspicious attempts, identify unusual patterns and let a verified user recover. Decide how support can distinguish one misconfigured device from failures across many accounts. The number of attempts is only the beginning of that investigation.

Which evidence can a sign-in log reveal?

When many accounts each show one failure, an analyst should look across accounts and time. When an old password from another service is accepted immediately, this service may have recorded no failures at all. A stolen database of password verifiers presents a third problem. Offline guessing can happen without sending a single request to the sign-in service. Rate limiting, unique passwords and slow salted verification each protect a different part of that story.

During recovery, let the student use a trusted device and a verified channel. Examine active sessions and recovery contacts, then test that an old session no longer reaches the account where revocation is expected. Help the student choose a password manager or enroll a supported passkey and document how to recover from loss of the authenticator. In a training exercise, completing that recovery successfully is a stronger outcome than memorizing a list of attack names.

Sign-in distribution

Inspect the three records, then use the evidence to answer the question.

1. Unique password

Limits the impact of credential reuse.

Twenty different accounts show one failure each

2. Additional factor

Adds another check at sign-in.

All failures come from the same unfamiliar source

3. Monitoring

Surfaces unusual authentication activity.

No account received repeated guesses in the sample

Apply the reading

Why can one exposed password matter to a service that has never lost its own database?

Compare your reasoning

A user may have reused it. Distinct passwords limit the effect, and an additional authentication factor can protect the account.