SYSTEM OPTIMAL
LATENCY: 12msALERT: HBM3E SUPPLY CONSTRAINED
04:05:38 UTC
snyk·Published Apr 27, 2026

The AI Security Summit 2025

AI’s next frontier isn’t just smarter — it’s safer. At "The AI Security Summit," theCUBE brings you exclusive access to insights as Snyk and partners bridge the "AI security chasm" through open-source

3 pillars · 16 citations· 16/16 verified (100%) against source transcripts·Source event on theCUBE ↗
QA PASSEditorial QA Gate · rubric
  • Citation verification rate:100.0% (≥ 95%)
  • Fabricated quote count:0 (= 0)
  • Verified citation density:16 (≥ 8)
  • Named operators cited:4 (≥ 4)
  • Tracked-ticker linkage:3 (≥ 2)
  • All three pillars present:developer + deepTech + cSuite (developer + deepTech + cSuite)

Developer

6 citations

For practitioners shipping against this infrastructure

Developer Infrastructure Shifts for AI Security

The enterprise AI security landscape is experiencing fundamental architectural changes that developers need to understand immediately. Ed Sim from Boldstart Ventures highlights a critical shift: "You need to scan the code first in order to then start protecting it... There's hundreds of [MCP servers and endpoints] now in organizations people don't even know about." This reflects a new reality where traditional code scanning must evolve to handle AI-generated code patterns and the explosion of Model Context Protocol (MCP) connections that create novel attack surfaces.

Snyk's announcement of Eva represents the first production-ready agentic security orchestrator specifically designed for this challenge. Manoj Nair, Snyk's Chief Innovation Officer, describes the technical approach: "You want them to be specialized but only give them enough agency and ability to do that particular task... We're training a red teaming agent to figure out how do you break this agentic application with an LLM." Eva deploys specialized autonomous agents for discovery, model risk assessment, and MCP security validation — addressing the gap where security teams report "zero" AI systems while CTOs acknowledge "thousands" in production.

The MCP protocol emergence creates particularly acute risks that developers must architect around. Nair identifies a specific vulnerability pattern: "We found the toxic flow attack pattern that the GitHub MCP server had an exploit potential, and that is a prompt injection, plus bringing this improper access." This chaining of traditional infrastructure vulnerabilities with AI-specific attack vectors requires new defensive patterns at the API and SDK level.

Francesca LaBianca from Factory emphasizes the operational shift required: "You're moving from single human in an IDE writing every line of code to now being able to send a task to an agent... that requires a fundamentally new way of working." Factory's approach centers on the AGENTS.md specification — an emerging open standard adopted by OpenAI and others that provides guardrails for agent behavior within development workflows.

The data architecture implications are substantial. Sanjay Poonen from Cohesity notes the regulatory complexity: "You have to have very strict roles-based access controls to ensure the wrong people aren't searching, summarizing, and that if you're going to do summarization... you got to make sure it's not hallucinating." This requires rethinking data governance APIs and implementing new access control patterns for AI-driven data operations, particularly as sovereign cloud requirements like Europe's DORA regulation force data localization.

Developers building on this infrastructure should immediately implement agent readiness patterns. LaBianca recommends starting with: "AGENTS.md file, which is an open source standard now... that sets up rules for your agents as they run. But this extends to how your tests are set up, how your linters are set up, how your dev containers are set up." The shift toward spec-driven development with deterministic guardrails becomes essential as AI code generation scales beyond human review capacity.

Deep Tech

6 citations

For analysts, investors, and infrastructure architects

The AI Security Infrastructure Gap: Why Traditional DevSecOps is Failing the Agentic Era

The enterprise AI security landscape is experiencing a fundamental infrastructure crisis that goes far beyond traditional vulnerability scanning. As organizations race to deploy agentic AI systems, they're discovering that existing security frameworks are catastrophically inadequate for non-deterministic, multi-agent environments. The evidence from operators suggests we're witnessing the emergence of an entirely new security paradigm that demands purpose-built infrastructure.

The scale of the visibility problem alone is staggering. As Manoj Nair from Snyk observed during customer meetings: "I've been in meetings where the CISO and CTO are on the call with me and ask the question, 'How many agents or LLMs do you have in production?' And the answer from the security team is zero. The answer from the CTO is thousands." This isn't just a communication gap—it's a fundamental breakdown in enterprise asset management that creates massive attack surfaces. When security teams can't even inventory their AI assets, traditional perimeter-based security models become meaningless.

