Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-08-04 · high
Snyk surveyed 3,000+ enterprise accounts and found real AI infrastructure runs three times what model inventories show, pushing AI-BOM into procurement.
Why now: The jump from 36% to 50% full-stack agentic adoption in six months is what's pushing AI-BOM tooling into procurement conversations.
Security teams see roughly a third of their real AI footprint, per Snyk's new survey of 3,000-plus enterprise accounts. That means agent frameworks, MCP servers, retrieval systems, and vector databases, the layers attackers actually reach, run two-thirds ungoverned by whatever policy tracks the models. The ratio holds across every region Snyk measured.
Full-stack agentic architecture means production systems with orchestration, memory, and tool-calling, not a single model call. Half of organizations run it, up from 36% six months earlier, per the survey. AI-BOM tooling, the inventory layer for that stack, is turning into its own procurement line separate from model governance budgets.
Model governance built around tracking which LLMs a company uses is already behind the actual footprint. The budget line that matters is the AI-BOM, everything downstream of the model call, because that's the two-thirds security teams can't see. Watch whether AI-BOM tooling gets funded as its own procurement category in the next few quarters, or gets folded into existing AppSec budgets and starved.
The jump from 36% to 50% full-stack adoption in six months is what's turning AI-BOM from a nice-to-have into a live procurement conversation.
Each link below shares sources, entities, or timing with this story.
Snyk criticizes ClawHub / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Snyk criticizes ClawHub); both cover MCP, Snyk; reported by the same outlet (snyk.io).
Snyk released Evo ADS / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Snyk released Evo ADS); both cover MCP, Snyk; overlapping topics (agent, model).
Snyk supports MCP / Shared entity: MCP / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Snyk supports MCP); both cover MCP; overlapping topics (agent, becoming, enterprise).
Snyk uses Claude / Shared entity: MCP / Shared topic / Earlier coverage
Linked by a graph relationship (Snyk uses Claude); both cover MCP; overlapping topics (account, agent, agentic, architecture).
Linked by a graph relationship (Snyk uses Claude); both cover MCP; overlapping topics (agent, architecture, becoming, model).
Linked by a graph relationship (Snyk uses Claude); both cover MCP; overlapping topics (adoption, agent, enterprise, model).
Snyk supports MCP / Shared entity: MCP / Shared topic / Earlier coverage
Linked by a graph relationship (Snyk supports MCP); both cover MCP; overlapping topics (agent, architecture, enterprise, framework).
Snyk supports MCP / Shared entities / Earlier coverage / Tension
Linked by a graph relationship (Snyk supports MCP); both cover MCP, State; earlier MCP coverage from 2026-04-21.