How to meet it
OWASP AISVS v1.01
AI-Assisted Secure Coding (Appendix C) · Validation of AI-Generated Code
Security-scan every AI pull request
Verify that automated security testing runs on every pull request containing AI-generated code: SAST, IAST, DAST, secret scanning, IaC scanning, and SCA. Where the scanner supports them, AI-attribution-aware rules are turned on.
OWASP AISVS v1.01, requirement AC.4.2
In plain English
Run automated security testing on every pull request with AI-generated code: static and dynamic analysis, secret scanning, infrastructure-as-code scanning and dependency checks.
What good looks like
- All listed scanners run on every PR.
- AI-aware rules are on where the scanner offers them.
- Results are visible in the PR.
How teams usually do it
- CI pipelines with SAST, secret scanning, IaC scanning and software composition analysis.
Evidence an auditor would accept
- CI configuration and a sample PR with results.
Common mistakes
- Scanners that run only on the main branch after merge.
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.