AI-Assisted Secure Coding (Appendix C) · CI/CD Pipeline Hardening Specific to AI Augmentation
Ephemeral, isolated runners for AI tooling
Verify that self-hosted or persistent runners used by AI tooling are ephemeral (destroyed after each job), network-segmented, and isolated from production credentials. Persistent or long-lived runners do not process fork PRs or AI-generated untrusted artifacts under any circumstances.
OWASP AISVS v1.01, requirement AC.12.4
In plain English
Runners used by AI tooling must be ephemeral, network-segmented and kept away from production credentials. Persistent runners never process fork PRs or untrusted AI output.
What good looks like
- Runners are destroyed after each job.
- They sit in a segmented network.
- Persistent runners are excluded from fork and AI workloads.
How teams usually do it
- Ephemeral runner services and runner groups with restricted labels.
Evidence an auditor would accept
- Runner configuration and group assignments.
Common mistakes
- A self-hosted runner shared between public PRs and deployments.
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.