OWASP - User contributions [en]

Phoenix

2010-07-01T03:44:06Z

Andrew Wilson:

{{Chapter Template|chaptername=Phoenix|extra=The chapter leaders are [mailto:peteroalofs@gmail.com Pete Roalofs] and [mailto:a.wilson82@gmail.com Andrew Wilson]
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-phoenix|emailarchives=http://lists.owasp.org/pipermail/owasp-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.

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

The meetings are now being hosted at University of Advanced Technology

The location is:

University of Advancing Technology
2625 W. BASELINE RD.
TEMPE, AZ 85283-1056

== JULY MEETING INFO - TUES July 6th 2010 6:30 PM ==

OWASP Phoenix invites you to it's July meeting!

Tuesday July 1st 2010 6:30 - 7:30 PM at University of Advancing Technology
The meetings are always free, unfortunately the drinks aren't.

This month's meeting:
* Updates and Discussion
* masSEXploitation, Mike Brooks 
**This talk covers the use of chaining vulnerabilities in order to bypass layered security systems. This talk will also cover ways of obtaining wormable remote code execution on a modern LAMP platform. These attacks where developed by me, and they are very new. These attacks are as real as it gets, and the results are making the headlines.

* Bio:
** I will be giving this talk at this years Defcon and it will 3rd year in a row that I spoken. According to the Department of Homeland Security I have found a vulnerability with a severity metric of 13.5 which makes it into the top 1,000 most dangerous of all time. I am the top answerer of security questions on StackOverflow.com (The Rook). I actively hunt for vulnerabilities on a verity of platforms. I write exploit code and make it public.

 
Drinks will be found afterword at Doc & Eddies.

Doc & Eddy's, 909 East Minton Drive, Tempe, AZ 85282-7021

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

* July - Michael Brooks
* August - TBD

== 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 
[http://www.owasp.org/index.php/Image:Scanner-Sparkly.ppt A Scanner Sparkly] - Web Application Proxy Editors and Scanners - Andre Gironda 
[http://www.owasp.org/index.php/Image:Owasp-lessonslearned.ppt Gray Box Assessment Lessons Learned] - Adam Muntner 
Risk Assessment Considerations for Web Applications (brief talk+discussion) - Erich Newell'''

'''[http://www.owasp.org/index.php/Image:Same-origin.pdf Reflections on Trusting the Same-Origin Policy] â 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. 

[http://www.stachliu.com/presentations/webapp0day/index.html 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."

[[Category:Arizona]]

Phoenix

2010-05-25T16:39:37Z

Andrew Wilson: /* JUNE MEETING INFO - TUES June 1st 2010 6:30 PM */

{{Chapter Template|chaptername=Phoenix|extra=The chapter leaders are [mailto:peteroalofs@gmail.com Pete Roalofs] and [mailto:a.wilson82@gmail.com Andrew Wilson]
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-phoenix|emailarchives=http://lists.owasp.org/pipermail/owasp-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.

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

The meetings are now being hosted at University of Advanced Technology

The location is:

University of Advancing Technology
2625 W. BASELINE RD.
TEMPE, AZ 85283-1056

== JUNE MEETING INFO - TUES June 1st 2010 6:30 PM ==

OWASP Phoenix invites you to it's June meeting!

Tuesday June 1st 2010 6:30 - 7:30 PM at University of Advancing Technology
The meetings are always free, unfortunately the drinks aren't.

This month's meeting:
* Updates and Discussion
* Involuntary Case Studies in Data Breaches, Rich Mogull, Securosis, [http://securosis.com/] 
**It's absolutely bass ackwards, but while the bad guys constantly share details of their exploits, including techniques, when it comes to real incidents, actual defenders rarely talk about what worked, and what didn't. Our entire industry is built on anecdote and the few tidbits we can glean from press reports. Thus we, as an industry, don't link means and methods to actual security outcomes. Without this information we're like a bunch of blindfolded wannabe ninjas trying to catch rounds from a machine gun with our bare hands. In this session we'll name names as we build in-depth case studies based on publicly available information, some of which isn't overly public. We will combine these with the latest information from breach reports released by incident response companies and the Dataloss Database. The session will build a picture of how real breaches happen, which security controls really work, and which compliance checkboxes are a complete and total waste of time.
 
Drinks will be found afterword at Doc & Eddies.

Doc & Eddy's, 909 East Minton Drive, Tempe, AZ 85282-7021

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

* July - Michael Brooks (tentative)
* August - TBD

== 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 
[http://www.owasp.org/index.php/Image:Scanner-Sparkly.ppt A Scanner Sparkly] - Web Application Proxy Editors and Scanners - Andre Gironda 
[http://www.owasp.org/index.php/Image:Owasp-lessonslearned.ppt Gray Box Assessment Lessons Learned] - Adam Muntner 
Risk Assessment Considerations for Web Applications (brief talk+discussion) - Erich Newell'''

'''[http://www.owasp.org/index.php/Image:Same-origin.pdf Reflections on Trusting the Same-Origin Policy] â 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. 

[http://www.stachliu.com/presentations/webapp0day/index.html 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."

[[Category:Arizona]]

Phoenix

2010-05-25T16:39:09Z

Andrew Wilson: /* 2010 Meetings Calendar */

{{Chapter Template|chaptername=Phoenix|extra=The chapter leaders are [mailto:peteroalofs@gmail.com Pete Roalofs] and [mailto:a.wilson82@gmail.com Andrew Wilson]
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-phoenix|emailarchives=http://lists.owasp.org/pipermail/owasp-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.

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

The meetings are now being hosted at University of Advanced Technology

The location is:

University of Advancing Technology
2625 W. BASELINE RD.
TEMPE, AZ 85283-1056

== JUNE MEETING INFO - TUES June 1st 2010 6:30 PM ==

OWASP Phoenix invites you to it's June meeting!

Tuesday June 1st 2010 6:30 - 7:30 PM at University of Advancing Technology
The meetings are always free, unfortunately the drinks aren't.

This month's meeting:
* Updates and Discussion
* Involuntary Case Studies in Data Breaches, Rich Mogull, Securosis, [http://securosis.com/] 
**It's absolutely bass ackwards, but while the bad guys constantly share details of their exploits, including techniques, when it comes to real incidents, actual defenders rarely talk about what worked, and what didn't. Our entire industry is built on anecdote and the few tidbits we can glean from press reports. Thus we, as an industry, don't link means and methods to actual security outcomes. Without this information we're like a bunch of blindfolded wannabe ninjas trying to catch rounds from a machine gun with our bare hands. In this session we'll name names as we build in-depth case studies based on publicly available information, some of which isn't overly public. We will combine these with the latest information from breach reports released by incident response companies and the Dataloss Database. The session will build a picture of how real breaches happen, which security controls really work, and which compliance checkboxes are a complete and total waste of time.
 
Drinks will be found afterword at Doc & Eddies.

Doc & Eddy's, 909 East Minton Drive, Tempe, AZ 85282-7021

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

* July - Michael Brooks (tentative)
* August - TBD

== 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 
[http://www.owasp.org/index.php/Image:Scanner-Sparkly.ppt A Scanner Sparkly] - Web Application Proxy Editors and Scanners - Andre Gironda 
[http://www.owasp.org/index.php/Image:Owasp-lessonslearned.ppt Gray Box Assessment Lessons Learned] - Adam Muntner 
Risk Assessment Considerations for Web Applications (brief talk+discussion) - Erich Newell'''

'''[http://www.owasp.org/index.php/Image:Same-origin.pdf Reflections on Trusting the Same-Origin Policy] â 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. 

[http://www.stachliu.com/presentations/webapp0day/index.html 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."

[[Category:Arizona]]

Phoenix

2010-05-25T16:31:03Z

Andrew Wilson: /*JUNE MEETING INFO - TUES JUNE 1ST 2010 6:30 PM */

{{Chapter Template|chaptername=Phoenix|extra=The chapter leaders are [mailto:peteroalofs@gmail.com Pete Roalofs] and [mailto:a.wilson82@gmail.com Andrew Wilson]
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-phoenix|emailarchives=http://lists.owasp.org/pipermail/owasp-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.

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

The meetings are now being hosted at University of Advanced Technology

The location is:

University of Advancing Technology
2625 W. BASELINE RD.
TEMPE, AZ 85283-1056

== JUNE MEETING INFO - TUES June 1st 2010 6:30 PM ==

OWASP Phoenix invites you to it's June meeting!

Tuesday June 1st 2010 6:30 - 7:30 PM at University of Advancing Technology
The meetings are always free, unfortunately the drinks aren't.

This month's meeting:
* Updates and Discussion
* Involuntary Case Studies in Data Breaches, Rich Mogull, Securosis, [http://securosis.com/] 
**It's absolutely bass ackwards, but while the bad guys constantly share details of their exploits, including techniques, when it comes to real incidents, actual defenders rarely talk about what worked, and what didn't. Our entire industry is built on anecdote and the few tidbits we can glean from press reports. Thus we, as an industry, don't link means and methods to actual security outcomes. Without this information we're like a bunch of blindfolded wannabe ninjas trying to catch rounds from a machine gun with our bare hands. In this session we'll name names as we build in-depth case studies based on publicly available information, some of which isn't overly public. We will combine these with the latest information from breach reports released by incident response companies and the Dataloss Database. The session will build a picture of how real breaches happen, which security controls really work, and which compliance checkboxes are a complete and total waste of time.
 
Drinks will be found afterword at Doc & Eddies.

Doc & Eddy's, 909 East Minton Drive, Tempe, AZ 85282-7021

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

* June - TBD
* July - TBD

== 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 
[http://www.owasp.org/index.php/Image:Scanner-Sparkly.ppt A Scanner Sparkly] - Web Application Proxy Editors and Scanners - Andre Gironda 
[http://www.owasp.org/index.php/Image:Owasp-lessonslearned.ppt Gray Box Assessment Lessons Learned] - Adam Muntner 
Risk Assessment Considerations for Web Applications (brief talk+discussion) - Erich Newell'''

'''[http://www.owasp.org/index.php/Image:Same-origin.pdf Reflections on Trusting the Same-Origin Policy] â 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. 

[http://www.stachliu.com/presentations/webapp0day/index.html 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."

[[Category:Arizona]]

Phoenix

2010-04-19T18:29:03Z

Andrew Wilson:

{{Chapter Template|chaptername=Phoenix|extra=The chapter leaders are [mailto:peteroalofs@gmail.com Pete Roalofs] and [mailto:a.wilson82@gmail.com Andrew Wilson]
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-phoenix|emailarchives=http://lists.owasp.org/pipermail/owasp-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.

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

The meetings are now being hosted at University of Advanced Technology

The location is:

University of Advancing Technology
2625 W. BASELINE RD.
TEMPE, AZ 85283-1056

== MAY MEETING INFO - TUES May 4TH 2010 6:30 PM ==

OWASP Phoenix invites you to it's MAY meeting!

Tues April 6th at 6:30 PM - 7:30 PM at University of Advancing Technology
The meetings are always free, unfortunately the drinks aren't.

This month's meeting:
* Updates and Discussion: TBD
* "Redefining & Understanding Security Posture" Andrew Wilson, [http://www.doublethunk.org] 
** One of the unfortunate realities of any industry is buzzword bingo. We often take terms and throw them around because they sound cool, but generally without any actual or well understood meaning. Security posture is one of those terms, that while rather popular, isn't really used in a well defined and functional fashion.
** This presentation will help better outline:
*** What is posture & why is it important
*** How can be used to gain advantage, how can it be used against people
*** How does that have valuable meaning as it relates to the security industry.

Drinks will be found afterword at Doc & Eddies.

Doc & Eddy's, 909 East Minton Drive, Tempe, AZ 85282-7021

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

* June - TBD
* July - TBD

== 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 
[http://www.owasp.org/index.php/Image:Scanner-Sparkly.ppt A Scanner Sparkly] - Web Application Proxy Editors and Scanners - Andre Gironda 
[http://www.owasp.org/index.php/Image:Owasp-lessonslearned.ppt Gray Box Assessment Lessons Learned] - Adam Muntner 
Risk Assessment Considerations for Web Applications (brief talk+discussion) - Erich Newell'''

'''[http://www.owasp.org/index.php/Image:Same-origin.pdf Reflections on Trusting the Same-Origin Policy] â 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. 

[http://www.stachliu.com/presentations/webapp0day/index.html 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."

[[Category:Arizona]]

Phoenix

2010-04-05T20:52:22Z

Andrew Wilson:

{{Chapter Template|chaptername=Phoenix|extra=The chapter leaders are [mailto:peteroalofs@gmail.com Pete Roalofs] and [mailto:a.wilson82@gmail.com Andrew Wilson]
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-phoenix|emailarchives=http://lists.owasp.org/pipermail/owasp-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.

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

The meetings are now being hosted at University of Advanced Technology

The location is:

University of Advanced Technology
2625 W. BASELINE RD.
TEMPE, AZ 85283-1056

== APRIL MEETING INFO - TUES APRIL 6TH 2010 6:30 PM ==

OWASP Phoenix invites you to it's APRIL meeting!
NOTE the LAST MINUTE Change of Venue!

Tues April 6th at 6:30 PM - 7:30 PM at University of Advanced Technology (CHANGE OF VENUE: WE WILL NOT BE MEETING AT ExecuTrain).
The meetings are always free, unfortunately the drinks aren't.

This month's meeting:
* Updates and Discussion: TBD
* "Protecting Your Applications from Backdoors: How to Secure Your Business Critical Applications from Time Bombs, Backdoors & Data" Mr. Jill Naymie, [http://www.veracode.com 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

Drinks will be found afterword, location will be decided after the meeting.

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

* May - TBD
* June - TBD

== 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 
[http://www.owasp.org/index.php/Image:Scanner-Sparkly.ppt A Scanner Sparkly] - Web Application Proxy Editors and Scanners - Andre Gironda 
[http://www.owasp.org/index.php/Image:Owasp-lessonslearned.ppt Gray Box Assessment Lessons Learned] - Adam Muntner 
Risk Assessment Considerations for Web Applications (brief talk+discussion) - Erich Newell'''

'''[http://www.owasp.org/index.php/Image:Same-origin.pdf Reflections on Trusting the Same-Origin Policy] â 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. 

[http://www.stachliu.com/presentations/webapp0day/index.html 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."

[[Category:Arizona]]

Phoenix

2010-04-05T20:46:50Z

Andrew Wilson:

{{Chapter Template|chaptername=Phoenix|extra=The chapter leaders are [mailto:peteroalofs@gmail.com Pete Roalofs] and [mailto:a.wilson82@gmail.com Andrew Wilson]
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-phoenix|emailarchives=http://lists.owasp.org/pipermail/owasp-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.

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

The meetings are now being hosted at University of Advanced Technology

The location is:

University of Advanced Technology
2625 W. BASELINE RD.
TEMPE, AZ 85283-1056

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

== APRIL MEETING INFO - TUES APRIL 6TH 2010 6:30 PM ==

OWASP Phoenix invites you to it's APRIL meeting!
NOTE the LAST MINUTE Change of Venue!

Tues April 6th at 6:30 PM - 7:30 PM at University of Advanced Technology (CHANGE OF VENUE: WE WILL NOT BE MEETING AT ExecuTrain).
The meetings are always free, unfortunately the drinks aren't.

This month's meeting:
* Updates and Discussion: TBD
* "Protecting Your Applications from Backdoors: How to Secure Your Business Critical Applications from Time Bombs, Backdoors & Data" Mr. Jill Naymie, [http://www.veracode.com 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

Drinks will be found afterword, location will be decided after the meeting.

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

* May - TBD
* June - TBD

== . ==

== 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 
[http://www.owasp.org/index.php/Image:Scanner-Sparkly.ppt A Scanner Sparkly] - Web Application Proxy Editors and Scanners - Andre Gironda 
[http://www.owasp.org/index.php/Image:Owasp-lessonslearned.ppt Gray Box Assessment Lessons Learned] - Adam Muntner 
Risk Assessment Considerations for Web Applications (brief talk+discussion) - Erich Newell'''

'''[http://www.owasp.org/index.php/Image:Same-origin.pdf Reflections on Trusting the Same-Origin Policy] â 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. 

[http://www.stachliu.com/presentations/webapp0day/index.html 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."

[[Category:Arizona]]