Next Chapter Meeting: January
Please stay tuned for an announcement of the January meeting. Anyone with questions about this meeting please contact Vitaly McLain <email@example.com>
Submit talks or ideas for talks to firstname.lastname@example.org and we'll get things rolling.
Also, follow (and/or DM us) on twitter @owaspchicago
We'll firm up the evening's agenda as we get submissions.
Anyone in our area interested in information security is welcome to attend. Our meetings are informal and encourage open discussion of all aspects of application security. We invite attendees to give short presentations about specific topics.
Make sure you sign up for the mailing list to receive meeting announcements.
We have a mailing list at: https://lists.owasp.org/mailman/listinfo/owasp-chicago
Bad Cocktail: Spear Phishing - Mike Zusman - Presentation slides here
Making Money on the Web The Blackhat Way - Jeremiah Grossman - Presentation slides here
Extreme Client-Side Exploitation - Nate McFeters - Presentation slides here
Automated Thrash Testing - Andre Gironda - Presentation slides here
Defeating Information Leak Prevention - Eric Monti - Presentation slides here
Webapps In Name Only Thomas Ptacek, Matasano Security
Where modern network architecture meets legacy application design, we get "The Port 80 Problem": vendors wrapping every conceivable network protocol in a series of POSTs and calling them "safe". These "Webapps In Name Only" are a nightmare for application security specialists.
In this talk, we'll discuss, with case studies, how tools from protocol reverse engineering can be brought to bear on web application security, covering the following areas:
- Locating and Decompiling Java and .NET Code - Structure and Interpretation of Binary Protocols in HTTP - Protocol Debugging Tools - Web App Crypto Tricks
Token-less strong authentication for web applications: A Security Review Cory Scott, ABN AMRO
A short presentation on the threat models and attack vectors for token-less schemes used to reduce the risk of password-only authentication, but yet do not implement "true" two-factor technologies for logistical costs or user acceptance reasons. We'll go over how device fingerprinting and IP geo-location work and discuss the pros and cons of the solutions.
Chicago OWASP Chapter Leaders