LLM firewalls & guardrails

Radware LLM Firewall: inline prompt-level LLM firewall

Radware LLM Firewall is an inline prompt-level LLM firewall from Radware. It is a commercial product offered as: SaaS. Pricing model: not published.

  • Last reviewed

Best for

Organizations that already use Radware's cloud application protection and want prompt screening for LLM apps added in front of the model without code changes

Consider instead if

  • You want an open-source guardrails toolkit that you host and configure yourself. See NeMo Guardrails.
  • You want a WAF-style AI firewall from an edge or CDN provider. See Firewall for AI.

What Radware LLM Firewall does

Radware LLM Firewall is a prompt-level firewall that Radware launched on November 18, 2025 as an add-on to all tiers of its Cloud Application Protection Services. Radware describes it as inline, pre-origin protection that inspects prompts before they reach the model and checks responses, is not tied to one model and needs no SDK or code changes. Radware's AWS Marketplace listing sells the cloud service as SaaS, with the LLM Firewall as an add-on. A Radware blog lists six guardrails: prompt injection protection, PII detection and masking, harmful and abusive language blocking, brand protection, allowed and banned topics, and a token limit watchdog. It has a blocking mode and a report-only mode. Radware's release says it is designed to address the OWASP Top 10 for LLM applications. Pricing is not published, and the solution overview sits behind a registration form.

This summary is our own wording of the sourced facts on this page.

Key facts

Each value links to the page that states it, with the date we checked it.

Latest release
Not documented in the sources we checked
Documentation
Not documented in the sources we checked
API reference
Not documented in the sources we checked
Quickstart
Not documented in the sources we checked
Security page
Not documented in the sources we checked
Attestations or disclosure
Not documented in the sources we checked

Capabilities

As documented by the vendor or project. The tag is our label from a controlled vocabulary.

Where Radware LLM Firewall fits in our AI security layers

Our analysis

Our editorial model, not a standard. The primary layer follows the category, except for tools whose main documented job is detection and response; other layers rest on a capability the sources document. How the model works.

AI security layers that Radware LLM Firewall covers, with the role, how each applies and what it rests on
LayerRoleHow it appliesBased on
L6 Runtime Runtime guardrails Primary Screen what goes into and comes out of a model in live traffic, and limit abuse of the model endpoint. Follows its category, LLM firewalls & guardrails
L5 Data Data protection Also covers Detects PII in prompts and responses and masks, blocks or logs it, which also places it in data protection. Detects and masks, blocks or logs PII in prompts and responses, and blocks attempts to extract PII before it reaches the LLM
L8 Monitoring Monitoring and response Also covers Documents dashboards that show prompts, outputs and which guardrails fired or blocked a prompt. Dashboards show user actions, prompts and outputs, including which guardrails fired and which prompts were blocked

OWASP LLM Top 10 mapping

Our analysis

The risk list is OWASP's (Top 10 for LLM Applications, 2025). The mapping is our analysis, and each row rests on a capability the sources document.

OWASP LLM risks mapped to Radware LLM Firewall, with the capabilities each mapping rests on
RiskHow it appliesBased on
LLM01 Prompt Injection Screens prompts for injection and jailbreak attempts before they reach the model. Inspects prompts for prompt injection and resource abuse before they reach the LLM; Blocks jailbreak attempts at the prompt level
LLM02 Sensitive Information Disclosure Detects PII in prompts and responses and blocks extraction attempts. Detects and masks, blocks or logs PII in prompts and responses, and blocks attempts to extract PII before it reaches the LLM
LLM05 Improper Output Handling Validates model responses against guardrails before they are used. Validates model responses in real time, with guardrails for PII, brand tone and topic filtering
LLM10 Unbounded Consumption A token watchdog limits input and output tokens. A token watchdog enforces input and output token limits

Alternatives and related tools

More in LLM firewalls & guardrails, ranked within the category by Coverage Score.

Open sourceApache-2.0
  • Library
  • Self-hosted
  • API

Adds programmable input, dialog, retrieval, execution and output rails to LLM applications.

Best for: Teams that want to script rules for one LLM application in Python and run them in their own infrastructure

Coverage Score 76 out of 100
  • LLM01 Prompt Injection
  • LLM02 Sensitive Information Disclosure
  • LLM05 Improper Output Handling
  • LLM06 Excessive Agency

Reviewed

Portkey AI Gateway

Palo Alto Networks (Portkey)

Open sourceMIT Freemium Now Prisma AIRS AI Gateway
  • SaaS
  • Self-hosted
  • API

Routes LLM traffic through one gateway API and runs input and output guardrail checks on each request.

Best for: Teams that want a single gateway for several LLM providers with guardrail checks, available as open source or as a hosted service

Coverage Score 69 out of 100
  • LLM01 Prompt Injection
  • LLM02 Sensitive Information Disclosure
  • LLM05 Improper Output Handling
  • LLM09 Misinformation

Reviewed

Open sourceApache-2.0
  • Self-hosted
  • SaaS
  • API

Routes LLM traffic through Kong with prompt guards, PII sanitization, spend limits and observability.

Best for: Teams that already run Kong as an API gateway and want LLM routing and prompt controls on the same data plane

Coverage Score 65 out of 100
  • LLM01 Prompt Injection
  • LLM02 Sensitive Information Disclosure
  • LLM10 Unbounded Consumption

Reviewed

Radware LLM Firewall FAQ

How is the Radware LLM Firewall sold?

Radware's November 18, 2025 release says it is an add-on to all tiers of its Cloud Application Protection Services. The pages we opened show no prices.

What guardrails does it list?

A Radware blog lists prompt injection protection, PII detection and masking, harmful and abusive language blocking, brand protection, allowed and banned topics, and a token limit watchdog.

Does it need code changes?

The blog describes it as no-code, with no SDKs or application changes, connected into the existing traffic flow. It offers a blocking mode and a report-only mode.

Key facts you can cite

We have no commercial relationship with Radware.

Sources & last reviewed

Last reviewed . We compile from the vendors' own public pages and repositories and we do not run the products. Source links open in a new tab. Found a mistake? Report a correction.