Account Security•7 min read•

Digital Security Audit: A Step-by-Step Account Security Checklist

Audit your accounts in one afternoon: account inventory, breach and strength checks, an MFA matrix, recovery details and third-party app permissions.

For most people a security audit only happens after something goes wrong: a password is stolen, or a sign-in alert arrives from an unknown device. You can reverse that. The steps in this guide fit into one afternoon, and you can compare the results with your next audit.

What Is a Digital Security Audit and Why Repeat It?

A digital security audit is a one-by-one review of your accounts, passwords, sign-in methods and app permissions. The goal is to answer "am I secure?" with a concrete list instead of a guess.

It needs repeating because your digital footprint keeps changing. You sign up for new services, forget old apps, change your phone number and click "Sign in with Google". Small changes add up to blind spots. A password's safety also depends on what happens to the service that stores it: a breach can make it worthless overnight even if you did nothing wrong.

The output of an audit is an action list: which passwords to change, which accounts lack a second factor, which permissions to remove.

Build an Account Inventory

Every account you own but have forgotten is a door you assume is locked. Look for accounts in:

  • Your password manager: every saved login.
  • Your inbox: search for "welcome", "confirm your account", "account created".
  • Your browser's saved passwords: logins from before you used a manager.
  • The app list on your phone: apps you deleted while the account stayed open.

Sort what you find by impact if it were taken over:

Priority Examples Risk
Critical Primary email, bank, cloud storage, domain registrar Password-reset chain and financial access
Medium Social media, shopping, subscriptions Impersonation, data loss
Low One-off sign-ups, old forums Low; can be closed

The most important row is your primary email: most reset links go there. If it is compromised, other accounts can be taken over through resets no matter how strong their passwords are. Always start the audit there. Close accounts you no longer use; a deleted account shrinks your attack surface directly.

Password Hygiene: Breach Check and Strength

For every critical account ask three questions:

  1. Is this password used anywhere else? Reuse is a bigger risk than weakness; one breach exposes every account that shares the password.
  2. Does this password appear in a known breach? Check with the HIBP-based breach checker. Thanks to k-anonymity, the password itself is never sent; only the first characters of its SHA-1 hash are queried.
  3. How strong is it? A zxcvbn-based Password Strength Test analyses patterns and estimates crack time, which is far more realistic than "8 characters and a digit".

Current guidance in line with NIST SP 800-63B moves away from "change every 90 days and always add a symbol":

  • Length is what makes a password strong; forced complexity rules push people into predictable patterns.
  • Passwords should be checked against breached-password lists and rejected if found.
  • Forced periodic changes are not recommended without evidence of compromise.
  • Pasting should not be blocked, so password managers work smoothly.

Replace weak passwords with a generator that uses cryptographic randomness in your browser. For passwords you must remember, use the Diceware/EFF-based passphrase generator; administrators may prefer the bulk generator with TXT/CSV export.

MFA Matrix: Fill the Gaps

However strong a password is, it is not enough on its own (what are 2FA and passkeys?). MFA adds something you have (a device or security key) to something you know.

From strongest to weakest:

  • Security key (FIDO2/WebAuthn): phishing-resistant, the strongest common option.
  • Authenticator app (TOTP): time-based codes on your phone; a good balance.
  • SMS: better than nothing, but the weakest link because of SIM swap attacks. NIST also treats SMS as a restricted method.

List your critical accounts, write the active method next to each one and keep going until no cell is empty.

Account Current Target
Primary email To check Authenticator app
Bank To check App + the bank's own approval
Cloud storage To check App; security key if possible

Order of priority: primary email → financial accounts → cloud storage → social media. Do not leave backup codes on screen; print them and store them safely. Imagine losing the phone with your authenticator: is your recovery path ready?

Recovery Details and Backup Channels

Recovery details are the way back into an account, and also a way in for attackers. For each critical account check:

  • Is the recovery email an address you can still reach? If reset links go to a closed mailbox, the account is effectively locked.
  • Is the recovery phone number current?
  • If security questions are mandatory: NIST does not recommend knowledge-based authentication. Pick random answers and store them in your password manager.
  • Have you generated backup codes, and is there an offline copy?

Your password manager is also a single point of failure: keep an encrypted backup offline and make sure its master password and its own MFA are in order.

Clean Up Third-Party App Permissions

"Sign in with Google" and "Connect with Facebook" grants pile up over the years. An OAuth grant is a key held by that developer, and it can stay valid after you delete the app from your phone.

  • Open the connected apps / third-party access pages of your email provider and social accounts one by one.
  • Remove anything you do not recognise or no longer use.
  • Review browser extensions; delete the unnecessary ones and question the permissions of the rest.
  • Developers: find and replace hardcoded API keys. Generate new ones with a cryptographically secure tool such as the Token Generator; a hand-made "secret" is not secret.

If you share an office or guest network, include the Wi-Fi password: handing out access through a Wi-Fi QR code is safer than sending the password back and forth in chats.

Action Plan and Routine

The audit ends with a list; security starts with action. Order your findings:

  1. Breached or reused passwords (critical accounts first): change them now.
  2. Missing MFA: add it, starting with critical accounts.
  3. Outdated recovery details: fix them.
  4. Unused accounts and permissions: close and remove them.

Then set a routine: a 30-minute quick check every three months (critical accounts, breach check, connected apps) and a full audit once a year. Put both reminders in your calendar.

The same logic scales to a company: a corporate password policy aligned with NIST SP 800-63B recommends breach screening and password manager support instead of forced periodic changes.

Frequently Asked Questions

How often should I run a security audit? A short check of critical accounts every three months and a full audit once a year is a sensible start. If you hear about a breach at a service you use, check that account immediately.

Do I need paid software? No. Breach checks, strength tests and secure password generation can all be done with free browser-based tools. A systematically completed checklist matters more than the tool.

Is my password sent during a breach check? HIBP-style checks use k-anonymity: only the first characters of the SHA-1 hash leave your device, never the password itself. Still, use tools that clearly implement the protocol.

Where should I keep my passwords? In a password manager with one strong master password, MFA turned on and an encrypted offline backup. Browsers, note apps and email drafts are common but risky places.

Is SMS two-step verification enough? It is better than nothing but the weakest method; a SIM swap lets an attacker receive your codes. Move to an authenticator app, or a security key if you can.

Start the Audit

The step that takes longest is replacing passwords, so keep a reliable generator at hand. The Password Generator creates passwords in your browser with crypto.getRandomValues; nothing is sent to a server or stored. You choose the length, character sets and characters to exclude, and the passphrase, PIN, breach check and strength test tools are on the same site.

Generate Strong Credentials Instantly

Hardware-backed Web Crypto API with zero logging and zero server contact.

Open Password Generator →