The technical complexity compounds exponentially when you examine the attack vectors emerging from agent orchestration systems. Nair's team discovered critical vulnerabilities in seemingly benign infrastructure: "We found the toxic flow attack pattern that the GitHub MCP server had an exploit potential, and that is a prompt injection, plus bringing this improper access." Model Control Protocol (MCP) servers, designed to connect AI agents with external tools and data sources, are creating novel attack chains that combine traditional infrastructure vulnerabilities with AI-specific prompt injection techniques. The result is a multiplication of risk rather than simple addition.

What's particularly concerning is how AI's pattern recognition capabilities are weaponizing existing enterprise data hygiene problems. Traditional security models relied on the statistical improbability of attackers finding sensitive data scattered across vast enterprise datasets. But as one operator noted, AI systems excel at "finding anomalies" and can act as "a magnet for those needles" in data haystacks. This means decades of accumulated technical debt in data classification and access controls are suddenly becoming critical vulnerabilities.

The infrastructure investment implications are massive. Ed Sim from Boldstart Ventures, whose portfolio company Protect AI sold to Palo Alto Networks for over $700 million, argues that organizations need "one vendor to help them solve more problems than just one." But the technical reality suggests something more fundamental: enterprises need entirely new security architectures. Snyk's Evo platform represents one approach—what they call "the world's first agentic security orchestrator"—but the broader market is still in its infancy.

The datacenter and cloud implications are equally profound. Sanjay Poonen from Cohesity highlighted emerging regulatory pressures: "In Europe, they have this regulation called DORA, requires data to stay in the country, and we think there's going to be a lot more sovereign cloud requirements." When combined with AI workloads that generate massive audit trails and require real-time security monitoring, this is driving demand for entirely new classes of infrastructure that can handle both the computational requirements of AI security and the regulatory requirements of data sovereignty.

Perhaps most critically, the economics of AI security are forcing a fundamental rethink of enterprise security budgets. Francesca LaBianca from Factory noted that successful AI adoption requires "agent readiness," which "incorporates a number of things" including comprehensive changes to testing frameworks, linting systems, and development containers. This isn't just about buying new security tools—it's about rebuilding core development infrastructure to be AI-native from the ground up.

The competitive landscape is already consolidating around platforms that can handle the full stack of AI security challenges. As Sim observed about the broader trend: "I've never seen a technology take off with AI-assisted coding like it has. About a year and a half ago, no one was like, 'Ah, we're trying out GitHub Copilot.' All of a sudden, it's wall to wall every large Fortune 500 right now." The organizations that can build comprehensive AI security platforms—not just point solutions—will capture disproportionate value as enterprises realize they can't patch their way to AI security.

The infrastructure implications extend beyond security into fundamental questions about how enterprises architect their AI systems. The move toward "agent-driven development," as Factory terms it, requires "a fundamentally new way of working" that touches everything from code review processes to production monitoring. Organizations that fail to make these infrastructure investments aren't just accepting security risks—they're limiting their ability to capture AI's productivity benefits entirely.

C-Suite

4 citations

For executives making bet-the-company calls

C-Suite: The AI Security Imperative

AI adoption has reached an inflection point where security can no longer be an afterthought. Enterprise leaders are discovering a dangerous gap: while engineering teams deploy thousands of AI models and agents in production, security teams often report zero visibility into these systems. This disconnect creates unprecedented risk as AI-generated code volumes surge 5-6x, agents access sensitive data through new attack vectors like MCP servers, and traditional security frameworks prove inadequate for non-deterministic AI systems.

Inventory crisis demands immediate action: CISOs and CTOs are discovering massive blind spots in AI deployments. Start with comprehensive discovery of all AI models, agents, and integrations across your organization before implementing any security controls.

Rethink security architecture for agentic systems: Traditional code-based security fails with stochastic AI systems. Implement "secure-by-design" threat modeling at the specification phase, before code generation, and deploy specialized agentic security orchestrators that can adapt to non-deterministic behaviors.

Establish agent readiness standards now: Create organizational guardrails through AGENTS.md files, standardized dev containers, and clear policies for model usage. This foundational work determines whether AI implementations become productivity multipliers or security nightmares.

