Tenant and account isolation

Check method

Checks that policies scope rows to their owner rather than to any signed-in user.

Possible evidence type

Code or configuration review, without exploiting the risk.

Access and limitations

Authorized access to a supported database. Actual results and checks not run appear in your report. A check with no finding does not guarantee the absence of risk.

Concrete scenario

A user from workspace A reads an object from workspace B.

What to inspect

Check tenant scoping in queries, policies, storage and background jobs. A workspace selector in the interface is not enforcement.

Remediation approach

Carry validated workspace membership to every protected operation and verify negative cross-tenant cases when authorized.

Understand grants, policies and identity

Database grants determine whether a role can reach a table or function; row-level security determines which rows it can access. Enabling RLS without a usable policy can block legitimate users, while a broad policy can expose every tenant. A privileged server credential may bypass these protections and must never be shipped to the browser.

1. Identify the role making the request and the identity used by the policy.
2. Review both table grants and policies for each read or write operation.
3. Check owner access to private, draft and archived rows separately from public access.

Validate without changing production data

Catalog-only inspection can show policy definitions and privilege configuration, but does not prove every application-level access path. Two-account isolation exercises provide stronger behavioral evidence when separately authorized. Backup availability is also different from a successful restore test.

1. Review definitions and grants in the supported read-only audit.
2. Use isolated test records for any owner-approved behavioral exercise.
3. Retest the expected owner access and denied cross-account access after changes.

References

OWASP A01