Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

9/22/2009
04:11 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

New Free Web Application Firewall 'Lives' In The App

Open-source project aims to put WAF control into application developers' hands

A researcher plans to release a free, software-based Web application firewall (WAF) that resides in the Web application.

The open-source ESAPI WAF is a departure from commercial, network-based firewalls, as well as ModSecurity's free WAF, says Arshan Dabirsiaghi, developer of the ESAPI WAF and director of research for Aspect Security. Dabirsiaghi will roll out the WAF at the OWASP Conference in Washington, D.C., in November.

"WAFs today are deployed as appliances meant to protect a suite of applications. They're kind of part of your network and not part of your application," Dabirsiaghi says. "This is really an application-layer WAF rather than a network or appliance-layer WAF...it lives inside your application so you have a lot more control as an application owner [who's] enforcing rules."

The ESAPI WAF isn't the first open-source (or free) WAF: ModSecurity, which is also a software-based WAF, was one of the first freebies. The ModSecurity WAF, which is an Apache module, runs outside the application on the server.

Dabirsiaghi says the Java-based ESAPI WAF is all about making it easier and cheaper to deploy a WAF, which can cost up to $200,000 to deploy in a commercial product, he says. "The whole point of a WAF is a short- to medium-term patching solution," he says. "Long-term, you want secure code. We want to give you a bridge between that gap when a vulnerability is exploited."

This puts the WAF in the hands of the application team rather than the network or security team. "I think it's better to decentralize that and have everyone maintain their own WAF," Dabirsiaghi says. "Application owners are hopefully discovering their own vulnerabilities, so the time to protection should be much shorter [for patching them]."

There are advantages and trade-offs with both the network and application-based WAF approaches, however. "From an operational perspective, a network device can be deployed without changing a standard system configuration. On the other hand, you have another physical device to manage -- and possibly fail, unlike software on the Web server," says Jeremiah Grossman, CTO of WhiteHat Security. "Also, network devices have to terminate SSL if the site uses SSL, while software WAFs do not."

Dabirsiaghi maintains that the application-resident WAF makes it easier to fix and stop nagging Web application security problems, such as business logic flaws. "If you have a WAF appliance that sits in front of a few different applications, there's a distance between you and the apps," Dabirsiaghi says. "Because the ESAPI WAF lives inside the app, it's easier to stop those types of flaws."

Among some of the features in the new WAF are egress/outbound filtering to help stop information-leakages vulnerabilities and cross-site scripting, he says.

Dabirsiaghi says the WAF simplifies things, such as adding an Internet Explorer 8 header for preventing clickjacking. "With a WAF in place, you open up a text file, add one line, and you're done. It's all configuration-driven versus code driven," he says.

But the ESAPI WAF doesn't detect new vulnerabilities. "This is not about preventing unknown vulnerabilities," he says.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
Active Directory Needs an Update: Here's Why
Raz Rafaeli, CEO and Co-Founder at Secret Double Octopus,  1/16/2020
New Attack Campaigns Suggest Emotet Threat Is Far From Over
Jai Vijayan, Contributing Writer,  1/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-5216
PUBLISHED: 2020-01-23
In Secure Headers (RubyGem secure_headers), a directive injection vulnerability is present in versions before 3.9.0, 5.2.0, and 6.3.0. If user-supplied input was passed into append/override_content_security_policy_directives, a newline could be injected leading to limited header injection. Upon seei...
CVE-2020-5217
PUBLISHED: 2020-01-23
In Secure Headers (RubyGem secure_headers), a directive injection vulnerability is present in versions before 3.8.0, 5.1.0, and 6.2.0. If user-supplied input was passed into append/override_content_security_policy_directives, a semicolon could be injected leading to directive injection. This could b...
CVE-2020-5223
PUBLISHED: 2020-01-23
In PrivateBin versions 1.2.0 before 1.2.2, and 1.3.0 before 1.3.2, a persistent XSS attack is possible. Under certain conditions, a user provided attachment file name can inject HTML leading to a persistent Cross-site scripting (XSS) vulnerability. The vulnerability has been fixed in PrivateBin v1.3...
CVE-2019-20399
PUBLISHED: 2020-01-23
A timing vulnerability in the Scalar::check_overflow function in Parity libsecp256k1-rs before 0.3.1 potentially allows an attacker to leak information via a side-channel attack.
CVE-2020-7915
PUBLISHED: 2020-01-22
An issue was discovered on Eaton 5P 850 devices. The Ubicacion SAI field allows XSS attacks by an administrator.