How to meet it
OWASP AISVS v1.01
Training Data Integrity & Traceability · Data Labeling and Annotation Security
Protect labels from tampering
Verify that cryptographic integrity is applied to labeling artifacts.
OWASP AISVS v1.01, requirement 1.2.2
In plain English
Protect finished labels and annotation files so they cannot be altered between labelling and training without anyone noticing.
What good looks like
- Exported label sets are hashed or signed when they are approved.
- The training pipeline checks the hash before using the labels.
- Changes to labels after approval create a new version and keep the old one.
How teams usually do it
- Signing label exports with a pipeline key and verifying the signature at training time.
- Versioned storage for label sets, with hashes recorded in the dataset manifest.
Evidence an auditor would accept
- Signed or hashed label exports.
- Pipeline logs showing verification.
Common mistakes
- Protecting the raw data but treating labels as editable spreadsheets.
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.