Skip to main content
Toolsbase Logo

How to Create Strong Passwords — Understanding Strength and Best Practices

Toolsbase Editorial Team
(Updated: )
PasswordSecurityPrivacy

The Current State of Password Security

As online services continue to multiply, passwords remain the front line of account protection. However, many users still rely on short, easily guessable passwords and reuse them across multiple services.

Analysis of password databases leaked in data breaches reveals that the top entries are consistently weak choices like "123456," "password," and "qwerty." Attackers are well aware of these tendencies and try the most common passwords first.

Common Attack Methods

Understanding the main attack methods used to crack passwords is the first step toward effective defense.

Brute Force Attack

This method systematically tries every possible combination of characters. The shorter the password, the dramatically shorter the time needed to crack it.

Password Length Lowercase Only Upper + Lower + Numbers + Symbols
4 characters Seconds Minutes
8 characters Hours Years
12 characters Thousands of years Millions of years
16 characters Astronomical Virtually impossible

As this table shows, password length is the most important defensive factor.

Dictionary Attack

This method uses word lists containing common dictionary words and frequently used passwords. Common English words like "sunshine," "welcome," and "dragon" can be cracked in seconds.

Note that romanized words from other languages (like "sakura," "tokyo," or "bonjour") are also included in modern attack dictionaries.

Credential Stuffing

This technique automatically tries email-password combinations leaked from previous data breaches against other services. Password reuse is the primary factor that makes this attack successful.

Social Engineering

Rather than a technical attack, this approach exploits human psychological vulnerabilities to obtain passwords. It includes phishing emails, fake login pages, and phone-based social engineering.

Entropy and Password Strength

"Entropy" is a quantitative metric for evaluating password strength. Measured in bits, a higher value means the password is harder to predict.

Calculating Entropy

Entropy is calculated using the following formula:

Entropy = log2(character set size ^ password length)
        = password length × log2(character set size)

The entropy per character for each character set is:

Character Set Count Entropy per Character
Digits only 10 3.32 bits
Lowercase only 26 4.70 bits
Upper + lowercase 52 5.70 bits
Upper + lower + digits 62 5.95 bits
Upper + lower + digits + symbols 94 6.55 bits

For example, a 12-character password using upper/lowercase letters and digits has an entropy of 12 × 5.95 = 71.4 bits, which is considered strong. Generally, 60 bits or more is recommended, and 80 bits or more is considered very strong.

Balancing Length and Complexity

The same entropy can be achieved either by using complex character sets in a shorter password or by using simpler character sets in a longer one.

8 chars (upper + lower + digits + symbols): 8 × 6.55 = 52.4 bits
16 chars (lowercase only):                 16 × 4.70 = 75.2 bits

This example demonstrates that a 16-character lowercase-only password has higher entropy than a complex 8-character password with symbols. A long, memorable password is actually more secure than a short, complex one.

Practical Password Strategies

Use Passphrases

A "passphrase" combining four or more random words achieves both high entropy and memorability.

Example: correct-horse-battery-staple
Length: 31 characters
Advantage: Easy to remember, resistant to brute force

However, avoid using well-known phrases, song lyrics, or proverbs directly, as they may be included in attacker phrase dictionaries.

Adopt a Password Manager

Setting unique, strong passwords for every service and remembering them all is not realistic. A password manager provides the following benefits:

  • Generates unique random passwords for each service
  • Stores them securely in an encrypted database
  • Auto-fill prevents accidental entry on phishing sites
  • You only need to remember one master password

Popular password managers include 1Password, Bitwarden, and KeePass.

Enable Two-Factor Authentication (2FA)

Rather than relying on passwords alone, combining them with two-factor authentication significantly strengthens security.

Method Security Convenience
SMS verification Moderate High
Authenticator app (TOTP) High Moderate
Hardware key (FIDO2) Very high Somewhat low
Passkey Very high High

SMS verification carries the risk of SIM swap attacks, so authenticator apps or hardware keys are recommended when possible.

What to Avoid

Here are practices to avoid in password management:

  • Reusing passwords: If one service is compromised, all other accounts using the same password are at risk
  • Using personal information: Birthdays, phone numbers, and pet names are easy to guess
  • Simple patterns: Keyboard patterns (qwerty), sequences (123456), repetitions (aaaaaa)
  • Leaving written notes: Writing passwords on sticky notes attached to your monitor is unacceptable
  • Sharing: Never share your passwords with others (separate accounts are recommended even for family members)

