How to meet it
OWASP AISVS v1.01
Access Control & Identity for AI Components & Users · Multi-Tenant Isolation
Tenants can't observe each other's compute
Verify that one tenant cannot influence or observe another tenant's operations through shared compute resources. Satisfying this requirement typically requires hardware partitioning, confidential computing, or dedicated per-tenant compute allocation.
OWASP AISVS v1.01, requirement 5.3.2
In plain English
Stop tenants affecting or observing each other through shared hardware. In practice that means partitioned hardware, confidential computing or dedicated compute per tenant.
What good looks like
- Tenants do not share GPUs without hardware partitioning or dedicated allocation.
- Side channels such as timing and memory reuse are considered in the design.
- The chosen approach is documented.
How teams usually do it
- Dedicated instances for high-risk tenants.
- GPU partitioning or confidential computing for shared pools.
Evidence an auditor would accept
- Compute allocation design per tenant tier.
Common mistakes
- Assuming container isolation is enough on shared GPUs.
Not sure which requirements apply to your system? Take the assessment.
Requirement text from the OWASP AI Security Verification Standard, licensed under CC BY-SA 4.0. This guidance is shared under the same licence.