Security Checkup

Price captures verified 2026-08-09; overall scores unpublished

What to Do After a Data Breach

After a data breach notification, prioritize containment: unique password changes for the affected account and anything reused, MFA, and fraud alerts or freezes where relevant, before shopping for new subscriptions. Paid identity monitoring may help later for residual alert needs, but it is not step one. This guide invents no victim counts or breach sizes. Optional product cards below use claim-ledger prices from 2026-08-09; overall scores stay unpublished.

Run Personal Security Checkup →
  • Guide · Incident · ~15 min read

Urgent framing

Contain accounts first. Paid monitoring is a later optional step, not a substitute for password changes, MFA, and freezes.

Do these immediately

  1. 1Confirm the notice is real (official vendor channels, not a phishing clone)
  2. 2Change the breached account password to a unique one
  3. 3Change any other account that shared that password
  4. 4Enable MFA everywhere you still can
  5. 5Watch statements; consider freezes/fraud alerts if financial data was involved
  6. 6Only later evaluate monitoring products if residual risk remains
Run Personal Security Checkup →

Response plan

  1. 1

    Contain the account

    Free

    Reset credentials on the breached service and any reused passwords.

    • Change password now
    • Revoke suspicious sessions
    • Enable MFA
  2. 2

    Protect identity rails

    Free

    If SSN or similar data may be involved, use free credit freezes and fraud alerts where available.

    • Freeze credit at major bureaus when appropriate
    • Watch bank and card activity
    • File official reports only through trusted government channels when needed
  3. 3

    Reduce public enrichment

    Free

    Broker listings can worsen fraud targeting. Free opt-outs help; paid removal is optional.

    • Search for fresh people-search listings
    • Submit free opt-outs
    • Consider automation only if volume is high
  4. 4

    Optional paid monitoring

    Optional paid

    After free steps, Aura may fit if you want ongoing monitoring. Do not buy out of panic alone.

    • Read who should not buy
    • Verify plan scope before purchase
  5. 5

    Assume phishing follows breaches

    Free

    Attackers know you are anxious. Be skeptical of messages that demand immediate payment, gift cards, or remote-access software. Use bookmarks to reach banks and vendors.

    • Do not click “urgent vault” links in email without verifying
    • Do not share one-time codes with callers
    • Document what data types the notice claims were involved
  6. 6

    When paid protection is a later step

    Optional paid

    After containment, some households want monitoring-oriented coverage (Aura is the pack qualitative option). Who should not buy yet: anyone still reusing the breached password elsewhere, or anyone who needs a published overall score before deciding.

    • Containment complete first
    • Match monitoring vs removal jobs
    • Use /go/aura only deliberately after disclosure

What this response plan cannot fix

  • Undo of data already stolen in the breach
  • Guaranteed prevention of all follow-on fraud
  • Requests for your passwords or banking data from Security Checklist
  • Undoing data already copied by attackers
  • A promise that any paid product erases breach consequences

Sources

  • Official breach notification / vendor status pages, Use primary sources for each incident; this guide stays generic on purpose
  • Credit freeze / fraud alert public guidance, Country-specific processes; confirm with local agencies
  • Aura / Incogni claim ledgers, Verified 2026-08-09 starting_price captures; scores unpublished
  • Vendor marketing pages, aura.com / incogni.com / joindeleteme.com / lifelock.norton.com feature and pricing claims, not independent evidence; re-verify same-day
  • Security Checklist methodology, How commercial pages are structured before scores publish, /methodology/
  • Claim ledger (T014), data/claim-ledgers/aura.json, incogni.json, deleteme.json, lifelock.json, surfshark.json: starting prices verified 2026-08-09; overall scores unpublished

Next steps

Frequently asked questions

Expert guides & insights

Related guides

Stay in the same problem space without jumping brands.

Want launch updates?

The email newsletter is not running yet. Use Contact if you want a human reply when it opens. No fake signup form.

Contact SecurityChecklist