StackPath’s cloud-based next-gen Web Application Firewall (WAF) provides your websites, web applications and APIs with the protection they need against known vulnerabilities and common exploits by applying sets of rules (policies) and behavioral analysis to incoming requests.
The StackPath WAF is designed to work out-of-the-box, as it includes pre-defined sets of protection policies, however, it also allows you to create customized sets of rules designed to filter traffic as desired. You can further analyze this traffic through our WAF’s built-in reporting system, which you can use to determine how to manage your policies and rules as needed.
StackPath’s WAF is composed of two parts:
|WAF Edge Nodes||Behavioral Components|
|WAF edge nodes help to validate traffic by applying various rule sets to incoming requests. After inspection is complete, these nodes are responsible for either blocking or allowing these requests, based on the analysis performed in the Behavioral Components portion. This feature is typical of a standard first-gen WAF.||The behavioral components of our WAF analyze incoming requests and determine the action the WAF edge nodes should perform against them. The addition of this deep analysis component is what separates a first-gen WAF from a next-gen.|
As you navigate through this Help Center, you will discover that StackPath’s WAF offers key features such as:
95% of questions can be answered using the search tool. This is the quickest way to get a response.