How to meet it
OWASP AISVS v1.01
Model Lifecycle Management & Change Control · Pipeline Fine-Tuning
Verify each fine-tuning stage's output
Verify that in multi-stage fine-tuning pipelines, each stage's output is integrity-verified before it is consumed by the next stage.
OWASP AISVS v1.01, requirement 3.5.3
In plain English
In a fine-tuning pipeline with several stages, check each stage's output before the next stage uses it.
What good looks like
- Each stage records a hash or signature of its output.
- The next stage verifies it before starting.
- Failures stop the pipeline.
How teams usually do it
- Pipeline steps that write a manifest and the next step checks it.
- Artifact stores that record hashes automatically.
Evidence an auditor would accept
- Pipeline definitions and logs showing the checks.
Common mistakes
- Passing intermediate files through a shared folder with no checks.
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.