AI Security
Model, data, prompt, agent, and identity security plus governance — spans the whole stack.
Stack position
Where AI Security sits in the AI stack
L15 · AI Agent
Agent runtimes, tool calling, MCP, memory, planning, and multi-agent orchestration.
L16 · AI Security
Model, data, prompt, agent, and identity security plus governance — spans the whole stack.
L17 · Enterprise AI
Copilots and workflow automation replacing part of the work, not just assisting it.
L18 · Vertical AI
AI-native products in healthcare, finance, legal, manufacturing, and other verticals.
Icons mark layer roles — not company logos. Position only; not a price chart.
Why this layer matters
The only layer that spans the whole stack. The access path used to be human → application; it is becoming human → agent → agent → tool → API → enterprise data. Each new hop needs identity, authorisation and audit, which is a different market from classic cybersecurity.
What is the bottleneck?
Agent identity has no settled standard. Until one exists, granting an autonomous process durable access to enterprise systems is an unpriced risk.
A structural observation about supplier concentration and lead times — not a view on any security.
Who sits in this layer?
This layer is left empty on purpose. Assigning a company to it would be our opinion rather than a statement about the company's primary business, and we would rather publish nothing than publish a classification we cannot defend as fact.
Coverage boundary
Coverage boundary: US-listed tickers or ADRs only (same rule as TSM / ASML). Important suppliers without a US listing are omitted even when they matter to the stack. That is a coverage rule, not a quality ranking.
No hand-listed notable omissions for this layer yet. The US-list / ADR rule still applies.
Checked 2026-10-09. Not exhaustive.
Same track
Descriptive positioning only. The positioning label says whether a company's business is exposed to a layer, never whether to buy it. Layers with no exposure are not recommendations to add any.