Comparing Web application firewall (WAF) security features

RELATED CONTENT Threats and security advisories Preventing phishing attacks: Enterprise best practices The value of booting from a VHD in Windows 7 What to do with network penetration test results How to prevent memory dump attacks How to prevent phishing attacks with social engineering tests Cyberwarfare and the enterprise: Is the threat real? How to avoid botnet attacks How to ensure the validity of Microsoft Windows updates How to defend against rogue DHCP server malware Mac OS memory flaws pose challenges for enterprise endpoint protection Web Application Security CISOs take measured steps to reduce social media risks Google to pay for Chrome browser vulnerabilities Facebook, McAfee partner to fix social network security issues PDF attack code complicates security analysis, skirts detection Annual security reports offer some hope Firefox, Opera, Safari browsers top list of high risk software Active PDF attacks target Reader, Acrobat zero-day vulnerability Using unique device identification for bank website security Avoid common Web application firewall configuration errors Microsoft gives Internet Explorer a major security overhaul

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary Serious Organized Crime Agency  (SearchSecurityUK.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

As for critical features, it is obviously important for the WAF to inspect and handle Web page content such as HTML, Dynamic HTML (DHTML), and cascading style sheets (CSS), as well as the protocols that your application uses, such as HTTP and HTTPS.

Also, check how quickly the vendor adopted new protocols in the past. Review their development and support policy to determine if they will support custom protocols or protect a set range of application protocols. In addition, a WAF must be able to inspect Web services messages, typically SOAP and XML.

Ask the Web application firewall vendor about their processes for auto-updating and applying dynamic signatures. This kind of review will help you assess their help services and technical support.

Of course, ask about how much additional, specific features cost as well. For example, some applications may require FIPS hardware key store support. A WAF vendor may support this requirement but at a dramatically higher price.

As you follow through on the list of PCI requirements, take the time to understand the technical approaches and depth of treatment that each Web application firewall uses to provide coverage of one or more security areas. For example, can you whitelist data types and ranges and create rules combining both whitelists and blacklists? How strong is the WAF against attack on itself? For example, it should run on a hardened OS, probably with components running in a non-privileged and closed runtime environment. If the product's security isn't rock solid, you should probably end the discussion right there.

For more on Web application firewall selection and deployment
  Understanding your Web application firewall (WAF) product options
  Comparing Web application firewall (WAF) security features
  Web application firewall implementation: Software vs. hardware
  How to deploy a Web application firewall (WAF)
  Web application firewall (WAF) management