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"
(→Local News) |
|||
Line 9: | Line 9: | ||
We have a mailing list at: https://lists.owasp.org/mailman/listinfo/owasp-chicago | We have a mailing list at: https://lists.owasp.org/mailman/listinfo/owasp-chicago | ||
==General Information== | ==General Information== | ||
− | |||
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. | 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. | ||
Line 18: | Line 17: | ||
<paypal>Chicago</paypal> | <paypal>Chicago</paypal> | ||
− | + | == Chapter Meetings == | |
− | The next quarterly Chicago OWASP Chapter meeting will be | + | The next quarterly Chicago OWASP Chapter meeting will be February 2nd, 2010 at a location to be determined at 6pm. Please RSVP to [email protected] by February 1st so we can enter your name into the building's security system. |
− | + | ==Agenda== | |
6:00 Refreshments and Welcome | 6:00 Refreshments and Welcome | ||
Line 31: | Line 30: | ||
7:15 Assessing Thick Web Applications - Timur Duehr | 7:15 Assessing Thick Web Applications - Timur Duehr | ||
− | + | ==Presentation abstracts== | |
''AppSensor: Real Time Defenses against Application Worms and Malicious Attackers'' | ''AppSensor: Real Time Defenses against Application Worms and Malicious Attackers'' |
Revision as of 19:55, 10 January 2010
OWASP Chicago
Welcome to the Chicago chapter homepage. The chapter leaders are Cory Scott and Jason Witty
Participation
OWASP Foundation (Overview Slides) is a professional association of global members and is open to anyone interested in learning more about software security. Local chapters are run independently and guided by the Chapter_Leader_Handbook. As a 501(c)(3) non-profit professional association your support and sponsorship of any meeting venue and/or refreshments is tax-deductible. Financial contributions should only be made online using the authorized online chapter donation button. To be a SPEAKER at ANY OWASP Chapter in the world simply review the speaker agreement and then contact the local chapter leader with details of what OWASP PROJECT, independent research or related software security topic you would like to present on.
Sponsorship/Membership
to this chapter or become a local chapter supporter. Or consider the value of Individual, Corporate, or Academic Supporter membership. Ready to become a member?
Next Meeting: February 2, 2010
Mark your calendars - agenda to follow.
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
General Information
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 Cory Scott or Jason Witty.
Chicago chapter meetings are hosted by Bank of America[1]
<paypal>Chicago</paypal>
Chapter Meetings
The next quarterly Chicago OWASP Chapter meeting will be February 2nd, 2010 at a location to be determined at 6pm. Please RSVP to [email protected] by February 1st so we can enter your name into the building's security system.
Agenda
6:00 Refreshments and Welcome
6:15 AppSensor: Real Time Defenses against Application Worms and Malicious Attackers - Michael Coates
7:15 Assessing Thick Web Applications - Timur Duehr
Presentation abstracts
AppSensor: Real Time Defenses against Application Worms and Malicious Attackers
ABSTRACT
The OWASP AppSensor project was created to address the lack of defensive systems within applications. Regardless if an application is secure or insecure, malicious actions should be recorded, analyzed and responded to by the system. It is unacceptable to allow an attacker unrestricted attack attempts against the application. Eventually a known or unknown vulnerability will be discovered by the attacker and exploited. AppSensor monitors attack activity and takes defensive actions such as throttling or disabling the malicious account. Behavior analysis techniques are also employed to identify application worms. Defensive techniques are described which provide real-time containment of the application worm while maintaining overall system availability.
SPEAKER BIO
Michael Coates is a Senior Application Security Engineer for Aspect Security and has performed numerous penetration assessments, security code reviews, and security training sessions for leading corporations worldwide. Michael is the creator and leader of the AppSensor project and is completing a Masters Degree in Computer Security from DePaul University. In past years, Michael assessed the security of GSM and WiMAX telecommunication networks, application and network systems for financial institutions and performed social engineering testing.
Assessing Thick Web Applications
ABSTRACT
Recently, web applications have been pushing more application to the browser and in many cases entirely out of the browser. Technologies for pushing richer content to the client, such as ActiveX, Flash, Google's NaCl and browser extensions, can frustrate efforts to assess an application. Occasionally, these technologies remove the browser entirely to create a semi thick client that uses standard web application methodologies and transport methods.
While a few framework specific tools have begun to mature, they are geared toward debugging an application for quality assurance purposes rather than security assessment. A solution for many of these technologies is simply repurposing and reinventing some of the old application assessment tool chain: the debugger. A new generation of scriptable debuggers is showing up. Using these tools allows increased automation and visibility into the newest thick web application frameworks.
SPEAKER BIO
Timur Duehr is a Security Consultant at Matasano Security and a graduate student in Mathematical Computer Science at the University of Illinois at Chicago. Timur is one of the lead developers of Ragweed, a scriptable debugger written in Ruby for win32, OSX and linux applications.
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.