waf-front-door-monitor.md

title	description	author	ms.service	ms.custom	ms.topic	services	ms.date	ms.author	zone_pivot_groups
Azure Web Application Firewall monitoring and logging	Learn about Azure Web Application Firewall in Azure Front Door monitoring and logging.	vhorne	azure-web-application-firewall	devx-track-js	how-to	web-application-firewall	05/23/2024	victorh	front-door-tiers

Azure Web Application Firewall monitoring and logging

Azure Web Application Firewall on Azure Front Door provides extensive logging and telemetry to help you understand how your web application firewall (WAF) is performing and the actions it takes.

The Azure Front Door WAF log is integrated with Azure Monitor. Azure Monitor enables you to track diagnostic information, including WAF alerts and logs. You can configure WAF monitoring within the Azure Front Door resource in the Azure portal under the Diagnostics tab, through infrastructure as code approaches, or by using Azure Monitor directly.

Metrics

Azure Front Door automatically records metrics to help you understand the behavior of your WAF.

To access your WAF's metrics:

1. Sign in to the Azure portal and go to your Azure Front Door profile.
2. On the leftmost pane under Monitoring, select the Metrics tab.
3. Add the Web Application Firewall Request Count metric to track the number of requests that match WAF rules.

You can create custom filters based on action types and rule names. Metrics include requests with all actions except Log.

:::image type="content" source="../media/waf-frontdoor-monitor/waf-frontdoor-metrics.png" alt-text="Screenshot that shows the metrics for an Azure Front Door WAF.":::

JavaScript challenge (preview) metrics

To access your JavaScript challenge WAF metrics:

• Add the Web Application Firewall JS Challenge Request Count metric to track the number of requests that match JavaScript challenge WAF rules.

The following filters are provided as part of this metric:

• PolicyName: This is the WAF policy name
• Rule: This can be any custom rule or bot rule
• Action: There are four possible values for JS Challenge action
  • Issued: JS Challenge is invoked the first time
  • Passed: JS Challenge computation succeeded and an answer was received
  • Valid: JS Challenge validity cookie was present
  • Blocked: JS Challenge computation failed

:::image type="content" source="../media/waf-frontdoor-monitor/javascript-challenge-metrics.png" alt-text="Screenshot showing the JavaScript challenge metrics.":::

Logs and diagnostics

The Azure Front Door WAF provides detailed reporting on each request and each threat that it detects. Logging is integrated with Azure's diagnostics logs and alerts by using Azure Monitor logs.

Logs aren't enabled by default. You must explicitly enable logs. You can configure logs in the Azure portal by using the Diagnostic settings tab.

:::image type="content" source="../media/waf-frontdoor-monitor/waf-diagnostic-setting.png" alt-text="Screenshot that shows how to enable the WAF logs." lightbox="../media/waf-frontdoor-monitor/waf-diagnostic-setting.png":::

If logging is enabled and a WAF rule is triggered, any matching patterns are logged in plain text to help you analyze and debug the WAF policy behavior. You can use exclusions to fine-tune rules and exclude any data that you want to be excluded from the logs. For more information, see Web application firewall exclusion lists in Azure Front Door.

You can enable three types of Azure Front Door logs:

• WAF logs
• Access logs
• Health probe logs

Activity logs are enabled by default and provide visibility into the operations performed on your Azure resources, such as configuration changes to your Azure Front Door profile.

WAF logs

::: zone pivot="front-door-standard-premium"

The log FrontDoorWebApplicationFirewallLog includes requests that match a WAF rule.

::: zone-end

::: zone pivot="front-door-classic"

The log FrontdoorWebApplicationFirewallLog includes any request that matches a WAF rule.

::: zone-end

The following table shows the values logged for each request.

