AI-Assisted Secure Coding (Appendix C) · AI Artifact Origin Validation for Deployment
Reject artifacts with missing provenance
Verify that artifacts are rejected at deployment and quarantined for review when they are missing required origin and generation information, signed by untrusted keys, or produced by an unapproved AI system or environment.
OWASP AISVS v1.01, requirement AC.9.3
In plain English
Reject an artifact at deployment, and quarantine it for review, when its provenance is missing, signed by a key you do not trust, or shows it was produced by an AI system or environment you have not approved. This is a Level 3 control.
What good looks like
- Each of the three failure cases results in rejection.
- Rejected artifacts are quarantined and kept for review.
- The approved AI systems, build environments and signing identities are listed in policy.
- Rejections raise an alert.
How teams usually do it
- Admission policies in the deployment platform that encode the approved lists.
- A quarantine repository or registry tag that nothing deploys from.
- A review step with a named owner for anything quarantined.
Suggested evidence
- Policy configuration with the approved lists.
- A rejected and quarantined example.
- The review record.
Common mistakes
- Logging a warning and deploying anyway.
- An "emergency" override that becomes the normal route.
- Deleting the rejected artifact, which removes the evidence.
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.