How to meet it
OWASP AISVS v1.01
Training Data Integrity & Traceability · Data Labeling and Annotation Security
Control who can label data
Verify that labeling platforms enforce access controls that restrict who can create, modify, or approve annotations.
OWASP AISVS v1.01, requirement 1.2.1
In plain English
Control who can create, change and approve labels. A label is training data, so anyone who can change labels can change what the model learns.
What good looks like
- Labellers, reviewers and admins have separate roles with only the permissions they need.
- Approving a label needs a different person from the one who created it.
- External labelling vendors get access only to the projects they work on.
How teams usually do it
- Role-based access in the labelling platform, connected to your single sign-on.
- Review workflows that require a second annotator or reviewer before labels are accepted.
Evidence an auditor would accept
- Role definitions and the current list of who holds them.
- Platform settings showing review is required.
Common mistakes
- Shared vendor accounts, so you cannot tell who labelled what.
- Admin rights left in place for contractors after a project ends.
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.