A New Stack analysis published on June 26 names a pattern CI/CD owners are starting to inherit: agentic systems pass functional review on day one and stall at security review, because no one scoped identity, permissions or audit at the platform layer first. The piece is sponsored by IBM, so the prescription leans opinionated. The gap it names is the one platform teams keep finding on their own.
The article opens on a familiar scene. A customer-support agent triages tickets and processes refunds without incident. Security then asks under whose identity it is running. The answer is a shared service account with broad permissions, no clear ownership, no audit trail. That answer stops the rollout.
Four decisions, picked once and rarely revisited
The article walks four binary choices: shared service accounts versus per-agent workload identity; static API keys versus short-lived credentials issued through identity federation; direct credentials versus a broker that evaluates policy at request time; standard operation logging versus full identity lineage across the call chain. Each pair is a familiar workload-identity question recast for a new caller. The article argues the strict side of all four is what an auditable system looks like, and that identity lineage is hard to retrofit once a fleet of agents is in production.
The cited scale is the headline. The 2026 Tech Leader Study from Oxford Economics and IBM puts the average expected agent count per surveyed enterprise at 1,661, a 38% increase over today. The article also cites Nightfall AI saying organizations expose nearly 350 secrets per 100 employees per year, with 35% of leaked API keys still active.
Where this lands in a pipeline
OIDC token exchange for short-lived cloud credentials is the same primitive whether the caller is a deploy job or an agent. A central policy broker is the same chokepoint whether it sits in front of kubectl or in front of an agent's tool calls. Extending the workload-identity machinery you already run to a new class of caller is cheaper on day one than retrofitting identity lineage on day two hundred.
The piece is sponsored content, and it closes on a vendor pitch. The framing does not need the logo to hold up. Shortcuts at agent rollout reduce friction at the start and accumulate risk through the year. The bill comes due at security review.
