Notifications
Clear all
Topic starter
19/08/2026 3:50 pm
TL;DR: AI coding agents now operate across developer machines, code repositories, and CI/CD pipelines, creating a multi-stage attack surface that includes credential theft, package abuse, and runtime exfiltration, according to StepSecurity. The governance gap is not code generation quality but control over agent behaviour, tool access, and pipeline visibility.
NHIMG editorial — based on content published by StepSecurity: Securing Vibe Coding and AI Coding Agents: An End-to-End Approach
By the numbers:
- 64% of valid secrets leaked in 2022 are still valid and exploitable today, proving that detection alone is not enough without automated revocation.
Questions worth separating out
Q: What breaks when an AI review system has write access to repositories and pipelines?
A: The boundary between detection and execution breaks.
Q: Why do AI coding agents increase supply-chain risk?
A: AI coding agents can choose tooling, install packages, and edit lock files in ways that may bypass the controls humans expect in a managed environment.
Q: How do security teams know if an AI agent is operating outside its approved role?
A: Teams should compare actual workflow behaviour against the approved use case.
Practitioner guidance
- Define agent identities and tool scopes Create explicit registration, ownership, and tool-allowance policies for every AI coding agent.
- Block risky dependency introduction before merge Require org-wide package allowlists, cooldown rules for newly published packages, and automated pull request blocking when an agent introduces an unfamiliar dependency into a repository.
- Instrument CI/CD for runtime attribution Monitor workflow process creation, outbound network activity, and file events so that every action can be traced back to the exact step and process that triggered it.
What's in the full article
StepSecurity's full blog post covers the operational detail this post intentionally leaves for the source:
- Step-by-step guidance for securing AI coding agents on developer machines and ephemeral environments.
- Workflow-level controls for GitHub Actions, including process tracing, network enforcement, and runtime attribution.
- Package governance techniques for blocking suspicious npm dependencies before they reach production workflows.
- Practical integration notes for Claude Code, Gemini, and GitHub Copilot inside CI/CD pipelines.
👉 Read StepSecurity's analysis of securing AI coding agents across the development lifecycle →
AI coding agents in CI/CD: what controls do teams need now?
Explore further
19/08/2026 4:26 pm
AI coding agents should be governed as non-human identities, not treated as code-generation tools. Once an agent can install packages, push commits, and act inside CI/CD, it inherits the governance problems that apply to service accounts and workload identities. The control question becomes who or what is authorised to act, with which tools, and under what boundary conditions. Practitioners should align agent governance with OWASP-NHI and NIST-CSF thinking, because the identity layer is now part of the software delivery threat model.
A question worth separating out:
Q: Who is accountable when leaked AI agent code leads to downstream abuse?
A: Accountability usually sits with the organisation operating the agent stack, the team that approved the release path, and the owners of telemetry and access controls. Under AI governance and security frameworks, the question is not only who made the error, but who owns provenance, review, and containment once the leak is public.
👉 Read our full editorial: Securing AI coding agents across development, repo, and CI/CD
