AI-Assisted Secure Coding (Appendix C) · AI-Generated Infrastructure & Pipeline Artifacts
Dual control for pipeline triggers
Verify that changes to high-impact pipeline trigger configurations require both dual control and a security-team review, no matter who or what produced the change. The configurations in scope include GitHub Actions `pull_request_target` and `workflow_run`, self-hosted runner labels, workflow `permissions:` blocks, OIDC trust policies, and secret-environment mappings.
OWASP AISVS v1.01, requirement AC.7.4
In plain English
A few pipeline settings decide who can run code with your secrets. Changing them should take two people and a security review, whoever or whatever made the change. On GitHub these include pull_request_target and workflow_run triggers, self-hosted runner labels, permissions: blocks, OIDC trust policies and secret-to-environment mappings.
What good looks like
- The high-impact settings are identified across your repositories.
- Any change to them needs dual control and a security-team review.
- Enforcement is automated and applies to people, bots and administrators alike.
- Reusable workflows and shared pipeline templates are covered.
How teams usually do it
- CODEOWNERS on workflow directories requiring the security team, with two approvals.
- A CI check or ruleset that detects the listed settings in a diff and requires the extra review.
- Cloud-side protection for OIDC trust policies, which live outside the repository.
Suggested evidence
- Rulesets and CODEOWNERS.
- A reviewed change to one of the settings.
- An inventory of where the high-impact settings are used.
Common mistakes
- Protecting the main workflow file and leaving reusable workflows and composite actions open.
- Forgetting the settings held in the cloud provider or the repository settings page.
- An exemption for bots.
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.