> For clean Markdown of this page, append .md to its URL. For the complete documentation index, see https://www.superagent.sh/llms.txt.


Review whether backend code keeps customer data and state within the correct tenant.

# Tenant isolation in backend code


[← Back to attack scenarios](https://www.superagent.sh/docs/products/red-teaming/attack-scenarios)

Multi-tenant services can share storage and processing code across customers. This scenario examines whether those shared components preserve the tenant boundary as data moves through the service.

Use it for repositories with tenant-scoped data, caches, or background work. A finding identifies the shared backend path that let data or state cross between tenants.

The app lists this scenario as **Cross tenant boundaries through shared backend state** (`REPO-02`) in [Repository Red Teaming](https://www.superagent.sh/docs/products/red-teaming/repositories).

## Standards and guidance

[OWASP A01:2025 Broken Access Control](https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/)

---
Source: https://www.superagent.sh/docs/products/red-teaming/attack-scenarios/repository-tenant-isolation
Index: https://www.superagent.sh/llms.txt
