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

Chicago

From OWASP
Revision as of 08:03, 18 May 2007 by Cscott (talk | contribs) (Next Meeting)

Jump to: navigation, search

Welcome to the OWASP Chicago Local Chapter

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.

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

The Chicago chapter is sponsored by LaSalle Bank[1]

Next Meeting

The next Quarterly Chicago OWASP Chapter meeting will be held on June 20th, 2007 at 6PM CST.

We hope to see you at the ABN AMRO Plaza at 540 W. Madison, Downtown Chicago, 23rd floor. Please RSVP to jason{AT}wittys.com by Monday 06/18/2007 if you plan to attend. Your name will need to be entered into the building's security system in order to gain access to the meeting.

Agenda:

6:00 Refreshments and Networking
6:30 Agile and Secure: Can We Be Both?, Dan Cornell, Principal, Denim Group
7:15 Roundtable (topic to be determined) and Questions

Presentation Abstract

Software development organizations find themselves pulled in two directions. Agile software development methodologies such as extreme Programming and Scrum have allowed organizations to be more responsive to business concerns by involving the customer, increasing the pace of stable releases and decreasing the time required before new features are deployed. In addition, a more aggressive regulatory environment as well as an increased focus on security requires that organizations more reliably produce secure software applications. Traditional approaches to security and compliance are very top-down and document-centric, but these approaches often run counter to the spirit of agile software development methodologies.

This presentation examines the goals of both agility and security and discusses strategies for making the two compatible – or at least for minimizing the conflict between them. First, the presentation outlines the fundamentals of secure software development to provide a baseline that any methodology – traditional or agile – must follow. The practices of agile development are then examined from the viewpoint of providing security assurance. Potential modifications to those practices are discussed that provide an approach to creating the artifacts required for compliance and security assurance with a minimum of impact on the typically documentation-light agile development practices. Finally, the unavoidable conflicts between security and agility are discussed and recommendations are provided so that organizations can make the tough decisions appropriate to their environment in order to enforce the requisite amount of security while still remaining responsive to business concerns.

Presentation Archives

[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.