SAAS SECURITY
Five multi-tenant mistakes we look for first
In a SaaS product, one customer must never see another's data. These are the places that tends to break.
Airintha Team · Engineering and security
6 min read

Multi-tenant products share code and infrastructure between customers. That is efficient, and it means one missing check can expose every customer. These are the places we look first.
01Ownership checked only on list views
A page that lists your orders filters by your account. The page that opens one order by ID often trusts the ID. Changing the number in the URL shows another customer's order. The fix is to check ownership on every read and write, not only on the list.
02Tenant scope enforced by convention
If every developer must remember to add the tenant filter to each query, one of them eventually forgets. Enforce the scope in one place, such as the data layer, so a forgotten filter fails closed.
03Webhooks that trust the sender
A payment webhook that does not verify the provider's signature lets anyone mark an order as paid. Verify the signature and reject replays of old events.
04Shared admin credentials
A staff password shared between people cannot be attributed or revoked per person. Use per-person accounts, single sign-on and multi-factor authentication, and review access regularly.
05Logs that keep too much
Card numbers, tokens and personal data written to application logs outlive the access controls on the database. Redact sensitive fields before logs leave the service.
None of these needs exotic tooling to find. They are design decisions, which is why we look for them while the architecture is still easy to change.

