11/04/09 Mention that this talk will be focused mostly on WAFs, ask if anyone is thoroughly disappointed
11/04/09
11/04/09
11/04/09
11/04/09 (Figures from 2009)
11/04/09
11/04/09
11/04/09
11/04/09 The smoking guy was the “boss” from the lovelycharts.com Notice that the intranet does not bypass the waf
11/04/09
11/04/09
11/04/09 Scope Creep!
11/04/09 WAFs take a LOT of time Too often I hear, if we have a WAF, why do we need to write secure code? One of the biggest surprises to us was how much time and effort is involved
11/04/09
11/04/09 Same goes for open source…
11/04/09 WAFs handle 4 out of 5 of these gracefully, RFI
11/04/09 AppScan/ Static analysis is difficult with a large number of small purpose apps.
11/04/09 This left us open when our device failed.
11/04/09
11/04/09
11/04/09
11/04/09
11/04/09 It’s no good if you can’t spend the time tuning after every alert Mention the “strict profile” versus normal profile Mention profiling reports!
11/04/09
11/04/09
11/04/09 SecureSphere Web Application Firewall Presentation May 21, 2007 Imperva Mentiond the hidden slide matrix
11/04/09
11/04/09
11/04/09
11/04/09
11/04/09
11/04/09
11/04/09 Outside scans may get blocked for other reasons.
11/04/09
11/04/09 Much more accurate for XSS protection. Correllation rules are sad, virtual patches are accurate
11/04/09
11/04/09
11/04/09 Inattentive? That just sounds weird
11/04/09 Note the single and double quote at the end of the name If a signature is detected, then the WAF doesn’t request
11/04/09
11/04/09
11/04/09
11/04/09 Connection resets instead of error pages for certain classes
11/04/09
11/04/09 Fixed DWH, Library problem, caught
11/04/09 Having DB on same host as web server forces us to install an agent Messed up parameters caused unknown param alertss: &variable
11/04/09 -1.02 is not considered “numeric”
11/04/09 Fortify will do static analysis on your code if it is open source
Securing Applications With Web Application Firewalls and Vulnerability Assessments - Presentation Transcript
Securing Campus Web Applications with Vulnerability Assessments (VA) and Web Application Firewalls (WAFs) Neil Matatall | November 5, 2009 University of California, Irvine OWASP Orange County Chapter Lead Educause Effective Practices WG Member
Glossary
WAF = Web Application Firewall
IDS = Intrusion Detection System
IPS = Intrusion Prevention System
AppSec = Application Security
SOX, PCI, HIPAA, FERPA = Compliance
OWASP = Open Web Application Security Project
WASC = Web Application Security Consortium
Agenda
Introduction
Web Application Firewalls
Implementing Web Application Firewalls
Vulnerability Assessments
Synergy
WAF Evasion Techniques
Wrap Up
Let’s Make It Clear
We have used open source WAFs as well as commercial WAFs
I am here to sell you on the idea of WAFs, but not to sell you a WAF
I will try to confuse you
Every situation is different
Key phrase: it depends!
About UCI
Founded in 1965
~27,631 Students
~14,228 employees
Rapidly expanding while our budget is rapidly shrinking
Recently started consolidating IT across the campus
The Security team was one of the first groups to work together across former business units
Security Is All About The Layers
No single solution that makes everything secure exists
When one layer fails, and it will, there should be a compensating strategy
This is commonly known as the “Defense in Depth” Strategy
Commonly Overheard Misconceptions of Application Security
“ Our site is secure because it uses SSL”
“ Our site is secure because we have a network firewall”
“ A hacker will never do that”
Agenda
Introduction
Web Application Firewalls
Implementing Web Application Firewalls
Vulnerability Assessments
Synergy
WAF Evasion Techniques
Wrap Up
Visual Representation of WAFs
What a WAF is:
From http://www.owasp.org :
An appliance, web server plugin, or filter that applies a set of rules to an HTTP conversation
Generally, these rules cover common attacks such as Cross-site Scripting (XSS) and SQL Injection
A WAF inspects the HTTP content at the application layer, beyond what a network firewall would typically inspect at the IP and transport layers
The OSI Stack The Application Set is handled by Web Application Firewalls The transport set is handle by traditional network firewalls
What a WAF is (Cont’d)
“ HTTP-aware IPS/IDS on steroids”
A way to analyze the requests and responses for suspicious activity
A way to increase visibility of web traffic 1
A debug tool 2
An incredibly powerful, complex, and difficult beast
1. We’ve Been Blind to Attacks on Our Web Sites
2. Ryan Barnett: Why Did Our Web Application Crash? Leveraging WAF Logging Data
What a WAF is not
A “traditional” firewall
Firewalls generally inspect IP addresses and ports, layers 3 and 4
WAFs inspect HTTP requests/responses at layer 7
A magical device that works on its own
An end-all solution to all application security problems
An excuse to write insecure code
XKCD – Missing the Point http://xkcd.com/538
Why You Need A WAF
82% of Web applications have vulnerabilities 1
75% of all Internet attacks target applications 2
PCI-DSS
6.6: Installing a web-application layer firewall in front of public facing web applications.
10: Track and monitor all access to credit card data
Software Vendors may not be willing (or even in business) to fix vulnerabilities
1 White Hat - statistic for initial examination; 2 Gartner Research;
The Most Widespread Vulnerabilities in Web Applications WASC - Web Application Security Statistics
Why WAFs Are Attractive in Higher ED
We typically have a very diverse pool of code
Tight resources make fixing the code a painful process
Many small, single-purpose applications make alternative technologies difficult to use
Why Did Our Web Application Crash? Leveraging WAF Logging Data
Scanner and WAF Data Sharing
Web Application Security Statistics
Methods to Bypass a Web Application Firewall
Web Application Firewall Products
Web Application Firewall Deployment Mode Considerations
Web Application Firewall Evaluation Criteria
Application Scanner Evaluation Criteria
Approved Scanning Vendors
xkcd : Security
Copyright Neil Matatall 2009. This work is the intellectual property of the author. Permission is granted for this material to be shared for non-commercial, educational purposes, provided that this copyright statement appears on the reproduced materials and notice is given that the copying is by permission of the author. To disseminate otherwise or to republish requires written permission from the author.
0 comments
Post a comment