Ubserve changelog update: paid audits now detect policy drift between schema evolution and RLS enforcement intent.
RLS policies often lag behind schema changes. Ubserve now flags drift patterns before they become cross-tenant data leaks.
Secure your vibe-coded app with Ubserve
- ✓Takes less than 60 seconds
- ✓100+ security checks run through your app
- ✓Plain English explanations for each issue
- ✓AI fix prompts for every issue
Paid audit plans now include Supabase RLS Drift Detection, designed to catch policy mismatches introduced after schema updates. This helps prevent silent authorization regressions in teams shipping frequently.
Start free scan | See sample audit
Why this matters
RLS failures are often not missing-policy bugs. They are stale-policy bugs created by iterative releases where auth logic changes faster than policy maintenance.
What we now validate
- Missing policy updates after new table columns/relations.
- Divergence across select/insert/update/delete policy symmetry.
- Tenant/ownership predicate inconsistency across related tables.
Recommended next steps
- Run a full audit before launch milestones.
- Use Pro for weekly shipping teams that need recurring scan and audit capacity.
- Re-test every migration touching multi-tenant data boundaries.
Run a free URL scan. If it finds issues, paid plans unlock the full report, exact AI fix prompts, PDF export, and deeper audit coverage.
About the author
I'm Samuel, known online as Mr. Ballaz. I build Ubserve, a security scanner for apps built with AI tools like Cursor, Bolt, Lovable, and Supabase. Before Ubserve, I did manual security audits by hand — checking auth, exposed keys, and RLS policies one by one. Ubserve is that manual audit, automated, running in under 60 seconds instead of days.
Related resources
FAQs
What is RLS drift detection?+
Turn this resource into a real security check.
Review the guidance, then run the free scan to see whether this issue is actually exploitable in your app, no signup required.