How to meet it
OWASP AISVS v1.01
Model Lifecycle Management & Change Control · Controlled Deployment & Rollback
Isolate model versions running side by side
Verify that model versions running in parallel use isolated runtime state so that AI-specific shared resources are not shared across deployments.
OWASP AISVS v1.01, requirement 3.3.3
In plain English
When two model versions run side by side, keep their caches, memory and other runtime state separate so one cannot affect the other.
What good looks like
- Each version has its own caches, vector stores and session state.
- Shared infrastructure is partitioned by version.
- Tests confirm data written by one version cannot be read by another.
How teams usually do it
- Separate namespaces or key prefixes per deployment.
- Separate cache instances for canary and stable versions.
Evidence an auditor would accept
- Configuration showing separation.
- Test results.
Common mistakes
- A shared prompt or response cache that serves one version's output from another.
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.