Multimeter Resolution vs Accuracy: How to Read the Specifications
How to Create a Strong Password and Protect Your Account
Last Updated: November 18, 2026
A strong password is long, difficult to predict, and used for only one account. A password manager can generate and store different passwords so you do not have to memorise them all.
Password strength is only one part of account protection. MFA, passkeys where available, secure recovery methods, and protection against phishing also matter.
The steps below apply generally. Individual services may have different length limits, supported characters, and recovery arrangements.
Table of Contents
What Makes a Password Strong?
CISA recommends long, random, unique passwords. Each quality addresses a different problem.
| Quality | Why it matters |
|---|---|
| Long | Makes exhaustive guessing more difficult when the password is otherwise unpredictable |
| Random or unpredictable | Avoids familiar patterns, personal details, and common phrases |
| Unique | Prevents one exposed password from directly unlocking other accounts |
Length alone is not enough. A long, recognisable phrase can still be predictable, while a unique password can still be weak if it follows an obvious pattern.
As a practical starting target, use at least 16 characters where the service supports them. Do not treat that number as a guarantee: randomness and uniqueness remain important.
Create the Password With a Password Manager
For most accounts, let an appropriate password manager generate a new password.
- Open the correct website or application.
- Use the manager’s password generator.
- Select a long, randomly generated password compatible with the service.
- Save it to the correct account entry.
- Confirm that the new credential works before discarding the old one.
CISA recommends password managers because they can create and store distinct credentials, reducing the need to remember many passwords.
Do not paste a real password into a public chat, unfamiliar strength checker, or support message. Use the manager’s own features or the account provider’s approved process.
No password published in an article should become your actual password.
If You Must Remember It, Use a Random Passphrase
A passphrase combines words into a longer password.
The important distinction is how the words are chosen. CISA suggests a memorable phrase built from four to seven unrelated words.
Prefer randomly selected words rather than:
- A famous quotation.
- Song lyrics.
- A passage from a popular book.
- A sentence from your public profile.
- Names, birthdays, or other personal information.
- A familiar phrase with predictable substitutions.
Turning a well-known quotation into initials does not necessarily make it unpredictable.
Generate a fresh phrase for your own use. Do not copy an example from a guide or reuse the phrase across accounts.
Use a Different Password for Every Account
Password reuse connects otherwise separate accounts.
If one service exposes your credentials, someone may try the same combination elsewhere. Google’s security guidance specifically warns that a compromised password reused across sites can expose multiple accounts.
Changing a final number or adding the site name to the same base password is not a strong separation strategy.
Prioritise replacing reused credentials on:
- Your main email account.
- Your password manager.
- Financial accounts.
- Important work accounts.
- Accounts used to recover other services.
Then work through the remaining reused passwords.
Protect the Password Manager Too
A password manager reduces the burden of remembering credentials, but its own access and recovery need protection.
Use a strong, unique master password if the product requires one. Enable supported MFA and understand how you would recover access if your usual device became unavailable.
The FTC recommends protecting the password manager with a strong password and using it to generate and remember other credentials.
Check:
- Which devices are signed in.
- How updates are installed.
- Whether automatic locking is configured.
- What recovery information exists.
- Where any recovery material is kept.
Do not store the only copy of essential recovery information in the account it is intended to recover.
Add MFA or Use a Passkey Where Available
MFA requires an additional type of proof beyond the password. It can reduce the risk that a stolen password alone is enough to enter the account.
Passkeys offer a different sign-in approach. Google describes them as an alternative that can use a device’s fingerprint, face verification, or screen lock and provides stronger resistance to phishing than a reusable password.
Where supported:
- Prefer phishing-resistant sign-in methods.
- Follow the account provider’s enrolment instructions.
- Protect the device used for sign-in.
- Review backup and recovery options.
- Remove access that is no longer needed.
Never approve an authentication request you did not initiate. A strong password is not a reason to ignore an unexpected prompt.
Keep Recovery Information Secure and Current
Recovery email addresses, telephone numbers, backup codes, and registered devices can help restore access. They must also be protected.
For a Google Account, Google’s account-security settings include a Security Checkup and recovery information that can support alerts and account recovery.
For any service:
- Keep recovery details current.
- Remove telephone numbers or addresses you no longer control.
- Protect the recovery email account with its own unique credentials.
- Store backup codes in a protected location.
- Understand what to do if a device is lost.
- Review recovery settings after a significant account change.
Go directly to the provider’s official application or website when making changes. Do not follow an unexpected recovery link merely because a message claims your account is at risk.
When Should You Change a Password?
Change a password when there is evidence or a reasonable suspicion that it has been exposed, when it is reused, or when the account provider or your organisation requires action after an incident.
NIST’s authentication guidance rejects routine periodic password changes without evidence of compromise. A calendar-based change does not fix phishing, reuse, or weak recovery arrangements.
If compromise is suspected:
- Use a device you believe is safe.
- Open the service through its official application or address.
- Create a new, unique password.
- Review active sessions and account changes.
- Check MFA and recovery methods.
- Replace the exposed password anywhere else it was reused.
- Follow the provider’s or employer’s incident instructions.
Changing the password may not be the only action needed. Review the account rather than assuming the reset resolves every problem.
Use Work-Approved Password Tools
Work accounts may have specific requirements for password storage, sharing, recovery, and administration.
Use the organisation’s approved manager and authentication methods. Do not move business credentials into a personal account or send them through ordinary chat simply because it is convenient.
A remote working cybersecurity checklist connects account protection with approved devices, remote access, file handling, recovery, and reporting.
Ask IT when a requirement is unclear or a supported sign-in method is not working. Avoid creating an unofficial workaround that others cannot maintain or recover.
Conclusion
Create a strong password by making it long, unpredictable, and unique. A password manager is usually the simplest way to apply those qualities across many accounts.
Then protect the surrounding access routes: MFA or passkeys, recovery information, signed-in devices, and the tools holding your credentials. A good password helps, but reliable account protection depends on those measures working together.