AI-Assisted Secure Coding (Appendix C) · Adversarial AI Detection in Inbound Contributions
Contain adversarial contributions automatically
Verify that confirmed or high-confidence adversarial contributions trigger automated containment: block the PR, quarantine the fork, suspend the contributor, notify maintainers, and freeze affected workflow files. Triage decisions feed back into detection tuning.
OWASP AISVS v1.01, requirement AC.13.5
In plain English
When an adversarial contribution is confirmed or highly likely, contain it automatically: block the PR, quarantine the fork, suspend the contributor, tell maintainers and freeze affected workflow files.
What good looks like
- Containment actions are automated.
- Maintainers are notified.
- Outcomes feed back into detection tuning.
How teams usually do it
- Automation triggered by high-confidence alerts, using the repository platform's API.
Evidence an auditor would accept
- Automation configuration and a test record.
Common mistakes
- Waiting for a maintainer to wake up before blocking.
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.