Is Regular Password Rotation Necessary?

The idea that passwords should be changed regularly was once mainstream, but NIST (National Institute of Standards and Technology) and many other security organizations no longer recommend routine password changes.

The reason is clear: when forced to change passwords regularly, users tend to set weaker, more memorable passwords or make trivial changes like incrementing a number at the end.

Password changes should only be necessary in cases such as:

  • When you receive a data breach notification from a service
  • When there are signs of unauthorized access
  • When someone may have learned your password

Deep Dive: Attack Methods Explained

Rainbow Table Attacks

Unlike brute force attacks that compute hashes on the fly, rainbow table attacks use precomputed tables mapping hash values back to their original passwords. If a password database using MD5 or SHA-1 is leaked, attackers can reverse-lookup millions of passwords in seconds.

Salting as a Defense

The countermeasure is "salting" — appending a random string to each password before hashing. This ensures that even identical passwords produce different hash values, rendering precomputed rainbow tables useless. Attackers would need to compute hashes from scratch for each individual user.

Modern secure password storage uses algorithms like bcrypt, scrypt, or Argon2, which incorporate built-in salting and are deliberately slow to compute, providing strong resistance against brute force and rainbow table attacks.

Password Spraying

The opposite of brute force: instead of trying many passwords against one account, password spraying tries one common password (e.g., "Summer2024!") against many accounts simultaneously.

By keeping the number of attempts per account low, attackers stay under the radar of lockout thresholds. This technique is especially effective against corporate authentication systems and has been used in numerous high-profile breaches.

Phishing and Spear Phishing

Phishing creates convincing replicas of legitimate sites to trick users into entering their credentials. No matter how strong your password is, entering it on a fake site hands it directly to the attacker.

Spear phishing is a more targeted form that uses personal information gathered from social media and public sources to craft convincing, personalized messages. Business Email Compromise (BEC) — where attackers impersonate executives to defraud finance teams — is a sophisticated variant that costs businesses billions annually.

Credential Stuffing (Expanded)

When attackers obtain a leaked database of email-password pairs, they don't just try those credentials on the original site. They run them against hundreds of other services simultaneously using automated tools. One leaked account can become the key to dozens of others.

This is why password reuse is so dangerous — even a breach at a low-security site can cascade into access to your email, bank, or corporate systems.


Password Managers: A Detailed Guide

Why You Need a Password Manager

The average person has between 80 and 150 online accounts. Memorizing unique, strong passwords for every service is humanly impossible. Without a password manager, most people fall into dangerous habits:

  • Reusing the same password across services
  • Storing passwords in a plain text file or spreadsheet
  • Choosing weak, memorable passwords
  • Making trivial variations when forced to change passwords ("password1" → "password2")
Tool Type Pricing Open Source Notable Features
Bitwarden Cloud / Self-hosted Free tier available Yes Security-audited, sufficient for most users
1Password Cloud From $3/month No Strong family and business features
KeePassXC Local only Free Yes Fully offline, complete self-control
Dashlane Cloud From $4.99/month No Dark web monitoring included
Nordpass Cloud From $1.49/month No Integration with NordVPN

Bitwarden is the top recommendation for most users. It's open source, independently audited, and the free tier covers everything most people need.

Is Putting All Passwords in One Place Safe?

This is a common concern — but the answer is yes, when done correctly. Well-designed password managers use zero-knowledge encryption: your vault is encrypted with a key derived from your master password, and the service provider cannot read your passwords even if they wanted to.

Even if the company's servers are breached, attackers only obtain encrypted data. Without your master password, it's computationally infeasible to decrypt.

