How to meet it
OWASP AISVS v1.01
Orchestration & Agentic Security · Component Isolation and Tool Authorization
Isolate agent-writable storage
Verify that services reachable from agent or tool sandboxes enforce the defined run, task, or tenant isolation policy on agent-writable state, including object names.
OWASP AISVS v1.01, requirement 9.3.9
In plain English
Services that agents and tools can write to, such as storage buckets or queues, must enforce isolation between runs, tasks and tenants, including in names of the objects they create.
What good looks like
- Writable services check which run, task or tenant a write belongs to.
- Object names cannot be chosen to land in another run's space.
- Tests try to read or overwrite other runs' data.
How teams usually do it
- Per-run prefixes that the service assigns and enforces.
Evidence an auditor would accept
- Service policies and test results.
Common mistakes
- Letting the agent choose file paths in a shared bucket.
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.