How to meet it
OWASP AISVS v1.01
AI-Assisted Secure Coding (Appendix C) · Continuous Feedback, Adversarial Testing & Model Fine-Tuning
Let people flag bad suggestions
Verify that developers and reviewers can flag insecure or non-compliant suggestions, and that each flag is tracked to closure with links back to the originating prompt and response and forward to any downstream artifacts.
OWASP AISVS v1.01, requirement AC.6.1
In plain English
Let developers flag insecure AI suggestions, and track each flag to closure, linked back to the prompt and forward to anything it affected.
What good looks like
- There is an easy way to flag a suggestion.
- Flags are tracked to closure.
- Links to the prompt and later artifacts are kept.
How teams usually do it
- A label or template in your issue tracker linked from the AI tool.
Evidence an auditor would accept
- Recent flags and their outcomes.
Common mistakes
- A feedback button that sends reports only to the vendor.
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.