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 "Phoenix"

From OWASP
Jump to: navigation, search
(Local News)
(First Phoenix OWASP meeting is scheduled for Thursday, Nov 9th starting at 6:30PM.)
Line 23: Line 23:
 
* Using Local Proxies<br/>
 
* Using Local Proxies<br/>
  
== First Phoenix OWASP meeting is scheduled for Thursday, Nov 9th starting at 6:30PM.  ==
+
== Next Phoenix OWASP meeting is scheduled for Thursday, Jan 11th starting at 6:30PM.  ==
 
 
  
 
====Where====
 
====Where====
Line 32: Line 31:
 
Tempe, Arizona<br />
 
Tempe, Arizona<br />
 
85283-1056<br />
 
85283-1056<br />
 
+
<br />
 +
Entrance back of building
 
====When====
 
====When====
  
6:30PM, Thursday, Nov 9th
+
6:30PM, Thursday, Jan 11th
  
 
====Agenda====
 
====Agenda====
Line 41: Line 41:
 
''' 6:30 to 6:45 News & Introductions'''
 
''' 6:30 to 6:45 News & Introductions'''
  
''' 6:45 to 7:15 (30 minutes): Web Application 0Day – Jon Rose'''
+
''' 6:45 to 7:45 (1 hour): Taking a Hybrid Approach to Ensuring Your Web Application Code is Secure - Brian Christian, Co-founder and Application Security Engineer, S.P.I. Dynamics, Inc.'''
  
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.
+
As Web application vulnerabilities skyrocketed over the past few years, developers are beginning to take security very seriously. A new class of products has emerged that enable developers to test the security of their Web applications during implementation called source code analyzers. But source code analysis tools prove to be only a partial solution because they are only able to infer, or guess, what the actual system behavior will be, and can only determine what security vulnerabilities might be possible in the application. To increase the fidelity of security testing results, developers should look to security testing products that feature a combination of analysis techniques of source code analysis and more practical approach called black box testing, also known as dynamic analysis.  
  
'''7:15 to 7:30: Break'''
+
This session discusses the difference between source code and black box testing and how the combination, or hybrid analysis, produces the accurate and reliable security information developers need to assess the security of their code.
  
''' 7:30 to 8:00 (30 minutes): 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."
+
'''7:45 to 8:00: Wrap up'''
  
''' 8:00 to 8:15: Wrap up'''
+
''' 8:00: Social'''
  
  
 
Im looking forward to seeing everyone there!
 
Im looking forward to seeing everyone there!
 +
 +
== Previous Meetings ==
 +
Web Application 0-Day – Jon Rose<br/>
 +
 +
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.<br/><br/><br/>
 +
 +
Building Application Security into the SDLC - Adam Muntner<br/>
 +
 +
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."

Revision as of 08:00, 10 November 2006

OWASP Phoenix

Welcome to the Phoenix chapter homepage. The chapter leader is Jon Rose


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

Btn donate SM.gif 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? Join Now BlueIcon.JPG


Local News

New Phoenix chapter open!

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.

What talks would you like to see?

Please Update


  • Certificates
  • Application Firewalls
  • PHP Magic Quotes
  • Security ROI
  • Penetration Testing Methods
  • AJAX
  • Cryptography in Web Applications
  • Reversing ActiveX controls
  • Using Local Proxies

Next Phoenix OWASP meeting is scheduled for Thursday, Jan 11th starting at 6:30PM.

Where

UAT - University of Advancing Technology
Auditorium
2625 West Baseline Road
Tempe, Arizona
85283-1056

Entrance back of building

When

6:30PM, Thursday, Jan 11th

Agenda

6:30 to 6:45 News & Introductions

6:45 to 7:45 (1 hour): Taking a Hybrid Approach to Ensuring Your Web Application Code is Secure - Brian Christian, Co-founder and Application Security Engineer, S.P.I. Dynamics, Inc.

As Web application vulnerabilities skyrocketed over the past few years, developers are beginning to take security very seriously. A new class of products has emerged that enable developers to test the security of their Web applications during implementation called source code analyzers. But source code analysis tools prove to be only a partial solution because they are only able to infer, or guess, what the actual system behavior will be, and can only determine what security vulnerabilities might be possible in the application. To increase the fidelity of security testing results, developers should look to security testing products that feature a combination of analysis techniques of source code analysis and more practical approach called black box testing, also known as dynamic analysis.

This session discusses the difference between source code and black box testing and how the combination, or hybrid analysis, produces the accurate and reliable security information developers need to assess the security of their code.


7:45 to 8:00: Wrap up

8:00: Social


Im looking forward to seeing everyone there!

Previous Meetings

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.


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