AI gateway and tool-connection controlsAdditional if: Model or tool traffic uses a security gateway · Model, tool, connector, API, or Model Context Protocol (MCP) traffic is routed through a security gateway.AI API and web application protectionAdditional if: System uses APIs, tool servers, or web apps · The system exposes or uses APIs, model endpoints, tool servers, web applications, or agent-to-tool traffic that application or API security controls can inspect.AI application runtime protectionDirectly addresses · Protect custom AI applications, information-retrieval systems, model calls, prompts, and outputs while they run.Action-taking agent safeguardsDirectly addresses · Observe and govern agent plans, memory, tool use, delegated tasks, and actions while the agent runs.Agent identity and permissionsAdditional if: Agents act with delegated authority · An agent acts with delegated authority and needs an accountable owner, task-level permissions, access reviews, or rapid revocation.AI data protectionAdditional if: Sensitive content enters AI flows · Sensitive content must be inspected or blocked in prompts, responses, files, retrieved information, or tool calls.
Vendor research
Kong AI Gateway
Review what this vendor says publicly, the security topics those statements may support, what remains unverified, and factual company context. This is not an assessment of product effectiveness or fit.
Use-case context
How this vendor relates to the selected use case
Related research availableBack to use case →
These links show approaches associated with this vendor. The relationship label describes how the approach maps to the use case—not product effectiveness, complete requirement coverage, or fit.
Company scale
Scaled?
ScaledA private provider with at least $100M in known funding or at least 250 employees.This is a company-scale signal, not a product-quality rating.
?
ScaledA private provider with at least $100M in known funding or at least 250 employees.This is a company-scale signal, not a product-quality rating.A descriptive band derived from retained public revenue, workforce, ownership, or funding signals.
Company scale is separate from product features, effectiveness, and suitability.
- $345M known funding
- 800+ employees
- Founded 2017
- Private-company revenue and profitability not sourced
Company context
Private, venture-backed independent company
Kong reported 800+ employees and 900+ customers in May 2026 and says its platform handles production application programming interface (API) and AI workloads
Research coverageCounts describe available public research, not product quality.View details
- Vendor statements
- 19 records
- Source-checked records
- 10
- Evaluation requirements
- 19 in this research model
- Unresolved requirements
- 9
Company intelligence
Who is behind the product
Company facts provide evaluation context. Each signal is kept separate because tenure, workforce, funding, and hiring answer different questions.
Founded2017 under the Kong identity, following the earlier Mashape product lineage
HeadquartersSan Francisco, California
OwnershipPrivate, venture-backed independent company
Employees800+
Capital and scalePlatform provider
Kong Inc.
- Known funding
- $345M
- Operating scale
- Kong reported 800+ employees and 900+ customers in May 2026 and says its platform handles production API and AI workloads
- Backing context
- $345M total capital raised, including a $175M Series E announced at a $2B valuation in 2024
Series E · $175M
Founders and leadershipMore research needed
Founder names and current roles are not yet supported by a public source in this research.
Operating signalsRead each signal separately
There is no combined company rating. The company-scale label uses stated size thresholds; product features and effectiveness require separate evidence.
- Company tenure
- 2017 under the Kong identity, following the earlier Mashape product lineage
- Workforce scale
- 800+
- Hiring activity
- Not displayed
A current count requires a retained, clickable source URL.
Open research questions
- Founder names and current-company status are not yet supported by a public source.
Company sources and research limits4 linked public sources
Only company facts supported by retained public sources are shown. Missing values remain unknown, and company scale does not establish product effectiveness.
Company sourceKong AI Security solution pageKong describes AI security controls for LLM, MCP, and agent use cases, including prompt guards, PII sanitization, authorization, and per-agent observability.Company sourceKong Agent Gateway releaseKong states that Agent Gateway is generally available in AI Gateway 3.14 for LLM, MCP, and agent-to-agent traffic governance.Company sourceKong Series E releaseKong announced a $175M Series E at a $2B valuation, bringing total disclosed capital raised to $345M.Company sourceKong headquarters announcementKong describes its 2017 inception, San Francisco headquarters, and global company footprint.
Solution areas
These areas describe how the vendor approaches enterprise AI security. They do not establish product quality or fit.
AI gateway and tool-connection controlsCore product focusAI API and web application protectionCore product focusAI application runtime protectionRelated coverageAction-taking agent safeguardsRelated coverageAgent identity and permissionsRelated coverageAI data protectionRelated coverageAI usage and cost controlsRelated coverage
Buyer context
- Evaluate Kong AI Gateway as the AI-native control layer in Kong's portfolio; do not map ordinary Kong application programming interface (API) Gateway capabilities to AI controls without direct large language model (LLM), Model Context Protocol (MCP), or agent evidence.
- Public evidence supports centralized policy and observability across large language model (LLM) calls, Model Context Protocol (MCP) tool access, and agent-to-agent (A2A) communication, including prompt guards, PII sanitization, authentication, authorization, rate limiting, and per-agent telemetry.
- Confirm edition, plugin, deployment-mode, and Kong Konnect entitlement boundaries during diligence; public evidence does not support workforce browser governance, model assurance, AI supply-chain security, or enterprise GRC coverage.
Related frameworks
Where public vendor statements relate to framework requirements
11 related frameworks · expand when needed
Related frameworks
Where public vendor statements relate to framework requirements
These links show related requirements for further review. They do not establish framework compliance or control implementation. Open the full framework crosswalk →
Current referenceCSA AI Controls Matrix
- Requirements with public support
- 9
- Related requirements
- 14
- References
- 71
- Requirements with public support
- 8
- Related requirements
- 12
- References
- 35
- Requirements with public support
- 8
- Related requirements
- 12
- References
- 71
- Requirements with public support
- 8
- Related requirements
- 13
- References
- 39
- Requirements with public support
- 8
- Related requirements
- 12
- References
- 39
- Requirements with public support
- 8
- Related requirements
- 12
- References
- 31
- Requirements with public support
- 8
- Related requirements
- 13
- References
- 31
- Requirements with public support
- 8
- Related requirements
- 13
- References
- 25
- Requirements with public support
- 7
- Related requirements
- 11
- References
- 58
- Requirements with public support
- 7
- Related requirements
- 11
- References
- 27
- Requirements with public support
- 4
- Related requirements
- 3
- References
- 3
Evaluation questions
What to verify beyond public claims
These questions come from security requirements with some public support. Use them as starting points for demonstrations, documentation review, customer references, or a buyer-observed pilot.
- 01Approved AI usage monitoring
Approved AI workspace activity appears with user, workspace or tenant, model or provider, and timestamp.
- 02Approved AI usage monitoring
Prompt, model, or admin activity can be exported or correlated for the selected approved AI platform.
- 03Sensitive-data protection for generative AI
Sensitive prompt, response, or file test data is detected and classified during an AI interaction.
- 04Sensitive-data protection for generative AI
A policy redacts, blocks, coaches, or records the sensitive data event before it leaves the approved path.
- 05Generative AI application security
A test large language model (LLM) application event records prompt, application programming interface (API), model, retrieval, or tool interaction context.
- 06Generative AI application security
A prompt-injection or unsafe-output test is detected, blocked, or flagged by the guardrail or large language model (LLM) firewall.
- 07AI gateway, tool-connection, and runtime controls
A model, agent, tool, or Model Context Protocol (MCP) request passes through a named policy enforcement point.
- 08AI gateway, tool-connection, and runtime controls
A test policy allows, blocks, transforms, redirects, or rate-limits the request with an explicit reason.
Detailed security-requirement research18 evaluation items · supporting evidence and open research are shown separatelyExpand
Security requirementPublic supportRelated frameworksWhat to verify
Unapproved AI use discovery
No supporting claim foundDiscover and monitor workforce AI tools, accounts, prompts, domains, models, users, and usage outside approved controls.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
An unmanaged AI app used by a test user appears in discovery inventory with user, app or domain, and timestamp.
AI-feature discovery in business applications
No supporting claim foundInventory software as a service (SaaS) applications that embed AI features, expose enterprise data to AI capabilities, or create AI-driven data movement.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A software as a service (SaaS) app with an embedded AI feature appears in the software as a service (SaaS) AI inventory with app, provider, and feature context.
Approved AI usage monitoring
Strong public supportMonitor approved AI workspaces, tenants, gateways, and model platforms such as ChatGPT Enterprise, Claude Enterprise, Gemini, Microsoft Copilot, Vertex AI, Elvex, or internal AI gateways.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
Approved AI workspace activity appears with user, workspace or tenant, model or provider, and timestamp.
Controls for unapproved AI use
No supporting claim foundBlock, coach, redirect, or contain non-approved AI use and policy-violating AI interactions.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A policy blocks, coaches, redirects, or contains a test interaction with an unapproved AI destination.
Sensitive-data protection for generative AI
Strong public supportDetect, classify, redact, or block sensitive data in prompts, responses, files, retrieval, memory, and AI-connected workflows.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
Sensitive prompt, response, or file test data is detected and classified during an AI interaction.
Browser and business-application controls
No supporting claim foundApply session-level controls in browser and software as a service (SaaS) workflows, including uploads, downloads, copy/paste, sharing, and identity-aware access decisions.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A session-level policy controls upload, download, copy, paste, sharing, or form submission in a browser or software as a service (SaaS) workflow.
Generative AI application security
Strong public supportProtect enterprise-built large language model (LLM) applications, retrieval-augmented generation (RAG) systems, prompts, application programming interfaces (APIs), model calls, tools, and production runtime behavior.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A test large language model (LLM) application event records prompt, application programming interface (API), model, retrieval, or tool interaction context.
AI governance, risk, and compliance
No supporting claim foundInventory AI systems and owners, translate policy and regulatory obligations into governed workflows, assess risk, manage approvals and exceptions, and retain audit evidence across the AI lifecycle.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A test AI system is registered with owner, intended use, risk tier, lifecycle state, and applicable obligations.
AI assurance and adversarial testing
No supporting claim foundTest models, applications, retrieval-augmented generation (RAG) systems, and agents before release and continuously thereafter using adversarial probes, evaluation suites, attack simulation, and security release gates.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A controlled test campaign exercises an AI model, application, or agent against named AI attack classes.
AI model and supply-chain security
No supporting claim foundDiscover, inventory, scan, validate, and monitor models, datasets, model artifacts, registries, dependencies, and AI development assets for tampering, unsafe serialization, provenance gaps, or malicious content.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A test model or AI artifact appears in inventory with origin, version, hash or provenance, and deployment context.
AI gateway, tool-connection, and runtime controls
Strong public supportMediate model, agent, tool, application programming interface (API), connector, and Model Context Protocol (MCP) traffic through an enforcement point that applies identity-aware policy, content controls, routing, rate limits, and auditable allow or deny decisions.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A model, agent, tool, or Model Context Protocol (MCP) request passes through a named policy enforcement point.
Action-taking agent monitoring
Limited public supportObserve and govern agent plans, memory, tool calls, delegated tasks, autonomy, runtime decisions, and outcomes.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A test agent run captures plan, steps, tool calls, outcome, and timestamps.
Agent-to-agent communication security
Strong public supportAuthorize, log, and control agent-to-agent, agent-to-tool, Model Context Protocol (MCP), connector, and tool-chain handoffs.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
An agent, tool, connector, or Model Context Protocol (MCP) handoff logs source identity, destination, and authorization decision.
Non-human identity and service-account security
No supporting claim foundInventory, least privilege, credential hygiene, monitoring, and lifecycle management for non-human identities, workloads, service accounts, application programming interface (API) keys, and machine credentials.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A test service account, agent identity, or non-human identity appears in inventory with owner and privileges.
AI agent identity and permissions
Limited public supportRegister AI agents as accountable identities, bind them to owners and delegating users, authorize task- and tool-level access, issue short-lived credentials, review access, and revoke or suspend agent authority.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A test agent is registered with a unique identity, accountable owner, purpose, and permitted resources.
AI coding-agent and workstation security
No supporting claim foundDiscover and govern AI coding agents, integrated development environment (IDE) assistants, command-line agents, skills, hooks, extensions, Model Context Protocol (MCP) tools, filesystem access, commands, network activity, secrets, and software-supply-chain actions on developer workstations and build environments.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A test coding agent and its skills, hooks, extensions, or Model Context Protocol (MCP) tools appear in an attributable inventory.
AI cost and usage controls
Limited public supportVisibility, attribution, budgeting, rate limiting, anomaly detection, and optimization for AI usage and spend across models, agents, workflows, and owners.
Commercial MetadataNIST AI RMF PlaybookNIST Cybersecurity Framework 2.0ISO/IEC 42001OWASP Agentic AI Security Solutions Landscape
A controlled AI usage event is attributed to user, team, model, workflow, or owner with cost or token metrics.
Licensing model
Limited public supportPublicly discoverable commercial model such as per user, per seat, per app, per token, per integration, or enterprise platform license.
The vendor can map the sourced commercial model to per-user, per-seat, per-app, per-token, per-integration, or platform packaging.
Public sources
Vendor statements and quoted evidence
Showing the first 6 of 19 source records. Open additional records only when needed.
Kong AI Gateway materials reviewed did not provide a public claim for workforce discovery of unmanaged AI tools, accounts, users, and usage.
No quoted source text is recorded for this claim.
Kong AI Gateway materials reviewed did not provide a public claim for AI-feature discovery across the enterprise business-application environment.
No quoted source text is recorded for this claim.
Kong claims unified observability for application programming interface (API), large language model (LLM), Model Context Protocol (MCP), and per-agent consumption through its AI gateway.
unified observability for API, LLM, and MCP consumption
Kong AI Gateway materials reviewed did not provide a public claim for blocking, coaching, redirecting, or containing unapproved AI use.
No quoted source text is recorded for this claim.
Kong claims built-in PII sanitization that prevents sensitive data from reaching an large language model (LLM).
sensitive data never leaks into an LLM
Kong AI Gateway materials reviewed did not provide a public claim for session-level browser or software as a service (SaaS) controls for employee AI use.
No quoted source text is recorded for this claim.
Show 13 additional evidence records
Kong claims standardized PII, authorization, and prompt guardrails for large language model (LLM) and agent applications.
PII sanitization, authorization, prompt guards
Kong AI Gateway materials reviewed did not provide a public claim for AI inventory, risk, approval, exception, and compliance workflows.
No quoted source text is recorded for this claim.
Kong AI Gateway materials reviewed did not provide a public claim for AI-specific adversarial testing and release assurance.
No quoted source text is recorded for this claim.
Kong AI Gateway materials reviewed did not provide a public claim for model and AI-artifact supply-chain inspection.
No quoted source text is recorded for this claim.
Kong claims one governance layer across large language model (LLM) calls, Model Context Protocol (MCP) tool access, application programming interface (API) traffic, events, and agent-to-agent (A2A) communication.
single governance layer across the entire stack
Kong claims unified observation of large language model (LLM) calls, Model Context Protocol (MCP) tool invocations, and agent-to-agent (A2A) communication.
observe LLM calls, MCP tool invocations, and A2A communication
Kong claims control and observation of agent-to-agent communication over agent-to-agent (A2A).
Control and observe agent-to-agent communication over the A2A protocol
Kong AI Gateway materials reviewed did not provide a public claim for non-human identity and machine-credential lifecycle controls.
No quoted source text is recorded for this claim.
Kong claims identity verification and enforcement for agents participating in agent-to-agent (A2A) workflows.
Verify and enforce identity for every agent in your workflows
Kong AI Gateway materials reviewed did not provide a public claim for coding-agent, integrated development environment (IDE), CLI, workstation, tool, and package-action governance.
No quoted source text is recorded for this claim.
Kong claims per-agent token and resource tracking for cost allocation.
Track token consumption and resource usage at the agent level
Kong states that Agent Gateway is included for Kong Konnect customers as part of AI Gateway.
available now for all Kong Konnect customers as part of Kong AI Gateway
Kong positions AI Gateway as an external control layer between applications, models, tools, and agents.
traffic between your applications and large language models