ASAI Security ResearchIndependent public-source research
Public reviewread only

Solution approach

AI API and web application protection

Find and protect AI-related application programming interfaces (APIs), model endpoints, tool servers, and agent traffic.

Use-case context

How this approach relates to the selected use case

Applications and agents: Additional 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.

Back to use case →
Research scopeVendorsPublicly documented vendor profiles
Evaluation guideRequirementsRequirements connected to the selected use case
Evidence basisSourcesPublic claims linked to their original sources
Unresolved itemsQuestionsMissing support is labeled instead of assumed
View research coverageThese counts describe available public research, not product quality or suitability.Expand
Vendor profiles
9 shown in this view
Security requirements
3 to review
Strong public support
19 requirement records
Limited public support
5 requirement records
Open research
3 with no supporting claim · 0 incomplete

Evaluation guide

What to verify for this use case

Additional security requirement

Generative AI application security

Protect enterprise-built large language model (LLM) applications, retrieval-augmented generation (RAG) systems, prompts, application programming interfaces (APIs), model calls, tools, and production runtime behavior.

Questions to test
  1. A test large language model (LLM) application event records prompt, application programming interface (API), model, retrieval, or tool interaction context.
  2. A prompt-injection or unsafe-output test is detected, blocked, or flagged by the guardrail or large language model (LLM) firewall.
  3. The evidence links the event to an application, endpoint, request identifier, or workflow.
Related frameworks

NIST AI RMF Playbook · NIST Cybersecurity Framework 2.0 · CIS Critical Security Controls · ISO/IEC 42001 · OWASP GenAI Security Solutions Landscape

Foundational security requirement

AI gateway, tool-connection, and runtime controls

Mediate 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.

Questions to test
  1. A model, agent, tool, or Model Context Protocol (MCP) request passes through a named policy enforcement point.
  2. A test policy allows, blocks, transforms, redirects, or rate-limits the request with an explicit reason.
  3. The audit event records caller identity, destination, tool or model, policy decision, and timestamp.
Related frameworks

NIST AI RMF Playbook · NIST Cybersecurity Framework 2.0 · CIS Critical Security Controls · ISO/IEC 42001 · OWASP GenAI Security Solutions Landscape

Foundational security requirement

Action-taking agent monitoring

Observe and govern agent plans, memory, tool calls, delegated tasks, autonomy, runtime decisions, and outcomes.

Questions to test
  1. A test agent run captures plan, steps, tool calls, outcome, and timestamps.
  2. Agent memory, delegated task, autonomy, or runtime decision detail is visible in a timeline or log.
  3. Out-of-policy or unusual agent behavior can be flagged or filtered for investigation.
Related frameworks

NIST AI RMF Playbook · NIST Cybersecurity Framework 2.0 · CIS Critical Security Controls · ISO/IEC 42001 · OWASP GenAI Security Solutions Landscape

Vendor research

Vendors with public research for this approach

Choose vendors to compare →

Only requirements explicitly connected to the selected use case are shown. Vendors are grouped by whether this approach is a core product focus or related coverage, then ordered by documented support across the requirements shown. This organizes public research coverage; it is not a product ranking or recommendation.

Evidence labelsStrong public supportLimited public supportNo supporting claim foundResearch incomplete
VendorGenerative AI app securityAI gateway and tool controlsAgent runtime telemetrySourcesAction
Core product focusThis approach is central to how these vendors present the product · 8 vendors
AktoEmergingSupport found for 3 of 3 requirementsStrong public supportStrong public supportStrong public support2Profile →
Cequence AI GatewayScaledSupport found for 3 of 3 requirementsStrong public supportStrong public supportStrong public support1Profile →
Wallarm AI Control PlatformGrowth stageSupport found for 3 of 3 requirementsStrong public supportStrong public supportStrong public support2Profile →
Kong AI GatewayScaledSupport found for 3 of 3 requirementsStrong public supportStrong public supportLimited public support2Profile →
Imperva AI Application SecurityEstablishedSupport found for 2 of 3 requirementsStrong public supportStrong public supportNo supporting claim found1Profile →
Salt Agentic Security PlatformScaledSupport found for 3 of 3 requirementsLimited public supportLimited public supportStrong public support1Profile →
Akamai API SecurityEstablishedSupport found for 2 of 3 requirementsStrong public supportLimited public supportNo supporting claim found2Profile →
Harness AI Security / TraceableEstablishedSupport found for 2 of 3 requirementsStrong public supportLimited public supportNo supporting claim found1Profile →
Related coverageThese vendors address the requirements through another core product focus · 1 vendor
Cloudflare AI Security SuiteEstablishedSupport found for 3 of 3 requirementsStrong public supportStrong public supportStrong public support2Profile →

Company maturity remains a filter and profile attribute; it does not affect the research-coverage order.