Passwords are the oldest security mechanism on the internet — and the most broken. Despite decades of advice about choosing strong passwords, the reality is that human beings are terrible at creating, remembering, and protecting them. Attackers know this, and they have built an entire industry around stealing, guessing, and buying passwords.
If your organisation relies solely on passwords to protect email, cloud applications, financial systems, or customer data, you are relying on a defence that attackers bypass routinely — often within minutes.
How Passwords Get Compromised
Most people assume a password breach means a hacker sitting in a dark room typing guesses into a login screen. The reality is far more industrialised. Passwords are compromised through several well-established attack methods:
- Phishing — fake login pages that trick users into entering their real credentials. This is the single most common method and succeeds even against security-aware employees.
- Credential stuffing — attackers take username/password pairs leaked from one breach and try them on other services. Because people reuse passwords across sites, this works at alarming scale.
- Brute force and password spraying — automated tools that try millions of password combinations, or try a small set of common passwords against every account in your organisation.
- Dark web marketplaces — stolen credentials are bought and sold in bulk. An employee’s email and password may already be available for purchase without anyone in your organisation knowing.
- Keyloggers and info-stealers — malware installed on a device that silently records every keystroke, including passwords.
Diagram
The Five Main Password Attack Methods
Visual showing Phishing, Credential Stuffing, Brute Force / Password Spraying, Dark Web Marketplaces, and Keyloggers — each with a brief description and an arrow pointing to a central “Compromised Password” outcome.
The Scale of the Problem
The numbers are staggering. Over 24 billion username-password pairs are available on criminal marketplaces. According to Verizon’s 2024 Data Breach Investigations Report, stolen credentials were involved in over 40% of all breaches. Microsoft reports that password-based attacks have increased tenfold since 2022, with over 4,000 password attacks blocked per second across their cloud services.
The uncomfortable truth is that no amount of password complexity rules — requiring uppercase letters, numbers, symbols, and minimum lengths — solves the core problem. A 20-character password is just as vulnerable to phishing as a 6-character one. Complexity rules address brute-force attacks but do nothing against the methods that actually dominate the threat landscape today.
Why Password Policies Are Not the Answer
Many organisations respond to password risk by making passwords harder: longer minimum lengths, forced rotation every 90 days, bans on common words. Research — including guidance from the UK National Cyber Security Centre (NCSC) and the US National Institute of Standards and Technology (NIST) — now shows that these policies often make things worse:
- Forced rotation leads people to choose weaker passwords and increment predictably (Password1, Password2, Password3)
- Complexity rules lead to patterns like “Company2024!” which are trivially guessable
- Password fatigue encourages reuse across personal and work accounts
Diagram
The Password Policy Paradox
Cycle diagram showing: Stricter rules → Weaker user behaviour (reuse, patterns, sticky notes) → More breaches → Even stricter rules. Contrasts with the escape path: MFA adoption breaks the cycle.
The NCSC now explicitly recommends against forced password expiration and instead advocates for MFA as the primary defence. NIST SP 800-63B takes the same position. The world’s leading security bodies have reached the same conclusion: passwords alone are not enough, and trying to make them “good enough” is a losing strategy.
What Multi-Factor Authentication Changes
Multi-factor authentication (MFA) adds a second verification step beyond the password. Even if an attacker steals, guesses, or phishes a password, they cannot log in without the second factor — typically something the legitimate user physically possesses, such as a phone or a hardware security key.
Microsoft’s data shows that MFA blocks over 99.2% of automated account compromise attacks. Google reported that adding a recovery phone number (a basic form of second factor) blocked 100% of automated bots, 99% of bulk phishing attacks, and 66% of targeted attacks.
MFA does not make passwords irrelevant — it makes stolen passwords insufficient. This single change transforms your organisation’s exposure from “one phishing email away from a breach” to “substantially resilient against credential-based attacks.”
Diagram
Attack Outcome: Password Only vs Password + MFA
Side-by-side comparison — Left: Attacker steals password → logs in → full access (breach). Right: Attacker steals password → MFA challenge → blocked (no breach). Shows 99.2% of automated attacks stopped.
Why This Matters
Every day your organisation operates with password-only authentication on critical systems, you carry risk that is both avoidable and well-understood. The question is not whether credential-based attacks will target your organisation — they already are, via automated bot traffic that probes every internet-facing login page continuously. The question is whether those attacks will succeed.
Regulators have caught up. Cyber Essentials now requires MFA for cloud services and administrator access. Cyber insurance providers increasingly mandate MFA as a condition of coverage. The cost of implementing MFA is a fraction of the cost of a single breach — and an even smaller fraction of the reputational damage that follows.
What to Do Now
- Audit which business-critical systems currently rely on password-only authentication
- Check whether any employee credentials from your domain appear in known breach databases (tools like Have I Been Pwned offer domain-level search)
- Review your current password policy — if it mandates forced rotation every 60–90 days, consider updating it in line with NCSC guidance
- Begin planning an MFA rollout starting with the highest-risk accounts (administrators and executives)
- Communicate to staff why this change is happening — framing it as protection, not inconvenience
Evidence to Collect
- A list of all internet-facing login portals and whether MFA is enabled on each
- Results of a credential exposure check against known breach databases
- Your current password policy document
- A record of any password-related security incidents in the past 12 months
- Confirmation of which accounts (especially admin accounts) are protected by MFA today
Common Mistakes
- Believing complex passwords are “good enough.” Complexity does not protect against phishing, credential stuffing, or info-stealing malware. The attack methods that dominate today bypass password strength entirely.
- Delaying MFA because “we haven’t been breached yet.” Credential-based attacks are automated and continuous. The absence of a known breach does not mean credentials have not been compromised — it may mean the compromise has not been detected.
- Focusing on password managers as a complete solution. Password managers help with reuse and complexity, but they do not protect against real-time phishing attacks where the user enters credentials into a fake site. MFA is still essential.
- Assuming only technical staff need MFA. Executives, finance staff, and HR personnel are the most targeted users in an organisation because of the data and systems they can access. They need MFA first, not last.
Knowledge Check
Question 1 of 4
Which of the following is the most common method used to compromise passwords today?
- Brute-force guessing of complex passwords
- Phishing — tricking users into entering credentials on fake login pages
- Physically looking over someone’s shoulder
- Guessing based on social media information
Reveal Answer
B. Phishing is the single most common method for credential compromise. It works regardless of password complexity because the user voluntarily enters the real password into a convincing fake page.
Question 2 of 4
Why do leading security bodies like the NCSC and NIST now recommend against forced password rotation?
- Because passwords are no longer used anywhere
- Because forced rotation leads users to choose weaker, more predictable passwords
- Because it is too expensive to administer
- Because regulations explicitly prohibit it
Reveal Answer
B. Research shows forced rotation causes users to choose weaker passwords and make predictable incremental changes (e.g., Password1 → Password2), ultimately reducing security rather than improving it.
Question 3 of 4
According to Microsoft’s data, what percentage of automated account compromise attacks does MFA block?
- 75%
- 85%
- Over 99%
- 100%
Reveal Answer
C. Microsoft’s data shows MFA blocks over 99.2% of automated account compromise attacks. It is the single most effective control against credential-based attacks.
Question 4 of 4
What is credential stuffing?
- Filling in login forms with random characters
- Using username/password pairs leaked from one breach to try logging into other services
- Sending excessive traffic to crash a login page
- Installing software that records keystrokes
Reveal Answer
B. Credential stuffing exploits the fact that people reuse passwords across services. Attackers take credentials leaked from one breach and automatically test them against other platforms at scale.
Summary Notes — Why Passwords Alone Are Not Enough
Key Takeaways
- Passwords are compromised through phishing, credential stuffing, brute force, dark web sales, and keyloggers — most methods bypass password complexity entirely.
- Over 24 billion stolen credential pairs exist on criminal marketplaces.
- Stricter password policies (forced rotation, complexity rules) often reduce security by encouraging weaker user behaviour.
- MFA blocks over 99% of automated credential attacks — it is the single most impactful defence.
- Leading security bodies (NCSC, NIST) now prioritise MFA over password complexity.
Action Items
- Audit which critical systems still use password-only authentication.
- Run a credential exposure check against known breach databases.
- Review and modernise your password policy in line with NCSC guidance.
- Begin MFA rollout planning, starting with admin and executive accounts.
- Communicate the business case for MFA to leadership and staff.
Compliance Relevance
This lesson supports Cyber Essentials (Access Control — MFA requirement for cloud and admin access), ISO 27001 Annex A.8.5 (Secure Authentication), NIST SP 800-63B (Digital Identity Guidelines), and GDPR Article 32 (Security of Processing — appropriate technical measures).