01 · Security audit
Locked down a multi-tenant database serving about 25 apps
A shared database project had 202 tables with row-level security switched off. Anyone holding the public client key, which ships inside every web and mobile app, could read and write them.
202
tables exposed
244
tables probed per run
3
client identities tested
What I did
- 1.Mapped which tables real client code actually needed, so the fix would not take production apps down.
- 2.Shipped one migration that enabled row-level security everywhere, with a short allow-list of deliberate exceptions.
- 3.Wrote a probe that tests all 244 tables as every client identity (anonymous, public key, signed-in user) and re-runs after any policy change.
Closed the exposure without breaking a single server-side pipeline, and turned a one-time fix into a repeatable control.




