How to meet it
OWASP AISVS v1.01
Memory, Embeddings & Vector Database Security · Access Controls on Memory & RAG Indices
Keep each tenant's vectors separate
Verify that vector identifiers and namespaces enforce uniqueness per tenant and prevent cross-tenant collisions.
OWASP AISVS v1.01, requirement 8.1.1
In plain English
In shared vector stores, make IDs and namespaces unique per tenant, so one tenant's data cannot overwrite or collide with another's.
What good looks like
- Vector IDs include the tenant identifier.
- Each tenant has its own namespace or collection.
- Writes are checked against the caller's tenant.
How teams usually do it
- Namespaces or collections per tenant in your vector database.
Evidence an auditor would accept
- Schema and write-path code.
Common mistakes
- Using document filenames as IDs, which collide across tenants.
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.