{“lastseen”:”2025-10-22T09:27:08″,”description”:”\\n\\nThe advice didn’t change for decades: use complex passwords with uppercase, lowercase, numbers, and symbols. The idea is to make passwords harder for hackers to crack via brute force methods. But more recent guidance shows our focus should be on password length, rather than complexity. Length is the more important security factor, and passphrases are the simplest way to get your users to create (and remember!) longer passwords.\\n\\n## The math that matters\\n\\nWhen attackers steal password hashes from a breach, they brute-force by hashing millions of guesses per second until something matches. The time this takes depends on one thing: how many possible combinations exist.\\n\\nA traditional 8-character \\”complex\\” password (P@ssw0rd!) offers roughly 218 trillion combinations. Sounds impressive until you realize modern GPU setups can test those combinations in months, not years. Increase that to 16 characters using only lowercase letters, and you’re looking at 26^16 combinations, billions of times harder to crack.\\n\\nThis is effective entropy: the actual randomness an attacker must work through. Three or four random common words strung together (\\”carpet-static-pretzel-invoke\\”) deliver far more entropy than cramming symbols into short strings. And users can actually remember them.\\n\\n## Why passphrases win on every front\\n\\nThe case for passphrases isn’t theoretical, it’s operational:\\n\\n**Fewer resets.** When passwords are memorable, users stop writing them on Post-it notes or recycling similar variations across accounts. Your helpdesk tickets drop, which alone should justify the change.\\n\\n**Better attack resistance.** Attackers optimize for patterns. They test dictionary words with common substitutions (@ for a, 0 for o) because that’s what people do. A four-word passphrase sidesteps these patterns entirely \u2013 but only when the words are truly random and unrelated.\\n\\n**Aligned with current guidance.** NIST has been clear: prioritize length over forced complexity. The traditional 8-character minimum should really be a thing of the past. \\n\\n## One rule worth following\\n\\nStop managing 47 password requirements. Give users one clear instruction:\\n\\n**Choose 3-4 unrelated common words + a separator. Avoid song lyrics, proper names, or famous phrases. Never reuse across accounts.**\\n\\nExamples: _mango-glacier-laptop-furnace_ or _cricket.highway.mustard.piano_\\n\\nThat’s it. No mandatory capitals, no required symbols, no complexity theater. Just length and randomness.\\n\\n## Rolling it out without chaos\\n\\nChanges to authentication can spark resistance. Here’s how to minimize friction:\\n\\nStart with a pilot group, grab 50-100 users from different departments. Give them the new guidance and monitor (but don’t enforce) for two weeks. Watch for patterns: Are people defaulting to phrases from pop culture? Are they hitting minimum length requirements consistently?\\n\\nThen move to warn-only mode across the organization. Users see alerts when their new passphrase is weak or has been compromised, but they’re not blocked. This builds awareness without creating support bottlenecks.\\n\\nEnforce only after you’ve measured:\\n\\n * Passphrase adoption percentage\\n * Helpdesk reset reduction\\n * Banned-password hits from your blocklist\\n * User-reported friction points\\n\\n\\n\\nTrack these as KPIs. They’ll tell you whether this is working better than the old policy.\\n\\n## Making it stick with the right policy tools\\n\\nYour Active Directory password policy needs three updates to support passphrases properly:\\n\\n 1. **Raise the minimum length.** Move from 8 to 14+ characters. This accommodates passphrases without creating problems for users who still prefer traditional passwords.\\n 2. **Drop forced complexity checks.** Stop requiring uppercase, numbers, and symbols. Length delivers better security with less user friction.\\n 3. **Block compromised credentials.** This is non-negotiable. Even the strongest passphrase doesn’t help if it’s already been leaked in a breach. Your policy should check submissions against known-compromised lists in real time.\\n\\n\\n\\nSelf-service password reset (SSPR) can help during the transition. Users can securely update credentials on their own time, and your helpdesk shouldn’t be the bottleneck.\\n\\nPassword auditing gives you visibility into adoption rates. You can identify accounts still using short passwords or common patterns, then target those users with additional guidance.\\n\\nTools like Specops Password Policy handle all three functions: extending policy minimums, blocking over 4 billion compromised passwords, and integrating with SSPR workflows. The policy updates sync to Active Directory and Azure AD without additional infrastructure, and the blocklist updates daily as new breaches emerge.\\n\\n## What this looks like in practice\\n\\nImagine your policy requires 15 characters but drops all complexity rules. A user creates _umbrella-coaster-fountain-sketch_ during their next password change. A tool like Specops Password Policy checks it against the compromised password database \u2013 it’s clean. The user remembers it without a password manager because it’s four concrete images linked together. They don’t reuse it because they know it’s specific to this account.\\n\\nSix months later, no reset request. No Post-it note and no call to the helpdesk because they fat-fingered a symbol. Nothing revolutionary \u2013 just simple and effective.\\n\\n## The security you actually need\\n\\nPassphrases aren’t a silver bullet. MFA still matters. Compromised credential monitoring still matters. But if you’re spending resources on password policy changes, this is where to spend it: longer minimums, simpler rules, and real protection against breached credentials.\\n\\nAttackers still steal hashes and brute-force them offline. What’s changed is our understanding of what actually slows them down, so your next password policy should reflect that. Interested in giving it a try? Book a live demo of Specops Password Policy. \\n\\nFound this article interesting? This article is a contributed piece from one of our valued partners. Follow us on Google News, Twitter and LinkedIn to read more exclusive content we post.\\n”,”published”:”2025-10-22T09:26:00″,”modified”:”2025-10-22T09:26:22″,”type”:”thn”,”title”:”Why You Should Swap Passwords for Passphrases”,”source”:””,”references”:””,”id”:”THN:1F21A766D66622CFEE98D2CD19BF4C08″,”bulletinFamily”:”info”,”cwe”:null,”cvelist”:[],”sourceData”:””,”sourceHref”:””,”cvss”:{“score”:0,”severity”:”NONE”,”vector”:”NONE”,”version”:”NONE”},”cvss2″:{},”cvss3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””,”cvssV3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””}},”href”:”https:\/\/thehackernews.com\/2025\/10\/why-you-should-swap-passwords-for.html”,”category_name”:”News”,”post_link”:””,”product”:””,”version”:””,”vendor”:””,”ai_description”:””,”ai_severity”:””,”ai_vendor”:””,”ai_product”:””,”ai_version”:””,”ai_score”:0}<\/p>\n","protected":false},"excerpt":{"rendered":"
{“lastseen”:”2025-10-22T09:27:08″,”description”:”\\n\\nThe advice didn’t change for decades: use complex passwords with uppercase, lowercase, numbers, and symbols. The idea is to make passwords harder for hackers to…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[6,8,12,13,33,7,11,43,5],"class_list":["post-22654","post","type-post","status-publish","format-standard","hentry","category-category_news","tag-cve","tag-cvss","tag-exploit","tag-news","tag-none","tag-security","tag-tapic","tag-thn","tag-vulnerability"],"yoast_head":"\n