Property	Description
Action	Action taken on the request. Logs include requests with all actions. Actions are: Allow and allow: The request was allowed to continue processing. Block and block: The request matched a WAF rule configured to block the request. Alternatively, the anomaly scoring threshold was reached and the request was blocked. Log and log: The request matched a WAF rule configured to use the Log action. AnomalyScoring and logandscore: The request matched a WAF rule. The rule contributes to the anomaly score. The request might or might not be blocked depending on other rules that run on the same request. JS Challenge and JSChallengeIssued: Issued due to missing/invalid challenge clearance, missing answer. The log is created when a client requests access to a web application for the first time and has not been challenged previously. This client receives the JS challenge page and proceeds to compute the JS challenge. Upon successful computation, the client is granted the validity cookie. JS Challenge and JSChallengePass: Passed due to valid challenge answer. This log is created when a client solves the JS challenge and resubmits the request with the correct answer. In this case, Azure WAF validates the cookie and proceeds to process the remaining rules without generating another JS challenge. JS Challenge and JSChallengeValid: Logged/passthrough due to valid challenge. This log is created when a client has previously solved a challenge. In this case, Azure WAF logs the request and proceeds to process the remaining rules. JS Challenge and JSChallengeBlock: Blocked This log is created when a JS challenge computation fails.
ClientIP	The IP address of the client that made the request. If there was an X-Forwarded-For header in the request, the client IP address is taken from that header field instead.
ClientPort	The IP port of the client that made the request.
Details	More details on the request, including any threats that were detected. matchVariableName: HTTP parameter name of the request matched, for example, header names (up to 100 characters maximum). matchVariableValue: Values that triggered the match (up to 100 characters maximum).
Host	The Host header of the request.
Policy	The name of the WAF policy that processed the request.
PolicyMode	Operations mode of the WAF policy. Possible values are Prevention and Detection.
RequestUri	Full URI of the request.
RuleName	The name of the WAF rule that the request matched.
SocketIP	The source IP address seen by WAF. This IP address is based on the TCP session and doesn't consider any request headers.
TrackingReference	The unique reference string that identifies a request served by Azure Front Door. This value is sent to the client in the X-Azure-Ref response header. Use this field when you search for a specific request in the log.

The following example query shows the requests that the Azure Front Door WAF blocked:

::: zone pivot="front-door-standard-premium"

AzureDiagnostics 
| where ResourceProvider == "MICROSOFT.CDN" and Category == "FrontDoorWebApplicationFirewallLog" 
| where action_s == "Block" 

::: zone-end

::: zone pivot="front-door-classic"

AzureDiagnostics
| where ResourceType == "FRONTDOORS" and Category == "FrontdoorWebApplicationFirewallLog"
| where action_s == "Block"

::: zone-end

The following snippet shows an example log entry, including the reason that the request was blocked:

::: zone pivot="front-door-standard-premium"

{
  "time": "2020-06-09T22:32:17.8376810Z",
  "category": "FrontdoorWebApplicationFirewallLog",
  "operationName": "Microsoft.Cdn/Profiles/Write",
  "properties": {
    "clientIP": "xxx.xxx.xxx.xxx",
    "clientPort": "52097",
    "socketIP": "xxx.xxx.xxx.xxx",
    "requestUri": "https://wafdemofrontdoorwebapp.azurefd.net:443/?q=%27%20or%201=1",
    "ruleName": "Microsoft_DefaultRuleSet-1.1-SQLI-942100",
    "policy": "WafDemoCustomPolicy",
    "action": "Block",
    "host": "wafdemofrontdoorwebapp.azurefd.net",
    "trackingReference": "08Q3gXgAAAAAe0s71BET/QYwmqtpHO7uAU0pDRURHRTA1MDgANjMxNTAwZDAtOTRiNS00YzIwLTljY2YtNjFhNzMyOWQyYTgy",
    "policyMode": "prevention",
    "details": {
      "matches": [
        {
          "matchVariableName": "QueryParamValue:q",
          "matchVariableValue": "' or 1=1"
        }
      ]
    }
  }
}

::: zone-end

::: zone pivot="front-door-classic"

{
  "time": "2020-06-09T22:32:17.8376810Z",
  "category": "FrontdoorWebApplicationFirewallLog",
  "operationName": "Microsoft.Network/FrontDoorWebApplicationFirewallLog/Write",
  "properties": {
    "clientIP": "xxx.xxx.xxx.xxx",
    "clientPort": "52097",
    "socketIP": "xxx.xxx.xxx.xxx",
    "requestUri": "https://wafdemofrontdoorwebapp.azurefd.net:443/?q=%27%20or%201=1",
    "ruleName": "Microsoft_DefaultRuleSet-1.1-SQLI-942100",
    "policy": "WafDemoCustomPolicy",
    "action": "Block",
    "host": "wafdemofrontdoorwebapp.azurefd.net",
    "trackingReference": "08Q3gXgAAAAAe0s71BET/QYwmqtpHO7uAU0pDRURHRTA1MDgANjMxNTAwZDAtOTRiNS00YzIwLTljY2YtNjFhNzMyOWQyYTgy",
    "policyMode": "prevention",
    "details": {
      "matches": [
        {
          "matchVariableName": "QueryParamValue:q",
          "matchVariableValue": "' or 1=1"
        }
      ]
    }
  }
}

::: zone-end

For more information about the other Azure Front Door logs, see Monitor metrics and logs in Azure Front Door.

Next steps

Learn more about Azure Front Door.