Backport includes a Web Application Firewall (WAF) that inspects every request before it reaches your backend. Here's how it works, what it catches, and how to use it.
The WAF uses 17 pre-compiled regex patterns that scan request bodies, paths, and query parameters. When a request matches a known attack pattern, the gateway immediately returns HTTP 403 (Forbidden) and your backend is never touched. The check adds minimal latency — under 1ms per request on average.
By default, WAF is OFF. You can enable it from Dashboard → Settings → Toggle WAF to ON. This gives you control — you can test your traffic first, then enable WAF when ready.
The WAF covers 6 categories of web attacks. Here's every pattern we check for:
| Category | Patterns | What It Catches |
|---|---|---|
| SQL Injection | 5 patterns | UNION SELECT, DROP TABLE, OR 1=1, xp_cmdshell, sp_executesql |
| XSS | 4 patterns | <script> tags, onerror handlers, javascript: URIs, <iframe>/<embed> |
| Path Traversal | 2 patterns | ../ directory escapes, /etc/passwd, /proc/self access |
| Command Injection | 3 patterns | Shell metacharacters, subshell execution, backtick injection |
| LDAP Injection | 1 pattern | LDAP filter manipulation syntax |
| XML/XXE | 1 pattern | <!DOCTYPE SYSTEM and <!ENTITY declarations |
We tested the WAF against common attack payloads. Every request below was sent through the proxy with WAF enabled, and all were blocked with HTTP 403:
WAF is toggled from your dashboard settings. Here's how to enable it:
Once enabled, every request through your proxy will be checked against all 17 patterns. Blocked requests return HTTP 403 with the response body {"detail":"WAF Blocked: Malicious payload detected"}.
Important:The WAF is a first line of defense. It catches common attack patterns, but it's not a replacement for secure coding practices. Always validate and sanitize inputs at your application layer.
Sign up, enable WAF, and test against your own payloads. Free plan includes full WAF protection.
Start Free