Skip to main content
Password Security

Why Your Passwords Are Weak: The 15-Character Rule You're Ignoring

Most people still use short, reused passwords. Here's why the 15-character minimum from NIST and CISA is your best defense, and how to build passphrases that stick.

Imagine you're sipping coffee, checking your bank app, and you see a charge for $1,200 at a store you've never visited. Your heart sinks. You didn't lose your phone. You didn't click a weird link. But somehow, someone got into your account. How? Because your password was 8 characters long, and it was the same one you used for that fitness app that got breached last year. This is the quiet reality of modern cybercrime: it's not about you being stupid, it's about your password being weak.

I'm not here to scare you with doom and gloom—well, maybe a little. But I'm here to answer one specific question that I think we all need to confront: Why do we keep using passwords that are too short, too simple, and too reused?

The answer isn't a lack of intelligence. It's that we've been given bad advice for decades. We've been told to use complex passwords with symbols and numbers, and to change them every 90 days. But that advice is wrong. In fact, the federal guidelines from NIST now say the opposite: stop forcing periodic changes, stop forcing complexity, and start using longer passphrases. The 15-character rule is the single most effective thing you can do to protect yourself, and I'm going to show you why.

The 15-Character Minimum: Not a Suggestion, a Standard

Let's start with the numbers. NIST SP 800-63B, the federal guideline for digital identity, requires that passwords used as the only authentication factor be at least 15 characters long. That's not a random number. It's based on the reality of how attackers crack passwords. A short password, even with symbols and numbers, can be cracked in minutes with modern hardware. But a 15-character passphrase of random words? That's exponentially harder.

And it's not just NIST. The NSA and CISA jointly identified 'poor credential hygiene,' including easily crackable passwords shorter than 15 characters, as one of the top ten most common network misconfigurations. They see it in the wild constantly. So if you're using an 8-character password, you're not just behind the curve—you're a prime target.

But here's the kicker: NIST also says that when passwords are used as part of MFA, they can be shorter, but still at least 8 characters. So why not just use 8 characters and rely on MFA? Because MFA isn't perfect, and you're still leaving the door unlocked if someone steals your password. The 15-character rule is your first line of defense, and it should be non-negotiable.

Why Complexity Rules Are a Trap

For years, we were told to use a mix of uppercase, lowercase, numbers, and symbols. So we all started using passwords like 'P@ssw0rd123!'—which is about as secure as a cardboard lock. Why? Because attackers know these patterns. They use dictionary attacks and rule-based cracking that can guess these 'complex' passwords in seconds. The NCSC (the UK's cybersecurity agency) explicitly warns that letter-to-symbol swaps like 'o' to '0' add little strength. They're just predictable.

NIST now forbids forced complexity rules. Instead, they recommend allowing passwords up to at least 64 characters, accepting spaces and Unicode characters, and screening against a blocklist of commonly used or compromised values. That's a huge shift. It means the best password is not 'Tr0ub4dor&3' but something like 'correct horse battery staple'—though that's been used so much it's now on blocklists. The point is length, not complexity.

So what should you do? The NCSC recommends building passwords from three random, unrelated words, like 'applenemobiro.' That's easy to remember and long enough to be strong. But I'd go further: use four or five words if you can. The 15-character minimum is a floor, not a ceiling.

The Reuse Epidemic: One Breach, Every Account

Now, let's talk about the elephant in the room: password reuse. Microsoft notes that password reuse enables password-spray and credential-stuffing attacks, where common or previously breached passwords are tried against corporate accounts. And it's not just corporations—it's you and me. The FBI's IC3 reported that personal data breach was the third most-reported crime category in 2024, with 64,882 complaints. But those are just the ones that get reported. Millions of credentials are stolen every day.

Here's a concrete scenario: You use the same password for your email and for a random forum. That forum gets breached, and your email and password are now in a database. Attackers then try that password on every major service—banking, social media, cloud storage. If you reused it, they're in. This is exactly why Have I Been Pwned exists. It's a free service run by Troy Hunt that lets you check if your email has appeared in a known breach. I check mine regularly, and I recommend you do too. If you find a breach, change that password immediately.

The solution is a password manager. CISA recommends using one to generate and store unique, random passwords for every account. That way, you only need to remember one strong master passphrase, and every other password is long and unique. I know some people worry about putting all their eggs in one basket, but the alternative—reusing passwords—is far riskier. I've been using one for years, and it's the single best security decision I've made.

What About MFA? It's Not a Silver Bullet

MFA is great, but it's not infallible. CISA documents four ways traditional MFA is bypassed: phishing, push bombing, exploitation of SS7 protocol vulnerabilities, and SIM swapping. That last one is especially nasty—attackers convince your cellular carrier to transfer your phone number to a SIM card they control, and then they receive your SMS codes. That's why CISA recommends phishing-resistant MFA like hardware security keys or passkeys over SMS codes. If you're using SMS for your bank, you're taking a risk.

Microsoft says that enabling MFA can block over 99.9% of account compromise attacks. That's a powerful statistic. But that 0.1% is still out there, and it's often the sophisticated attackers who target you specifically. So MFA is a layer, not a cure-all. The foundation is still a strong, unique password.

So here's my recommendation, and I'm not shy about it: Use a password manager, generate passwords that are at least 15 characters long, and enable MFA on every account that supports it—preferably with an authenticator app or hardware key, not SMS. Check Have I Been Pwned regularly. And never reuse a password. Ever.

The most important thing to remember is this: Your password is the key to your digital life. Make it long, make it unique, and let a password manager do the heavy lifting.

Sources

  • CISA (Secure Our World) - https://www.cisa.gov/secure-our-world
  • NIST SP 800-63B - https://pages.nist.gov/800-63-4/sp800-63b.html
  • NCSC (Three Random Words) - https://www.ncsc.gov.uk/collection/top-tips-for-staying-secure-online/three-random-words
  • NSA/CISA Top Ten Misconfigurations - https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-278a
  • Have I Been Pwned - https://haveibeenpwned.com/About
  • Microsoft Security Blog (MFA) - https://www.microsoft.com/en-us/security/blog/2019/08/20/one-simple-action-you-can-take-to-prevent-99-9-percent-of-account-attacks/

Share this article:

Comments (0)

No comments yet. Be the first to comment!