ByteAssure

Supabase RLS review

RLS on is not the same as RLS right. A policy of using (true) passes most dashboards and still hands every signed-in user every row. I read every policy, then sign in as two users and try each other's data on read, update and delete. Five working days after access.

£449The 5-Day Two-Account Check. No request and response for a check in scope, no payment.

What gets checked on your app

What you receive

  • The request sent and the response received for every check
  • A short video of any request where one user gets another user's data
  • Findings ranked by what a stranger could do, each with the fix
  • A one-page note of what was tested and what was left out
  • One recheck after you apply the priority fixes
  • £449 off the fix invoice if the fix starts within 14 days

See a sample report from a real test, or watch the recording of user A reading user B's note.

Questions

Doesn't the Security Advisor catch this?

It catches tables with RLS off and some risky patterns. On our recorded demo, it raised no warning about a using (true) read policy, because only you know whether that table is meant to be shared.

Do you need database access?

Read-only access to your schema and policies (or the repository's migrations), the project URL and publishable key, and written permission. We create our own two test users.

Can you fix the policies too?

Yes, quoted in writing after the report. The £449 comes off the fix invoice if the fix starts within 14 days.

Do it yourself first

How to run a Supabase RLS audit yourself before launch

The method is free. The check is the run, the evidence and the recheck. It is not a penetration test and does not certify the app as safe to launch.

Book before you launch

At checkout, add the app URL and the date you plan to turn on payments or let real users in. After payment, send read-only repository access and the signed permission. Run by David Salami. Full scope on the 5-Day Two-Account Check.