Difference between revisions of "Chicago"
(→Next Chapter Meeting: February 2, 2010 *New Location*)
|Line 1:||Line 1:|
== Next Chapter Meeting:
== Next Chapter Meeting: , 2010 *New Location* ==
The next quarterly Chicago OWASP Chapter meeting will be
The next quarterly Chicago OWASP Chapter meeting will be 2010 at 6pm. Please RSVP to .@.by so we can enter your name into the 's security system.
Revision as of 11:57, 1 June 2010
Next Chapter Meeting: June 17th, 2010 *New Location*
The next quarterly Chicago OWASP Chapter meeting will be June 17th 2010 at a location yet to be determined at 6pm. Please RSVP to email@example.com by EOB on the 16th so we can enter your name into the venue's security system.
Have a subject you can talk about in 10-20 minutes? Have a subject you'd like to see talked about in the same span? OWASP Chicago chapter is hosting an evening of lightning talks on the subjects you want to hear.
We're hoping to meet Thursday, June 17th at a venue still to be determined.
Paul Petefish will give a short presentation on the new OWASP Top 10 list. Thomas Ptacek will give a short presentation on an interesting subject. <insert your talk or subject here>
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
Protecting Your Applications from Backdoors: How to Secure Your Business Critical Applications from Time Bombs, Backdoors & Data
With the increasing practice of outsourcing and using 3rd party libraries, it is nearly impossible for an enterprise to identify the pedigree and security of the software running its business critical applications. As a result backdoors and malicious code are increasingly becoming the prevalent attack vector used by hackers. Whether you manage internal development activities, work with third party developers or are developing a COTS application for enterprise, your mandate is clear- safeguard your code and make applications security a priority for internal and external development teams. In this session we will cover;
- Prevalence of backdoors and malicious code in third party attacks
- Definitions and classifications of backdoors and their impact on your applications
- Methods to identify, track and remediate these vulnerabilities
Erik Peterson from Veracode will be presenting.
Open Software Assurance Maturity Model (OpenSAMM)
The Open Software Assurance Maturity Model (SAMM) (http://www.opensamm.org/) is a flexible and prescriptive framework for building security into a software development organization. Covering more than typical SDLC-based models for security, SAMM enables organizations to self-assess their security assurance program and then use recommended roadmaps to improve in a way that's aligned to the specific risks facing the organization. Beyond that, SAMM enables creation of scorecards for an organization's effectiveness at secure software development throughout the typical governance, development, and deployment business functions. Scorecards also enable management within an organization to demonstrate quantitative improvements through iterations of building a security assurance program. This workshop will introduce the SAMM framework and walk through useful activities such as assessing an assurance program, mapping an existing organization to a recommended roadmap, and iteratively building an assurance program. Time allowing, additional case studies will also be discussed. OpenSAMM is an open a free project and has recently been donated to the Open Web Application Security Project (OWASP) Foundation. For more information on OpenSAMM, visit http://www.opensamm.org/.
Pravir Chandra is Director of Strategic Services at Fortify Software and works with clients on software security assurance programs. Pravir is recognized for his expertise in software security, code analysis, and his ability to strategically apply technical knowledge. Prior to Fortify, he was a Principal Consultant affiliated with Cigital and led large software security programs at Fortune 500 companies. Pravir Co-Founded Secure Software, Inc. and was Chief Security Architect prior to its acquisition by Fortify. He recently created and led the Open Software Assurance Maturity Model (OpenSAMM) project with the OWASP Foundation, leads the OWASP CLASP project, and also serves as member of the OWASP Global Projects Committee. Pravir is author of the book Network Security with OpenSSL.
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.