How to meet it
OWASP AISVS v1.01
Model Lifecycle Management & Change Control · Secure Development Practices
Keep dev, staging and production apart
Verify that AI-specific runtime components are not shared across environment boundaries (e.g., development, staging, production).
OWASP AISVS v1.01, requirement 3.4.1
In plain English
Keep AI runtime components such as model servers, vector stores and caches separate between development, staging and production.
What good looks like
- Each environment has its own model endpoints, vector stores and caches.
- Credentials for one environment do not work in another.
- Production data is not copied into lower environments without controls.
How teams usually do it
- Separate cloud accounts or projects per environment.
- Environment-specific credentials issued by your secrets manager.
Evidence an auditor would accept
- An architecture diagram showing separation.
- Access policies per environment.
Common mistakes
- A shared vector store "to save cost", so test data and production data mix.
- Developers using production API keys for testing.
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.