This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "Chicago"

From OWASP
Jump to: navigation, search
Line 1: Line 1:
== Welcome to the OWASP Chicago Local Chapter ==
+
==== Local News ====
  
 
<paypal>Chicago</paypal>
 
<paypal>Chicago</paypal>
Line 11: Line 11:
 
The Chicago chapter is sponsored by Bank of America[http://www.bankofamerica.com/]
 
The Chicago chapter is sponsored by Bank of America[http://www.bankofamerica.com/]
  
== Next Meeting ==
+
==== Chapter Meetings ====
  
 
The next quarterly Chicago OWASP Chapter meeting will be November 13th at the Bank of America Plaza, 540 W Madison Street at 6pm. Please RSVP to [email protected] by November 12th so we can enter your name into the building's security system.
 
The next quarterly Chicago OWASP Chapter meeting will be November 13th at the Bank of America Plaza, 540 W Madison Street at 6pm. Please RSVP to [email protected] by November 12th so we can enter your name into the building's security system.
Line 75: Line 75:
 
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.  
 
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 ====
 +
[mailto:[email protected] Cory Scott]
 +
 +
[mailto:[email protected] Jason Witty]
 +
__NOTOC__
 +
<headertabs/>
 
[[Category:OWASP Chapter]]
 
[[Category:OWASP Chapter]]
 
[[Category:Illinois]]
 
[[Category:Illinois]]

Revision as of 19:12, 11 March 2009

Local News

<paypal>Chicago</paypal>

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.

We have a mailing list at: https://lists.owasp.org/mailman/listinfo/owasp-chicago

If you have any questions about the Chicago chapter, please send an email to our chapter leaders Cory Scott or Jason Witty.

The Chicago chapter is sponsored by Bank of America[1]

Chapter Meetings

The next quarterly Chicago OWASP Chapter meeting will be November 13th at the Bank of America Plaza, 540 W Madison Street at 6pm. Please RSVP to [email protected] by November 12th so we can enter your name into the building's security system.


Agenda

6:00 Refreshments and Networking / Overview of recent OWASP projects - Cory Scott

6:15 Concurrency Attacks in Web Applications - Scott Stender, iSEC Partners

7:15 The Seven Deadly Features of Web Applications - Matasano Security

Presentation abstracts

Concurrency Attacks in Web Applications

ABSTRACT

Modern web application frameworks are designed for developer productivity and performance. They are highly scalable, object-oriented, and can be used to create a usable web site in a matter of minutes. However, these attributes often encourage programming practices that make managing state difficult for a typical programmer.

Web application developers must carefully manage access to all resources that can shared by threads. Global variables, session variables, back-end systems, and application-specific data stores are common examples of such resources.

Concurrency flaws result when access to shared resources is not managed properly - something that is easy to do when the development environment purposefully encapsulates and abstracts the resources that need to be managed! When manipulating those resources carries a security impact, the attackers take notice.

Each prevalent class of security flaw shares a common attribute: mistakes happen when doing the right thing is difficult. It is our opinion that concurrency flaws, especially in the context of web applications, share this attribute. This presentation will provide insight into the ease with which concurrency flaws can be introduced into systems, offer guidance on evaluating the security impact of such flaws, and discuss strategies for eliminating such flaws that will be helpful to developers and testers alike.

SPEAKER BIO

Scott Stender Principal Partner, iSEC Partners

Scott Stender is a founding partner of iSEC Partners, a strategic digital security organization. Scott brings with him several years of experience in large-scale software development and security consulting, having worked at companies such as @stake and Microsoft. Scott is a noted researcher who focuses on secure software engineering and security analysis of core technologies. He holds a BS in Computer Engineering from the University of Notre Dame.

Presentation Archives

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


[2]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

[3]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

Cory Scott

Jason Witty