Your master password should:

  • Be at least 20 characters (a passphrase is ideal)
  • Never be reused anywhere else
  • Be written down on paper and stored in a physically secure location as a backup (don't rely solely on digital memory)

How to Get Started

  1. Choose a tool: Bitwarden is a solid starting point
  2. Create a strong master password: Use a 20+ character passphrase
  3. Install the browser extension: Available for Chrome, Firefox, Safari, and Edge
  4. Import existing passwords: Export from your browser's password manager and import
  5. Update critical accounts first: Start with email, banking, and work accounts — replace with randomly generated passwords
  6. Enable 2FA on the password manager itself: Use TOTP or a hardware key

Two-Factor Authentication (2FA): A Complete Guide

The Three Factors of Authentication

Security authentication relies on three types of factors:

  1. Something you know: Password, PIN, security question
  2. Something you have: Smartphone, hardware key, smart card
  3. Something you are: Fingerprint, face scan, iris recognition

Two-factor authentication combines any two of these from different categories. The most common pairing is a password (knowledge) plus an authenticator app (possession).

Problems with SMS-Based 2FA

SMS 2FA is convenient and widely supported, but it has significant weaknesses:

SIM Swapping: Attackers convince your mobile carrier's customer service representatives to transfer your phone number to a SIM card they control. Once successful, they receive all your SMS messages, including 2FA codes. High-profile celebrities, cryptocurrency holders, and executives are frequent targets.

SS7 Protocol Vulnerabilities: The legacy Signaling System No. 7 (SS7) protocol that underpins global mobile networks has known security flaws that can be exploited to intercept SMS messages. This requires sophisticated capabilities, but is within reach of well-resourced threat actors.

Real-Time Phishing (AiTM): Adversary-in-the-Middle phishing proxies relay your OTP code to the real site in real time, allowing attackers to hijack your session before the code expires.

How TOTP Works

Apps like Google Authenticator, Microsoft Authenticator, and Authy generate Time-based One-Time Passwords (TOTP).

The mechanism:

  1. The service and app share a secret key (scanned via QR code at setup)
  2. Both combine the current Unix timestamp and the secret key using the HMAC algorithm
  3. A new 6-digit code is generated every 30 seconds
  4. The code is generated locally — no network connection required

Unlike SMS, the code is never transmitted over a network, making it immune to interception. However, TOTP codes can still be phished if a user enters them on a fake site.

FIDO2 / WebAuthn and Passkeys

Hardware security keys (like YubiKey or Google Titan Key) offer the strongest phishing-resistant 2FA available today.

Under the FIDO2 protocol, authentication uses public-key cryptography tied to the specific domain of the site. Even if you're tricked into visiting a near-identical fake domain, authentication fails because the domain doesn't match. Phishing is cryptographically neutralized.

Passkeys make FIDO2 accessible to everyone. Instead of a physical key, your device's built-in biometrics (fingerprint, Face ID) or screen lock serve as the authenticator.


Enterprise Password Policy Best Practices

What NIST Says Now

The National Institute of Standards and Technology (NIST) significantly revised its password guidelines in 2017 and again in 2024. The updates challenged many long-held assumptions:

What NIST no longer recommends:

  • Mandatory periodic password changes
  • Complex composition rules (must include uppercase, number, symbol)
  • Password hints
  • Knowledge-based security questions

What NIST recommends instead:

  • Minimum length of 8 characters (12+ recommended)
  • Accept passwords up to 64+ characters
  • Allow all Unicode characters including spaces
  • Do not prevent users from pasting into password fields
  • Screen new passwords against lists of commonly used and previously breached passwords

Key Security Controls for Organizations

1. Single Sign-On (SSO)

SSO allows employees to authenticate once and access multiple systems. This reduces the number of passwords employees must manage and centralizes authentication — making it easier to enforce strong security and revoke access quickly when needed.

Leading SSO solutions: Okta, Microsoft Entra ID (formerly Azure AD), Google Workspace

2. Privileged Access Management (PAM)

Administrative accounts should not be permanently active. Implement Just-in-Time (JIT) access: privileged access is granted only when needed and automatically revoked afterward. This limits the blast radius if credentials are compromised.

3. Compromised Password Screening

Integrate with services like Have I Been Pwned (HIBP) to automatically block employees from setting passwords that appear in known breach databases. This is a low-cost, high-impact control.

4. Zero Trust Architecture

Moving from "trust but verify" to "never trust, always verify." Every access request is authenticated and authorized regardless of network location. Zero Trust is now considered the gold standard for enterprise security architecture.

Security Awareness Training

Technology alone isn't enough. Human factors are involved in the majority of security incidents.

  • Simulated phishing campaigns: Send mock phishing emails and use click-throughs as a teaching moment rather than a punitive one
  • Regular security training: Annual or semi-annual mandatory training covering social engineering, phishing recognition, and password hygiene
  • Incident reporting culture: Make it psychologically safe to report mistakes — people who fear punishment hide errors, making breaches worse

Passwordless Authentication: The Future Is Now

Why Passwords Are Fundamentally Problematic

Passwords carry inherent limitations:

  • Memory limitations: Humans cannot reliably remember large numbers of strong, unique passwords
  • Theft risk: Phishing, malware, and shoulder surfing can steal passwords regardless of strength
  • Cost: Password resets reportedly account for 20–50% of IT helpdesk volume at many organizations
  • Friction: Password entry is consistently identified as a top source of login abandonment

How Passkeys Work

Passkeys are built on the FIDO2/WebAuthn standard, jointly championed by Apple, Google, and Microsoft.

Registration:

  1. When registering, your device generates a public-private key pair
  2. The public key is sent to the service and stored on their server
  3. The private key is stored in your device's secure hardware element (Secure Enclave on Apple, TPM on Windows)

Login:

  1. The service sends a cryptographic challenge
  2. You unlock the private key using biometrics or device PIN — locally on your device
  3. The private key signs the challenge
  4. The service verifies the signature using your stored public key

The private key never leaves your device and is never transmitted over the network. There is no password to phish, leak, or crack.

Key advantages:

  • Phishing-resistant: Bound to the specific domain, fake sites get nothing
  • Zero server-side secrets: Even if the server is breached, no passwords are exposed
  • Cross-device sync: Via iCloud Keychain, Google Password Manager, or 1Password
  • Better UX: A touch of your fingerprint is faster than typing any password

Adoption Landscape

As of 2025, passkeys are supported by Google, Apple, Microsoft, GitHub, PayPal, Amazon, Shopify, and hundreds of other services. The FIDO Alliance reports over 13 billion passkey-enabled user accounts worldwide.

Consumer-facing deployments are accelerating, and enterprise adoption is following through solutions like Okta FastPass, Microsoft Entra ID passwordless authentication, and Cisco Duo.

An alternative passwordless approach: clicking a link or entering a short code sent to your email logs you in directly — no password needed. These expire quickly (typically 10–15 minutes) and are single-use.

The trade-off: email account security becomes paramount. If your email is compromised, all services using magic links are accessible to the attacker.


Tools for Better Password Security

If creating strong passwords manually feels daunting, dedicated tools make the job easy:

  • Password Generator: Instantly generate random passwords to your exact specifications — length, character sets, and more. Try the Password Generator →
  • Password Strength Checker: Evaluate how strong your current passwords are with detailed metrics including entropy calculation and estimated crack time. Try the Password Strength Checker →

Both tools run entirely in your browser — your passwords are never sent to any server.


Detecting Security Breaches Early

Using Have I Been Pwned (HIBP)

Regularly check whether your email address or passwords have appeared in known data breaches at haveibeenpwned.com. The service maintains a database of billions of leaked credentials. Enter your email address to see which services have been compromised, and sign up for breach notifications to be alerted when your address appears in a new leak.

Most modern password managers integrate with the HIBP API to automatically alert you when any of your stored passwords appear in breach databases — without ever sending your actual passwords to the API.

Warning Signs of Unauthorized Access

If you notice any of the following, change your password immediately and audit the account for unauthorized activity:

  • Login notification emails or SMS messages you didn't trigger
  • Account settings (email, phone number, password) changed without your action
  • Purchase history or activity logs showing transactions you didn't make
  • Inability to log in — an attacker may have changed your password
  • Contacts reporting suspicious messages or posts that appear to be from your account

After a Breach: What to Do

  1. Change the compromised password immediately — on the affected service and anywhere else you used the same password
  2. Revoke active sessions — most services have a "sign out all devices" option in security settings
  3. Check for unauthorized changes — review connected apps, email forwarding rules, and recovery methods
  4. Enable 2FA if it wasn't already active
  5. Monitor for identity theft — if financial accounts are affected, monitor credit reports and consider a credit freeze

Conclusion

The fundamentals of secure passwords come down to three things: length, uniqueness, and management. Set random passwords of 12 or more characters for each service, manage them with a password manager, and enable two-factor authentication wherever possible. Implementing these three measures alone will significantly reduce your password-related risks.

If you want to go further, migrate to passkeys wherever supported. Passkeys are phishing-resistant, require no memorization, and deliver a better login experience than any password. The transition away from passwords is already underway — and it's a change that benefits everyone.

Password security is a moving target. The threat landscape evolves constantly, and yesterday's best practices may be outdated tomorrow. Stay informed, follow updated guidelines from NIST and your country's cybersecurity agency, and keep your security posture current.