After a Breach Notice: 7 Account Changes to Make Today
Archi4 min read
Contents
- The notice is the starting gun, not the story
- 1. Separate your email into tiers
- 2. Replace reused passwords, starting with email
- 3. Turn on phishing-resistant two-factor authentication
- 4. Audit sessions and connected apps
- 5. Freeze your credit, do not just monitor it
- 6. Change how you answer security questions
- 7. Check what the breach actually exposed before you act
- A note on the companies
The notice is the starting gun, not the story#
When a company discloses a breach, the useful question is not which database leaked. It is what an attacker can now do with your name, email, address, and possibly a password hash. Most follow-on damage comes from a handful of habits that take an afternoon to fix. This checklist is ordered by impact, not by how easy the settings are to find.
1. Separate your email into tiers#
Your primary address is probably on dozens of marketing lists and in at least one leaked database. Create two more: one for shopping and newsletters, one for financial and government accounts. Point recovery for the important tier only at the address you never publish. This single change limits how much a future breach exposes, because the address that appears in dumps is no longer the one that resets your bank login.
Use a password manager's alias feature if it has one. Apple's Hide My Email and similar tools generate throwaway addresses that forward to your inbox. Turn off forwarding for the alias once a service stops being useful.
2. Replace reused passwords, starting with email#
Attackers do not crack hashes for every account. They take a leaked password and try it against mail providers, social networks, and retailers. Your email password is the master key because it can reset everything else. Change it first, then work outward to banking, cloud storage, and social accounts.
A manager makes this an hour of work instead of a weekend. If you are not using one, start with the built-in option on your phone or browser and export the list later. The point is unique strings, not a perfect tool.
3. Turn on phishing-resistant two-factor authentication#
SMS codes are better than nothing, but they can be intercepted through SIM swaps and real-time phishing proxies. Move your most important accounts to an authenticator app or, better, a hardware security key or passkey. Google, Microsoft, and Apple all support passkeys now, and many banks do too.
Keep SMS as a backup only where a provider forces it. Print recovery codes and store them somewhere physical, not in a note on the same phone.
4. Audit sessions and connected apps#
Breaches often expose tokens, not passwords. Check the active sessions list on your email, social, and cloud accounts and sign out anything you do not recognize. Then open the connected apps or third-party access page and revoke everything you stopped using. An old calendar app with full mailbox access is a standing invitation.
Do this quarterly. It takes ten minutes and catches the slow leaks that password changes miss.
5. Freeze your credit, do not just monitor it#
Credit monitoring tells you after a loan application is filed in your name. A freeze blocks the check. In the United States, freezes at the three major bureaus are free and can be lifted temporarily when you actually need credit. In the UK and much of Europe, similar controls exist through the major agencies.
Do this today if your notice included a national ID number, date of birth, or full address. Those three fields are enough for synthetic identity fraud, and the cleanup can take months.
6. Change how you answer security questions#
Mother's maiden name and first pet are public facts on social media. Treat security questions as another password field: store invented answers in your manager. If a provider lets you skip them, skip them.
For phone support, ask whether the agent will accept a callback number on file rather than a code read aloud. Some banks and mobile carriers now support a verbal passphrase. Ask for it; the feature exists more often than the website suggests.
7. Check what the breach actually exposed before you act#
Not every notice warrants a credit freeze. A leaked newsletter list is different from a leaked password hash and different again from a leaked government ID. Read the notice for the specific data categories and whether passwords were hashed with a modern algorithm or stored in plain text. If the company is vague, check your own account history for unfamiliar logins and password reset emails.
Keep a short log: date of notice, company, data exposed, actions taken. If a second notice arrives from the same company, that record changes how you respond.
A note on the companies#
Most breach notices arrive months after the incident. That lag is normal and not a reason to wait. The settings above are within your control, and each one reduces the value of the data that leaked. Start with the email password and the credit freeze. The rest can follow this week.
More articles