As of July 13, 2020, Fastly's original WAF offering became a legacy product. It will continue to be supported for all existing users. As an alternative, Fastly Next-Gen WAF (powered by Signal Sciences) offers proactive monitoring of and protection against suspicious and anomalous web traffic directed at your applications and origin servers. It can be controlled via the web interface dashboard or application programming interface (API). Contact email@example.com or your Fastly account team to evaluate or move to the Fastly Next-Gen WAF option.
The Fastly WAF dashboard allows you to monitor the Fastly WAF deployed within your Fastly service. If you've been assigned the role of engineer or superuser, you can use the information in the Fastly WAF dashboard to determine whether or not the WAF is active, see how many requests the WAF is currently processing, and review recent configuration changes. The Fastly WAF dashboard consists of the WAF summary and WAF audit log pages.
Accessing the Fastly WAF dashboard
To access the Fastly WAF dashboard, follow the steps below:
Log in to the Fastly web interface. The Home page appears displaying a list of all services associated with your account.
Find your Fastly service in the list, and then click the WAF link. The WAF summary page appears.
About the WAF summary page
The WAF summary page displays the status of your WAF. The top of the page provides links to the WAF audit log page and Fastly control panel.
The WAF status section indicates whether the WAF is currently active. To be considered active, the WAF must not be disabled and must have at least one rule status set in either logging or blocking mode. The total number of active rules appears first and represents the combined total of OWASP rules set to active and strict match rules set to blocking or logging. The charts below the total number of active rules separates these out into the number of active and disabled OWASP rules, application-specific rules, and Fastly-created rules. Sample charts are shown below.
The Requests graph displays how many requests are served from cache and how many requests are processed by the WAF. Of the requests that are processed by the WAF, the WAF Process graph displays how many requests were blocked by the WAF, logged by the WAF and sent to the origin server, and were passed (not blocked or logged) and sent to the origin server.
You can exclude certain data from the graphs by clicking the hide link next to a data label. Clicking this link will hide that value in the graph's display.
The Fastly WAF only executes on traffic sent to the origin server.
About the WAF audit log page
The WAF audit log page displays all configuration changes made to your WAF. You can use this page to determine who made certain types of configuration changes to the WAF and when the changes were made. The line items indicate when rules were set to log or block, when they were updated, and whether they were disabled.
Some line items include changes for multiple rules. Click Show rule IDs to see all of the changes.
You can use the Fastly WAF rule statuses API endpoint to view the state of an individual rule.
Some entries contain information about the WAF's OWASP properties. To learn more about the OWASP properties, refer to the OWASP properties section.
You may see OWASP properties referenced on the WAF audit log page. The table below contains a list of all available properties and their descriptions. The properties shown here reflect changes made by altering the settings in the OWASP object.
|Allowed HTTP versions||HTTP versions that a client is allowed to use.|
|Allowed HTTP methods||HTTP methods that a client is allowed to use.|
|Allowed client content types||HTTP Content-Types that a client is allowed to use.|
|Maximum length for parameter names||Maximum length of any parameter names passed in the query string and request body.|
|Maximum length for parameter values||Maximum length of any parameter values passed in the query string and request body.|
|Combined file sizes||Total size of MIME bodies in the request.|
|Critical anomaly score||Configured critical anomaly score. Rules using the critical severity will increment scores using this value.|
|Validate UTF8 encoding||Validates the client request as UTF-8 prior to the execution of WAF rules.|
|Error anomaly score||Configured error anomaly score. Rules using the error severity will increment scores using this value.|
|High risk countries||Block clients from high risk countries based on their IP address.|
|HTTP violation threshold||Configured HTTP violation threshold. Action is taken when rules that trigger HTTP violations exceed the threshold.|
|Inbound anomaly threshold||Configured inbound anomaly threshold. Action is taken when the sum of the individual category scores exceed the threshold.|
|LFI threshold||Configured LFI threshold. Action is taken when rules that trigger Local File Inclusion (LFI) rules exceed the threshold.|
|Maximum file size (bytes)||Maximum size of any MIME body in the request.|
|Maximum argument count||Maximum number of parameters in the query string and request body.|
|Notice anomaly score||Configured notice anomaly score. Rules using the notice severity will increment scores using this value.|
|Paranoia level||The paranoia level setting can be set from 1 through 4 and determines the number of rules to include by default. Higher levels indicate higher levels of security but potentially a larger number of false positives.|
|PHP injection threshold||Configured PHP injection score threshold. Action is taken when rules that trigger PHP related violations exceed the threshold.|
|RCE threshold||Configured RCE injection score threshold. Action is taken when rules that trigger Remote Code Execution (RCE) violations exceed the threshold.|
|Restricted extensions||Control on restricted file extensions in the client request.|
|Restricted headers||Control on restricted HTTP headers in the client request.|
|RFI threshold||Configured RFI violation threshold. Action is taken when rules that trigger Remote File Inclusion (RFI) violations exceed the threshold.|
|Session fixation threshold||Configured Session Fixation violation threshold. Action is taken when rules that trigger Session Fixation violations exceed the threshold.|
|SQLi threshold||Configured SQLi threshold. Action is taken when rules that trigger SQL Injection (SQLi) violations exceed the threshold.|
|Total parameter length||Maximum length of all parameters passed in the query string and request body.|
|Warning anomaly score||Configured warning anomaly score. Rules using the warning severity will increment scores using this value.|
|XSS threshold||Configured XSS threshold. Action is taken when rules that trigger Cross-Site Scripting (XSS) violations exceed the threshold.|
About the WAF stats
The WAF stats graph appears on the Stats page. For the selected service, this graph shows three things: the blocked traffic that was stopped by the WAF based on rules, the logged traffic that triggered rules but was sent to the origin, and the passed traffic that didn't trigger rules and was sent to the origin.