Phoenix

Local News
2010 Meetings

OWASP Phoenix is running our 2010 meetings at the following time and location.

Meetings will now be the first Tuesday of the month, every month, 6:30 PM - 7:30 PM, for 1 hour.

Afterwards, we'll head to a local watering hole for socializing and fun.

The meetings are being generously hosted by ExecuTrain and QuietMove, at Executrain's training facility.

The location is: Executrain 3600 E University Dr # A1400 Phoenix, AZ 85034

The entrance is on the West side of the building. Look for the suite number on the door.

FEBRUARY MEETING INFO - TUES FEB 2ND 2010 6:30 PM
OWASP Phoenix invites you to it's FEBRUARY meeting! NOTE the LAST MINUTE Change of Venue!

Tues FEB 2nd at 6:30 PM - 7:30 PM at Taste of Top's (CHANGE OF VENUE: WE WILL NOT BE MEETING AT ExecuTrain). The meetings are always free, unfortunately the drinks aren't.

This month's meeting:
 * Introduction, chapter business. web application security news update by Adam Muntner, Managing Partner, QuietMove Inc. and Phoenix OWASP Chapter Lead
 * Discussion: TBD

The location is: Taste of Tops 403 West University Drive, Tempe, AZ 85281 Top's Liquor is next door to the bar, which is where we'll be at.

2010 Meetings Calendar
This calendar will likely be updated on month to month basis. In absence of a speaker for a monthly meeting we will opt for a short discussion.


 * March 2, Meeting potentially cancelled due to timing with the RSA Security Conference in San Francisco


 * April 6, "Protecting Your Applications from Backdoors: How to Secure Your Business Critical Applications from Time Bombs, Backdoors & Data" Mr. Jill Naymie, Veracode


 * 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

Resources
Archived pages on Phoenix/Tools and Phoenix/ToolsProfile

This chapter is dedicated to bringing together local businesses, students, and web and security enthusiasts in order to discuss current events, trends, tools, and offensive/defensive techniques related to web application security. We currently hold meetings every month, typically with one or two speakers at each meeting.

What talks would you like to see?
Please Update


 * Certificates
 * Application Firewalls
 * PHP
 * Security ROI
 * Penetration Testing Methods
 * AJAX
 * Cryptography in Web Applications
 * Reversing ActiveX controls
 * Using Local Proxies
 * Browser Safety / Security
 * Web services security: XML/SOAP/WSDL

Previous Meetings
'''Application Security Tools - Web Application Proxy Editors and Scanners - Andre Gironda - Adam Muntner Risk Assessment Considerations for Web Applications (brief talk+discussion) - Erich Newell'''

 â and other web+network trust issues â Andre Gironda

In computing, the same origin policy is an important security measure for client-side scripting (mostly Javascript). It prevents a document or script loaded from one "origin" from getting or setting properties of a document from a different "origin". It was designed to protect browsers from executing code from external websites, which could be malicious.

XSS and CSRF vulnerabilities exploit trust shared between a user and a website by circumventing the same-domain policy. DNS Pinning didn't pan out exactly right, either. Can client-side scripting allow malicious code to get into your browser history and cache? Can it enumerate what plugins you have installed in your browser, or even programs you have installed to your computer? Can it access and modify files on your local hard drive or other connected filesystems? Can client-side scripts be used to access and control everything you access online? Can it be used to scan and attack your Intranet / local network? Does an attacker have to target you in order to pull off one of these attacks successfully? If I turn off Javascript or use NoScript, am I safe? What other trust relationships does the web application n-Tier model break?

Data@Risk â Protecting Web Applications Throughout the Development Lifecycle from Hackers - Brian Christian

Brian Christian, Co-founder and Application Security Engineer, S.P.I. Dynamics, Inc. discussed what Web application security is and why it is needed throughout the entire development lifecycle. We will discuss common vulnerabilities in the Web application layer and why they are so easily exploited. This session demonstrates how to defend against common attacks at the Web application layer with examples covering Web application hacking methods such as SQL Injection, Blind SQL Injection, Cross-Site Scripting (XSS), Parameter Manipulation, etc. We will also review how compliance and regulatory legislation such as PCI, GLBA, HIPAA, CASB 1386, and Sarbanes-Oxley, etc. specifically relates to and affects Web application security. Additionally, we will examine how security throughout the development lifecycle is essential to the security of Web application code and the protection of proprietary data.

Web Application 0-Day â Jon Rose

Learn about how to identify, exploit, and remediate some of the most common security vulnerabilities in web applications. Weâll be using real-world examples in a dynamic, fun, and open discussion using publicly available source code.

Discovering Web Application Vulnerabilities with Google CodeSearch

Building Application Security into the SDLC - Adam Muntner

Adam will share his experiences about how organizations can integrate application security into all phases of the Software Development Life Cycle, from the creation of functional specifications all the way through deployment, maintenance, and updates. He will explain how to "bake security in" rather than "ice it on."