//Web Application Firewall

Application and API protection you can control and trust

Inspect every request close to where it comes from and stop attacks before they reach your network and application, without slowing it down.

Zero-day defense

WAF scores what each request carries by threat family and stops attacks on unpatched flaws, with no rules to update.

Global performance

WAF inspects each request on Azion's globally distributed infrastructure, so your applications stay secure and fast.

Low false positives

Tune the sensitivity of each threat family, see in Logging what the rules would block, and turn false positives into narrow exceptions.

//Features

Tune WAF to your traffic, then block

Fit WAF to each application's real traffic, so it blocks attacks and lets your customers through.

Set how strict WAF is, per threat. WAF scores each request by threat family, such as SQL injection and XSS, and you set the sensitivity of each family for each application.

Docs

See before you block. Run a rule set in Logging to record what it would block on your real traffic, then switch to Blocking when the results look right.

Docs

Fine-tune false positives. Turn a false positive into an exception for one rule, one path, and one field, so legitimate traffic flows while attacks keep being blocked.

Docs
//Integrations

One firewall, every layer of protection

WAF works with the rest of the firewall and with Azion observability, from the network layer to your SIEM.

  1. Every firewall carries DDoS Protection, which checks each request for DoS and DDoS attacks before any rule runs.

    firewall.tf
    01resource "azion_firewall_main_setting" "main" {
    02 data = {
    03 name = "my-firewall"
    04 active = true
    05
    06 # DDoS Protection is always on: there is no module to enable
    07 modules = {
    08 network_protection = { enabled = true }
    09 functions = { enabled = true }
    10 waf = { enabled = true }
    11 }
    12 }
    13}
  2. Allow or deny requests by address, network, or country with network lists, in the same firewall rules as WAF.

    allowlist.tf
    01resource "azion_network_list" "allowed" {
    02 results = {
    03 name = "Allowed addresses"
    04 type = "ip_cidr"
    05 items = ["203.0.113.0/24"]
    06 }
    07}
    08
    09resource "azion_firewall_rule_engine" "allowlist" {
    10 firewall_id = azion_firewall_main_setting.main.data.id
    11 results = {
    12 name = "Allow only listed addresses"
    13 active = true
    14 criteria = [{
    15 entries = [{
    16 criterion = {
    17 variable = "$${network}"
    18 operator = "is_not_in_list"
    19 conditional = "if"
    20 argument = tostring(azion_network_list.allowed.results.id)
    21 }
    22 }]
    23 }]
    24 behaviors = [{ behavior = { type = "deny" } }]
    25 }
    26}
  3. Cap the requests each client sends to a path and answer the excess with 429, next to WAF scoring.

    rate-limit.tf
    01resource "azion_firewall_rule_engine" "rate_limit" {
    02 firewall_id = azion_firewall_main_setting.main.data.id
    03 results = {
    04 name = "Rate limit the login"
    05 active = true
    06 criteria = [{
    07 entries = [{
    08 criterion = {
    09 variable = "$${request_uri}"
    10 operator = "matches"
    11 conditional = "if"
    12 argument = "^/login"
    13 }
    14 }]
    15 }]
    16 behaviors = [{
    17 behavior = {
    18 type = "set_rate_limit"
    19 attributes = {
    20 type = "second"
    21 limit_by = "client_ip"
    22 average_rate_limit = 10
    23 maximum_burst_size = 10
    24 }
    25 }
    26 }]
    27 }
    28}
  4. Run Bot Manager on the same firewall to tell scripts from people before they reach login and checkout.

    bot-manager.tf
    01resource "azion_firewall_functions_instance" "bot_manager" {
    02 firewall_id = azion_firewall_main_setting.main.data.id
    03 data = {
    04 name = "bot-manager"
    05 function = var.bot_manager_function_id
    06 active = true
    07 args = jsonencode({
    08 threshold = 18
    09 action = "deny"
    10 mode = "web"
    11 })
    12 }
    13}
  5. Add your own checks in code on the same firewall: change headers, deny, or drop a request before it reaches your application.

    firewall.js
    01addEventListener("firewall", (event) => {
    02 event.addRequestHeader("X-Custom-Header-1", "1");
    03 event.addRequestHeader("X-Custom-Header-2", "2");
    04 event.continue();
    05});
  6. Look up a blocked request to see the rules it matched and the score it reached.

    read-block-score.graphql
    01query {
    02 workloadEvents(
    03 limit: 1
    04 filter: { tsGte: "<start>", tsLt: "<end>", requestIdEq: "<request-id>" }
    05 ) {
    06 ts
    07 requestUri
    08 status
    09 upstreamStatus
    10 wafBlock
    11 wafMatch
    12 wafScore
    13 wafAttackFamily
    14 wafAttackAction
    15 }
    16}
  7. Stream WAF events to your SIEM, each with its score, the rules it matched, and the action WAF took.

    waf-to-siem.sh
    01curl -X POST 'https://api.azion.com/v4/workspace/stream/streams' \
    02 -H 'Content-Type: application/json' \
    03 -H 'Authorization: Token [TOKEN VALUE]' \
    04 -d {
    05 "name": "waf-to-siem",
    06 "active": true,
    07 "inputs": [
    08 { "type": "raw_logs", "attributes": { "data_source": "waf" } }
    09 ],
    10 "transform": [
    11 { "type": "filter_workloads", "attributes": { "workloads": [<workload-id>] } },
    12 { "type": "render_template", "attributes": { "template": 4 } }
    13 ],
    14 "outputs": [
    15 {
    16 "type": "kafka",
    17 "attributes": {
    18 "bootstrap_servers": "kafka1.example.com:9092,kafka2.example.com:9092",
    19 "kafka_topic": "azion.waf",
    20 "use_tls": true
    21 }
    22 }
    23 ]
    24 }
//Use cases

What can you protect with Azion WAF?

See where teams put Azion WAF to work, and how to set up each case in the docs.

Docs

Protect web applications from OWASP Top 10 and zero-day attacks

Block emerging attacks with rules that update as threats evolve, without waiting for an application patch.

Protect public APIs from abuse

Protect REST and GraphQL APIs from injection attacks, abusive traffic, and automated exploitation attempts.

Prepare regulated web applications for security audits

Block attacks on payment flows and sensitive data, with the WAF records an audit asks for.

Block account takeover on login and checkout flows

Filter attacks on login, signup, and checkout while Bot Manager stops credential stuffing and card testing.

GPA
Azion shielded us from sophisticated cyberattacks and empowered us to modernize our infrastructure, reduce costs, and deliver the best shopping experiences to millions of customers.
Allan MonteiroCISO & Head of Technology

Serverless AI-native primitives for autonomous workloads

Frequently asked questions

Protect your apps today

Turn on protection against attacks and bad bots now, without blocking real customers.

Bot Manager Lite Starter KitNew stack with Bot Manager Lite in action.
Deploy now
Bot Manager Lite and TOR Block Starter KitBlocks bad bots and Tor exit nodes.
Deploy now
Bot Manager Lite Integration KitAdds Bot Manager Lite to your firewall.
Deploy now
Upstash Rate LimitingRate limiting with Functions and Upstash.
Deploy now
Azion Starter KitBasic stack to explore Azion Web Platform.
Deploy now
AI Inference Starter KitAI app with no origin dependency.
Deploy now