Incident Response•6 min read•
What to Do After a Data Breach: Incident Response Action Plan
Step-by-step incident response playbook for when your credentials appear in a data breach: what to change, check and secure first.
What to Do When You Receive a Breach Notification
- Stay calm and verify the source: Check whether the notification is a genuine email or a phishing lure. Instead of clicking links in the email, go directly to the official website of the service.
- Change the breached password immediately: Use our Web Crypto based password generator to create a new, unique password of at least 18 characters.
- Update every other account that used the same password: If you reused that password anywhere else, those accounts are now direct targets. Change them all right away.
- Sign out of active sessions: Use the "sign out of all other devices" option under Settings > Security.
- Turn on 2FA or a passkey: If the account does not have it yet, set up hardware or TOTP-based multi-factor authentication.
- Watch your bank and financial accounts: If card or identity details leaked, contact your bank to cancel the cards or enable alerts for suspicious transactions.
How to Find Out Whether You Were Affected
- Check your email address: Services such as Have I Been Pwned list the public breaches in which an email address has appeared.
- Check your passwords: Our pwned password check tells you whether a password appears in known breach data. Thanks to k-anonymity, only the first 5 characters of its SHA-1 hash are sent; the password itself never leaves your browser.
- Review account activity: Look at recent logins, connected devices, forwarding rules in your email and any recovery email or phone number that was changed without your knowledge.
Mistakes to Avoid After a Breach
- Changing only one character: Moving from
Password1!toPassword2!is the first variation attackers try. Generate a completely new random password. - Answering "verification" calls or messages: Breached data is often followed by targeted phishing. Your bank or provider will not ask for your password or one-time code.
- Waiting: Leaked credentials are traded and tested by bots within hours of exposure, so act on the same day.
Preventing the Next Breach from Hurting You
You cannot stop a service from being breached, but you can limit the damage: use a unique password for every account, keep them in a password manager, enable 2FA everywhere and use passkeys where they are available.
Generate Strong Credentials Instantly
Hardware-backed Web Crypto API with zero logging and zero server contact.