๐ข Beginner11 min readยทUpdated Feb 18, 2026
Data Breach Response: What to Do When Your Data Is Leaked
Step-by-step guide for individuals and businesses when a data breach occurs. Immediate actions, long-term protection, and recovery strategies.
In This Guide
|
Proactive monitoring:
- Have I Been Pwned (HIBP): Free service that checks if your email/phone appears in known breaches. Sign up for notifications.
- Password manager alerts: Bitwarden, 1Password, and Dashlane check your passwords against breach databases.
- Firefox Monitor: Mozilla's breach notification service (powered by HIBP).
- Google Password Checkup: Checks saved Chrome passwords against known breaches.
- Unexpected password reset emails
- Login alerts from unfamiliar locations
- Unfamiliar charges on bank/credit card statements
- Friends receiving spam from your accounts
- Account lockouts you didn't trigger
- New accounts opened in your name
- US: State-specific laws (all 50 states), typically within 30-60 days
- EU/UK: GDPR requires notification within 72 hours
- Australia: Notifiable Data Breaches scheme (OAIC)
Warning signs to watch for:
Breach notification laws:
Most countries require companies to notify you of breaches:
Step 1: Assess what was exposed
- What data was in the breach? (email, password, SSN, financial, health)
- Was the password hashed or plaintext?
- Is the compromised password used on other accounts?
- Change the password on the breached service (use your password generator!)
Step 2: Secure affected accounts
- Change the password on ANY account using the same password
- Enable 2FA if you haven't already
- Revoke all active sessions
- Check for unauthorized changes (email forwarding rules, recovery email/phone, connected apps)
- If financial data was exposed, contact your bank immediately
- Place a fraud alert on your credit reports (Equifax, Experian, TransUnion)
- Consider a credit freeze (prevents new accounts being opened)
- Review recent transactions for unauthorized charges
- File a dispute for any fraudulent charges
- Screenshot any breach notifications
Step 3: Protect financial information
Step 4: Document everything
Identity protection:
- Monitor your credit reports (free annual reports at AnnualCreditReport.com)
- Consider an identity monitoring service (many breached companies offer free monitoring)
- Set up Google Alerts for your name and phone number
- File an Identity Theft Report at identitytheft.gov (US)
- Transition to a password manager if you haven't already
- Audit and update ALL passwords (not just the breached one)
- Enable 2FA on every account that supports it
- Review and clean up account recovery options
- Remove unnecessary accounts (reduce attack surface)
- Check haveibeenpwned.com regularly
- Enable breach alerts in your password manager
- Review bank and credit card statements weekly
- Keep software updated on all devices
- Be extra vigilant for phishing (attackers may use breached data to craft convincing emails)
- Many data breaches result in class action lawsuits
- You may be entitled to compensation (credit monitoring, cash payment)
- Document your losses (time spent, financial impact)
Account security hardening:
Ongoing monitoring:
Legal options:
Before a breach (preparation):
โ Document an Incident Response Plan
โ Assign incident response team roles
โ Identify legal requirements (notification timelines, regulators)
โ Establish relationships with forensic investigators
โ Maintain cyber insurance
โ Conduct tabletop exercises annually
During a breach:
- Contain: Isolate affected systems, revoke compromised credentials
- Investigate: Determine scope, timeline, and attack vector
- Preserve evidence: Don't wipe systems before forensic analysis
- Notify: Legal counsel, regulators, affected individuals
- Remediate: Patch vulnerabilities, rotate secrets, review access controls
- Communicate: Transparent, factual updates to affected parties
- Post-mortem: Document what happened, how, and why
- Improve: Update security controls based on findings
- Test: Verify remediations are effective
- Train: Brief staff on lessons learned
- Audit: Review similar systems for the same vulnerability
- What happened (factual, specific)
After a breach:
Communication template: