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.
Editorial analysis by NHI Mgmt Group, based on content published by StepSecurity: “Securing Vibe Coding and AI Coding Agents: An End-to-End Approach with StepSecurity”.
By the numbers:
- StepSecurity says customers with cooldown policies enabled were protected from npm supply chain attacks in 2025 such as the Shai-Hulud campaigns.
Key questions
Q: Where do AI coding agents fail first when they have developer and CI/CD access?
A: They fail first at the boundary between delegated action and uncontrolled tool access.
Q: Why do AI coding agents create credential and release risk in CI/CD pipelines?
A: Because they often operate where production secrets, build credentials and repository privileges overlap.
Q: What do security teams get wrong about vibe coding and mobile risk?
A: They assume speed and polish imply security.
Practitioner guidance
- Map every coding agent to a governed execution identity Inventory where AI coding agents run, what credentials they can access and which tools they can invoke across developer machines, repos and CI/CD.
- Block risky package intake at the pull-request boundary Apply cooldown and allowlist controls so new or suspicious packages cannot enter the codebase through agent-generated changes without review.
- Constrain MCP servers and IDE extensions Treat development-time extensions and MCP integrations as privileged tooling.
Bottom line: AI coding agents are not just code-generation tools. They now participate in package selection, pull requests and CI/CD execution, which turns development workflow into an access-control problem.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
19/08/2026 4:26 pm
AI coding agents are becoming non-human identities with delegated delivery authority. Once an agent can install packages, open pull requests and operate in CI/CD, the governance question changes from code quality to authority control. That means identity, privilege and runtime behaviour must be managed together, because the agent’s action boundary is now part of the supply chain. Practitioners should treat these systems as governed execution identities, not just developer productivity tools.
A few things that frame the scale:
- 96% of organisations store secrets outside of secrets managers in vulnerable locations including code, config files, and CI/CD tools, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: How should teams compare IDE controls with CI/CD controls for AI coding agents?
A: They solve different problems and should not be treated as substitutes. IDE and extension controls reduce local trust expansion, while CI/CD controls reduce runtime exfiltration and release tampering. A mature programme uses both, because a compromise can start in the workstation and only become visible once it reaches the pipeline.
👉 Read our full editorial: Securing AI coding agents across development, repo, and CI/CD