# Claude Code, Codex and Cursor have become part of your software supply chain - without approval

DevFeed: [Claude Code, Codex and Cursor have become part of your software supply chain - without approval](<https://devfeed.tech/articles/claude-code-codex-and-cursor-have-become-part-of-your-software-supply-chain-without-approval-123502.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4245820/claude-code-codex-and-cursor-have-become-part-of-your-software-supply-chain-without-approval.html>)

Author: Vipin Jain

Published: 2026-11-09T10:00:00Z

Content type: opinion

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [AI software supply chain security](<https://devfeed.tech/topics/ai-software-supply-chain-security.md>), [shadow AI](<https://devfeed.tech/topics/shadow-ai.md>), [Agent Harness](<https://devfeed.tech/topics/agent-harness.md>), [Platform Engineering](<https://devfeed.tech/topics/platform-engineering.md>), [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [OpenAI](<https://devfeed.tech/topics/openai.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [ChainDrop](<https://devfeed.tech/topics/chaindrop.md>), [codex](<https://devfeed.tech/topics/codex.md>), [anthropic](<https://devfeed.tech/topics/anthropic.md>)

Tags: [adoption](<https://devfeed.tech/tags/adoption.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-coding-agent](<https://devfeed.tech/tags/ai-coding-agent.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-it-governance-it-leadership-software-development](<https://devfeed.tech/tags/artificial-intelligence-it-governance-it-leadership-software-development.md>), [bank](<https://devfeed.tech/tags/bank.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [codex](<https://devfeed.tech/tags/codex.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [context](<https://devfeed.tech/tags/context.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [control](<https://devfeed.tech/tags/control.md>), [credential-exposure](<https://devfeed.tech/tags/credential-exposure.md>), [cursor](<https://devfeed.tech/tags/cursor.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [it-governance](<https://devfeed.tech/tags/it-governance.md>), [it-leadership](<https://devfeed.tech/tags/it-leadership.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [software](<https://devfeed.tech/tags/software.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [software-supply-chain](<https://devfeed.tech/tags/software-supply-chain.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>)

## AI overview

AI coding agents should be governed as privileged suppliers because they can read repository data, use tools and connect to downstream services, while their model providers or ownership may change. The article describes four control areas: contract terms and dependency visibility; managed restrictions on secrets; approval, provenance checks and least-privilege access for MCP servers; and isolated execution with default-deny network egress. It recommends assigning one platform team ownership of a governed agent harness, with procurement, security and infrastructure retaining decision rights. Its five steps for the next 90 days are to inventory agents and dependencies, establish contract and exit terms, limit agents to short-lived scoped credentials, maintain an approved MCP registry, and restrict outbound traffic while routing changes through CI/CD controls. The examples show that credentials in an agent's context do not by themselves prove external transmission, and that controls can often build on existing capabilities.

## Source excerpt

At a Fortune 100 bank, I watched a coding agent open a routine session on a payments service. Before the developer typed a word, the agent had read the repository, including the .env file. Production database credentials had entered the agent's working context, potentially exposing them to a model provider the bank had never assessed. Whether the credentials left the environment depended on controls nobody had verified. Nothing malicious happened. The agent did what it was built to do. That is the problem. My argument is simple. AI coding-agent vendors and their downstream dependencies form a supplier ecosystem, not just another developer tool. They need the same four control disciplines applied to other privileged suppliers. Govern vendor terms and downstream dependencies. Limit the secrets they hold. Approve the servers they connect to. Restrict where they can send data. Much of this builds on existing controls, though an enterprise may need a governed gateway or platform service. It requires procurement, security and engineering to recognize a supplier when they see one. In May, I wrote about how agentic AI is rewiring the SDLC. This is the security half of that argument. Adoption has outrun control On Aug. 28, OpenAI told SpaceX, Cursor's new owner, that it intends to stop supplying models to Cursor, with Nov. 12 proposed as the cutoff. Cursor CEO Michael Truell said OpenAI models carry about 5 percent of its traffic, DevOps.com reported, so the operational risk is small. The governance lesson is not. Enterprises that standardized on Cursor learned they depended on a downstream model supplier whose terms they did not directly control and a change of ownership they had not planned for. That gap is now the norm. Coding agents are developers' most common AI use, and investment is accelerating. Governance is not keeping pace, and emerging evidence of credential exposure underscores the gap. Figure 1. Rapid AI coding-agent adoption exposes gaps in enterprise governan