AI-Assisted Secure Coding (Appendix C) · CI/CD Pipeline Hardening Specific to AI Augmentation
Approve secret-bearing jobs for forks
Verify that secrets are not exposed to workflows running code from forks or first-time contributors. Environment-protection rules (or the platform equivalent, such as protected variables and deployment approvals) require a manual approval before any secret-bearing job runs for those contributions. This control pairs with AC.11.7 and AC.13.2. Bot-level enforcement under AC.11.7 does not substitute for the platform-level enforcement required here.
OWASP AISVS v1.01, requirement AC.12.3
In plain English
Do not expose secrets to workflows running code from forks or first-time contributors. Require a manual approval before any secret-bearing job runs for those contributions, at the platform level.
What good looks like
- Environment protection rules require approval.
- Fork and first-time contributions cannot reach secrets without it.
- Bot restrictions (see AC.11.7) add to this platform rule.
How teams usually do it
- Protected environments and approval requirements for fork workflows on your CI platform.
Evidence an auditor would accept
- Environment and repository settings.
Common mistakes
- Relying on the bot to refuse instead of the platform.
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.