Cloudflare AI Gateway
Overview
Product details compiled from public sources, each with a citation.
Matrix Coverage
Where this product defends, by asset class and NIST CSF function. The Coverage column shows whether each asset is Primary, Secondary, or Adjacent to what the product does. The table omits empty rows and columns.
| Asset class | Identify | Protect | Detect | Coverage | Source |
|---|---|---|---|---|---|
| AI Gateways and Routers | Identify: Covered | Protect: Covered | Detect: Covered | Primary | 1 |
| Runtime AI Data | Identify: Not covered | Protect: Covered | Detect: Covered | Secondary | 2 |
Framework Relevance
These frameworks include controls relevant to the asset classes Cloudflare AI Gateway defends. This is an editorial inference from the AI Defense Matrix asset-level crossmap, not a statement that Cloudflare implements these controls or is certified against them.
Expand Collapse
| Framework | Asset class | Relevant controls |
|---|---|---|
| NIST IR 8596 | AI Gateways and Routers | AI data flows; APIs; inference endpoints (traffic side); model registries and dataset sources |
| Runtime AI Data | Prompts (runtime); inference data | |
| CSA AI Controls Matrix | AI Gateways and Routers | Infrastructure Security; Interoperability and Portability |
| Runtime AI Data | Data Security and Privacy Lifecycle Management; Application and Interface Security | |
| ISO 42001 | AI Gateways and Routers | A.8 Information for interested parties; A.9 Use of AI systems; A.10 Third-party and customer relationships |
| Runtime AI Data | A.7 Data for AI systems; A.8 Information for interested parties | |
| Google SAIF | AI Gateways and Routers | Harden and monitor infrastructure; network-level access and egress controls |
| Runtime AI Data | Expand AI red-teaming; runtime input and output safety; prompt defense | |
| SANS Critical AI Security Guidelines | AI Gateways and Routers | Conventional Security Controls (authenticate and control access to inference APIs; API key management); Model I/O Handling (rate limiting; egress output filtering); Monitoring (interaction and API-usage logging) |
| Runtime AI Data | Model I/O Handling (sanitize, validate, and filter inputs and outputs; segregate user and system prompts; multilayered prompt-injection defense); Conventional Security Controls (protect augmentation and RAG data with vector-store access controls and validation); Data Minimization and Obfuscation (limit sensitive prompt content; context-window management); Limit Model Behavior (AI guardrails) | |
| MITRE ATLAS | AI Gateways and Routers | AML.T0057 LLM Data Leakage; AML.T0024 Exfiltration via AI Inference API (network-side observation) |
| Runtime AI Data | AML.T0051 LLM Prompt Injection; AML.T0054 LLM Jailbreak; AML.T0056 Extract LLM System Prompt | |
| OWASP AI Exchange | AI Gateways and Routers | Runtime threats: data leakage via AI egress; network-level access control gaps |
| Runtime AI Data | Input threats: prompt injection, adversarial inputs, evasion; runtime threats: RAG poisoning, memory tampering | |
| OWASP LLM Top 10 | AI Gateways and Routers | LLM10 Unbounded Consumption (cost and rate control); shadow AI egress and output handling |
| Runtime AI Data | LLM01 Prompt Injection; LLM02 Sensitive Information Disclosure; LLM08 Vector and Embedding Weaknesses; LLM05 Improper Output Handling | |
| OWASP Agentic Security Top 10 | AI Gateways and Routers | ASI07 Insecure Inter-Agent Communication; ASI02 Tool Misuse and Exploitation (egress and tool-invocation scope); ASI04 Agentic Supply Chain Vulnerabilities (MCP and tool-registry trust) |
| Runtime AI Data | ASI06 Memory & Context Poisoning; ASI01 Agent Goal Hijack (via prompt injection in runtime inputs) |
Provenance
Last sourced 2026-06-09.
Expand Collapse
Changelog
-
Enriched from the Cloudflare AI Gateway documentation.
Found an error? Corrections are welcome. Suggest an edit.
Product Strategy and Positioning
You can use the following frameworks to understand the product’s strategy and its competitive positioning. Performing this analysis is outside the scope of the AI Defense Matrix Catalog, but the following guidance can help you with such an assessment.
Expand Collapse
Product Strategy
Lenny Zeltser’s Guide to Creating Cybersecurity Products can help you understand key aspects of the product strategy. You can use your AI tool to gather the data and apply this framework.
- Market segment
- Who the product is built for: industry, size, and the persona who evaluates it.
- Go-to-market motion
- How it reaches buyers: top-down sales, bottom-up adoption, or open source.
- Pricing model
- How value is captured: per-seat, consumption, or outcome-based.
- Delivery and operations
- How it is deployed, configured, and maintained, including infrastructure-as-code and API coverage.
- Customer trust
- Certifications, transparency, and supply-chain security a buyer expects from the vendor.
- Ecosystem position
- A point solution, a platform others build on, or a component of a larger platform.
Strategy Defensibility
Ben Vierck’s rubric can help you assess the defensibility of the SaaS product’s strategy against competitive and other market forces. You can use it with your AI tool for a methodical analysis.
- Value delivery
- How much of the value is hard to replicate versus standard software a competitor could rebuild.
- Switching cost
- How costly it is to leave once deployed: integrations, data, workflow, and platform ties.
- Compliance moat
- Whether certifications or regulatory alignment are a durable advantage or table stakes for this buyer.
- Problem complexity
- How hard, adversarial, and fast-moving the underlying problem is to solve well.
- Buyer profile
- Who holds the budget, and how durable that demand is across the market.
- Layer
- Where the product operates: application, model, infrastructure, platform, or identity control plane.
- Proprietary data, content, or IP
- Whether it accumulates data, content, or IP that others would find difficult to replicate.