Prepare for sovereign cloud requirements: Regulatory pressures like Europe's DORA are forcing data localization. Build federation strategies for sovereign clouds across key markets to maintain AI capabilities while meeting compliance requirements.

Decision Framework: Treat AI security as a parallel workstream to AI adoption, not a follow-on project. The companies winning this transition are those implementing security orchestration and agent readiness standards simultaneously with AI deployment, creating sustainable competitive advantages through secure-by-design AI systems.

The window for reactive AI security is closing. Leaders who act now on comprehensive AI security frameworks will capture the productivity benefits while avoiding the catastrophic risks that will sideline their competitors.

Primary-source citations

Ed SimFounder & General Partner@ boldstart ventures✓ Verified

"You need to scan the code first in order to then start protecting it... There's hundreds of [MCP servers and endpoints] now in organizations people don't even know about."

Manoj NairChief Innovation Officer@ Snyk✓ Verified

"You want them to be specialized but only give them enough agency and ability to do that particular task... We're training a red teaming agent to figure out how do you break this agentic application with an LLM."

Manoj NairChief Innovation Officer@ Snyk✓ Verified

"We found the toxic flow attack pattern that the GitHub MCP server had an exploit potential, and that is a prompt injection, plus bringing this improper access."

Francesca LaBiancaHead of Business Operations@ Factory✓ Verified

"You're moving from single human in an IDE writing every line of code to now being able to send a task to an agent... that requires a fundamentally new way of working."

Sanjay PoonenPresident & CEO@ Cohesity✓ Verified

"You have to have very strict roles-based access controls to ensure the wrong people aren't searching, summarizing, and that if you're going to do summarization... you got to make sure it's not hallucinating."

Francesca LaBiancaHead of Business Operations@ Factory✓ Verified

"AGENTS.md file, which is an open source standard now... that sets up rules for your agents as they run. But this extends to how your tests are set up, how your linters are set up, how your dev containers are set up."

Manoj NairChief Innovation Officer@ Snyk✓ Verified

"I've been in meetings where the CISO and CTO are on the call with me and ask the question, 'How many agents or LLMs do you have in production?' And the answer from the security team is zero. The answer from the CTO is thousands."

Manoj NairChief Innovation Officer@ Snyk✓ Verified

"We found the toxic flow attack pattern that the GitHub MCP server had an exploit potential, and that is a prompt injection, plus bringing this improper access."

Ed SimFounder & General Partner@ boldstart ventures✓ Verified

"We ended up funding a company called Protect AI a year before ChatGPT even came out... they ended up selling to Palo Alto Networks a few months ago for over 700 million."

Ed SimFounder & General Partner@ boldstart ventures✓ Verified

"I've never seen a technology take off with AI-assisted coding like it has. About a year and a half ago, no one was like, 'Ah, we're trying out GitHub Copilot.' All of a sudden, it's wall to wall every large Fortune 500 right now."

Sanjay PoonenPresident & CEO@ Cohesity✓ Verified

"In Europe, they have this regulation called DORA, requires data to stay in the country, and we think there's going to be a lot more sovereign cloud requirements."

Francesca LaBiancaHead of Business Operations@ Factory✓ Verified

"We call this agent-driven development and it's really you spec out a task to an agent much like you would to an engineer on your team... that requires a fundamentally new way of working."

Manoj NairChief Innovation Officer@ Snyk✓ Verified

"I've been in meetings where the CISO and CTO are on the call with me and ask the question, 'How many agents or LLMs do you have in production?' And the answer from the security team is zero. The answer from the CTO is thousands."

Ed SimFounder & General Partner@ boldstart ventures✓ Verified

"About a year and a half ago, no one was like, 'Ah, we're trying out GitHub Copilot.' All of a sudden, it's wall to wall every large Fortune 500 right now. And because of that, people are then saying, 'Holy crap, I think there's a problem here.'"

Sanjay PoonenPresident & CEO@ Cohesity✓ Verified

"In Europe, they have this regulation called DORA, requires data to stay in the country, and we think there's going to be a lot more sovereign cloud requirements that force... we think that that's going to lead to a federation of sovereign clouds."

Francesca LaBiancaHead of Business Operations@ Factory✓ Verified

"Commits have gone up like 6x, but pull requests have not gone up proportionately and the size of the commits has also gone up exponentially. So we're creating thousands of additional lines of code."