Skip to content
Post Mortem

Playbook ยท Act in the first 15 minutes

My database or storage might be open to the public

Close the door first, then work out who walked in.

CRITICALTake a breath. Do these in order.

How you might know

  • A researcher or user tells you they can see other people's data.
  • Your app shows data to logged-out visitors.
  • A provider or scanner warns that a table or bucket is public.
  • Row Level Security shows as disabled on a table.

Do this now

  1. Block public access now

    Turn on access rules for the table or storage, or switch access to private. On Supabase, enable Row Level Security and add a policy. If you are unsure, take the app offline briefly.

  2. Rotate keys and treat stored secrets as leaked

    If a powerful key (such as a Supabase secret key, or the older service_role key) appeared in your website's public code, replace it immediately. Also assume that anything secret sitting inside the exposed data (keys, scrambled passwords, sign-in codes) was copied. Replace or cancel those too.

  3. Check the access logs

    Look for reads or downloads by unknown users or addresses. Note the time range.

  4. List what was in there

    Write down what kinds of data were exposed: emails, messages, payments, tokens.

  5. Fix the root cause

    Add proper rules for every table. Test as a stranger: log out and try to reach data.

  6. Notify the people affected

    If personal data was exposed, tell them what happened and what to do. Notification rules vary. For example, GDPR generally expects you to tell the regulator within 72 hours of becoming aware of a personal data breach, where feasible, unless it is unlikely to put people at risk. Ask a lawyer or your data protection contact early.

Do not do this

  • Do not just hide the page and assume the data is safe.
  • Do not delete the data to "clean up". You need to know what was exposed.
  • Do not argue with the researcher who reported it. Thank them.

Who to tell

  • Whoever is in charge
  • Affected users
  • Your data protection contact or lawyer if personal data was exposed

What to save before you clean up

  • Access logs
  • The configuration as it was
  • The report that alerted you

In the next 24 hours

  • Review every table and bucket for access rules.
  • Add automated checks so new tables are private by default.
  • Plan the customer notification with plain, specific wording.

Official help for the platforms involved

Links open each provider's own documentation, so you do not have to search for it.

What to write in the post mortem afterwards

  • Why the data was reachable
  • How long it was exposed
  • Which checks would have caught it before launch

Finished this one?

Add it to What I learned and earn 30 Trust. You can open your list from the badge at the bottom of the page.