Delivery and access

Fewer outages, safer sign-in

ZWAF is also your load balancer and the sign-in in front of your applications. It sends users only to healthy servers, checks who they are before they reach an application, and works in pairs. If one appliance fails, the other takes over and signed-in users stay signed in.

Load balancing (ADC)

Applications stay available, even when a server does not

ZWAF is a load balancer and reverse proxy for TCP, UDP and HTTP: an application delivery controller (ADC). It sends each user to a server that is working, takes failing servers out by itself and gives you the controls you expect from an ADC.

  • Traffic spread by real server load

    Round robin, least connections, fastest response or priority groups. Or let ZWAF weigh each server by its actual CPU, memory and network load, read over SNMP or from a small agent for Linux and Windows.

  • Failing servers taken out for you

    Health checks for HTTP, HTTPS, HTTP/2, TCP, UDP, ICMP, DNS, LDAP, RADIUS and SMTP, or your own scripts. ZWAF also watches the live traffic and takes a server out after real errors.

  • Users stay on their server

    A user's session sticks to the same server by address, TLS session, cookie, header, parameter or path, with a fallback when the first key is missing.

  • HTTP/2 and HTTP/3 for older applications

    Your users connect over HTTP/1.1, HTTP/2 or HTTP/3, whatever your servers speak. Compression and an HTTP cache take work off the servers, and old HTTP/1.0 clients reach them as HTTP/1.1.

  • Rules, scripts and your iRules

    Route by host, path, method, header, cookie, browser, client address or TLS details. When rules are not enough, write scripts in Lua, or bring your F5 iRules: they run on a compatibility layer, which flags any command it does not support.

  • Tuned for every kind of network

    TCP profiles for LAN, WAN and mobile users, with CUBIC or BBR, TCP Fast Open and automatic buffers, set separately for the users' side and the servers' side.

  • Full and reverse proxy
  • Fast L4 in XDP
  • SNAT, NAPT and 1:1 NAT
  • Auto last hop
  • X-Forwarded-For
  • ICAP
  • Packet filter L3 to L7
  • Resource cloaking
  • UDP bandwidth control

Access, MFA and SSL VPN

Strong sign-in in front of every application

Many internal applications have a weak login, or none at all. ZWAF asks users who they are before their request reaches the application, with single sign-on and MFA, using the directories you already have. You do not have to change the application to protect it.

  • Works with your directories

    Active Directory and LDAP over TLS, RADIUS and RadSec, TACACS+, Kerberos, RSA SecurID, a local user database with Argon2id passwords, or an HTTP service of your own.

  • Single sign-on

    SAML 2.0 as service provider or identity provider, OpenID Connect with PKCE as relying party or provider, and OAuth 2.0 with token exchange. Importing metadata makes a certificate change a single step.

  • MFA that is easy to use

    Authenticator apps (TOTP), security keys and passkeys (WebAuthn), codes by e-mail or SMS, RADIUS challenges and SecurID. You draw the sign-in flow in a visual editor, with a branch for each result.

  • Checked on every request

    Rules apply to every request of a session: groups, method and path, country, IP reputation, bot score, device posture and how long ago the user signed in. The answer is allow, deny, read-only or sign in again.

  • API access under control

    JWTs checked against your providers' keys, opaque tokens by introspection, API keys stored only as hashes, tokens bound to a certificate or a DPoP key, scopes per method and path, rate limits and daily quotas.

  • SSL VPN for remote staff

    A VPN for OpenConnect and AnyConnect-compatible clients, and a web portal with the applications each group may use, behind the same sign-in and the same MFA.

High availability

A second appliance takes over when one fails

Run two ZWAF appliances as a pair, Active/Passive or Active/Active. If one fails, or you take it down for maintenance, the other carries the traffic with the same configuration.

  • Nobody is signed out

    Connections and TLS sessions are copied to the other appliance, and so are the sessions of signed-in users, their second factors, OAuth tokens and SAML state. A failover does not sign anyone out.

  • VPN users reconnect by themselves

    After a failover, VPN clients reconnect to the other appliance with their session and are let in without signing in again.

  • Traffic groups

    Floating addresses move with their traffic group. In Active/Active each appliance carries its own groups, and ZWAF warns you when one appliance alone could not carry the load of both.

  • Change once, both stay in sync

    The configuration is synchronised as a whole version: everything, WAF policies and certificates included, except each appliance's own settings.

Next step

See ZWAF in front of your applications

Tell us what you run and how your traffic looks. We will show you how ZWAF would protect it and answer your questions about licensing and support. Resellers and integrators are welcome too: we are building our partner network and would like to hear from you.