Implementation guide
OWASP AISVS v1.01
Monitoring, Logging & Anomaly Detection · Training Data & Model Lifecycle Audit
Keep immutable records of model changes
Verify that all model changes generate immutable audit records.
OWASP AISVS v1.01, requirement 12.5.3
In plain English
Every change to a model should create an audit record that cannot be altered afterwards. That includes weights, configuration, prompts, adapters and guardrail settings. When behaviour changes, you need a trustworthy answer to "what changed, who did it and who approved it".
What good looks like
- Every model change produces a record: what changed, from and to which version, who made it, who approved it and when.
- Records are stored in append-only or write-once storage.
- Changes can be made only through routes that create a record.
- Prompt and configuration changes are covered as well as weights.
How teams usually do it
- Deployment pipeline events written to immutable storage, such as object storage with a retention lock.
- Model registry stage transitions with required approvals.
- Removing direct console and manual access to production model configuration.
Suggested evidence
- Records for recent changes.
- Storage settings showing immutability.
- Evidence that no direct change route exists, or that the routes are alarmed.
Common mistakes
- Changes made directly in a console, outside the pipeline.
- Audit records in a database that administrators can edit.
- Treating a system prompt edit as too small to record.
Not sure which requirements apply to your system? Take the assessment, or browse every guide in this chapter.
Requirement text from the OWASP AI Security Verification Standard, licensed under CC BY-SA 4.0. This guidance is shared under the same licence.