<?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=John+Steven</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=John+Steven"/>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php/Special:Contributions/John_Steven"/>
		<updated>2026-05-03T10:54:32Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.27.2</generator>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Password_Storage_Cheat_Sheet&amp;diff=147633</id>
		<title>Password Storage Cheat Sheet</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Password_Storage_Cheat_Sheet&amp;diff=147633"/>
				<updated>2013-03-12T15:03:39Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Introduction */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Introduction =&lt;br /&gt;
&lt;br /&gt;
Media covers the theft of large collections of passwords on an almost daily basis. Media coverage of password theft discloses the password storage scheme, the weakness of that scheme, and often discloses a large population of compromised credentials that can affect multiple web sites or other applications. This article provides guidance on properly storing passwords, secret question responses, and similar credential information. Proper storage helps prevent theft, compromise, and malicious use of credentials.&lt;br /&gt;
Information systems store passwords and other credentials in a variety of protected forms. Common vulnerabilities allow the theft of protected passwords through attack vectors such as SQL Injection. Protected passwords can also be stolen from artifacts such as logs, dumps, and backups.&lt;br /&gt;
&lt;br /&gt;
Specific guidance herein protects against stored credential theft but the bulk of guidance aims to prevent credential compromise. That is, this guidance helps designs resist revealing users’ credentials or allowing system access in the event threats steal protected credential information. For more information and a thorough treatment of this topic, refer to the Secure Password Storage Threat Model here [http://goo.gl/Spvzs http://goo.gl/Spvzs]. The link to this document is here [http://goo.gl/2loKu http://goo.gl/2loKu].&lt;br /&gt;
&lt;br /&gt;
= Guidance =&lt;br /&gt;
&lt;br /&gt;
== Do not limit the character set or length of credentials ==&lt;br /&gt;
&lt;br /&gt;
Some organizations restrict the 1) types of special characters and 2) length of credentials accepted by systems because of their inability to prevent SQL Injection, Cross-site scripting, command-injection and other forms of injection attacks. These restrictions, while well-intentioned, facilitate certain simple attacks such as brute force.&lt;br /&gt;
&lt;br /&gt;
Do not apply length, character set, or encoding restrictions on the entry or storage of credentials. Continue applying encoding, escaping, masking, outright omission, and other best practices to eliminate injection risks.&lt;br /&gt;
&lt;br /&gt;
== Use a cryptographically strong credential-specific salt ==&lt;br /&gt;
&lt;br /&gt;
A salt is fixed-length cryptographically-strong random value. Append credential data to the salt and use this as input to a protective function. Store the protected form appended to the salt as follows:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;[protected form] = [salt] + protect([protection func], [salt] + [credential]);&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Follow these practices to properly implement credential-specific salts:&lt;br /&gt;
&lt;br /&gt;
* Generate a unique salt upon creation of each stored credential (not just per user or system wide);&lt;br /&gt;
* Use cryptographically-strong random [*3] data;&lt;br /&gt;
* As storage permits, use a 32bit or 64b salt (actual size dependent on protection function);&lt;br /&gt;
* Scheme security does not depend on hiding, splitting, or otherwise obscuring the salt.&lt;br /&gt;
&lt;br /&gt;
Salts serve two purposes: 1) prevent the protected form from revealing two identical credentials and 2) augment entropy fed to protecting function without relying on credential complexity. The second aims to make pre-computed lookup attacks [*2] on an individual credential and time-based attacks on a population intractable.&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=137647</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=137647"/>
				<updated>2012-10-15T16:36:36Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Next Meeting */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra =Come see us at a chapter meeting, jump on our Google Group, or email any of us directly.&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board ===&lt;br /&gt;
Previously having had a Chapter Leader, then a Chapter &amp;quot;Program Committee&amp;quot;, the chapter is now run by a full board (alphabetical order):&lt;br /&gt;
* Jeremy Long&lt;br /&gt;
* Jack Mannino&lt;br /&gt;
* John Steven - Board Chair&lt;br /&gt;
&lt;br /&gt;
Board member responsibilities include:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre style=&amp;quot;white-space: pre-wrap;&amp;quot;&amp;gt;   * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics&lt;br /&gt;
   * Recruiting OWASP membership&lt;br /&gt;
   * Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
   * Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
   * Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
   * Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
   * Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations&lt;br /&gt;
   * Collecting and auditing use of chapter funds&lt;br /&gt;
   * Voting on chapter matters&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
For more information on how the board was elected and what it's responsibilities are, please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;amp;authkey=CIS9zFM Chapter Board Election] |mailinglistsite=https://groups.google.com/forum/#!forum/owasp-nova|emailarchives=https://groups.google.com/forum/#!forum/owasp-nova}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
=== Schedule  ===&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
==== Next Meeting  ====&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' October 4th, 2012 @ 6:30pm &lt;br /&gt;
&lt;br /&gt;
'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''Registration:''' [http://www.eventbrite.com/event/4430947082 Eventbrite]&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: [https://www.owasp.org/index.php/Dan_Cornell Dan Cornell] - &amp;quot;Benchmarking Web Application Scanners for YOUR Organization&amp;quot;, [https://www.owasp.org/images/7/73/OWASP_BenchmarkingWebApplicationScannersForYourOrganization_Content-1.pptx Presentation Slides]&lt;br /&gt;
* Firetalks!&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:'''&lt;br /&gt;
Benchmarking Web Application Scanners for YOUR Organization&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
Web applications pose significant risks for organizations. The selection of an appropriate scanning product or service can be challenging because every organization develops their web applications differently and decisions made by developers can cause wide swings in the value of different scanning technologies. To make a solid, informed decision, organizations need to create development team- and organization-specific benchmarks for the effectiveness of potential scanning technologies. This involves creating a comprehensive model of false positives, false negatives and other factors prior to mandating analysis technologies and making decisions about application risk management. This presentation provides a model for evaluating application analysis technologies, introduces an open source tool for benchmarking and comparing tool effectiveness, and outlines a process for making organization-specific decisions about analysis technology selection.&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
Dan Cornell has over 15 years experience architecting and developing web-based software systems. As CTO, he leads Denim Group's security research team in investigating the application of secure coding and development techniques to improve web-based software development methodologies. He also heads the Denim Group security research team, investigating the application of secure coding and development techniques to the improvement of web-based software development methodologies. Dan currently serves as the OWASP San Antonio chapter leader, member of the OWASP Global Membership Committee and co-lead of the OWASP Open Review Project. Dan has spoken at numerous security conferences, such as RSA in San Francisco, OWASP EU Research in Athens and OWASP AppSec USA in Minneapolis.&lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]).&lt;br /&gt;
&lt;br /&gt;
==== Upcoming Speakers  ====&lt;br /&gt;
&lt;br /&gt;
We need speakers and topics! If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== July 2012 ===&lt;br /&gt;
'''Date/Time:''' July 12th, 2012 @ 6:30pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: [https://www.owasp.org/index.php/John_Steven| John Steven] - &amp;quot;Password Storage Security&amp;quot;&lt;br /&gt;
* Firetalks!&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:'''&lt;br /&gt;
&amp;quot;Password Storage Security&amp;quot; [https://www.owasp.org/images/7/78/PSM_-_Problem_Definition.pdf|Password Storage Security.pdf] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
During the June meeting we discussed the LinkedIn password theft which was just beginning its the news cycle. We'll use the July chapter meeting to discuss issues around password hashing and a solution. While wholly different schemes for protecting passwords at rest are preferable, it's instructive to look at hashing passwords as a threat modeling exercise and take the time to follow through to a fix. &lt;br /&gt;
&lt;br /&gt;
To read up on the issue, look at my latest blog post on the topic: [http://goo.gl/sGyi8|Justice League Blog - Securing Password Storage]&lt;br /&gt;
&lt;br /&gt;
For those who were sufficiently intrigued, mystified, or inspired by the presentation on password protection at the last chapter meeting, Coursera is offering a free 6-week Stanford course on cryptography that begins on August 27th (&amp;quot;Learn about the inner workings of cryptographic primitives and how to apply this knowledge in real-world applications!&amp;quot;): [https://www.coursera.org/course/crypto|Crypto Course] &lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
&lt;br /&gt;
See  [https://www.owasp.org/index.php/John_Steven| John Steven Bio]&lt;br /&gt;
&lt;br /&gt;
=== June 2012 ===&lt;br /&gt;
'''Date/Time:''' June 7th, 2012 @ 6:30pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: Ken Johnson (LivingSocial) - &amp;quot;AppSec, Ritalin, and Failing Fast&amp;quot;&lt;br /&gt;
* Firetalks!&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:'''&lt;br /&gt;
&amp;quot;AppSec, Ritalin, and Failing Fast&amp;quot; [https://www.owasp.org/images/e/e9/Ken_Johnson_July_2012.pptx|AppSec, Ritalin, and Failing Fast.pptx] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
In early April Ken Johnson and Matt Ahrens presented a high-level overview of building an Application Security program at LivingSocial. This talk will differ in that it will focus on the granular aspects involved with introducing security into an incredibly intense development environment. The discussion will be compromised of experiences in:&lt;br /&gt;
* Developing technical solutions to solving difficult challenges&lt;br /&gt;
* Remaining proactive with an increased workload&lt;br /&gt;
* What it means to innovate&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
&lt;br /&gt;
Ken Johnson is the Application Security Manager for LivingSocial.com. Prior to joining LivingSocial.com, Ken worked in various application security consulting roles. Ken is the primary developer of the Web Exploitation Framework (wXf) and enjoys contributing to other open source projects as often as time permits. Ken has spoken at AppSec DC 2010 &amp;amp; 2012, OWASP DC and Phoenix chapters and is a member of the Attack Research Team.&lt;br /&gt;
&lt;br /&gt;
=== May 2012 ===&lt;br /&gt;
'''Date/Time:''' May 3rd, 2012 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* &amp;quot;Chill Out&amp;quot; conversations (formal talked pushed back due to logistical issues)&lt;br /&gt;
&lt;br /&gt;
=== April 2012 ===&lt;br /&gt;
'''Date/Time:''' April 16th, 2012 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''Food Sponsor:''' Jeremy Long - jeremy.long[at]owasp.org&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: &amp;quot;Malicious Code Detection or BRIC Breaking Through Static Analysis&amp;quot; by Masha Khainson (Cigital)&lt;br /&gt;
* Firetalks!&lt;br /&gt;
* ISSA NoVA Social @Champps! &amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Malicious Code Detection or BRIC Breaking Through Static Analysis&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
Malicious Code Detection or BRIC Breaking Through Static Analysis: As&lt;br /&gt;
organizations outsource development to less trustworthy providers&lt;br /&gt;
malware becomes as much a problem as introduction of honest&lt;br /&gt;
vulnerability by one's own development shop. Assessment practices&lt;br /&gt;
currently look for vulnerability within source code and a running&lt;br /&gt;
systems but these are but a few of windows of opportunity for malware&lt;br /&gt;
introduction. This presentation demonstrates an approach for&lt;br /&gt;
augmenting an existing security practice with the capability to detect&lt;br /&gt;
potentially malicious code through secure code review. First, we show&lt;br /&gt;
how to break malicious intent--often quite subtle--into concrete&lt;br /&gt;
patterns we can reliably detect. The framework then demonstrates how&lt;br /&gt;
to build suspicion around reliance of particular patterns' use in&lt;br /&gt;
concert which, increasingly, imply malicious intent. These techniques&lt;br /&gt;
will be explained through a demonstration in a real world application.&lt;br /&gt;
&lt;br /&gt;
'''Bio'''&lt;br /&gt;
Masha (a.k.a Marina) has dreamed of becoming a security consultant&lt;br /&gt;
before she ever knew what a ballerina was, and that's a good thing -&lt;br /&gt;
because she does not intend her talk to be a ballet recital. Having&lt;br /&gt;
been in software security for over seven years, Ms. Khainson has&lt;br /&gt;
delivered Architecture Risk Assessment, Secure Code Review, and&lt;br /&gt;
Ethical Hacking on many architectures, platforms and technologies.&lt;br /&gt;
Marina has also developed training materials for clients and led&lt;br /&gt;
remediation assistance teams.&lt;br /&gt;
&lt;br /&gt;
Prior to joining Cigital, Marina was a member of a research team at a&lt;br /&gt;
leading security research provider, where using disassembly as well as&lt;br /&gt;
protocol and source code analysis, she provided key information on&lt;br /&gt;
newly released vulnerabilities. Before that, Marina assisted the same&lt;br /&gt;
research team in producing detailed reports on critical malware and&lt;br /&gt;
spyware threats, as well as developing and testing content for network&lt;br /&gt;
security devices from some of the top providers of intrusion detection&lt;br /&gt;
and prevention technologies.&lt;br /&gt;
&lt;br /&gt;
Download: https://www.owasp.org/index.php/File:MCD-OWASPNoVA.pdf&lt;br /&gt;
&lt;br /&gt;
=== November 2011 ===&lt;br /&gt;
'''Date/Time:''' November 3rd, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.qinetiq.com/ QinetiQ], 2677 Prosperity Ave Fairfax, VA 22031&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # Talk: &amp;quot;Lessons Learned from the SQL Injection Challenge&amp;quot; by Ryan Barnett (Trustwave SpiderLabs)&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Lessons Learned from the SQL Injection Challenge&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
How effective are blacklist filters vs. SQL Injection attacks?  What is the failure rate vs. automated scanning or manual testing?  Are there any &amp;quot;Time-to-Bypass&amp;quot; metrics?  In an attempt to answer these questions, Trustwave SpiderLabs' Research Team (the development team behind the ModSecurity WAF and the OWASP ModSecurity Core Rule Set) held a community &amp;quot;SQL Injection Challenge&amp;quot; to test the effectiveness of the OWASP ModSecurity Core Rule Set protections.  This presentation will provide an overview of the challenge, a step-by-step walk-through of the bypass tactics used by the winners, as well as, present a new approach to attack detection using ModSecurity's Lua API to perform Bayesian analysis.&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
[mailto:ryan.barnett@owasp.org Ryan C. Barnett] (Twitter: [http://twitter.com/#!/ryancbarnett @ryancbarnett]) is a senior security researcher on Trustwave's SpiderLabs Team. He is a SANS Institute certified instructor and a member of both the Top 20 Vulnerabilities and CWE/SANS Top 25 Most Dangerous Programming Errors teams. In addition to working with SANS, he is also a WASC Member where he leads the Web Hacking Incidents Database (WHID) and Distributed Web Honeypots Projects and is also the OWASP ModSecurity Core Rule Set (CRS) project leader. Mr. Barnett has also authored a Web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== October 2011 ===&lt;br /&gt;
'''Date/Time:''' October 6th, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location/Food Sponsor:''' [http://www.cigital.com/ Cigital], 21351 Ridgetop Circle, Suite 400, Sterling, VA 20166 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # AppSec USA 2011 Recap&lt;br /&gt;
 # Talk: Jack Mannino: [http://www.slideshare.net/JackMannino/owasp-top-10-mobile-risks &amp;quot;OWASP Top 10 Mobile Risks&amp;quot;]&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2011 ===&lt;br /&gt;
&lt;br /&gt;
The September meeting was cancelled due to inclement weather (flash flooding).&lt;br /&gt;
&lt;br /&gt;
=== August 2011  ===&lt;br /&gt;
&lt;br /&gt;
We held a &amp;quot;social&amp;quot; event at Sweetwater Tavern in Sterling, VA. &lt;br /&gt;
&lt;br /&gt;
=== July 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' July 7th, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.cigital.com Cigital], Suite 400 21351 Ridgetop Circle, Dulles, VA, 20166&amp;lt;br&amp;gt; '''Food Sponsor:'''&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: iGoat - Ken Van Wyk&lt;br /&gt;
&lt;br /&gt;
=== June 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190&amp;lt;br&amp;gt; '''Food Sponsor:''' The College Board&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 &amp;quot;Insecure Direct Object References&amp;quot;]&lt;br /&gt;
 * College Board Speaker: &amp;quot;Attack-in-Depth:  Exploits of the OWASP Top Ten in Action&amp;quot;&lt;br /&gt;
 * Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
 - Jack Mannino: &amp;quot;Android Security 101&amp;quot;&lt;br /&gt;
 - Others!&lt;br /&gt;
&lt;br /&gt;
=== May 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''Food Sponsor:''' Akamai&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
 * 2011 Election (voice vote on the entire slate)&lt;br /&gt;
 * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 &amp;quot;Broken Authentication and Session Management&amp;quot;]&lt;br /&gt;
 * Speaker: Steve Witmer on A3 from the &amp;quot;breakers&amp;quot; perspective&lt;br /&gt;
 * Speaker:&amp;amp;nbsp;??? on A3 from the &amp;quot;fixers/defenders&amp;quot; perspective&lt;br /&gt;
 * Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
 * '''Update:''' All election candidates were elected by voice vote. &lt;br /&gt;
    * Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;authkey=CIS9zFM '11 Chapter Board Election Material]&lt;br /&gt;
&lt;br /&gt;
=== April 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &amp;lt;br&amp;gt; '''Food Sponsor:''' [https://www.cigital.com Cigital]&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
 * 2011 Election&lt;br /&gt;
 * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
 * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson ([https://www.owasp.org/images/9/92/Xssnotfriend-edited.pptx PPTX] or [https://www.owasp.org/images/0/06/Xssnotfriend-edited.pdf PDF])&lt;br /&gt;
 * Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])&lt;br /&gt;
 * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
 * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 &amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
  * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
  * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
  * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
  * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
  * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group]. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360! &lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective. &lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History  ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile Mobile]&lt;br /&gt;
&lt;br /&gt;
=== OWASP NoVa Members On Twitter  ===&lt;br /&gt;
&lt;br /&gt;
John Steven [http://twitter.com/m1splacedsoul http://twitter.com/m1splacedsoul] &lt;br /&gt;
&lt;br /&gt;
Jack Mannino [http://twitter.com/jack_mannino http://twitter.com/jack_mannino] &lt;br /&gt;
&lt;br /&gt;
Ben Tomhave [http://twitter.com/falconsview http://twitter.com/falconsview] &lt;br /&gt;
&lt;br /&gt;
Ken Johnson [http://twitter.com/cktricky http://twitter.com/cktricky] &lt;br /&gt;
&lt;br /&gt;
Mike Smith [http://twitter.com/rybolov http://twitter.com/rybolov] &lt;br /&gt;
&lt;br /&gt;
Trevor Hawthorn [http://twitter.com/packetwerks http://twitter.com/packetwerks] &lt;br /&gt;
&lt;br /&gt;
Jeremy Long [http://twitter.com/ctxt http://twitter.com/ctxt] &lt;br /&gt;
&lt;br /&gt;
Ari Elias-Bachrach [http://twitter.com/angelofsecurity http://twitter.com/angelofsecurity] &lt;br /&gt;
&lt;br /&gt;
Venkat Sundaram [http://twitter.com/Vnk3889 http://twitter.com/Vnk3889] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=File:OWASP_BenchmarkingWebApplicationScannersForYourOrganization_Content-1.pptx&amp;diff=137646</id>
		<title>File:OWASP BenchmarkingWebApplicationScannersForYourOrganization Content-1.pptx</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=File:OWASP_BenchmarkingWebApplicationScannersForYourOrganization_Content-1.pptx&amp;diff=137646"/>
				<updated>2012-10-15T16:34:58Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=137645</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=137645"/>
				<updated>2012-10-15T16:32:33Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra =Come see us at a chapter meeting, jump on our Google Group, or email any of us directly.&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board ===&lt;br /&gt;
Previously having had a Chapter Leader, then a Chapter &amp;quot;Program Committee&amp;quot;, the chapter is now run by a full board (alphabetical order):&lt;br /&gt;
* Jeremy Long&lt;br /&gt;
* Jack Mannino&lt;br /&gt;
* John Steven - Board Chair&lt;br /&gt;
&lt;br /&gt;
Board member responsibilities include:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre style=&amp;quot;white-space: pre-wrap;&amp;quot;&amp;gt;   * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics&lt;br /&gt;
   * Recruiting OWASP membership&lt;br /&gt;
   * Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
   * Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
   * Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
   * Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
   * Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations&lt;br /&gt;
   * Collecting and auditing use of chapter funds&lt;br /&gt;
   * Voting on chapter matters&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
For more information on how the board was elected and what it's responsibilities are, please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;amp;authkey=CIS9zFM Chapter Board Election] |mailinglistsite=https://groups.google.com/forum/#!forum/owasp-nova|emailarchives=https://groups.google.com/forum/#!forum/owasp-nova}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
=== Schedule  ===&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
==== Next Meeting  ====&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' October 4th, 2012 @ 6:30pm &lt;br /&gt;
&lt;br /&gt;
'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''Registration:''' [http://www.eventbrite.com/event/4430947082 Eventbrite]&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: [https://www.owasp.org/index.php/Dan_Cornell Dan Cornell] - &amp;quot;Benchmarking Web Application Scanners for YOUR Organization&amp;quot;&lt;br /&gt;
* Firetalks!&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:'''&lt;br /&gt;
Benchmarking Web Application Scanners for YOUR Organization&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
Web applications pose significant risks for organizations. The selection of an appropriate scanning product or service can be challenging because every organization develops their web applications differently and decisions made by developers can cause wide swings in the value of different scanning technologies. To make a solid, informed decision, organizations need to create development team- and organization-specific benchmarks for the effectiveness of potential scanning technologies. This involves creating a comprehensive model of false positives, false negatives and other factors prior to mandating analysis technologies and making decisions about application risk management. This presentation provides a model for evaluating application analysis technologies, introduces an open source tool for benchmarking and comparing tool effectiveness, and outlines a process for making organization-specific decisions about analysis technology selection.&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
Dan Cornell has over 15 years experience architecting and developing web-based software systems. As CTO, he leads Denim Group's security research team in investigating the application of secure coding and development techniques to improve web-based software development methodologies. He also heads the Denim Group security research team, investigating the application of secure coding and development techniques to the improvement of web-based software development methodologies. Dan currently serves as the OWASP San Antonio chapter leader, member of the OWASP Global Membership Committee and co-lead of the OWASP Open Review Project. Dan has spoken at numerous security conferences, such as RSA in San Francisco, OWASP EU Research in Athens and OWASP AppSec USA in Minneapolis.&lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]).&lt;br /&gt;
&lt;br /&gt;
==== Upcoming Speakers  ====&lt;br /&gt;
&lt;br /&gt;
We need speakers and topics! If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== July 2012 ===&lt;br /&gt;
'''Date/Time:''' July 12th, 2012 @ 6:30pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: [https://www.owasp.org/index.php/John_Steven| John Steven] - &amp;quot;Password Storage Security&amp;quot;&lt;br /&gt;
* Firetalks!&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:'''&lt;br /&gt;
&amp;quot;Password Storage Security&amp;quot; [https://www.owasp.org/images/7/78/PSM_-_Problem_Definition.pdf|Password Storage Security.pdf] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
During the June meeting we discussed the LinkedIn password theft which was just beginning its the news cycle. We'll use the July chapter meeting to discuss issues around password hashing and a solution. While wholly different schemes for protecting passwords at rest are preferable, it's instructive to look at hashing passwords as a threat modeling exercise and take the time to follow through to a fix. &lt;br /&gt;
&lt;br /&gt;
To read up on the issue, look at my latest blog post on the topic: [http://goo.gl/sGyi8|Justice League Blog - Securing Password Storage]&lt;br /&gt;
&lt;br /&gt;
For those who were sufficiently intrigued, mystified, or inspired by the presentation on password protection at the last chapter meeting, Coursera is offering a free 6-week Stanford course on cryptography that begins on August 27th (&amp;quot;Learn about the inner workings of cryptographic primitives and how to apply this knowledge in real-world applications!&amp;quot;): [https://www.coursera.org/course/crypto|Crypto Course] &lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
&lt;br /&gt;
See  [https://www.owasp.org/index.php/John_Steven| John Steven Bio]&lt;br /&gt;
&lt;br /&gt;
=== June 2012 ===&lt;br /&gt;
'''Date/Time:''' June 7th, 2012 @ 6:30pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: Ken Johnson (LivingSocial) - &amp;quot;AppSec, Ritalin, and Failing Fast&amp;quot;&lt;br /&gt;
* Firetalks!&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:'''&lt;br /&gt;
&amp;quot;AppSec, Ritalin, and Failing Fast&amp;quot; [https://www.owasp.org/images/e/e9/Ken_Johnson_July_2012.pptx|AppSec, Ritalin, and Failing Fast.pptx] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
In early April Ken Johnson and Matt Ahrens presented a high-level overview of building an Application Security program at LivingSocial. This talk will differ in that it will focus on the granular aspects involved with introducing security into an incredibly intense development environment. The discussion will be compromised of experiences in:&lt;br /&gt;
* Developing technical solutions to solving difficult challenges&lt;br /&gt;
* Remaining proactive with an increased workload&lt;br /&gt;
* What it means to innovate&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
&lt;br /&gt;
Ken Johnson is the Application Security Manager for LivingSocial.com. Prior to joining LivingSocial.com, Ken worked in various application security consulting roles. Ken is the primary developer of the Web Exploitation Framework (wXf) and enjoys contributing to other open source projects as often as time permits. Ken has spoken at AppSec DC 2010 &amp;amp; 2012, OWASP DC and Phoenix chapters and is a member of the Attack Research Team.&lt;br /&gt;
&lt;br /&gt;
=== May 2012 ===&lt;br /&gt;
'''Date/Time:''' May 3rd, 2012 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* &amp;quot;Chill Out&amp;quot; conversations (formal talked pushed back due to logistical issues)&lt;br /&gt;
&lt;br /&gt;
=== April 2012 ===&lt;br /&gt;
'''Date/Time:''' April 16th, 2012 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''Food Sponsor:''' Jeremy Long - jeremy.long[at]owasp.org&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: &amp;quot;Malicious Code Detection or BRIC Breaking Through Static Analysis&amp;quot; by Masha Khainson (Cigital)&lt;br /&gt;
* Firetalks!&lt;br /&gt;
* ISSA NoVA Social @Champps! &amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Malicious Code Detection or BRIC Breaking Through Static Analysis&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
Malicious Code Detection or BRIC Breaking Through Static Analysis: As&lt;br /&gt;
organizations outsource development to less trustworthy providers&lt;br /&gt;
malware becomes as much a problem as introduction of honest&lt;br /&gt;
vulnerability by one's own development shop. Assessment practices&lt;br /&gt;
currently look for vulnerability within source code and a running&lt;br /&gt;
systems but these are but a few of windows of opportunity for malware&lt;br /&gt;
introduction. This presentation demonstrates an approach for&lt;br /&gt;
augmenting an existing security practice with the capability to detect&lt;br /&gt;
potentially malicious code through secure code review. First, we show&lt;br /&gt;
how to break malicious intent--often quite subtle--into concrete&lt;br /&gt;
patterns we can reliably detect. The framework then demonstrates how&lt;br /&gt;
to build suspicion around reliance of particular patterns' use in&lt;br /&gt;
concert which, increasingly, imply malicious intent. These techniques&lt;br /&gt;
will be explained through a demonstration in a real world application.&lt;br /&gt;
&lt;br /&gt;
'''Bio'''&lt;br /&gt;
Masha (a.k.a Marina) has dreamed of becoming a security consultant&lt;br /&gt;
before she ever knew what a ballerina was, and that's a good thing -&lt;br /&gt;
because she does not intend her talk to be a ballet recital. Having&lt;br /&gt;
been in software security for over seven years, Ms. Khainson has&lt;br /&gt;
delivered Architecture Risk Assessment, Secure Code Review, and&lt;br /&gt;
Ethical Hacking on many architectures, platforms and technologies.&lt;br /&gt;
Marina has also developed training materials for clients and led&lt;br /&gt;
remediation assistance teams.&lt;br /&gt;
&lt;br /&gt;
Prior to joining Cigital, Marina was a member of a research team at a&lt;br /&gt;
leading security research provider, where using disassembly as well as&lt;br /&gt;
protocol and source code analysis, she provided key information on&lt;br /&gt;
newly released vulnerabilities. Before that, Marina assisted the same&lt;br /&gt;
research team in producing detailed reports on critical malware and&lt;br /&gt;
spyware threats, as well as developing and testing content for network&lt;br /&gt;
security devices from some of the top providers of intrusion detection&lt;br /&gt;
and prevention technologies.&lt;br /&gt;
&lt;br /&gt;
Download: https://www.owasp.org/index.php/File:MCD-OWASPNoVA.pdf&lt;br /&gt;
&lt;br /&gt;
=== November 2011 ===&lt;br /&gt;
'''Date/Time:''' November 3rd, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.qinetiq.com/ QinetiQ], 2677 Prosperity Ave Fairfax, VA 22031&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # Talk: &amp;quot;Lessons Learned from the SQL Injection Challenge&amp;quot; by Ryan Barnett (Trustwave SpiderLabs)&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Lessons Learned from the SQL Injection Challenge&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
How effective are blacklist filters vs. SQL Injection attacks?  What is the failure rate vs. automated scanning or manual testing?  Are there any &amp;quot;Time-to-Bypass&amp;quot; metrics?  In an attempt to answer these questions, Trustwave SpiderLabs' Research Team (the development team behind the ModSecurity WAF and the OWASP ModSecurity Core Rule Set) held a community &amp;quot;SQL Injection Challenge&amp;quot; to test the effectiveness of the OWASP ModSecurity Core Rule Set protections.  This presentation will provide an overview of the challenge, a step-by-step walk-through of the bypass tactics used by the winners, as well as, present a new approach to attack detection using ModSecurity's Lua API to perform Bayesian analysis.&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
[mailto:ryan.barnett@owasp.org Ryan C. Barnett] (Twitter: [http://twitter.com/#!/ryancbarnett @ryancbarnett]) is a senior security researcher on Trustwave's SpiderLabs Team. He is a SANS Institute certified instructor and a member of both the Top 20 Vulnerabilities and CWE/SANS Top 25 Most Dangerous Programming Errors teams. In addition to working with SANS, he is also a WASC Member where he leads the Web Hacking Incidents Database (WHID) and Distributed Web Honeypots Projects and is also the OWASP ModSecurity Core Rule Set (CRS) project leader. Mr. Barnett has also authored a Web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== October 2011 ===&lt;br /&gt;
'''Date/Time:''' October 6th, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location/Food Sponsor:''' [http://www.cigital.com/ Cigital], 21351 Ridgetop Circle, Suite 400, Sterling, VA 20166 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # AppSec USA 2011 Recap&lt;br /&gt;
 # Talk: Jack Mannino: [http://www.slideshare.net/JackMannino/owasp-top-10-mobile-risks &amp;quot;OWASP Top 10 Mobile Risks&amp;quot;]&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2011 ===&lt;br /&gt;
&lt;br /&gt;
The September meeting was cancelled due to inclement weather (flash flooding).&lt;br /&gt;
&lt;br /&gt;
=== August 2011  ===&lt;br /&gt;
&lt;br /&gt;
We held a &amp;quot;social&amp;quot; event at Sweetwater Tavern in Sterling, VA. &lt;br /&gt;
&lt;br /&gt;
=== July 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' July 7th, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.cigital.com Cigital], Suite 400 21351 Ridgetop Circle, Dulles, VA, 20166&amp;lt;br&amp;gt; '''Food Sponsor:'''&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: iGoat - Ken Van Wyk&lt;br /&gt;
&lt;br /&gt;
=== June 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190&amp;lt;br&amp;gt; '''Food Sponsor:''' The College Board&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 &amp;quot;Insecure Direct Object References&amp;quot;]&lt;br /&gt;
 * College Board Speaker: &amp;quot;Attack-in-Depth:  Exploits of the OWASP Top Ten in Action&amp;quot;&lt;br /&gt;
 * Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
 - Jack Mannino: &amp;quot;Android Security 101&amp;quot;&lt;br /&gt;
 - Others!&lt;br /&gt;
&lt;br /&gt;
=== May 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''Food Sponsor:''' Akamai&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
 * 2011 Election (voice vote on the entire slate)&lt;br /&gt;
 * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 &amp;quot;Broken Authentication and Session Management&amp;quot;]&lt;br /&gt;
 * Speaker: Steve Witmer on A3 from the &amp;quot;breakers&amp;quot; perspective&lt;br /&gt;
 * Speaker:&amp;amp;nbsp;??? on A3 from the &amp;quot;fixers/defenders&amp;quot; perspective&lt;br /&gt;
 * Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
 * '''Update:''' All election candidates were elected by voice vote. &lt;br /&gt;
    * Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;authkey=CIS9zFM '11 Chapter Board Election Material]&lt;br /&gt;
&lt;br /&gt;
=== April 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &amp;lt;br&amp;gt; '''Food Sponsor:''' [https://www.cigital.com Cigital]&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
 * 2011 Election&lt;br /&gt;
 * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
 * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson ([https://www.owasp.org/images/9/92/Xssnotfriend-edited.pptx PPTX] or [https://www.owasp.org/images/0/06/Xssnotfriend-edited.pdf PDF])&lt;br /&gt;
 * Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])&lt;br /&gt;
 * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
 * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 &amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
  * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
  * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
  * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
  * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
  * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group]. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360! &lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective. &lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History  ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile Mobile]&lt;br /&gt;
&lt;br /&gt;
=== OWASP NoVa Members On Twitter  ===&lt;br /&gt;
&lt;br /&gt;
John Steven [http://twitter.com/m1splacedsoul http://twitter.com/m1splacedsoul] &lt;br /&gt;
&lt;br /&gt;
Jack Mannino [http://twitter.com/jack_mannino http://twitter.com/jack_mannino] &lt;br /&gt;
&lt;br /&gt;
Ben Tomhave [http://twitter.com/falconsview http://twitter.com/falconsview] &lt;br /&gt;
&lt;br /&gt;
Ken Johnson [http://twitter.com/cktricky http://twitter.com/cktricky] &lt;br /&gt;
&lt;br /&gt;
Mike Smith [http://twitter.com/rybolov http://twitter.com/rybolov] &lt;br /&gt;
&lt;br /&gt;
Trevor Hawthorn [http://twitter.com/packetwerks http://twitter.com/packetwerks] &lt;br /&gt;
&lt;br /&gt;
Jeremy Long [http://twitter.com/ctxt http://twitter.com/ctxt] &lt;br /&gt;
&lt;br /&gt;
Ari Elias-Bachrach [http://twitter.com/angelofsecurity http://twitter.com/angelofsecurity] &lt;br /&gt;
&lt;br /&gt;
Venkat Sundaram [http://twitter.com/Vnk3889 http://twitter.com/Vnk3889] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=137644</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=137644"/>
				<updated>2012-10-15T16:31:52Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra =Come see us at a chapter meeting, jump on our Google Group, or email any of us directly.&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board ===&lt;br /&gt;
Previously having had a Chapter Leader, then a Chapter &amp;quot;Program Committee&amp;quot;, the chapter is now run by a full board (alphabetical order):&lt;br /&gt;
* Jeremy Long&lt;br /&gt;
* Jack Mannino&lt;br /&gt;
* John Steven - Board Chair&lt;br /&gt;
&lt;br /&gt;
Board member responsibilities include:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre style=&amp;quot;white-space: pre-wrap;&amp;quot;&amp;gt;   * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics&lt;br /&gt;
   * Recruiting OWASP membership&lt;br /&gt;
   * Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
   * Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
   * Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
   * Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
   * Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations&lt;br /&gt;
   * Collecting and auditing use of chapter funds&lt;br /&gt;
   * Voting on chapter matters&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
For more information on how the board was elected and what it's responsibilities are, please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;amp;authkey=CIS9zFM Chapter Board Election]fckLRfckLR|mailinglistsite=https://groups.google.com/forum/#!forum/owasp-nova|emailarchives=https://groups.google.com/forum/#!forum/owasp-nova}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
=== Schedule  ===&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
==== Next Meeting  ====&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' October 4th, 2012 @ 6:30pm &lt;br /&gt;
&lt;br /&gt;
'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''Registration:''' [http://www.eventbrite.com/event/4430947082 Eventbrite]&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: [https://www.owasp.org/index.php/Dan_Cornell Dan Cornell] - &amp;quot;Benchmarking Web Application Scanners for YOUR Organization&amp;quot;&lt;br /&gt;
* Firetalks!&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:'''&lt;br /&gt;
Benchmarking Web Application Scanners for YOUR Organization&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
Web applications pose significant risks for organizations. The selection of an appropriate scanning product or service can be challenging because every organization develops their web applications differently and decisions made by developers can cause wide swings in the value of different scanning technologies. To make a solid, informed decision, organizations need to create development team- and organization-specific benchmarks for the effectiveness of potential scanning technologies. This involves creating a comprehensive model of false positives, false negatives and other factors prior to mandating analysis technologies and making decisions about application risk management. This presentation provides a model for evaluating application analysis technologies, introduces an open source tool for benchmarking and comparing tool effectiveness, and outlines a process for making organization-specific decisions about analysis technology selection.&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
Dan Cornell has over 15 years experience architecting and developing web-based software systems. As CTO, he leads Denim Group's security research team in investigating the application of secure coding and development techniques to improve web-based software development methodologies. He also heads the Denim Group security research team, investigating the application of secure coding and development techniques to the improvement of web-based software development methodologies. Dan currently serves as the OWASP San Antonio chapter leader, member of the OWASP Global Membership Committee and co-lead of the OWASP Open Review Project. Dan has spoken at numerous security conferences, such as RSA in San Francisco, OWASP EU Research in Athens and OWASP AppSec USA in Minneapolis.&lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]).&lt;br /&gt;
&lt;br /&gt;
==== Upcoming Speakers  ====&lt;br /&gt;
&lt;br /&gt;
We need speakers and topics! If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== July 2012 ===&lt;br /&gt;
'''Date/Time:''' July 12th, 2012 @ 6:30pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: [https://www.owasp.org/index.php/John_Steven| John Steven] - &amp;quot;Password Storage Security&amp;quot;&lt;br /&gt;
* Firetalks!&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:'''&lt;br /&gt;
&amp;quot;Password Storage Security&amp;quot; [https://www.owasp.org/images/7/78/PSM_-_Problem_Definition.pdf|Password Storage Security.pdf] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
During the June meeting we discussed the LinkedIn password theft which was just beginning its the news cycle. We'll use the July chapter meeting to discuss issues around password hashing and a solution. While wholly different schemes for protecting passwords at rest are preferable, it's instructive to look at hashing passwords as a threat modeling exercise and take the time to follow through to a fix. &lt;br /&gt;
&lt;br /&gt;
To read up on the issue, look at my latest blog post on the topic: [http://goo.gl/sGyi8|Justice League Blog - Securing Password Storage]&lt;br /&gt;
&lt;br /&gt;
For those who were sufficiently intrigued, mystified, or inspired by the presentation on password protection at the last chapter meeting, Coursera is offering a free 6-week Stanford course on cryptography that begins on August 27th (&amp;quot;Learn about the inner workings of cryptographic primitives and how to apply this knowledge in real-world applications!&amp;quot;): [https://www.coursera.org/course/crypto|Crypto Course] &lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
&lt;br /&gt;
See  [https://www.owasp.org/index.php/John_Steven| John Steven Bio]&lt;br /&gt;
&lt;br /&gt;
=== June 2012 ===&lt;br /&gt;
'''Date/Time:''' June 7th, 2012 @ 6:30pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: Ken Johnson (LivingSocial) - &amp;quot;AppSec, Ritalin, and Failing Fast&amp;quot;&lt;br /&gt;
* Firetalks!&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:'''&lt;br /&gt;
&amp;quot;AppSec, Ritalin, and Failing Fast&amp;quot; [https://www.owasp.org/images/e/e9/Ken_Johnson_July_2012.pptx|AppSec, Ritalin, and Failing Fast.pptx] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
In early April Ken Johnson and Matt Ahrens presented a high-level overview of building an Application Security program at LivingSocial. This talk will differ in that it will focus on the granular aspects involved with introducing security into an incredibly intense development environment. The discussion will be compromised of experiences in:&lt;br /&gt;
* Developing technical solutions to solving difficult challenges&lt;br /&gt;
* Remaining proactive with an increased workload&lt;br /&gt;
* What it means to innovate&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
&lt;br /&gt;
Ken Johnson is the Application Security Manager for LivingSocial.com. Prior to joining LivingSocial.com, Ken worked in various application security consulting roles. Ken is the primary developer of the Web Exploitation Framework (wXf) and enjoys contributing to other open source projects as often as time permits. Ken has spoken at AppSec DC 2010 &amp;amp; 2012, OWASP DC and Phoenix chapters and is a member of the Attack Research Team.&lt;br /&gt;
&lt;br /&gt;
=== May 2012 ===&lt;br /&gt;
'''Date/Time:''' May 3rd, 2012 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* &amp;quot;Chill Out&amp;quot; conversations (formal talked pushed back due to logistical issues)&lt;br /&gt;
&lt;br /&gt;
=== April 2012 ===&lt;br /&gt;
'''Date/Time:''' April 16th, 2012 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''Food Sponsor:''' Jeremy Long - jeremy.long[at]owasp.org&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: &amp;quot;Malicious Code Detection or BRIC Breaking Through Static Analysis&amp;quot; by Masha Khainson (Cigital)&lt;br /&gt;
* Firetalks!&lt;br /&gt;
* ISSA NoVA Social @Champps! &amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Malicious Code Detection or BRIC Breaking Through Static Analysis&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
Malicious Code Detection or BRIC Breaking Through Static Analysis: As&lt;br /&gt;
organizations outsource development to less trustworthy providers&lt;br /&gt;
malware becomes as much a problem as introduction of honest&lt;br /&gt;
vulnerability by one's own development shop. Assessment practices&lt;br /&gt;
currently look for vulnerability within source code and a running&lt;br /&gt;
systems but these are but a few of windows of opportunity for malware&lt;br /&gt;
introduction. This presentation demonstrates an approach for&lt;br /&gt;
augmenting an existing security practice with the capability to detect&lt;br /&gt;
potentially malicious code through secure code review. First, we show&lt;br /&gt;
how to break malicious intent--often quite subtle--into concrete&lt;br /&gt;
patterns we can reliably detect. The framework then demonstrates how&lt;br /&gt;
to build suspicion around reliance of particular patterns' use in&lt;br /&gt;
concert which, increasingly, imply malicious intent. These techniques&lt;br /&gt;
will be explained through a demonstration in a real world application.&lt;br /&gt;
&lt;br /&gt;
'''Bio'''&lt;br /&gt;
Masha (a.k.a Marina) has dreamed of becoming a security consultant&lt;br /&gt;
before she ever knew what a ballerina was, and that's a good thing -&lt;br /&gt;
because she does not intend her talk to be a ballet recital. Having&lt;br /&gt;
been in software security for over seven years, Ms. Khainson has&lt;br /&gt;
delivered Architecture Risk Assessment, Secure Code Review, and&lt;br /&gt;
Ethical Hacking on many architectures, platforms and technologies.&lt;br /&gt;
Marina has also developed training materials for clients and led&lt;br /&gt;
remediation assistance teams.&lt;br /&gt;
&lt;br /&gt;
Prior to joining Cigital, Marina was a member of a research team at a&lt;br /&gt;
leading security research provider, where using disassembly as well as&lt;br /&gt;
protocol and source code analysis, she provided key information on&lt;br /&gt;
newly released vulnerabilities. Before that, Marina assisted the same&lt;br /&gt;
research team in producing detailed reports on critical malware and&lt;br /&gt;
spyware threats, as well as developing and testing content for network&lt;br /&gt;
security devices from some of the top providers of intrusion detection&lt;br /&gt;
and prevention technologies.&lt;br /&gt;
&lt;br /&gt;
Download: https://www.owasp.org/index.php/File:MCD-OWASPNoVA.pdf&lt;br /&gt;
&lt;br /&gt;
=== November 2011 ===&lt;br /&gt;
'''Date/Time:''' November 3rd, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.qinetiq.com/ QinetiQ], 2677 Prosperity Ave Fairfax, VA 22031&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # Talk: &amp;quot;Lessons Learned from the SQL Injection Challenge&amp;quot; by Ryan Barnett (Trustwave SpiderLabs)&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Lessons Learned from the SQL Injection Challenge&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
How effective are blacklist filters vs. SQL Injection attacks?  What is the failure rate vs. automated scanning or manual testing?  Are there any &amp;quot;Time-to-Bypass&amp;quot; metrics?  In an attempt to answer these questions, Trustwave SpiderLabs' Research Team (the development team behind the ModSecurity WAF and the OWASP ModSecurity Core Rule Set) held a community &amp;quot;SQL Injection Challenge&amp;quot; to test the effectiveness of the OWASP ModSecurity Core Rule Set protections.  This presentation will provide an overview of the challenge, a step-by-step walk-through of the bypass tactics used by the winners, as well as, present a new approach to attack detection using ModSecurity's Lua API to perform Bayesian analysis.&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
[mailto:ryan.barnett@owasp.org Ryan C. Barnett] (Twitter: [http://twitter.com/#!/ryancbarnett @ryancbarnett]) is a senior security researcher on Trustwave's SpiderLabs Team. He is a SANS Institute certified instructor and a member of both the Top 20 Vulnerabilities and CWE/SANS Top 25 Most Dangerous Programming Errors teams. In addition to working with SANS, he is also a WASC Member where he leads the Web Hacking Incidents Database (WHID) and Distributed Web Honeypots Projects and is also the OWASP ModSecurity Core Rule Set (CRS) project leader. Mr. Barnett has also authored a Web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== October 2011 ===&lt;br /&gt;
'''Date/Time:''' October 6th, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location/Food Sponsor:''' [http://www.cigital.com/ Cigital], 21351 Ridgetop Circle, Suite 400, Sterling, VA 20166 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # AppSec USA 2011 Recap&lt;br /&gt;
 # Talk: Jack Mannino: [http://www.slideshare.net/JackMannino/owasp-top-10-mobile-risks &amp;quot;OWASP Top 10 Mobile Risks&amp;quot;]&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2011 ===&lt;br /&gt;
&lt;br /&gt;
The September meeting was cancelled due to inclement weather (flash flooding).&lt;br /&gt;
&lt;br /&gt;
=== August 2011  ===&lt;br /&gt;
&lt;br /&gt;
We held a &amp;quot;social&amp;quot; event at Sweetwater Tavern in Sterling, VA. &lt;br /&gt;
&lt;br /&gt;
=== July 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' July 7th, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.cigital.com Cigital], Suite 400 21351 Ridgetop Circle, Dulles, VA, 20166&amp;lt;br&amp;gt; '''Food Sponsor:'''&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: iGoat - Ken Van Wyk&lt;br /&gt;
&lt;br /&gt;
=== June 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190&amp;lt;br&amp;gt; '''Food Sponsor:''' The College Board&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 &amp;quot;Insecure Direct Object References&amp;quot;]&lt;br /&gt;
 * College Board Speaker: &amp;quot;Attack-in-Depth:  Exploits of the OWASP Top Ten in Action&amp;quot;&lt;br /&gt;
 * Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
 - Jack Mannino: &amp;quot;Android Security 101&amp;quot;&lt;br /&gt;
 - Others!&lt;br /&gt;
&lt;br /&gt;
=== May 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''Food Sponsor:''' Akamai&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
 * 2011 Election (voice vote on the entire slate)&lt;br /&gt;
 * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 &amp;quot;Broken Authentication and Session Management&amp;quot;]&lt;br /&gt;
 * Speaker: Steve Witmer on A3 from the &amp;quot;breakers&amp;quot; perspective&lt;br /&gt;
 * Speaker:&amp;amp;nbsp;??? on A3 from the &amp;quot;fixers/defenders&amp;quot; perspective&lt;br /&gt;
 * Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
 * '''Update:''' All election candidates were elected by voice vote. &lt;br /&gt;
    * Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;authkey=CIS9zFM '11 Chapter Board Election Material]&lt;br /&gt;
&lt;br /&gt;
=== April 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &amp;lt;br&amp;gt; '''Food Sponsor:''' [https://www.cigital.com Cigital]&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
 * 2011 Election&lt;br /&gt;
 * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
 * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson ([https://www.owasp.org/images/9/92/Xssnotfriend-edited.pptx PPTX] or [https://www.owasp.org/images/0/06/Xssnotfriend-edited.pdf PDF])&lt;br /&gt;
 * Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])&lt;br /&gt;
 * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
 * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 &amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
  * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
  * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
  * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
  * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
  * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group]. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360! &lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective. &lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History  ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile Mobile]&lt;br /&gt;
&lt;br /&gt;
=== OWASP NoVa Members On Twitter  ===&lt;br /&gt;
&lt;br /&gt;
John Steven [http://twitter.com/m1splacedsoul http://twitter.com/m1splacedsoul] &lt;br /&gt;
&lt;br /&gt;
Jack Mannino [http://twitter.com/jack_mannino http://twitter.com/jack_mannino] &lt;br /&gt;
&lt;br /&gt;
Ben Tomhave [http://twitter.com/falconsview http://twitter.com/falconsview] &lt;br /&gt;
&lt;br /&gt;
Ken Johnson [http://twitter.com/cktricky http://twitter.com/cktricky] &lt;br /&gt;
&lt;br /&gt;
Mike Smith [http://twitter.com/rybolov http://twitter.com/rybolov] &lt;br /&gt;
&lt;br /&gt;
Trevor Hawthorn [http://twitter.com/packetwerks http://twitter.com/packetwerks] &lt;br /&gt;
&lt;br /&gt;
Jeremy Long [http://twitter.com/ctxt http://twitter.com/ctxt] &lt;br /&gt;
&lt;br /&gt;
Ari Elias-Bachrach [http://twitter.com/angelofsecurity http://twitter.com/angelofsecurity] &lt;br /&gt;
&lt;br /&gt;
Venkat Sundaram [http://twitter.com/Vnk3889 http://twitter.com/Vnk3889] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Chicago&amp;diff=137643</id>
		<title>Chicago</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Chicago&amp;diff=137643"/>
				<updated>2012-10-15T16:22:15Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Presentation Archives */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Next Chapter Meeting: October 11th, 2012 ==&lt;br /&gt;
&lt;br /&gt;
The next OWASP Chicago chapter will be on '''October 11th, 2012''' from 6PM to approximately 9:30PM. Space for the meeting is being graciously provided by [http://www.morningstar.com/ Morningstar] at their [http://goo.gl/maps/wfqQ8 Chicago headquarters location] (22 West Washington Street, Chicago, IL 60602). &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''This is event is completely free and open to everyone, but you must RSVP.''' Please RSVP at the following EventBrite page so that security can let you into the building: https://owaspchicago.eventbrite.com/&lt;br /&gt;
&lt;br /&gt;
When you arrive, you will need to sign in with security in the lobby of the building, who will direct you to the cafeteria for refreshments. We will then move to the Auditorium for talks. &lt;br /&gt;
&lt;br /&gt;
The schedule is as follows:&lt;br /&gt;
&lt;br /&gt;
* 6:00PM - 6:30PM - Refreshments @ Cafeteria -  Light snacks. If you want food, you can bring your own and eat here. Food is not allowed in the auditorium.&lt;br /&gt;
* 6:30PM - ~9:30PM - Talks! @ Auditorium&lt;br /&gt;
&lt;br /&gt;
Stay tuned to this page for more information.&lt;br /&gt;
&lt;br /&gt;
==Agenda==&lt;br /&gt;
&lt;br /&gt;
'''10/7 update:''' We now have two talks, which should give more time for Q/A and interaction.&lt;br /&gt;
&lt;br /&gt;
'''John Steven''' on '''Secure Password Storage: Increasing Resistance to Brute Force Attacks''' -- 6:30 - 7:30pm + Q/A time&lt;br /&gt;
&lt;br /&gt;
'''Jeff Jarmoc''' and '''Zack Fasel''' on the '''Stripe CTF 2.0''' -- ~7:45 - 8:45pm + Q/A time&lt;br /&gt;
&lt;br /&gt;
== General Information ==&lt;br /&gt;
&lt;br /&gt;
Anyone in our area interested in information security is welcome to attend. Our meetings are informal and encourage open discussion of all aspects of application security. We invite attendees to give short presentations about specific topics.&lt;br /&gt;
&lt;br /&gt;
Make sure you sign up for the mailing list to receive meeting announcements.&lt;br /&gt;
&lt;br /&gt;
We have a mailing list at: https://lists.owasp.org/mailman/listinfo/owasp-chicago&lt;br /&gt;
&lt;br /&gt;
Follow (and/or DM us) on Twitter: [https://twitter.com/owaspchicago @owaspchicago]&lt;br /&gt;
&lt;br /&gt;
If you have any questions about the Chicago chapter, please send an email to [mailto:vitaly.mclain+owasp@gmail.com Vitaly McLain].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Presentation abstracts==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Presentation Archives ==&lt;br /&gt;
&lt;br /&gt;
Bad Cocktail: Spear Phishing - Mike Zusman - Presentation slides [https://www.owasp.org/images/6/60/Zusman_Chicago_2008.pdf here]&lt;br /&gt;
&lt;br /&gt;
Making Money on the Web The Blackhat Way - Jeremiah Grossman - Presentation slides [https://www.owasp.org/images/2/24/Grossman_Chicago_2008.pdf here]&lt;br /&gt;
&lt;br /&gt;
Extreme Client-Side Exploitation - Nate McFeters - Presentation slides [http://www.blackhat.com/presentations/bh-usa-08/McFeters_Carter_Heasman/BH_US_08_Mcfeters_Carter_Heasman_Extreme_Client-Side_Exploitation.pdf here]&lt;br /&gt;
&lt;br /&gt;
Automated Thrash Testing - Andre Gironda - Presentation slides [http://www.owasp.org/images/3/32/Auto-thrash-testing.pdf here]&amp;lt;BR&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Defeating Information Leak Prevention - Eric Monti - Presentation slides [https://www.owasp.org/images/4/4a/OWASP-CHI07-Defeating_Extrusion_Detection.pdf here]&amp;lt;BR&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''[http://wittys.com/owasp/OWASP_Chicago_Thomas_Ptacek.pdf]Webapps In Name Only'''&lt;br /&gt;
Thomas Ptacek, Matasano Security&lt;br /&gt;
&lt;br /&gt;
Where modern network architecture meets legacy application design, we get &amp;quot;The Port 80 Problem&amp;quot;: vendors wrapping every conceivable network protocol in a series of POSTs and calling them &amp;quot;safe&amp;quot;. These &amp;quot;Webapps In Name Only&amp;quot; are a nightmare for application security specialists.&lt;br /&gt;
&lt;br /&gt;
In this talk, we'll discuss, with case studies, how tools from protocol reverse engineering can be brought to bear on web application security, covering the following areas:&lt;br /&gt;
&lt;br /&gt;
- Locating and Decompiling Java and .NET Code&lt;br /&gt;
- Structure and Interpretation of Binary Protocols in HTTP&lt;br /&gt;
- Protocol Debugging Tools&lt;br /&gt;
- Web App Crypto Tricks&lt;br /&gt;
&lt;br /&gt;
'''[http://wittys.com/owasp/cscott-Stronger%20Web%20Authentication-v1.0.ppt]Token-less strong authentication for web applications: A Security Review'''&lt;br /&gt;
Cory Scott, ABN AMRO&lt;br /&gt;
&lt;br /&gt;
A short presentation on the threat models and attack vectors for token-less schemes used to reduce the risk of password-only authentication, but yet do not implement &amp;quot;true&amp;quot; two-factor technologies for logistical costs or user acceptance reasons. We'll go over how device fingerprinting and IP geo-location work and discuss the pros and cons of the solutions. &lt;br /&gt;
&lt;br /&gt;
'''[https://www.owasp.org/images/8/88/Secure_Password_Storage_%40OWASPChicago.pdf]Secure Password Storage'''&lt;br /&gt;
John Steven, Cigital&lt;br /&gt;
&lt;br /&gt;
This talk discusses the pros and cons of the current practices such as salted-hashes, adaptive hashes and proposes an alternative solution for strengthening these existing practices.  The talk will discuss the cryptographic properties of the current practices, but does not require a PhD in mathematics to understand the details.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Chicago&amp;lt;/paypal&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Chicago OWASP Chapter Leaders ====&lt;br /&gt;
* [mailto:vitaly.mclain+owasp@gmail.com Vitaly McLain]&lt;br /&gt;
* Mahmood Khan&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&amp;lt;headertabs/&amp;gt;&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Illinois]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=File:Secure_Password_Storage_@OWASPChicago.pdf&amp;diff=137641</id>
		<title>File:Secure Password Storage @OWASPChicago.pdf</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=File:Secure_Password_Storage_@OWASPChicago.pdf&amp;diff=137641"/>
				<updated>2012-10-15T16:17:32Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=133463</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=133463"/>
				<updated>2012-07-25T11:31:34Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* July 2012 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra =Come see us at a chapter meeting, jump on our Google Group, or email any of us directly.&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board ===&lt;br /&gt;
Previously having had a Chapter Leader, then a Chapter &amp;quot;Program Committee&amp;quot;, the chapter is now run by a full board (alphabetical order):&lt;br /&gt;
* Jeremy Long&lt;br /&gt;
* Jack Mannino&lt;br /&gt;
* John Steven - Board Chair&lt;br /&gt;
* Ben Tomhave&lt;br /&gt;
&lt;br /&gt;
Board member responsibilities include:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre style=&amp;quot;white-space: pre-wrap;&amp;quot;&amp;gt;   * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics&lt;br /&gt;
   * Recruiting OWASP membership&lt;br /&gt;
   * Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
   * Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
   * Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
   * Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
   * Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations&lt;br /&gt;
   * Collecting and auditing use of chapter funds&lt;br /&gt;
   * Voting on chapter matters&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
fckLRFor more information on how the board was elected and what it's responsibilities are, please see:fckLRfckLR[https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;amp;authkey=CIS9zFM Chapter Board Election]fckLRfckLR|mailinglistsite=https://groups.google.com/forum/#!forum/owasp-nova|emailarchives=https://groups.google.com/forum/#!forum/owasp-nova}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
'''Date/Time:''' July 12th, 2012 @ 6:30pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: John Steven (Cigital) speaking on doing authentication and password management better&lt;br /&gt;
* Firetalks!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''[http://owaspnova071212.eventbrite.com/ Please RSVP]'''&lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
We need speakers and topics! If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== July 2012 ===&lt;br /&gt;
'''Date/Time:''' July 12th, 2012 @ 6:30pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: [https://www.owasp.org/index.php/John_Steven| John Steven] - &amp;quot;Password Storage Security&amp;quot;&lt;br /&gt;
* Firetalks!&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:'''&lt;br /&gt;
&amp;quot;Password Storage Security&amp;quot; [https://www.owasp.org/images/7/78/PSM_-_Problem_Definition.pdf|Password Storage Security.pdf] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
During the June meeting we discussed the LinkedIn password theft which was just beginning its the news cycle. We'll use the July chapter meeting to discuss issues around password hashing and a solution. While wholly different schemes for protecting passwords at rest are preferable, it's instructive to look at hashing passwords as a threat modeling exercise and take the time to follow through to a fix. &lt;br /&gt;
&lt;br /&gt;
To read up on the issue, look at my latest blog post on the topic: [http://goo.gl/sGyi8|Justice League Blog - Securing Password Storage]&lt;br /&gt;
&lt;br /&gt;
For those who were sufficiently intrigued, mystified, or inspired by the presentation on password protection at the last chapter meeting, Coursera is offering a free 6-week Stanford course on cryptography that begins on August 27th (&amp;quot;Learn about the inner workings of cryptographic primitives and how to apply this knowledge in real-world applications!&amp;quot;): [https://www.coursera.org/course/crypto|Crypto Course] &lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
&lt;br /&gt;
See  [https://www.owasp.org/index.php/John_Steven| John Steven Bio]&lt;br /&gt;
&lt;br /&gt;
=== June 2012 ===&lt;br /&gt;
'''Date/Time:''' June 7th, 2012 @ 6:30pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: Ken Johnson (LivingSocial) - &amp;quot;AppSec, Ritalin, and Failing Fast&amp;quot;&lt;br /&gt;
* Firetalks!&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:'''&lt;br /&gt;
&amp;quot;AppSec, Ritalin, and Failing Fast&amp;quot; [https://www.owasp.org/images/e/e9/Ken_Johnson_July_2012.pptx|AppSec, Ritalin, and Failing Fast.pptx] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
In early April Ken Johnson and Matt Ahrens presented a high-level overview of building an Application Security program at LivingSocial. This talk will differ in that it will focus on the granular aspects involved with introducing security into an incredibly intense development environment. The discussion will be compromised of experiences in:&lt;br /&gt;
* Developing technical solutions to solving difficult challenges&lt;br /&gt;
* Remaining proactive with an increased workload&lt;br /&gt;
* What it means to innovate&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
&lt;br /&gt;
Ken Johnson is the Application Security Manager for LivingSocial.com. Prior to joining LivingSocial.com, Ken worked in various application security consulting roles. Ken is the primary developer of the Web Exploitation Framework (wXf) and enjoys contributing to other open source projects as often as time permits. Ken has spoken at AppSec DC 2010 &amp;amp; 2012, OWASP DC and Phoenix chapters and is a member of the Attack Research Team.&lt;br /&gt;
&lt;br /&gt;
=== May 2012 ===&lt;br /&gt;
'''Date/Time:''' May 3rd, 2012 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* &amp;quot;Chill Out&amp;quot; conversations (formal talked pushed back due to logistical issues)&lt;br /&gt;
&lt;br /&gt;
=== April 2012 ===&lt;br /&gt;
'''Date/Time:''' April 16th, 2012 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''Food Sponsor:''' Jeremy Long - jeremy.long[at]owasp.org&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: &amp;quot;Malicious Code Detection or BRIC Breaking Through Static Analysis&amp;quot; by Masha Khainson (Cigital)&lt;br /&gt;
* Firetalks!&lt;br /&gt;
* ISSA NoVA Social @Champps! &amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Malicious Code Detection or BRIC Breaking Through Static Analysis&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
Malicious Code Detection or BRIC Breaking Through Static Analysis: As&lt;br /&gt;
organizations outsource development to less trustworthy providers&lt;br /&gt;
malware becomes as much a problem as introduction of honest&lt;br /&gt;
vulnerability by one's own development shop. Assessment practices&lt;br /&gt;
currently look for vulnerability within source code and a running&lt;br /&gt;
systems but these are but a few of windows of opportunity for malware&lt;br /&gt;
introduction. This presentation demonstrates an approach for&lt;br /&gt;
augmenting an existing security practice with the capability to detect&lt;br /&gt;
potentially malicious code through secure code review. First, we show&lt;br /&gt;
how to break malicious intent--often quite subtle--into concrete&lt;br /&gt;
patterns we can reliably detect. The framework then demonstrates how&lt;br /&gt;
to build suspicion around reliance of particular patterns' use in&lt;br /&gt;
concert which, increasingly, imply malicious intent. These techniques&lt;br /&gt;
will be explained through a demonstration in a real world application.&lt;br /&gt;
&lt;br /&gt;
'''Bio'''&lt;br /&gt;
Masha (a.k.a Marina) has dreamed of becoming a security consultant&lt;br /&gt;
before she ever knew what a ballerina was, and that's a good thing -&lt;br /&gt;
because she does not intend her talk to be a ballet recital. Having&lt;br /&gt;
been in software security for over seven years, Ms. Khainson has&lt;br /&gt;
delivered Architecture Risk Assessment, Secure Code Review, and&lt;br /&gt;
Ethical Hacking on many architectures, platforms and technologies.&lt;br /&gt;
Marina has also developed training materials for clients and led&lt;br /&gt;
remediation assistance teams.&lt;br /&gt;
&lt;br /&gt;
Prior to joining Cigital, Marina was a member of a research team at a&lt;br /&gt;
leading security research provider, where using disassembly as well as&lt;br /&gt;
protocol and source code analysis, she provided key information on&lt;br /&gt;
newly released vulnerabilities. Before that, Marina assisted the same&lt;br /&gt;
research team in producing detailed reports on critical malware and&lt;br /&gt;
spyware threats, as well as developing and testing content for network&lt;br /&gt;
security devices from some of the top providers of intrusion detection&lt;br /&gt;
and prevention technologies.&lt;br /&gt;
&lt;br /&gt;
Download: https://www.owasp.org/index.php/File:MCD-OWASPNoVA.pdf&lt;br /&gt;
&lt;br /&gt;
=== November 2011 ===&lt;br /&gt;
'''Date/Time:''' November 3rd, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.qinetiq.com/ QinetiQ], 2677 Prosperity Ave Fairfax, VA 22031&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # Talk: &amp;quot;Lessons Learned from the SQL Injection Challenge&amp;quot; by Ryan Barnett (Trustwave SpiderLabs)&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Lessons Learned from the SQL Injection Challenge&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
How effective are blacklist filters vs. SQL Injection attacks?  What is the failure rate vs. automated scanning or manual testing?  Are there any &amp;quot;Time-to-Bypass&amp;quot; metrics?  In an attempt to answer these questions, Trustwave SpiderLabs' Research Team (the development team behind the ModSecurity WAF and the OWASP ModSecurity Core Rule Set) held a community &amp;quot;SQL Injection Challenge&amp;quot; to test the effectiveness of the OWASP ModSecurity Core Rule Set protections.  This presentation will provide an overview of the challenge, a step-by-step walk-through of the bypass tactics used by the winners, as well as, present a new approach to attack detection using ModSecurity's Lua API to perform Bayesian analysis.&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
[mailto:ryan.barnett@owasp.org Ryan C. Barnett] (Twitter: [http://twitter.com/#!/ryancbarnett @ryancbarnett]) is a senior security researcher on Trustwave's SpiderLabs Team. He is a SANS Institute certified instructor and a member of both the Top 20 Vulnerabilities and CWE/SANS Top 25 Most Dangerous Programming Errors teams. In addition to working with SANS, he is also a WASC Member where he leads the Web Hacking Incidents Database (WHID) and Distributed Web Honeypots Projects and is also the OWASP ModSecurity Core Rule Set (CRS) project leader. Mr. Barnett has also authored a Web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== October 2011 ===&lt;br /&gt;
'''Date/Time:''' October 6th, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location/Food Sponsor:''' [http://www.cigital.com/ Cigital], 21351 Ridgetop Circle, Suite 400, Sterling, VA 20166 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # AppSec USA 2011 Recap&lt;br /&gt;
 # Talk: Jack Mannino: [http://www.slideshare.net/JackMannino/owasp-top-10-mobile-risks &amp;quot;OWASP Top 10 Mobile Risks&amp;quot;]&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2011 ===&lt;br /&gt;
&lt;br /&gt;
The September meeting was cancelled due to inclement weather (flash flooding).&lt;br /&gt;
&lt;br /&gt;
=== August 2011  ===&lt;br /&gt;
&lt;br /&gt;
We held a &amp;quot;social&amp;quot; event at Sweetwater Tavern in Sterling, VA. &lt;br /&gt;
&lt;br /&gt;
=== July 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' July 7th, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.cigital.com Cigital], Suite 400 21351 Ridgetop Circle, Dulles, VA, 20166&amp;lt;br&amp;gt; '''Food Sponsor:'''&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: iGoat - Ken Van Wyk&lt;br /&gt;
&lt;br /&gt;
=== June 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190&amp;lt;br&amp;gt; '''Food Sponsor:''' The College Board&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 &amp;quot;Insecure Direct Object References&amp;quot;]&lt;br /&gt;
 * College Board Speaker: &amp;quot;Attack-in-Depth:  Exploits of the OWASP Top Ten in Action&amp;quot;&lt;br /&gt;
 * Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
 - Jack Mannino: &amp;quot;Android Security 101&amp;quot;&lt;br /&gt;
 - Others!&lt;br /&gt;
&lt;br /&gt;
=== May 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''Food Sponsor:''' Akamai&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
 * 2011 Election (voice vote on the entire slate)&lt;br /&gt;
 * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 &amp;quot;Broken Authentication and Session Management&amp;quot;]&lt;br /&gt;
 * Speaker: Steve Witmer on A3 from the &amp;quot;breakers&amp;quot; perspective&lt;br /&gt;
 * Speaker:&amp;amp;nbsp;??? on A3 from the &amp;quot;fixers/defenders&amp;quot; perspective&lt;br /&gt;
 * Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
 * '''Update:''' All election candidates were elected by voice vote. &lt;br /&gt;
    * Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;authkey=CIS9zFM '11 Chapter Board Election Material]&lt;br /&gt;
&lt;br /&gt;
=== April 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &amp;lt;br&amp;gt; '''Food Sponsor:''' [https://www.cigital.com Cigital]&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
 * 2011 Election&lt;br /&gt;
 * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
 * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson ([https://www.owasp.org/images/9/92/Xssnotfriend-edited.pptx PPTX] or [https://www.owasp.org/images/0/06/Xssnotfriend-edited.pdf PDF])&lt;br /&gt;
 * Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])&lt;br /&gt;
 * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
 * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 &amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
  * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
  * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
  * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
  * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
  * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group]. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360! &lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective. &lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History  ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile Mobile]&lt;br /&gt;
&lt;br /&gt;
=== OWASP NoVa Members On Twitter  ===&lt;br /&gt;
&lt;br /&gt;
John Steven [http://twitter.com/m1splacedsoul http://twitter.com/m1splacedsoul] &lt;br /&gt;
&lt;br /&gt;
Jack Mannino [http://twitter.com/jack_mannino http://twitter.com/jack_mannino] &lt;br /&gt;
&lt;br /&gt;
Ben Tomhave [http://twitter.com/falconsview http://twitter.com/falconsview] &lt;br /&gt;
&lt;br /&gt;
Ken Johnson [http://twitter.com/cktricky http://twitter.com/cktricky] &lt;br /&gt;
&lt;br /&gt;
Mike Smith [http://twitter.com/rybolov http://twitter.com/rybolov] &lt;br /&gt;
&lt;br /&gt;
Trevor Hawthorn [http://twitter.com/packetwerks http://twitter.com/packetwerks] &lt;br /&gt;
&lt;br /&gt;
Joey Tyson [http://twitter.com/theharmonyguy http://twitter.com/theharmonyguy] &lt;br /&gt;
&lt;br /&gt;
Jeremy Long [http://twitter.com/ctxt http://twitter.com/ctxt] &lt;br /&gt;
&lt;br /&gt;
Ari Elias-Bachrach [http://twitter.com/angelofsecurity http://twitter.com/angelofsecurity] &lt;br /&gt;
&lt;br /&gt;
Venkat Sundaram [http://twitter.com/Vnk3889 http://twitter.com/Vnk3889] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=133462</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=133462"/>
				<updated>2012-07-25T11:30:12Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* June 2012 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra =Come see us at a chapter meeting, jump on our Google Group, or email any of us directly.&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board ===&lt;br /&gt;
Previously having had a Chapter Leader, then a Chapter &amp;quot;Program Committee&amp;quot;, the chapter is now run by a full board (alphabetical order):&lt;br /&gt;
* Jeremy Long&lt;br /&gt;
* Jack Mannino&lt;br /&gt;
* John Steven - Board Chair&lt;br /&gt;
* Ben Tomhave&lt;br /&gt;
&lt;br /&gt;
Board member responsibilities include:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre style=&amp;quot;white-space: pre-wrap;&amp;quot;&amp;gt;   * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics&lt;br /&gt;
   * Recruiting OWASP membership&lt;br /&gt;
   * Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
   * Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
   * Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
   * Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
   * Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations&lt;br /&gt;
   * Collecting and auditing use of chapter funds&lt;br /&gt;
   * Voting on chapter matters&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
fckLRFor more information on how the board was elected and what it's responsibilities are, please see:fckLRfckLR[https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;amp;authkey=CIS9zFM Chapter Board Election]fckLRfckLR|mailinglistsite=https://groups.google.com/forum/#!forum/owasp-nova|emailarchives=https://groups.google.com/forum/#!forum/owasp-nova}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
'''Date/Time:''' July 12th, 2012 @ 6:30pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: John Steven (Cigital) speaking on doing authentication and password management better&lt;br /&gt;
* Firetalks!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''[http://owaspnova071212.eventbrite.com/ Please RSVP]'''&lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
We need speakers and topics! If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== July 2012 ===&lt;br /&gt;
'''Date/Time:''' July 12th, 2012 @ 6:30pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: [https://www.owasp.org/index.php/John_Steven|John Steven] - &amp;quot;Password Storage Security&amp;quot;&lt;br /&gt;
* Firetalks!&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:'''&lt;br /&gt;
&amp;quot;Password Storage Security&amp;quot; [https://www.owasp.org/images/7/78/PSM_-_Problem_Definition.pdf|Password Storage Security.pdf] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
During the June meeting we discussed the LinkedIn password theft which was just beginning its the news cycle. We'll use the July chapter meeting to discuss issues around password hashing and a solution. While wholly different schemes for protecting passwords at rest are preferable, it's instructive to look at hashing passwords as a threat modeling exercise and take the time to follow through to a fix. &lt;br /&gt;
&lt;br /&gt;
To read up on the issue, look at my latest blog post on the topic: [http://goo.gl/sGyi8|Justice League Blog - Securing Password Storage]&lt;br /&gt;
&lt;br /&gt;
For those who were sufficiently intrigued, mystified, or inspired by the presentation on password protection at the last chapter meeting, Coursera is offering a free 6-week Stanford course on cryptography that begins on August 27th (&amp;quot;Learn about the inner workings of cryptographic primitives and how to apply this knowledge in real-world applications!&amp;quot;): [https://www.coursera.org/course/crypto|Crypto Course] &lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
&lt;br /&gt;
See  [https://www.owasp.org/index.php/John_Steven|John Steven Bio]&lt;br /&gt;
&lt;br /&gt;
=== June 2012 ===&lt;br /&gt;
'''Date/Time:''' June 7th, 2012 @ 6:30pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: Ken Johnson (LivingSocial) - &amp;quot;AppSec, Ritalin, and Failing Fast&amp;quot;&lt;br /&gt;
* Firetalks!&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:'''&lt;br /&gt;
&amp;quot;AppSec, Ritalin, and Failing Fast&amp;quot; [https://www.owasp.org/images/e/e9/Ken_Johnson_July_2012.pptx|AppSec, Ritalin, and Failing Fast.pptx] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
In early April Ken Johnson and Matt Ahrens presented a high-level overview of building an Application Security program at LivingSocial. This talk will differ in that it will focus on the granular aspects involved with introducing security into an incredibly intense development environment. The discussion will be compromised of experiences in:&lt;br /&gt;
* Developing technical solutions to solving difficult challenges&lt;br /&gt;
* Remaining proactive with an increased workload&lt;br /&gt;
* What it means to innovate&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
&lt;br /&gt;
Ken Johnson is the Application Security Manager for LivingSocial.com. Prior to joining LivingSocial.com, Ken worked in various application security consulting roles. Ken is the primary developer of the Web Exploitation Framework (wXf) and enjoys contributing to other open source projects as often as time permits. Ken has spoken at AppSec DC 2010 &amp;amp; 2012, OWASP DC and Phoenix chapters and is a member of the Attack Research Team.&lt;br /&gt;
&lt;br /&gt;
=== May 2012 ===&lt;br /&gt;
'''Date/Time:''' May 3rd, 2012 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* &amp;quot;Chill Out&amp;quot; conversations (formal talked pushed back due to logistical issues)&lt;br /&gt;
&lt;br /&gt;
=== April 2012 ===&lt;br /&gt;
'''Date/Time:''' April 16th, 2012 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''Food Sponsor:''' Jeremy Long - jeremy.long[at]owasp.org&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Talk: &amp;quot;Malicious Code Detection or BRIC Breaking Through Static Analysis&amp;quot; by Masha Khainson (Cigital)&lt;br /&gt;
* Firetalks!&lt;br /&gt;
* ISSA NoVA Social @Champps! &amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Malicious Code Detection or BRIC Breaking Through Static Analysis&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
Malicious Code Detection or BRIC Breaking Through Static Analysis: As&lt;br /&gt;
organizations outsource development to less trustworthy providers&lt;br /&gt;
malware becomes as much a problem as introduction of honest&lt;br /&gt;
vulnerability by one's own development shop. Assessment practices&lt;br /&gt;
currently look for vulnerability within source code and a running&lt;br /&gt;
systems but these are but a few of windows of opportunity for malware&lt;br /&gt;
introduction. This presentation demonstrates an approach for&lt;br /&gt;
augmenting an existing security practice with the capability to detect&lt;br /&gt;
potentially malicious code through secure code review. First, we show&lt;br /&gt;
how to break malicious intent--often quite subtle--into concrete&lt;br /&gt;
patterns we can reliably detect. The framework then demonstrates how&lt;br /&gt;
to build suspicion around reliance of particular patterns' use in&lt;br /&gt;
concert which, increasingly, imply malicious intent. These techniques&lt;br /&gt;
will be explained through a demonstration in a real world application.&lt;br /&gt;
&lt;br /&gt;
'''Bio'''&lt;br /&gt;
Masha (a.k.a Marina) has dreamed of becoming a security consultant&lt;br /&gt;
before she ever knew what a ballerina was, and that's a good thing -&lt;br /&gt;
because she does not intend her talk to be a ballet recital. Having&lt;br /&gt;
been in software security for over seven years, Ms. Khainson has&lt;br /&gt;
delivered Architecture Risk Assessment, Secure Code Review, and&lt;br /&gt;
Ethical Hacking on many architectures, platforms and technologies.&lt;br /&gt;
Marina has also developed training materials for clients and led&lt;br /&gt;
remediation assistance teams.&lt;br /&gt;
&lt;br /&gt;
Prior to joining Cigital, Marina was a member of a research team at a&lt;br /&gt;
leading security research provider, where using disassembly as well as&lt;br /&gt;
protocol and source code analysis, she provided key information on&lt;br /&gt;
newly released vulnerabilities. Before that, Marina assisted the same&lt;br /&gt;
research team in producing detailed reports on critical malware and&lt;br /&gt;
spyware threats, as well as developing and testing content for network&lt;br /&gt;
security devices from some of the top providers of intrusion detection&lt;br /&gt;
and prevention technologies.&lt;br /&gt;
&lt;br /&gt;
Download: https://www.owasp.org/index.php/File:MCD-OWASPNoVA.pdf&lt;br /&gt;
&lt;br /&gt;
=== November 2011 ===&lt;br /&gt;
'''Date/Time:''' November 3rd, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.qinetiq.com/ QinetiQ], 2677 Prosperity Ave Fairfax, VA 22031&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # Talk: &amp;quot;Lessons Learned from the SQL Injection Challenge&amp;quot; by Ryan Barnett (Trustwave SpiderLabs)&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Lessons Learned from the SQL Injection Challenge&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
How effective are blacklist filters vs. SQL Injection attacks?  What is the failure rate vs. automated scanning or manual testing?  Are there any &amp;quot;Time-to-Bypass&amp;quot; metrics?  In an attempt to answer these questions, Trustwave SpiderLabs' Research Team (the development team behind the ModSecurity WAF and the OWASP ModSecurity Core Rule Set) held a community &amp;quot;SQL Injection Challenge&amp;quot; to test the effectiveness of the OWASP ModSecurity Core Rule Set protections.  This presentation will provide an overview of the challenge, a step-by-step walk-through of the bypass tactics used by the winners, as well as, present a new approach to attack detection using ModSecurity's Lua API to perform Bayesian analysis.&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
[mailto:ryan.barnett@owasp.org Ryan C. Barnett] (Twitter: [http://twitter.com/#!/ryancbarnett @ryancbarnett]) is a senior security researcher on Trustwave's SpiderLabs Team. He is a SANS Institute certified instructor and a member of both the Top 20 Vulnerabilities and CWE/SANS Top 25 Most Dangerous Programming Errors teams. In addition to working with SANS, he is also a WASC Member where he leads the Web Hacking Incidents Database (WHID) and Distributed Web Honeypots Projects and is also the OWASP ModSecurity Core Rule Set (CRS) project leader. Mr. Barnett has also authored a Web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== October 2011 ===&lt;br /&gt;
'''Date/Time:''' October 6th, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location/Food Sponsor:''' [http://www.cigital.com/ Cigital], 21351 Ridgetop Circle, Suite 400, Sterling, VA 20166 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # AppSec USA 2011 Recap&lt;br /&gt;
 # Talk: Jack Mannino: [http://www.slideshare.net/JackMannino/owasp-top-10-mobile-risks &amp;quot;OWASP Top 10 Mobile Risks&amp;quot;]&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2011 ===&lt;br /&gt;
&lt;br /&gt;
The September meeting was cancelled due to inclement weather (flash flooding).&lt;br /&gt;
&lt;br /&gt;
=== August 2011  ===&lt;br /&gt;
&lt;br /&gt;
We held a &amp;quot;social&amp;quot; event at Sweetwater Tavern in Sterling, VA. &lt;br /&gt;
&lt;br /&gt;
=== July 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' July 7th, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.cigital.com Cigital], Suite 400 21351 Ridgetop Circle, Dulles, VA, 20166&amp;lt;br&amp;gt; '''Food Sponsor:'''&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: iGoat - Ken Van Wyk&lt;br /&gt;
&lt;br /&gt;
=== June 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190&amp;lt;br&amp;gt; '''Food Sponsor:''' The College Board&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 &amp;quot;Insecure Direct Object References&amp;quot;]&lt;br /&gt;
 * College Board Speaker: &amp;quot;Attack-in-Depth:  Exploits of the OWASP Top Ten in Action&amp;quot;&lt;br /&gt;
 * Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
 - Jack Mannino: &amp;quot;Android Security 101&amp;quot;&lt;br /&gt;
 - Others!&lt;br /&gt;
&lt;br /&gt;
=== May 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''Food Sponsor:''' Akamai&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
 * 2011 Election (voice vote on the entire slate)&lt;br /&gt;
 * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 &amp;quot;Broken Authentication and Session Management&amp;quot;]&lt;br /&gt;
 * Speaker: Steve Witmer on A3 from the &amp;quot;breakers&amp;quot; perspective&lt;br /&gt;
 * Speaker:&amp;amp;nbsp;??? on A3 from the &amp;quot;fixers/defenders&amp;quot; perspective&lt;br /&gt;
 * Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
 * '''Update:''' All election candidates were elected by voice vote. &lt;br /&gt;
    * Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;authkey=CIS9zFM '11 Chapter Board Election Material]&lt;br /&gt;
&lt;br /&gt;
=== April 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &amp;lt;br&amp;gt; '''Food Sponsor:''' [https://www.cigital.com Cigital]&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
 * 2011 Election&lt;br /&gt;
 * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
 * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson ([https://www.owasp.org/images/9/92/Xssnotfriend-edited.pptx PPTX] or [https://www.owasp.org/images/0/06/Xssnotfriend-edited.pdf PDF])&lt;br /&gt;
 * Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])&lt;br /&gt;
 * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
 * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 &amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
  * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
  * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
  * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
  * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
  * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group]. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360! &lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective. &lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History  ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile Mobile]&lt;br /&gt;
&lt;br /&gt;
=== OWASP NoVa Members On Twitter  ===&lt;br /&gt;
&lt;br /&gt;
John Steven [http://twitter.com/m1splacedsoul http://twitter.com/m1splacedsoul] &lt;br /&gt;
&lt;br /&gt;
Jack Mannino [http://twitter.com/jack_mannino http://twitter.com/jack_mannino] &lt;br /&gt;
&lt;br /&gt;
Ben Tomhave [http://twitter.com/falconsview http://twitter.com/falconsview] &lt;br /&gt;
&lt;br /&gt;
Ken Johnson [http://twitter.com/cktricky http://twitter.com/cktricky] &lt;br /&gt;
&lt;br /&gt;
Mike Smith [http://twitter.com/rybolov http://twitter.com/rybolov] &lt;br /&gt;
&lt;br /&gt;
Trevor Hawthorn [http://twitter.com/packetwerks http://twitter.com/packetwerks] &lt;br /&gt;
&lt;br /&gt;
Joey Tyson [http://twitter.com/theharmonyguy http://twitter.com/theharmonyguy] &lt;br /&gt;
&lt;br /&gt;
Jeremy Long [http://twitter.com/ctxt http://twitter.com/ctxt] &lt;br /&gt;
&lt;br /&gt;
Ari Elias-Bachrach [http://twitter.com/angelofsecurity http://twitter.com/angelofsecurity] &lt;br /&gt;
&lt;br /&gt;
Venkat Sundaram [http://twitter.com/Vnk3889 http://twitter.com/Vnk3889] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=File:PSM_-_Problem_Definition.pdf&amp;diff=133461</id>
		<title>File:PSM - Problem Definition.pdf</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=File:PSM_-_Problem_Definition.pdf&amp;diff=133461"/>
				<updated>2012-07-25T11:29:47Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=File:Ken_Johnson_July_2012.pptx&amp;diff=133460</id>
		<title>File:Ken Johnson July 2012.pptx</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=File:Ken_Johnson_July_2012.pptx&amp;diff=133460"/>
				<updated>2012-07-25T11:19:46Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=128589</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=128589"/>
				<updated>2012-04-25T20:38:31Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* April 2012 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra =Come see us at a chapter meeting, jump on our Google Group, or email any of us directly.&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board ===&lt;br /&gt;
Previously having had a Chapter Leader, then a Chapter &amp;quot;Program Committee&amp;quot;, the chapter is now run by a full board (alphabetical order):&lt;br /&gt;
&lt;br /&gt;
* Jeremy Long&lt;br /&gt;
* Jack Mannino&lt;br /&gt;
* John Steven - Board Chair&lt;br /&gt;
* Ben Tomhave&lt;br /&gt;
&lt;br /&gt;
Board member responsibilities include:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre style=&amp;quot;white-space: pre-wrap;&amp;quot;&amp;gt;   * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics&lt;br /&gt;
   * Recruiting OWASP membership&lt;br /&gt;
   * Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
   * Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
   * Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
   * Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
   * Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations&lt;br /&gt;
   * Collecting and auditing use of chapter funds&lt;br /&gt;
   * Voting on chapter matters&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
fckLRFor more information on how the board was elected and what it's responsibilities are, please see:fckLRfckLR[https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;amp;authkey=CIS9zFM Chapter Board Election]fckLRfckLR|mailinglistsite=https://groups.google.com/forum/#!forum/owasp-nova|emailarchives=https://groups.google.com/forum/#!forum/owasp-nova}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
'''Date/Time:''' May 3rd (TENTATIVE) 2012 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # Talk: &amp;quot;Starting a Security Group&amp;quot; by Ken Thompson&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''[http://owaspnova120111.eventbrite.com/ Please RSVP]'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;TBD: TBD&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
TBD.&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
TBD.&lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
We need speakers and topics! If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== April 2012 ===&lt;br /&gt;
'''Date/Time:''' April 16th, 2012 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''Food Sponsor:''' Jeremy Long - jeremy.long[at]owasp.org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # Talk: &amp;quot;Malicious Code Detection or BRIC Breaking Through Static Analysis&amp;quot; by Masha Khainson (Cigital)&lt;br /&gt;
 # Firetalks!&lt;br /&gt;
 # ISSA NoVA Social @Champps!&lt;br /&gt;
&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Malicious Code Detection or BRIC Breaking Through Static Analysis&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
Malicious Code Detection or BRIC Breaking Through Static Analysis: As&lt;br /&gt;
organizations outsource development to less trustworthy providers&lt;br /&gt;
malware becomes as much a problem as introduction of honest&lt;br /&gt;
vulnerability by one's own development shop. Assessment practices&lt;br /&gt;
currently look for vulnerability within source code and a running&lt;br /&gt;
systems but these are but a few of windows of opportunity for malware&lt;br /&gt;
introduction. This presentation demonstrates an approach for&lt;br /&gt;
augmenting an existing security practice with the capability to detect&lt;br /&gt;
potentially malicious code through secure code review. First, we show&lt;br /&gt;
how to break malicious intent--often quite subtle--into concrete&lt;br /&gt;
patterns we can reliably detect. The framework then demonstrates how&lt;br /&gt;
to build suspicion around reliance of particular patterns' use in&lt;br /&gt;
concert which, increasingly, imply malicious intent. These techniques&lt;br /&gt;
will be explained through a demonstration in a real world application.&lt;br /&gt;
&lt;br /&gt;
'''Bio'''&lt;br /&gt;
Masha (a.k.a Marina) has dreamed of becoming a security consultant&lt;br /&gt;
before she ever knew what a ballerina was, and that's a good thing -&lt;br /&gt;
because she does not intend her talk to be a ballet recital. Having&lt;br /&gt;
been in software security for over seven years, Ms. Khainson has&lt;br /&gt;
delivered Architecture Risk Assessment, Secure Code Review, and&lt;br /&gt;
Ethical Hacking on many architectures, platforms and technologies.&lt;br /&gt;
Marina has also developed training materials for clients and led&lt;br /&gt;
remediation assistance teams.&lt;br /&gt;
&lt;br /&gt;
Prior to joining Cigital, Marina was a member of a research team at a&lt;br /&gt;
leading security research provider, where using disassembly as well as&lt;br /&gt;
protocol and source code analysis, she provided key information on&lt;br /&gt;
newly released vulnerabilities. Before that, Marina assisted the same&lt;br /&gt;
research team in producing detailed reports on critical malware and&lt;br /&gt;
spyware threats, as well as developing and testing content for network&lt;br /&gt;
security devices from some of the top providers of intrusion detection&lt;br /&gt;
and prevention technologies.&lt;br /&gt;
&lt;br /&gt;
Download: https://www.owasp.org/index.php/File:MCD-OWASPNoVA.pdf&lt;br /&gt;
&lt;br /&gt;
=== November 2011 ===&lt;br /&gt;
'''Date/Time:''' November 3rd, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.qinetiq.com/ QinetiQ], 2677 Prosperity Ave Fairfax, VA 22031&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # Talk: &amp;quot;Lessons Learned from the SQL Injection Challenge&amp;quot; by Ryan Barnett (Trustwave SpiderLabs)&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Lessons Learned from the SQL Injection Challenge&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
How effective are blacklist filters vs. SQL Injection attacks?  What is the failure rate vs. automated scanning or manual testing?  Are there any &amp;quot;Time-to-Bypass&amp;quot; metrics?  In an attempt to answer these questions, Trustwave SpiderLabs' Research Team (the development team behind the ModSecurity WAF and the OWASP ModSecurity Core Rule Set) held a community &amp;quot;SQL Injection Challenge&amp;quot; to test the effectiveness of the OWASP ModSecurity Core Rule Set protections.  This presentation will provide an overview of the challenge, a step-by-step walk-through of the bypass tactics used by the winners, as well as, present a new approach to attack detection using ModSecurity's Lua API to perform Bayesian analysis.&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
[mailto:ryan.barnett@owasp.org Ryan C. Barnett] (Twitter: [http://twitter.com/#!/ryancbarnett @ryancbarnett]) is a senior security researcher on Trustwave's SpiderLabs Team. He is a SANS Institute certified instructor and a member of both the Top 20 Vulnerabilities and CWE/SANS Top 25 Most Dangerous Programming Errors teams. In addition to working with SANS, he is also a WASC Member where he leads the Web Hacking Incidents Database (WHID) and Distributed Web Honeypots Projects and is also the OWASP ModSecurity Core Rule Set (CRS) project leader. Mr. Barnett has also authored a Web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== October 2011 ===&lt;br /&gt;
'''Date/Time:''' October 6th, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location/Food Sponsor:''' [http://www.cigital.com/ Cigital], 21351 Ridgetop Circle, Suite 400, Sterling, VA 20166 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # AppSec USA 2011 Recap&lt;br /&gt;
 # Talk: Jack Mannino: [http://www.slideshare.net/JackMannino/owasp-top-10-mobile-risks &amp;quot;OWASP Top 10 Mobile Risks&amp;quot;]&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2011 ===&lt;br /&gt;
&lt;br /&gt;
The September meeting was cancelled due to inclement weather (flash flooding).&lt;br /&gt;
&lt;br /&gt;
=== August 2011  ===&lt;br /&gt;
&lt;br /&gt;
We held a &amp;quot;social&amp;quot; event at Sweetwater Tavern in Sterling, VA. &lt;br /&gt;
&lt;br /&gt;
=== July 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' July 7th, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.cigital.com Cigital], Suite 400 21351 Ridgetop Circle, Dulles, VA, 20166&amp;lt;br&amp;gt; '''Food Sponsor:'''&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: iGoat - Ken Van Wyk&lt;br /&gt;
&lt;br /&gt;
=== June 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190&amp;lt;br&amp;gt; '''Food Sponsor:''' The College Board&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 &amp;quot;Insecure Direct Object References&amp;quot;]&lt;br /&gt;
 * College Board Speaker: &amp;quot;Attack-in-Depth:  Exploits of the OWASP Top Ten in Action&amp;quot;&lt;br /&gt;
 * Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
 - Jack Mannino: &amp;quot;Android Security 101&amp;quot;&lt;br /&gt;
 - Others!&lt;br /&gt;
&lt;br /&gt;
=== May 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''Food Sponsor:''' Akamai&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
 * 2011 Election (voice vote on the entire slate)&lt;br /&gt;
 * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 &amp;quot;Broken Authentication and Session Management&amp;quot;]&lt;br /&gt;
 * Speaker: Steve Witmer on A3 from the &amp;quot;breakers&amp;quot; perspective&lt;br /&gt;
 * Speaker:&amp;amp;nbsp;??? on A3 from the &amp;quot;fixers/defenders&amp;quot; perspective&lt;br /&gt;
 * Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
 * '''Update:''' All election candidates were elected by voice vote. &lt;br /&gt;
    * Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;authkey=CIS9zFM '11 Chapter Board Election Material]&lt;br /&gt;
&lt;br /&gt;
=== April 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &amp;lt;br&amp;gt; '''Food Sponsor:''' [https://www.cigital.com Cigital]&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
 * 2011 Election&lt;br /&gt;
 * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
 * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson ([https://www.owasp.org/images/9/92/Xssnotfriend-edited.pptx PPTX] or [https://www.owasp.org/images/0/06/Xssnotfriend-edited.pdf PDF])&lt;br /&gt;
 * Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])&lt;br /&gt;
 * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
 * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 &amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
  * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
  * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
  * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
  * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
  * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group]. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360! &lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective. &lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History  ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile Mobile]&lt;br /&gt;
&lt;br /&gt;
=== OWASP NoVa Members On Twitter  ===&lt;br /&gt;
&lt;br /&gt;
John Steven [http://twitter.com/m1splacedsoul http://twitter.com/m1splacedsoul] &lt;br /&gt;
&lt;br /&gt;
Jack Mannino [http://twitter.com/jack_mannino http://twitter.com/jack_mannino] &lt;br /&gt;
&lt;br /&gt;
Ben Tomhave [http://twitter.com/falconsview http://twitter.com/falconsview] &lt;br /&gt;
&lt;br /&gt;
Ken Johnson [http://twitter.com/cktricky http://twitter.com/cktricky] &lt;br /&gt;
&lt;br /&gt;
Mike Smith [http://twitter.com/rybolov http://twitter.com/rybolov] &lt;br /&gt;
&lt;br /&gt;
Trevor Hawthorn [http://twitter.com/packetwerks http://twitter.com/packetwerks] &lt;br /&gt;
&lt;br /&gt;
Joey Tyson [http://twitter.com/theharmonyguy http://twitter.com/theharmonyguy] &lt;br /&gt;
&lt;br /&gt;
Jeremy Long [http://twitter.com/ctxt http://twitter.com/ctxt] &lt;br /&gt;
&lt;br /&gt;
Ari Elias-Bachrach [http://twitter.com/angelofsecurity http://twitter.com/angelofsecurity] &lt;br /&gt;
&lt;br /&gt;
Venkat Sundaram [http://twitter.com/Vnk3889 http://twitter.com/Vnk3889] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=128588</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=128588"/>
				<updated>2012-04-25T20:37:10Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra =Come see us at a chapter meeting, jump on our Google Group, or email any of us directly.&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board ===&lt;br /&gt;
Previously having had a Chapter Leader, then a Chapter &amp;quot;Program Committee&amp;quot;, the chapter is now run by a full board (alphabetical order):&lt;br /&gt;
&lt;br /&gt;
* Jeremy Long&lt;br /&gt;
* Jack Mannino&lt;br /&gt;
* John Steven - Board Chair&lt;br /&gt;
* Ben Tomhave&lt;br /&gt;
&lt;br /&gt;
Board member responsibilities include:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre style=&amp;quot;white-space: pre-wrap;&amp;quot;&amp;gt;   * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics&lt;br /&gt;
   * Recruiting OWASP membership&lt;br /&gt;
   * Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
   * Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
   * Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
   * Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
   * Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations&lt;br /&gt;
   * Collecting and auditing use of chapter funds&lt;br /&gt;
   * Voting on chapter matters&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
fckLRFor more information on how the board was elected and what it's responsibilities are, please see:fckLRfckLR[https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;amp;authkey=CIS9zFM Chapter Board Election]fckLRfckLR|mailinglistsite=https://groups.google.com/forum/#!forum/owasp-nova|emailarchives=https://groups.google.com/forum/#!forum/owasp-nova}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
'''Date/Time:''' May 3rd (TENTATIVE) 2012 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # Talk: &amp;quot;Starting a Security Group&amp;quot; by Ken Thompson&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''[http://owaspnova120111.eventbrite.com/ Please RSVP]'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;TBD: TBD&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
TBD.&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
TBD.&lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
We need speakers and topics! If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== April 2012 ===&lt;br /&gt;
'''Date/Time:''' April 16th, 2012 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
'''Food Sponsor:''' Jeremy Long - jeremy.long[at]owasp.org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # Talk: &amp;quot;Malicious Code Detection or BRIC Breaking Through Static Analysis&amp;quot; by Masha Khainson (Cigital)&lt;br /&gt;
 # Firetalks!&lt;br /&gt;
 # ISSA NoVA Social @Champps!&lt;br /&gt;
&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Malicious Code Detection or BRIC Breaking Through Static Analysis&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
Malicious Code Detection or BRIC Breaking Through Static Analysis: As&lt;br /&gt;
organizations outsource development to less trustworthy providers&lt;br /&gt;
malware becomes as much a problem as introduction of honest&lt;br /&gt;
vulnerability by one's own development shop. Assessment practices&lt;br /&gt;
currently look for vulnerability within source code and a running&lt;br /&gt;
systems but these are but a few of windows of opportunity for malware&lt;br /&gt;
introduction. This presentation demonstrates an approach for&lt;br /&gt;
augmenting an existing security practice with the capability to detect&lt;br /&gt;
potentially malicious code through secure code review. First, we show&lt;br /&gt;
how to break malicious intent--often quite subtle--into concrete&lt;br /&gt;
patterns we can reliably detect. The framework then demonstrates how&lt;br /&gt;
to build suspicion around reliance of particular patterns' use in&lt;br /&gt;
concert which, increasingly, imply malicious intent. These techniques&lt;br /&gt;
will be explained through a demonstration in a real world application.&lt;br /&gt;
&lt;br /&gt;
'''Bio'''&lt;br /&gt;
Masha (a.k.a Marina) has dreamed of becoming a security consultant&lt;br /&gt;
before she ever knew what a ballerina was, and that's a good thing -&lt;br /&gt;
because she does not intend her talk to be a ballet recital. Having&lt;br /&gt;
been in software security for over seven years, Ms. Khainson has&lt;br /&gt;
delivered Architecture Risk Assessment, Secure Code Review, and&lt;br /&gt;
Ethical Hacking on many architectures, platforms and technologies.&lt;br /&gt;
Marina has also developed training materials for clients and led&lt;br /&gt;
remediation assistance teams.&lt;br /&gt;
&lt;br /&gt;
Prior to joining Cigital, Marina was a member of a research team at a&lt;br /&gt;
leading security research provider, where using disassembly as well as&lt;br /&gt;
protocol and source code analysis, she provided key information on&lt;br /&gt;
newly released vulnerabilities. Before that, Marina assisted the same&lt;br /&gt;
research team in producing detailed reports on critical malware and&lt;br /&gt;
spyware threats, as well as developing and testing content for network&lt;br /&gt;
security devices from some of the top providers of intrusion detection&lt;br /&gt;
and prevention technologies.&lt;br /&gt;
&lt;br /&gt;
Download: https://www.owasp.org/index.php/File:MCD-OWASPNoVA.pdf&lt;br /&gt;
&lt;br /&gt;
=== November 2011 ===&lt;br /&gt;
'''Date/Time:''' November 3rd, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.qinetiq.com/ QinetiQ], 2677 Prosperity Ave Fairfax, VA 22031&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # Talk: &amp;quot;Lessons Learned from the SQL Injection Challenge&amp;quot; by Ryan Barnett (Trustwave SpiderLabs)&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Lessons Learned from the SQL Injection Challenge&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
How effective are blacklist filters vs. SQL Injection attacks?  What is the failure rate vs. automated scanning or manual testing?  Are there any &amp;quot;Time-to-Bypass&amp;quot; metrics?  In an attempt to answer these questions, Trustwave SpiderLabs' Research Team (the development team behind the ModSecurity WAF and the OWASP ModSecurity Core Rule Set) held a community &amp;quot;SQL Injection Challenge&amp;quot; to test the effectiveness of the OWASP ModSecurity Core Rule Set protections.  This presentation will provide an overview of the challenge, a step-by-step walk-through of the bypass tactics used by the winners, as well as, present a new approach to attack detection using ModSecurity's Lua API to perform Bayesian analysis.&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
[mailto:ryan.barnett@owasp.org Ryan C. Barnett] (Twitter: [http://twitter.com/#!/ryancbarnett @ryancbarnett]) is a senior security researcher on Trustwave's SpiderLabs Team. He is a SANS Institute certified instructor and a member of both the Top 20 Vulnerabilities and CWE/SANS Top 25 Most Dangerous Programming Errors teams. In addition to working with SANS, he is also a WASC Member where he leads the Web Hacking Incidents Database (WHID) and Distributed Web Honeypots Projects and is also the OWASP ModSecurity Core Rule Set (CRS) project leader. Mr. Barnett has also authored a Web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== October 2011 ===&lt;br /&gt;
'''Date/Time:''' October 6th, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location/Food Sponsor:''' [http://www.cigital.com/ Cigital], 21351 Ridgetop Circle, Suite 400, Sterling, VA 20166 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # AppSec USA 2011 Recap&lt;br /&gt;
 # Talk: Jack Mannino: [http://www.slideshare.net/JackMannino/owasp-top-10-mobile-risks &amp;quot;OWASP Top 10 Mobile Risks&amp;quot;]&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2011 ===&lt;br /&gt;
&lt;br /&gt;
The September meeting was cancelled due to inclement weather (flash flooding).&lt;br /&gt;
&lt;br /&gt;
=== August 2011  ===&lt;br /&gt;
&lt;br /&gt;
We held a &amp;quot;social&amp;quot; event at Sweetwater Tavern in Sterling, VA. &lt;br /&gt;
&lt;br /&gt;
=== July 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' July 7th, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.cigital.com Cigital], Suite 400 21351 Ridgetop Circle, Dulles, VA, 20166&amp;lt;br&amp;gt; '''Food Sponsor:'''&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: iGoat - Ken Van Wyk&lt;br /&gt;
&lt;br /&gt;
=== June 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190&amp;lt;br&amp;gt; '''Food Sponsor:''' The College Board&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 &amp;quot;Insecure Direct Object References&amp;quot;]&lt;br /&gt;
 * College Board Speaker: &amp;quot;Attack-in-Depth:  Exploits of the OWASP Top Ten in Action&amp;quot;&lt;br /&gt;
 * Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
 - Jack Mannino: &amp;quot;Android Security 101&amp;quot;&lt;br /&gt;
 - Others!&lt;br /&gt;
&lt;br /&gt;
=== May 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''Food Sponsor:''' Akamai&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
 * 2011 Election (voice vote on the entire slate)&lt;br /&gt;
 * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 &amp;quot;Broken Authentication and Session Management&amp;quot;]&lt;br /&gt;
 * Speaker: Steve Witmer on A3 from the &amp;quot;breakers&amp;quot; perspective&lt;br /&gt;
 * Speaker:&amp;amp;nbsp;??? on A3 from the &amp;quot;fixers/defenders&amp;quot; perspective&lt;br /&gt;
 * Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
 * '''Update:''' All election candidates were elected by voice vote. &lt;br /&gt;
    * Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;authkey=CIS9zFM '11 Chapter Board Election Material]&lt;br /&gt;
&lt;br /&gt;
=== April 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &amp;lt;br&amp;gt; '''Food Sponsor:''' [https://www.cigital.com Cigital]&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
 * 2011 Election&lt;br /&gt;
 * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
 * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson ([https://www.owasp.org/images/9/92/Xssnotfriend-edited.pptx PPTX] or [https://www.owasp.org/images/0/06/Xssnotfriend-edited.pdf PDF])&lt;br /&gt;
 * Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])&lt;br /&gt;
 * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
 * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 &amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
  * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
  * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
  * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
  * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
  * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group]. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360! &lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective. &lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History  ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile Mobile]&lt;br /&gt;
&lt;br /&gt;
=== OWASP NoVa Members On Twitter  ===&lt;br /&gt;
&lt;br /&gt;
John Steven [http://twitter.com/m1splacedsoul http://twitter.com/m1splacedsoul] &lt;br /&gt;
&lt;br /&gt;
Jack Mannino [http://twitter.com/jack_mannino http://twitter.com/jack_mannino] &lt;br /&gt;
&lt;br /&gt;
Ben Tomhave [http://twitter.com/falconsview http://twitter.com/falconsview] &lt;br /&gt;
&lt;br /&gt;
Ken Johnson [http://twitter.com/cktricky http://twitter.com/cktricky] &lt;br /&gt;
&lt;br /&gt;
Mike Smith [http://twitter.com/rybolov http://twitter.com/rybolov] &lt;br /&gt;
&lt;br /&gt;
Trevor Hawthorn [http://twitter.com/packetwerks http://twitter.com/packetwerks] &lt;br /&gt;
&lt;br /&gt;
Joey Tyson [http://twitter.com/theharmonyguy http://twitter.com/theharmonyguy] &lt;br /&gt;
&lt;br /&gt;
Jeremy Long [http://twitter.com/ctxt http://twitter.com/ctxt] &lt;br /&gt;
&lt;br /&gt;
Ari Elias-Bachrach [http://twitter.com/angelofsecurity http://twitter.com/angelofsecurity] &lt;br /&gt;
&lt;br /&gt;
Venkat Sundaram [http://twitter.com/Vnk3889 http://twitter.com/Vnk3889] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=128587</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=128587"/>
				<updated>2012-04-25T20:31:39Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* April 2012 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra =Come see us at a chapter meeting, jump on our Google Group, or email any of us directly.&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board ===&lt;br /&gt;
Previously having had a Chapter Leader, then a Chapter &amp;quot;Program Committee&amp;quot;, the chapter is now run by a full board (alphabetical order):&lt;br /&gt;
&lt;br /&gt;
* Jeremy Long&lt;br /&gt;
* Jack Mannino&lt;br /&gt;
* John Steven - Board Chair&lt;br /&gt;
* Ben Tomhave&lt;br /&gt;
&lt;br /&gt;
Board member responsibilities include:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre style=&amp;quot;white-space: pre-wrap;&amp;quot;&amp;gt;   * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics&lt;br /&gt;
   * Recruiting OWASP membership&lt;br /&gt;
   * Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
   * Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
   * Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
   * Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
   * Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations&lt;br /&gt;
   * Collecting and auditing use of chapter funds&lt;br /&gt;
   * Voting on chapter matters&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
fckLRFor more information on how the board was elected and what it's responsibilities are, please see:fckLRfckLR[https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;amp;authkey=CIS9zFM Chapter Board Election]fckLRfckLR|mailinglistsite=https://groups.google.com/forum/#!forum/owasp-nova|emailarchives=https://groups.google.com/forum/#!forum/owasp-nova}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
'''Date/Time:''' December 1st, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.qinetiq.com/ QinetiQ], 11091 Sunset Hills Road, ''1st floor (Rooms 207/208)'', Reston VA 20190&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # Talk: &amp;quot;Cloud Control: Assurance in a Massively Scalable World&amp;quot; by Ben Tomhave&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''[http://owaspnova120111.eventbrite.com/ Please RSVP]'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Cloud Control: Assurance in a Massively Scalable World&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
Ubiquitous access to data and applications is here. No longer are our resources confined to enterprise networks and data centers of our own making. Rather, applications and platforms are now available on-demand, anywhere, anytime, to virtually anybody. Moreover, these environments can scale on demand, automating what has traditionally required expertise in system design and capacity planning. Assuring security in this environment poses new and evolving challenges. While they may resemble the same obstacles we've been managing for decades, they are increasingly more difficult to address. Now, more than ever, companies need to extend their governance, risk, and compliance initiatives to take cloud-related strategies and initiatives into account to proactively protect their data and their bottom line.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
[mailto:benjamin.tomhave@owasp.org Ben Tomhave] (Twitter: [http://twitter.com/#!/falconsview @falconsview]) Ben Tomhave, MS, CISSP, helps global enterprises, SMBs and service partners unlock the real promise of integrated governance, risk and compliance in his current role as Principal Consultant for LockPath, a market-changing GRC software company. A distinguished author and experienced speaker, he currently serves on the OWASP NoVA chapter board and as the co-vice-chair of the ABA InfoSec Committee. He is also a member of ISSA and the IEEE Computer Society, and earned a MS in Engineering Management from The George Washington University with an InfoSec Management concentration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
We need speakers and topics! If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== April 2012 ===&lt;br /&gt;
'''Date/Time:''' April 16th, 2012 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # Talk: &amp;quot;Malicious Code Detection or BRIC Breaking Through Static Analysis&amp;quot; by Masha Khainson (Cigital)&lt;br /&gt;
 # Firetalks!&lt;br /&gt;
 # ISSA NoVA Social @Champps!&lt;br /&gt;
&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Malicious Code Detection or BRIC Breaking Through Static Analysis&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
Malicious Code Detection or BRIC Breaking Through Static Analysis: As&lt;br /&gt;
organizations outsource development to less trustworthy providers&lt;br /&gt;
malware becomes as much a problem as introduction of honest&lt;br /&gt;
vulnerability by one's own development shop. Assessment practices&lt;br /&gt;
currently look for vulnerability within source code and a running&lt;br /&gt;
systems but these are but a few of windows of opportunity for malware&lt;br /&gt;
introduction. This presentation demonstrates an approach for&lt;br /&gt;
augmenting an existing security practice with the capability to detect&lt;br /&gt;
potentially malicious code through secure code review. First, we show&lt;br /&gt;
how to break malicious intent--often quite subtle--into concrete&lt;br /&gt;
patterns we can reliably detect. The framework then demonstrates how&lt;br /&gt;
to build suspicion around reliance of particular patterns' use in&lt;br /&gt;
concert which, increasingly, imply malicious intent. These techniques&lt;br /&gt;
will be explained through a demonstration in a real world application.&lt;br /&gt;
&lt;br /&gt;
'''Bio'''&lt;br /&gt;
Masha (a.k.a Marina) has dreamed of becoming a security consultant&lt;br /&gt;
before she ever knew what a ballerina was, and that's a good thing -&lt;br /&gt;
because she does not intend her talk to be a ballet recital. Having&lt;br /&gt;
been in software security for over seven years, Ms. Khainson has&lt;br /&gt;
delivered Architecture Risk Assessment, Secure Code Review, and&lt;br /&gt;
Ethical Hacking on many architectures, platforms and technologies.&lt;br /&gt;
Marina has also developed training materials for clients and led&lt;br /&gt;
remediation assistance teams.&lt;br /&gt;
&lt;br /&gt;
Prior to joining Cigital, Marina was a member of a research team at a&lt;br /&gt;
leading security research provider, where using disassembly as well as&lt;br /&gt;
protocol and source code analysis, she provided key information on&lt;br /&gt;
newly released vulnerabilities. Before that, Marina assisted the same&lt;br /&gt;
research team in producing detailed reports on critical malware and&lt;br /&gt;
spyware threats, as well as developing and testing content for network&lt;br /&gt;
security devices from some of the top providers of intrusion detection&lt;br /&gt;
and prevention technologies.&lt;br /&gt;
&lt;br /&gt;
Download: https://www.owasp.org/index.php/File:MCD-OWASPNoVA.pdf&lt;br /&gt;
&lt;br /&gt;
=== November 2011 ===&lt;br /&gt;
'''Date/Time:''' November 3rd, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.qinetiq.com/ QinetiQ], 2677 Prosperity Ave Fairfax, VA 22031&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # Talk: &amp;quot;Lessons Learned from the SQL Injection Challenge&amp;quot; by Ryan Barnett (Trustwave SpiderLabs)&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Lessons Learned from the SQL Injection Challenge&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
How effective are blacklist filters vs. SQL Injection attacks?  What is the failure rate vs. automated scanning or manual testing?  Are there any &amp;quot;Time-to-Bypass&amp;quot; metrics?  In an attempt to answer these questions, Trustwave SpiderLabs' Research Team (the development team behind the ModSecurity WAF and the OWASP ModSecurity Core Rule Set) held a community &amp;quot;SQL Injection Challenge&amp;quot; to test the effectiveness of the OWASP ModSecurity Core Rule Set protections.  This presentation will provide an overview of the challenge, a step-by-step walk-through of the bypass tactics used by the winners, as well as, present a new approach to attack detection using ModSecurity's Lua API to perform Bayesian analysis.&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
[mailto:ryan.barnett@owasp.org Ryan C. Barnett] (Twitter: [http://twitter.com/#!/ryancbarnett @ryancbarnett]) is a senior security researcher on Trustwave's SpiderLabs Team. He is a SANS Institute certified instructor and a member of both the Top 20 Vulnerabilities and CWE/SANS Top 25 Most Dangerous Programming Errors teams. In addition to working with SANS, he is also a WASC Member where he leads the Web Hacking Incidents Database (WHID) and Distributed Web Honeypots Projects and is also the OWASP ModSecurity Core Rule Set (CRS) project leader. Mr. Barnett has also authored a Web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== October 2011 ===&lt;br /&gt;
'''Date/Time:''' October 6th, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location/Food Sponsor:''' [http://www.cigital.com/ Cigital], 21351 Ridgetop Circle, Suite 400, Sterling, VA 20166 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # AppSec USA 2011 Recap&lt;br /&gt;
 # Talk: Jack Mannino: [http://www.slideshare.net/JackMannino/owasp-top-10-mobile-risks &amp;quot;OWASP Top 10 Mobile Risks&amp;quot;]&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2011 ===&lt;br /&gt;
&lt;br /&gt;
The September meeting was cancelled due to inclement weather (flash flooding).&lt;br /&gt;
&lt;br /&gt;
=== August 2011  ===&lt;br /&gt;
&lt;br /&gt;
We held a &amp;quot;social&amp;quot; event at Sweetwater Tavern in Sterling, VA. &lt;br /&gt;
&lt;br /&gt;
=== July 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' July 7th, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.cigital.com Cigital], Suite 400 21351 Ridgetop Circle, Dulles, VA, 20166&amp;lt;br&amp;gt; '''Food Sponsor:'''&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: iGoat - Ken Van Wyk&lt;br /&gt;
&lt;br /&gt;
=== June 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190&amp;lt;br&amp;gt; '''Food Sponsor:''' The College Board&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 &amp;quot;Insecure Direct Object References&amp;quot;]&lt;br /&gt;
 * College Board Speaker: &amp;quot;Attack-in-Depth:  Exploits of the OWASP Top Ten in Action&amp;quot;&lt;br /&gt;
 * Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
 - Jack Mannino: &amp;quot;Android Security 101&amp;quot;&lt;br /&gt;
 - Others!&lt;br /&gt;
&lt;br /&gt;
=== May 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''Food Sponsor:''' Akamai&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
 * 2011 Election (voice vote on the entire slate)&lt;br /&gt;
 * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 &amp;quot;Broken Authentication and Session Management&amp;quot;]&lt;br /&gt;
 * Speaker: Steve Witmer on A3 from the &amp;quot;breakers&amp;quot; perspective&lt;br /&gt;
 * Speaker:&amp;amp;nbsp;??? on A3 from the &amp;quot;fixers/defenders&amp;quot; perspective&lt;br /&gt;
 * Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
 * '''Update:''' All election candidates were elected by voice vote. &lt;br /&gt;
    * Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;authkey=CIS9zFM '11 Chapter Board Election Material]&lt;br /&gt;
&lt;br /&gt;
=== April 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &amp;lt;br&amp;gt; '''Food Sponsor:''' [https://www.cigital.com Cigital]&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
 * 2011 Election&lt;br /&gt;
 * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
 * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson ([https://www.owasp.org/images/9/92/Xssnotfriend-edited.pptx PPTX] or [https://www.owasp.org/images/0/06/Xssnotfriend-edited.pdf PDF])&lt;br /&gt;
 * Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])&lt;br /&gt;
 * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
 * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 &amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
  * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
  * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
  * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
  * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
  * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group]. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360! &lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective. &lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History  ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile Mobile]&lt;br /&gt;
&lt;br /&gt;
=== OWASP NoVa Members On Twitter  ===&lt;br /&gt;
&lt;br /&gt;
John Steven [http://twitter.com/m1splacedsoul http://twitter.com/m1splacedsoul] &lt;br /&gt;
&lt;br /&gt;
Jack Mannino [http://twitter.com/jack_mannino http://twitter.com/jack_mannino] &lt;br /&gt;
&lt;br /&gt;
Ben Tomhave [http://twitter.com/falconsview http://twitter.com/falconsview] &lt;br /&gt;
&lt;br /&gt;
Ken Johnson [http://twitter.com/cktricky http://twitter.com/cktricky] &lt;br /&gt;
&lt;br /&gt;
Mike Smith [http://twitter.com/rybolov http://twitter.com/rybolov] &lt;br /&gt;
&lt;br /&gt;
Trevor Hawthorn [http://twitter.com/packetwerks http://twitter.com/packetwerks] &lt;br /&gt;
&lt;br /&gt;
Joey Tyson [http://twitter.com/theharmonyguy http://twitter.com/theharmonyguy] &lt;br /&gt;
&lt;br /&gt;
Jeremy Long [http://twitter.com/ctxt http://twitter.com/ctxt] &lt;br /&gt;
&lt;br /&gt;
Ari Elias-Bachrach [http://twitter.com/angelofsecurity http://twitter.com/angelofsecurity] &lt;br /&gt;
&lt;br /&gt;
Venkat Sundaram [http://twitter.com/Vnk3889 http://twitter.com/Vnk3889] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=File:MCD-OWASPNoVA.pdf&amp;diff=128586</id>
		<title>File:MCD-OWASPNoVA.pdf</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=File:MCD-OWASPNoVA.pdf&amp;diff=128586"/>
				<updated>2012-04-25T20:28:36Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=128585</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=128585"/>
				<updated>2012-04-25T20:22:57Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* November 2011 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra =Come see us at a chapter meeting, jump on our Google Group, or email any of us directly.&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board ===&lt;br /&gt;
Previously having had a Chapter Leader, then a Chapter &amp;quot;Program Committee&amp;quot;, the chapter is now run by a full board (alphabetical order):&lt;br /&gt;
&lt;br /&gt;
* Jeremy Long&lt;br /&gt;
* Jack Mannino&lt;br /&gt;
* John Steven - Board Chair&lt;br /&gt;
* Ben Tomhave&lt;br /&gt;
&lt;br /&gt;
Board member responsibilities include:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre style=&amp;quot;white-space: pre-wrap;&amp;quot;&amp;gt;   * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics&lt;br /&gt;
   * Recruiting OWASP membership&lt;br /&gt;
   * Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
   * Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
   * Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
   * Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
   * Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations&lt;br /&gt;
   * Collecting and auditing use of chapter funds&lt;br /&gt;
   * Voting on chapter matters&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
fckLRFor more information on how the board was elected and what it's responsibilities are, please see:fckLRfckLR[https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;amp;authkey=CIS9zFM Chapter Board Election]fckLRfckLR|mailinglistsite=https://groups.google.com/forum/#!forum/owasp-nova|emailarchives=https://groups.google.com/forum/#!forum/owasp-nova}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
'''Date/Time:''' December 1st, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.qinetiq.com/ QinetiQ], 11091 Sunset Hills Road, ''1st floor (Rooms 207/208)'', Reston VA 20190&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # Talk: &amp;quot;Cloud Control: Assurance in a Massively Scalable World&amp;quot; by Ben Tomhave&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''[http://owaspnova120111.eventbrite.com/ Please RSVP]'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Cloud Control: Assurance in a Massively Scalable World&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
Ubiquitous access to data and applications is here. No longer are our resources confined to enterprise networks and data centers of our own making. Rather, applications and platforms are now available on-demand, anywhere, anytime, to virtually anybody. Moreover, these environments can scale on demand, automating what has traditionally required expertise in system design and capacity planning. Assuring security in this environment poses new and evolving challenges. While they may resemble the same obstacles we've been managing for decades, they are increasingly more difficult to address. Now, more than ever, companies need to extend their governance, risk, and compliance initiatives to take cloud-related strategies and initiatives into account to proactively protect their data and their bottom line.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
[mailto:benjamin.tomhave@owasp.org Ben Tomhave] (Twitter: [http://twitter.com/#!/falconsview @falconsview]) Ben Tomhave, MS, CISSP, helps global enterprises, SMBs and service partners unlock the real promise of integrated governance, risk and compliance in his current role as Principal Consultant for LockPath, a market-changing GRC software company. A distinguished author and experienced speaker, he currently serves on the OWASP NoVA chapter board and as the co-vice-chair of the ABA InfoSec Committee. He is also a member of ISSA and the IEEE Computer Society, and earned a MS in Engineering Management from The George Washington University with an InfoSec Management concentration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
We need speakers and topics! If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== April 2012 ===&lt;br /&gt;
'''Date/Time:''' April 16th, 2012 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # Talk: &amp;quot;Malicious Code Detection or BRIC Breaking Through Static Analysis&amp;quot; by Masha Khainson (Cigital)&lt;br /&gt;
 # Firetalks!&lt;br /&gt;
 # ISSA NoVA Social @Champps!&lt;br /&gt;
&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Malicious Code Detection or BRIC Breaking Through Static Analysis&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
Malicious Code Detection or BRIC Breaking Through Static Analysis: As&lt;br /&gt;
organizations outsource development to less trustworthy providers&lt;br /&gt;
malware becomes as much a problem as introduction of honest&lt;br /&gt;
vulnerability by one's own development shop. Assessment practices&lt;br /&gt;
currently look for vulnerability within source code and a running&lt;br /&gt;
systems but these are but a few of windows of opportunity for malware&lt;br /&gt;
introduction. This presentation demonstrates an approach for&lt;br /&gt;
augmenting an existing security practice with the capability to detect&lt;br /&gt;
potentially malicious code through secure code review. First, we show&lt;br /&gt;
how to break malicious intent--often quite subtle--into concrete&lt;br /&gt;
patterns we can reliably detect. The framework then demonstrates how&lt;br /&gt;
to build suspicion around reliance of particular patterns' use in&lt;br /&gt;
concert which, increasingly, imply malicious intent. These techniques&lt;br /&gt;
will be explained through a demonstration in a real world application.&lt;br /&gt;
&lt;br /&gt;
'''Bio'''&lt;br /&gt;
Masha (a.k.a Marina) has dreamed of becoming a security consultant&lt;br /&gt;
before she ever knew what a ballerina was, and that's a good thing -&lt;br /&gt;
because she does not intend her talk to be a ballet recital. Having&lt;br /&gt;
been in software security for over seven years, Ms. Khainson has&lt;br /&gt;
delivered Architecture Risk Assessment, Secure Code Review, and&lt;br /&gt;
Ethical Hacking on many architectures, platforms and technologies.&lt;br /&gt;
Marina has also developed training materials for clients and led&lt;br /&gt;
remediation assistance teams.&lt;br /&gt;
&lt;br /&gt;
Prior to joining Cigital, Marina was a member of a research team at a&lt;br /&gt;
leading security research provider, where using disassembly as well as&lt;br /&gt;
protocol and source code analysis, she provided key information on&lt;br /&gt;
newly released vulnerabilities. Before that, Marina assisted the same&lt;br /&gt;
research team in producing detailed reports on critical malware and&lt;br /&gt;
spyware threats, as well as developing and testing content for network&lt;br /&gt;
security devices from some of the top providers of intrusion detection&lt;br /&gt;
and prevention technologies.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== November 2011 ===&lt;br /&gt;
'''Date/Time:''' November 3rd, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.qinetiq.com/ QinetiQ], 2677 Prosperity Ave Fairfax, VA 22031&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # Talk: &amp;quot;Lessons Learned from the SQL Injection Challenge&amp;quot; by Ryan Barnett (Trustwave SpiderLabs)&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
'''Presentation Title:''' &amp;quot;Lessons Learned from the SQL Injection Challenge&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''Abstract:'''&lt;br /&gt;
How effective are blacklist filters vs. SQL Injection attacks?  What is the failure rate vs. automated scanning or manual testing?  Are there any &amp;quot;Time-to-Bypass&amp;quot; metrics?  In an attempt to answer these questions, Trustwave SpiderLabs' Research Team (the development team behind the ModSecurity WAF and the OWASP ModSecurity Core Rule Set) held a community &amp;quot;SQL Injection Challenge&amp;quot; to test the effectiveness of the OWASP ModSecurity Core Rule Set protections.  This presentation will provide an overview of the challenge, a step-by-step walk-through of the bypass tactics used by the winners, as well as, present a new approach to attack detection using ModSecurity's Lua API to perform Bayesian analysis.&lt;br /&gt;
&lt;br /&gt;
'''Speaker Bio:'''&lt;br /&gt;
[mailto:ryan.barnett@owasp.org Ryan C. Barnett] (Twitter: [http://twitter.com/#!/ryancbarnett @ryancbarnett]) is a senior security researcher on Trustwave's SpiderLabs Team. He is a SANS Institute certified instructor and a member of both the Top 20 Vulnerabilities and CWE/SANS Top 25 Most Dangerous Programming Errors teams. In addition to working with SANS, he is also a WASC Member where he leads the Web Hacking Incidents Database (WHID) and Distributed Web Honeypots Projects and is also the OWASP ModSecurity Core Rule Set (CRS) project leader. Mr. Barnett has also authored a Web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== October 2011 ===&lt;br /&gt;
'''Date/Time:''' October 6th, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location/Food Sponsor:''' [http://www.cigital.com/ Cigital], 21351 Ridgetop Circle, Suite 400, Sterling, VA 20166 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
 # News / Updates&lt;br /&gt;
 # AppSec USA 2011 Recap&lt;br /&gt;
 # Talk: Jack Mannino: [http://www.slideshare.net/JackMannino/owasp-top-10-mobile-risks &amp;quot;OWASP Top 10 Mobile Risks&amp;quot;]&lt;br /&gt;
 # Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2011 ===&lt;br /&gt;
&lt;br /&gt;
The September meeting was cancelled due to inclement weather (flash flooding).&lt;br /&gt;
&lt;br /&gt;
=== August 2011  ===&lt;br /&gt;
&lt;br /&gt;
We held a &amp;quot;social&amp;quot; event at Sweetwater Tavern in Sterling, VA. &lt;br /&gt;
&lt;br /&gt;
=== July 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' July 7th, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.cigital.com Cigital], Suite 400 21351 Ridgetop Circle, Dulles, VA, 20166&amp;lt;br&amp;gt; '''Food Sponsor:'''&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: iGoat - Ken Van Wyk&lt;br /&gt;
&lt;br /&gt;
=== June 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190&amp;lt;br&amp;gt; '''Food Sponsor:''' The College Board&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 &amp;quot;Insecure Direct Object References&amp;quot;]&lt;br /&gt;
 * College Board Speaker: &amp;quot;Attack-in-Depth:  Exploits of the OWASP Top Ten in Action&amp;quot;&lt;br /&gt;
 * Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
 - Jack Mannino: &amp;quot;Android Security 101&amp;quot;&lt;br /&gt;
 - Others!&lt;br /&gt;
&lt;br /&gt;
=== May 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''Food Sponsor:''' Akamai&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
 * 2011 Election (voice vote on the entire slate)&lt;br /&gt;
 * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 &amp;quot;Broken Authentication and Session Management&amp;quot;]&lt;br /&gt;
 * Speaker: Steve Witmer on A3 from the &amp;quot;breakers&amp;quot; perspective&lt;br /&gt;
 * Speaker:&amp;amp;nbsp;??? on A3 from the &amp;quot;fixers/defenders&amp;quot; perspective&lt;br /&gt;
 * Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
 * '''Update:''' All election candidates were elected by voice vote. &lt;br /&gt;
    * Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;authkey=CIS9zFM '11 Chapter Board Election Material]&lt;br /&gt;
&lt;br /&gt;
=== April 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &amp;lt;br&amp;gt; '''Food Sponsor:''' [https://www.cigital.com Cigital]&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
 * 2011 Election&lt;br /&gt;
 * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
 * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson ([https://www.owasp.org/images/9/92/Xssnotfriend-edited.pptx PPTX] or [https://www.owasp.org/images/0/06/Xssnotfriend-edited.pdf PDF])&lt;br /&gt;
 * Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])&lt;br /&gt;
 * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
 * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm &amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 &amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
  * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
  * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
  * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
  * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
  * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group]. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360! &lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective. &lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History  ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile Mobile]&lt;br /&gt;
&lt;br /&gt;
=== OWASP NoVa Members On Twitter  ===&lt;br /&gt;
&lt;br /&gt;
John Steven [http://twitter.com/m1splacedsoul http://twitter.com/m1splacedsoul] &lt;br /&gt;
&lt;br /&gt;
Jack Mannino [http://twitter.com/jack_mannino http://twitter.com/jack_mannino] &lt;br /&gt;
&lt;br /&gt;
Ben Tomhave [http://twitter.com/falconsview http://twitter.com/falconsview] &lt;br /&gt;
&lt;br /&gt;
Ken Johnson [http://twitter.com/cktricky http://twitter.com/cktricky] &lt;br /&gt;
&lt;br /&gt;
Mike Smith [http://twitter.com/rybolov http://twitter.com/rybolov] &lt;br /&gt;
&lt;br /&gt;
Trevor Hawthorn [http://twitter.com/packetwerks http://twitter.com/packetwerks] &lt;br /&gt;
&lt;br /&gt;
Joey Tyson [http://twitter.com/theharmonyguy http://twitter.com/theharmonyguy] &lt;br /&gt;
&lt;br /&gt;
Jeremy Long [http://twitter.com/ctxt http://twitter.com/ctxt] &lt;br /&gt;
&lt;br /&gt;
Ari Elias-Bachrach [http://twitter.com/angelofsecurity http://twitter.com/angelofsecurity] &lt;br /&gt;
&lt;br /&gt;
Venkat Sundaram [http://twitter.com/Vnk3889 http://twitter.com/Vnk3889] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Projects/OWASP_GoatDroid_Project&amp;diff=124408</id>
		<title>Projects/OWASP GoatDroid Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Projects/OWASP_GoatDroid_Project&amp;diff=124408"/>
				<updated>2012-02-16T19:07:33Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Template:&amp;lt;includeonly&amp;gt;{{{1}}}&amp;lt;/includeonly&amp;gt;&amp;lt;noinclude&amp;gt;Project About&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
| project_name = OWASP GoatDroid Project&lt;br /&gt;
| project_home_page = OWASP_Mobile_Security_Project&lt;br /&gt;
| project_description = &lt;br /&gt;
*The OWASP GoatDroid Project pays homage to the OWASP WebGoat Project. It is a fully functional and self-contained environment for learning more about vulnerabilities and security issues for the Android platform.&lt;br /&gt;
*The initial release is of alpha-level maturity and contains a fully functional functional RESTful web service and an Android application to get started. Future releases will add new applications and services, and will expand upon the current codebase to provide new and increasingly difficult to discover security flaws.&lt;br /&gt;
*The entire application and framework is Java based. There is no need to install an external web server or container. Each web service runs on embedded Jetty instances and uses the Jersey implementation of JAX-RS.&lt;br /&gt;
*In the first release, solutions will not be provided. You are encouraged to figure out where the holes are and determine the best way to mitigate them. The next release will include the solutions for version 1.&lt;br /&gt;
*You can download the project via Google Code: http://code.google.com/p/owasp-goatdroid/&lt;br /&gt;
 &lt;br /&gt;
| project_license =&lt;br /&gt;
&lt;br /&gt;
| leader_name1 = Jack Mannino &lt;br /&gt;
| leader_email1 = Jack@nvisiumsecurity.com&lt;br /&gt;
| leader_username1 = Jack Mannino&lt;br /&gt;
&lt;br /&gt;
| leader_name[2-10] = &lt;br /&gt;
| leader_email[2-10] = &lt;br /&gt;
| leader_username[2-10] = &lt;br /&gt;
&lt;br /&gt;
| contributor_name1 = Gunnar Peterson&lt;br /&gt;
| contributor_email1 = &lt;br /&gt;
| contributor_username1 = &lt;br /&gt;
&lt;br /&gt;
| contributor_name2 = John Steven&lt;br /&gt;
| contributor_email2 =  john.steven@owasp.org&lt;br /&gt;
| contributor_username2 = John Steven&lt;br /&gt;
&lt;br /&gt;
| pamphlet_link = &lt;br /&gt;
&lt;br /&gt;
| presentation_link =&lt;br /&gt;
&lt;br /&gt;
| mailing_list_name = https://lists.owasp.org/mailman/listinfo/owasp-mobile-security-project&lt;br /&gt;
&lt;br /&gt;
| project_road_map = https://www.owasp.org/index.php/Projects/OWASP_GoatDroid_Project/Roadmap&lt;br /&gt;
&lt;br /&gt;
| links_url[1-10] = &lt;br /&gt;
&lt;br /&gt;
| links_name[1-10] = &lt;br /&gt;
&lt;br /&gt;
| release_1 = &lt;br /&gt;
| release_2 = &lt;br /&gt;
| release_3 =&lt;br /&gt;
| release_4 =&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--- The line below is for GPC usage only. Please do not edit it ---&amp;gt;&lt;br /&gt;
| project_about_page = Projects/OWASP_GoatDroid_Project&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=116817</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=116817"/>
				<updated>2011-09-06T22:36:50Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Next Meeting */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra =Come see us at a chapter meeting, jump on our Google Group, or email any of us directly.&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board ===&lt;br /&gt;
Previously having had a Chapter Leader, then a Chapter &amp;quot;Program Committee&amp;quot;, the chapter is now run by a full board (alphabetical order):&lt;br /&gt;
&lt;br /&gt;
* Jeremy Long&lt;br /&gt;
* Jack Mannino&lt;br /&gt;
* John Steven - Board Chair&lt;br /&gt;
* Ben Tomhave&lt;br /&gt;
&lt;br /&gt;
Board member responsibilities include:&lt;br /&gt;
&amp;lt;pre style=&amp;quot;white-space: pre-wrap;&amp;quot;&amp;gt;&lt;br /&gt;
   * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics&lt;br /&gt;
   * Recruiting OWASP membership&lt;br /&gt;
   * Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
   * Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
   * Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
   * Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
   * Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations&lt;br /&gt;
   * Collecting and auditing use of chapter funds&lt;br /&gt;
   * Voting on chapter matters&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
For more information on how the board was elected and what it's responsibilities are, please see:&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;authkey=CIS9zFM Chapter Board Election]&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=https://groups.google.com/forum/#!forum/owasp-nova|emailarchives=https://groups.google.com/forum/#!forum/owasp-nova}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month.&lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
[http://owaspnova09082011.eventbrite.com/ PLEASE RSVP!] &lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' September 8th, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location/Food Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&amp;lt;div style=&amp;quot;width:90%;white-space:pre-wrap&amp;quot;&amp;gt;&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Getting Back On Track...&lt;br /&gt;
 * Mike Smith on HTTP Slow-DDOS Attacks&lt;br /&gt;
 * [https://plus.google.com/115010545042017654487/about John Steven] on &amp;quot;A Boot Camp on Code Understanding: How Modern Framework&lt;br /&gt;
 Dynamism Affects Assessments &amp;amp;amp;&amp;amp;nbsp;Remediation&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
 Abstract: How much bang for the buck to you really get from all that application &lt;br /&gt;
 pen testing and source code review? This presentation will present from-the-&lt;br /&gt;
 field evidence to validate the long-held opinions of most appsec professionals: &lt;br /&gt;
 today’s app sec tactics don’t really provide much value. Furthermore, they &lt;br /&gt;
 distract significantly from the objective of improving the security of the &lt;br /&gt;
 software being inspected in many cases due to inadequate understanding of the &lt;br /&gt;
 software’s design, resulting in poor coverage, inhibited automation, and &lt;br /&gt;
 low-yield, adverse-impact remediation.&lt;br /&gt;
 &lt;br /&gt;
 * Firetalks!&amp;amp;nbsp;:)&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
We need speakers and topics! If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== August 2011 ===&lt;br /&gt;
&lt;br /&gt;
We held a &amp;quot;social&amp;quot; event at Sweetwater Tavern in Sterling, VA.&lt;br /&gt;
&lt;br /&gt;
=== July 2011 ===&lt;br /&gt;
'''Date/Time:''' July 7th, 2011 @ 6pm&amp;lt;br&amp;gt;&lt;br /&gt;
'''Location Sponsor:''' [http://www.cigital.com Cigital], Suite 400 21351 Ridgetop Circle, Dulles, VA, 20166&amp;lt;br&amp;gt;&lt;br /&gt;
'''Food Sponsor:'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''AGENDA:'''&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: iGoat - Ken Van Wyk&lt;br /&gt;
&lt;br /&gt;
=== June 2011 ===&lt;br /&gt;
'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)&amp;lt;br&amp;gt;&lt;br /&gt;
'''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190&amp;lt;br&amp;gt;&lt;br /&gt;
'''Food Sponsor:''' The College Board&amp;lt;br&amp;gt;&lt;br /&gt;
'''AGENDA:'''&lt;br /&gt;
 * News / Updates&lt;br /&gt;
 * Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 &amp;quot;Insecure Direct Object References&amp;quot;]&lt;br /&gt;
 * College Board Speaker: &amp;quot;Attack-in-Depth:  Exploits of the OWASP Top Ten in Action&amp;quot;&lt;br /&gt;
 * Firetalks! :)&lt;br /&gt;
  - Jack Mannino: &amp;quot;Android Security 101&amp;quot;&lt;br /&gt;
  - Others!&lt;br /&gt;
&lt;br /&gt;
=== May 2011 ===&lt;br /&gt;
'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm &amp;lt;br&amp;gt;&lt;br /&gt;
'''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt;&lt;br /&gt;
'''Food Sponsor:''' Akamai&amp;lt;br&amp;gt;&lt;br /&gt;
'''AGENDA:'''&lt;br /&gt;
  * News / Updates&lt;br /&gt;
  * 2011 Election (voice vote on the entire slate)&lt;br /&gt;
  * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 &amp;quot;Broken Authentication and Session Management&amp;quot;]&lt;br /&gt;
  * Speaker: Steve Witmer on A3 from the &amp;quot;breakers&amp;quot; perspective&lt;br /&gt;
  * Speaker: ??? on A3 from the &amp;quot;fixers/defenders&amp;quot; perspective&lt;br /&gt;
  * Firetalks! :)&lt;br /&gt;
  * '''Update:''' All election candidates were elected by voice vote. &lt;br /&gt;
     * Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;authkey=CIS9zFM '11 Chapter Board Election Material]&lt;br /&gt;
&lt;br /&gt;
=== April 2011 ===&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &amp;lt;br&amp;gt;&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &amp;lt;br&amp;gt;&lt;br /&gt;
'''Food Sponsor:''' [https://www.cigital.com Cigital]&amp;lt;br&amp;gt;&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
  * News / Updates&lt;br /&gt;
  * 2011 Election&lt;br /&gt;
  * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson ([https://www.owasp.org/images/9/92/Xssnotfriend-edited.pptx PPTX] or [https://www.owasp.org/images/0/06/Xssnotfriend-edited.pdf PDF])&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm &amp;lt;br&amp;gt;&lt;br /&gt;
'''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 &amp;lt;br&amp;gt;&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; &lt;br /&gt;
'''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; &lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
   * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
=== OWASP NoVa Members On Twitter ===&lt;br /&gt;
&lt;br /&gt;
John Steven [http://twitter.com/m1splacedsoul http://twitter.com/m1splacedsoul]&lt;br /&gt;
&lt;br /&gt;
Jack Mannino [http://twitter.com/jack_mannino http://twitter.com/jack_mannino]&lt;br /&gt;
&lt;br /&gt;
Ben Tomhave [http://twitter.com/falconsview http://twitter.com/falconsview]&lt;br /&gt;
&lt;br /&gt;
Ken Johnson [http://twitter.com/cktricky http://twitter.com/cktricky]&lt;br /&gt;
&lt;br /&gt;
Mike Smith [http://twitter.com/rybolov http://twitter.com/rybolov]&lt;br /&gt;
&lt;br /&gt;
Trevor Hawthorn [http://twitter.com/packetwerks http://twitter.com/packetwerks]&lt;br /&gt;
&lt;br /&gt;
Joey Tyson [http://twitter.com/theharmonyguy http://twitter.com/theharmonyguy]&lt;br /&gt;
&lt;br /&gt;
Jeremy Long [http://twitter.com/long_twit http://twitter.com/long_twit]&lt;br /&gt;
&lt;br /&gt;
Ari Elias-Bachrach [http://twitter.com/angelofsecurity http://twitter.com/angelofsecurity]&lt;br /&gt;
&lt;br /&gt;
Venkat Sundaram [http://twitter.com/Vnk3889 http://twitter.com/Vnk3889]&lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=DOM_based_XSS_Prevention_Cheat_Sheet&amp;diff=115440</id>
		<title>DOM based XSS Prevention Cheat Sheet</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=DOM_based_XSS_Prevention_Cheat_Sheet&amp;diff=115440"/>
				<updated>2011-08-10T19:09:17Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Introduction =&lt;br /&gt;
&lt;br /&gt;
When looking at XSS (Cross-Site Scripting), there are three generally recognized forms of [[XSS]].  [[XSS#Stored_and_Reflected_XSS_Attacks | Reflected, Stored]], and [[DOM Based XSS]].  The [[XSS_(Cross_Site_Scripting)_Prevention_Cheat_Sheet | XSS Prevention Cheatsheet]] does an excellent job of addressing Reflected and Stored XSS. This cheatsheet addresses DOM (Document Object Model) based XSS and is an extension (and assumes comprehension of) the [[XSS_(Cross_Site_Scripting)_Prevention_Cheat_Sheet | XSS Prevention Cheatsheet]].&lt;br /&gt;
&lt;br /&gt;
In order to understand DOM based XSS, one needs to see the fundamental difference between reflected and stored XSS when compared to DOM based XSS.  Reflected and Stored XSS exist in a higher level rendering context and DOM based XSS is primarily found in a lower level execution context.  A rendering context is associated with the parsing of HTML tags and their attributes.  The HTML parser of the rendering context dictates how data is presented and laid out on the page and can be further broken down into the standard contexts of HTML, HTML attribute, URL, and CSS.  The JavaScript or VBScript parser of an execution context is associated with the parsing and execution of script code.  Each parser has distinct and separate semantics in the way they can possibly execute script code (XSS) which make creating consistent rules for mitigating both rendering and execution based contexts difficult.   The complication is compounded by the differing meanings and treatment of encoded values within each subcontext (HTML, HTML attribute, URL, and CSS) within the execution context.  &lt;br /&gt;
&lt;br /&gt;
This paper refers to the HTML, HTML attribute, URL, and CSS Cheatsheet contexts as subcontexts because each of these contexts can be reached and set within a JavaScript execution context.  In JavaScript code, the main context is JavaScript but since an attacker can try to attack the other 4 contexts using equivalent JavaScript DOM methods, we refer to the other contexts besides the JavaScript context as subcontexts.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following is an example of an attack which occurs in the JavaScript context and HTML subcontext:&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 &amp;lt;script&amp;gt;&lt;br /&gt;
 var x = ‘&amp;lt;%= taintedVar %&amp;gt;’;&lt;br /&gt;
 var d = document.createElement(‘div’);&lt;br /&gt;
 d.innerHTML = x;&lt;br /&gt;
 document.body.appendChild(d);&lt;br /&gt;
 &amp;lt;/script&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
One consistency, however, is the need to JavaScript encode in addition to the encoding required for the subcontext in the execution context.  Let’s look at the individual subcontexts of the execution context in turn.&lt;br /&gt;
&lt;br /&gt;
= HTML Subcontext within the Execution Context =&lt;br /&gt;
&lt;br /&gt;
There are several methods and attributes which can be used to directly render HTML content within JavaScript.  These methods constitute the HTML Subcontext within the Execution Context.&lt;br /&gt;
&lt;br /&gt;
==Attributes==&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 element.innerHTML = “&amp;lt;HTML&amp;gt; Tags and markup”;&lt;br /&gt;
 element.outerHTML = “&amp;lt;HTML&amp;gt; Tags and markup”;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Methods==&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 document.write(“&amp;lt;HTML&amp;gt; Tags and markup”);&lt;br /&gt;
 document.writeln(“&amp;lt;HTML&amp;gt; Tags and markup”);&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Guideline==&lt;br /&gt;
In a pure HTML execution context (not HTML Attribute) use HTML and JavaScript encoding to mitigate against attacks.&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 element.innerHTML = “&amp;lt;%=Encoder.encodeForJS(Encoder.encodeForHTML(untrustedData))%&amp;gt;”;&lt;br /&gt;
 element.outerHTML = “&amp;lt;%=Encoder.encodeForJS(Encoder.encodeForHTML(untrustedData))%&amp;gt;”;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Methods==&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 document.write(“&amp;lt;%=Encoder.encodeForJS(Encoder.encodeForHTML(untrustedData))%&amp;gt;”);&lt;br /&gt;
 document.writeln(“&amp;lt;%=Encoder.encodeForJS(Encoder.encodeForHTML(untrustedData))%&amp;gt;”);&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= HTML Attribute Subcontext within the Execution Context =&lt;br /&gt;
&lt;br /&gt;
The HTML attribute Subcontext within the Execution context is divergent from the standard encoding rules.  This is because the rule to HTML attribute encode in an HTML attribute rendering context is mitigating attacks which try to exit out of the attribute to add additional attributes and/or tags which could have executable code.  When you are in a DOM execution context you only need to JavaScript encode HTML attributes which do not execute code (attributes other than event handler, CSS, and URL attributes).&lt;br /&gt;
&lt;br /&gt;
For example, the general rule is to HTML Attribute encode untrusted data (data from the database, http request, user, backend system, etc.) placed in an HTML Attribute.  This is the appropriate step to take when outputting data in a rendering context, however using HTML Attribute encoding in an execution context will break the application display of data.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 var x = document.createElement(“input”);&lt;br /&gt;
 x.setAttribute(“name”, “company_name”);&lt;br /&gt;
 x.setAttribute(“value”, ‘&amp;lt;%=Encoder.encodeForJS(Encoder.encodeForHTMLAttr(companyName))%&amp;gt;’);&lt;br /&gt;
 var form1 = document.forms[0];&lt;br /&gt;
 form1.appendChild(x);&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The problem is that if companyName had the value “Johnson &amp;amp; Johnson”.  What would be displayed in the input text field would be “Johnson &amp;amp;amp;amp; Johnson”.  The appropriate encoding to use in the above case would be only JavaScript encoding to disallow an attacker from closing out the single quotes and in-lining code, or escaping to HTML and opening a new script tag.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 var x = document.createElement(“input”);&lt;br /&gt;
 x.setAttribute(“name”, “company_name”);&lt;br /&gt;
 x.setAttribute(“value”, ‘&amp;lt;%=Encoder.encodeForJS(companyName)%&amp;gt;’);&lt;br /&gt;
 var form1 = document.forms[0];&lt;br /&gt;
 form1.appendChild(x);&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It is important to note that when setting an HTML attribute which does not execute code the value is set directly within the object attribute of the HTML element so there is no concerns with injecting up.&lt;br /&gt;
&lt;br /&gt;
= URL Attribute Subcontext within the Execution Context =&lt;br /&gt;
&lt;br /&gt;
The logic which parses URLs in both execution and rendering contexts looks to be the same.  Therefore there is little change in the encoding rules for URL attributes in an execution (DOM) context.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;var x = document.createElement(“a”);&amp;lt;/code&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;x.setAttribute(“href”, ‘&amp;lt;%=Encoder.encodeForJS(Encoder.encodeForURL(userRelativePath))%&amp;gt;’);&amp;lt;/code&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;var y = document.createTextElement(“Click Me To Test”);&amp;lt;/code&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;x.appendChild(y);&amp;lt;/code&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;document.body.appendChild(x);&amp;lt;/code&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you utilize fully qualified URLs then this will break the links as the colon in the protocol identifier (“http:” or “javascript:”) will be URL encoded preventing the “http” and “javascript” protocols from being invoked.&lt;br /&gt;
&lt;br /&gt;
=CSS Attribute Subcontext within the Execution Context=&lt;br /&gt;
&lt;br /&gt;
Normally executing JavaScript from a CSS context required either passing &amp;lt;code&amp;gt;javascript:attackCode()&amp;lt;/code&amp;gt; to the CSS url() method or invoking the CSS expression() method passing JavaScript code to be directly executed.  From my experience, calling the expression() function from an execution context (JavaScript) has been disabled.  In order to mitigate against the CSS url() method ensure that you are URL encoding the data passed to the CSS url() method.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 document.body.style.backgroundImage = &amp;quot;url(&amp;lt;%=Encoder.encodeForJS(Encoder.encodeForURL(companyName))%&amp;gt;)&amp;quot;;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
TODO: We have not been able to get the expression() function working from DOM JavaScript code.  Need some help.&lt;br /&gt;
&lt;br /&gt;
=Event Handler and JavaScript code Subcontexts within an Execution Context=&lt;br /&gt;
&lt;br /&gt;
Putting dynamic data within JavaScript code is especially dangerous because JavaScript encoding has different semantics for JavaScript encoded data when compared to other encodings.  In many cases, JavaScript encoding does not stop attacks within an execution context.  For example, a JavaScript encoded string will execute even though it is JavaScript encoded. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 var x = document.createElement(&amp;quot;a&amp;quot;);&lt;br /&gt;
 x.href=&amp;quot;#”;&lt;br /&gt;
 x.setAttribute(&amp;quot;onclick&amp;quot;, &amp;quot;\u0061\u006c\u0065\u0072\u0074\u0028\u0032\u0032\u0029&amp;quot;);&lt;br /&gt;
 var y = document.createTextNode(&amp;quot;Click To Test&amp;quot;);&lt;br /&gt;
 x.appendChild(y);&lt;br /&gt;
 document.body.appendChild(x);&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The setAttribute(&amp;lt;i&amp;gt;name_string&amp;lt;/i&amp;gt;,&amp;lt;i&amp;gt;value_string&amp;lt;/i&amp;gt;) method is dangerous because it implicitly coerces the  &amp;lt;i&amp;gt;string_value&amp;lt;/i&amp;gt; into the DOM attribute datatype of &amp;lt;i&amp;gt;name_string&amp;lt;/i&amp;gt;.  In the case above, the attribute name is an JavaScript event handler, so the attribute value is implicitly converted to JavaScript code and evaluated.  In the case above, JavaScript encoding does not mitigate against DOM based XSS.  Other JavaScript methods which take code as a string types will have a similar problem as outline above (setTimeout, setInterval, new Function, etc.).  This is in stark contrast to JavaScript encoding in the event handler attribute of a HTML tag (HTML parser) where JavaScript encoding mitigates against XSS.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
&amp;lt;!-- Does NOT work  --&amp;gt;&lt;br /&gt;
&amp;lt;a id=&amp;quot;bb&amp;quot; href=&amp;quot;#&amp;quot; onclick=&amp;quot;\u0061\u006c\u0065\u0072\u0074\u0028\u0031\u0029&amp;quot;&amp;gt; Test Me&amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
An alternative to using Element.setAttribute(...) to set DOM attributes is to set the attribute directly.  Directly setting event handler attributes will allow JavaScript encoding to mitigate against DOM based XSS.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
    &amp;lt;a id=&amp;quot;bb&amp;quot; href=&amp;quot;#&amp;quot;&amp;gt; Test Me&amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
            //The following does NOT work because the event handler is being set to a string.  &amp;quot;alert(7)&amp;quot; is JavaScript encoded.&lt;br /&gt;
            document.getElementById(&amp;quot;bb&amp;quot;).onclick = &amp;quot;\u0061\u006c\u0065\u0072\u0074\u0028\u0037\u0029&amp;quot;;&lt;br /&gt;
            &lt;br /&gt;
            //The following does NOT work because the event handler is being set to a string.&lt;br /&gt;
            document.getElementById(&amp;quot;bb&amp;quot;).onmouseover = &amp;quot;testIt&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
            //The following does NOT work because of the encoded &amp;quot;(&amp;quot; and &amp;quot;)&amp;quot;. &amp;quot;alert(77)&amp;quot; is JavaScript encoded.&lt;br /&gt;
            document.getElementById(&amp;quot;bb&amp;quot;).onmouseover = \u0061\u006c\u0065\u0072\u0074\u0028\u0037\u0037\u0029;&lt;br /&gt;
&lt;br /&gt;
            //The following does NOT work because of the encoded &amp;quot;;&amp;quot;. &amp;quot;testIt;testIt&amp;quot; is JavaScript encoded.&lt;br /&gt;
            document.getElementById(&amp;quot;bb&amp;quot;).onmouseover = \u0074\u0065\u0073\u0074\u0049\u0074\u003b\u0074\u0065\u0073\u0074\u0049\u0074;&lt;br /&gt;
      &lt;br /&gt;
            //The following DOES WORK because the encoded value is a valid variable name or function reference.  &amp;quot;testIt&amp;quot; is JavaScript encoded&lt;br /&gt;
            document.getElementById(&amp;quot;bb&amp;quot;).onmouseover = \u0074\u0065\u0073\u0074\u0049\u0074;&lt;br /&gt;
&lt;br /&gt;
            function testIt() {&lt;br /&gt;
                &lt;br /&gt;
                alert(&amp;quot;I was called.&amp;quot;);&lt;br /&gt;
            }&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There are other places in JavaScript where JavaScript encoding is accepted as valid executable code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 for ( var \u0062=0; \u0062 &amp;lt; 10; \u0062++){&lt;br /&gt;
     \u0064\u006f\u0063\u0075\u006d\u0065\u006e\u0074                  &lt;br /&gt;
     .\u0077\u0072\u0069\u0074\u0065\u006c\u006e&lt;br /&gt;
     (&amp;quot;\u0048\u0065\u006c\u006c\u006f\u0020\u0057\u006f\u0072\u006c\u0064&amp;quot;);&lt;br /&gt;
 }&lt;br /&gt;
 \u0077\u0069\u006e\u0064\u006f\u0077&lt;br /&gt;
 .\u0065\u0076\u0061\u006c&lt;br /&gt;
 \u0064\u006f\u0063\u0075\u006d\u0065\u006e\u0074&lt;br /&gt;
 .\u0077\u0072\u0069\u0074\u0065(111111111));&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 var s = &amp;quot;\u0065\u0076\u0061\u006c&amp;quot;;&lt;br /&gt;
 var t = &amp;quot;\u0061\u006c\u0065\u0072\u0074\u0028\u0031\u0031\u0029&amp;quot;;&lt;br /&gt;
 window[s](t);&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Because JavaScript is based on an international standard (ECMAScript), JavaScript encoding enables the support of international characters in programming constructs and variables in addition to alternate string representations (string escapes).  &lt;br /&gt;
&lt;br /&gt;
However the opposite is the case with HTML encoding.  HTML tag elements are well defined and do not support alternate representations of the same tag.  So HTML encoding cannot be used to allow the developer to have alternate representations of the &amp;lt;code&amp;gt;&amp;lt;a&amp;gt;&amp;lt;/code&amp;gt; tag for example.&lt;br /&gt;
&lt;br /&gt;
==HTML Encoding’s Disarming Nature==&lt;br /&gt;
&lt;br /&gt;
In general, HTML encoding serves to castrate HTML tags which are placed in HTML and HTML attribute contexts.&lt;br /&gt;
Working example (no HTML encoding):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 &amp;lt;a href=”…” &amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Normally encoded example (Does Not Work – DNW):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 &amp;amp;amp;#x3c;a href=… &amp;amp;amp;#x3e;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
HTML encoded example to highlight a fundamental difference with JavaScript encoded values (DNW):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 &amp;lt;&amp;amp;amp;#x61; href=…&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If HTML encoding followed the same semantics as JavaScript encoding.  The line above could have possibily worked to render a link.  This difference makes JavaScript encoding a less viable weapon in our fight against XSS.&lt;br /&gt;
&lt;br /&gt;
=Guidelines for Developing Secure Applications Utilizing JavaScript=&lt;br /&gt;
&lt;br /&gt;
DOM based XSS is extremely difficult to mitigate against because of its large attack surface and lack of standardization across browsers.  The guidelines below are an attempt to provide guidelines for developers when developing Web based JavaScript applications (Web 2.0) such that they can avoid XSS.&lt;br /&gt;
&lt;br /&gt;
1. Untrusted data should only be treated as displayable text.  Never treat untrusted data as code or markup within JavaScript code. &amp;lt;br/&amp;gt;&lt;br /&gt;
2. Always JavaScript encode and delimit untrusted data as quoted strings when entering the application (Jim Manico and Robert Hansen) &amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 var x = “&amp;lt;%=encodedJavaScriptData%&amp;gt;”;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
3. Use &amp;lt;code&amp;gt;document.createElement(“…”), element.setAttribute(“…”,”value”), element.appendChild(…)&amp;lt;/code&amp;gt;, etc. to build dynamic interfaces.  Avoid use of HTML rendering methods:&amp;lt;br/&amp;gt;&lt;br /&gt;
#&amp;lt;code&amp;gt;element.innerHTML = “…”; &amp;lt;/code&amp;gt;&lt;br /&gt;
#&amp;lt;code&amp;gt;element.outerHTML = “…”; &amp;lt;/code&amp;gt;&lt;br /&gt;
#&amp;lt;code&amp;gt;document.write(…); &amp;lt;/code&amp;gt;&lt;br /&gt;
#&amp;lt;code&amp;gt;document.writeln(…); &amp;lt;/code&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
4. Understand the dataflow of untrusted data through your JavaScript code.  If you do have to use the methods above remember to HTML and them JavaScript encode the untrusted data (Stefano Di Paola).&amp;lt;br/&amp;gt;&lt;br /&gt;
5. There are numerous methods which implicitly eval() data passed to it.  Make sure that any untrusted data passed to these methods is delimited with string delimiters and enclosed within a closure or JavaScript encoded to N-levels based on usage, and wrapped in a custom function.  Ensure to follow step 4 above to make sure that the untrusted data is not sent to dangerous methods within the custom function or handle it by adding an extra layer of encoding.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Utilizing an Enclosure (as suggested by Gaz)&amp;lt;/b&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The example that follows illustrates using closures to avoid double JavaScript encoding.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 setTimeout((function(param) { return function() {&lt;br /&gt;
          customFunction(param);&lt;br /&gt;
          }&lt;br /&gt;
 })(&amp;quot;&amp;lt;%=Encoder.encodeForJS(untrustedData)%&amp;gt;&amp;quot;), y);&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The other alternative is using N-levels of encoding.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;N-Levels of Encoding&amp;lt;/b&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If your code looked like the following, you would need to only double JavaScript encode input data.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 setTimeout(“customFunction(‘&amp;lt;%=doubleJavaScriptEncodedData%&amp;gt;’, y)”);&lt;br /&gt;
 function customFunction (firstName, lastName)&lt;br /&gt;
       alert(&amp;quot;Hello&amp;quot; + firstName + &amp;quot; &amp;quot; + lastNam);&lt;br /&gt;
 }&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;doubleJavaScriptEncodedData&amp;lt;/code&amp;gt; has its first layer of JavaScript encoding reversed (upon execution) in the single quotes.  Then the implicit &amp;lt;code&amp;gt;eval()&amp;lt;/code&amp;gt; of &amp;lt;code&amp;gt;setTimeout()&amp;lt;/code&amp;gt; reverses another layer of JavaScript encoding to pass the correct value to &amp;lt;code&amp;gt;customFunction&amp;lt;/code&amp;gt;.  The reason why you only need to double JavaScript encode is that the &amp;lt;code&amp;gt;customFunction&amp;lt;/code&amp;gt; function did not itself pass the input to another method which implicitly or explicitly called &amp;lt;code&amp;gt;eval()&amp;lt;/code&amp;gt;.  If &amp;quot;firstName&amp;quot; was passed to another JavaScript method which implicitly or explicitly called eval() then &amp;lt;code&amp;gt;&amp;lt;%=doubleJavaScriptEncodedData%&amp;gt;&amp;lt;/code&amp;gt; above would need to be changed to &amp;lt;code&amp;gt;&amp;lt;%=tripleJavaScriptEncodedData%&amp;gt;&amp;lt;/code&amp;gt;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
An important implementation note is that if the JavaScript code tries to utilize the double or triple encoded data in string comparisons, the value may be interpreted as different values based on the number of evals() the data has passed through before being passed to the if comparison and the number of times the value was JavaScript encoded.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If &amp;quot;A&amp;quot; is double JavaScript encoded then the following if check will return false.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 var x = &amp;quot;doubleJavaScriptEncodedA&amp;quot;;  //\u005c\u0075\u0030\u0030\u0034\u0031&lt;br /&gt;
 if (x == &amp;quot;A&amp;quot;) {&lt;br /&gt;
    alert(&amp;quot;x is A&amp;quot;);&lt;br /&gt;
 } else if (x == &amp;quot;\u0041&amp;quot;) {&lt;br /&gt;
    alert(&amp;quot;This is what pops&amp;quot;);&lt;br /&gt;
 }&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This brings up an interesting design point.  Ideally, the correct way to apply encoding and avoid the problem stated above is to server-side encode for the output context where data is introduced into the application.  Then client-side encode (using a JavaScript encoding library such as ESAPI4JS) for the individual subcontext (DOM methods) which untrusted data is passed to.  ESAPI4JS (located at http://bit.ly/9hRTLH) and jQuery Encoder (located at https://github.com/chrisisbeef/jquery-encoder/blob/master/src/main/javascript/org/owasp/esapi/jquery/encoder.js) are two client side encoding libraries developed by Chris Schmidt.&amp;lt;br/&amp;gt;&lt;br /&gt;
Here are some examples of how they are used:&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 var input = “&amp;lt;%=Encoder.encodeForJS(untrustedData)%&amp;gt;”;  //server-side encoding&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 window.location = ESAPI4JS.encodeForURL(input);  //URL encoding is happening in JavaScript&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 document.writeln(ESAPI4JS.encodeForHTML(input));  //HTML encoding is happening in JavaScript&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It has been well noted by the group that any kind of reliance on a JavaScript library for encoding would be problematic as the JavaScript library could be subverted by attackers.  One option is to wait till ECMAScript 5 so the JavaScript library could support immutable properties.&amp;lt;br/&amp;gt;&lt;br /&gt;
Another option provided by Gaz (Gareth) was to use a specific code construct to limit mutability with anonymous clousures.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
An example follows:&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 function escapeHTML(str) {&lt;br /&gt;
      str = str + &amp;quot;''&amp;quot;;&lt;br /&gt;
      var out = &amp;quot;''&amp;quot;;&lt;br /&gt;
      for(var i=0; i&amp;lt;str.length; i++) {&lt;br /&gt;
          if(str[i] === '&amp;lt;') {&lt;br /&gt;
              out += '&amp;amp;amp;lt;';&lt;br /&gt;
          } else if(str[i] === '&amp;gt;') {&lt;br /&gt;
              out += '&amp;amp;amp;gt;';&lt;br /&gt;
          } else if(str[i] === &amp;quot;'&amp;quot;) {&lt;br /&gt;
              out += '&amp;amp;amp;#39;'; &lt;br /&gt;
          } else if(str[i] === '&amp;quot;') {&lt;br /&gt;
              out += '&amp;amp;amp;quot;';                        &lt;br /&gt;
          } else {&lt;br /&gt;
              out += str[i];&lt;br /&gt;
          }&lt;br /&gt;
      }&lt;br /&gt;
      return out;                    &lt;br /&gt;
 }&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;Chris Schmidt has put together another implementation of a JavaScript encoder at http://yet-another-dev.blogspot.com/2011/02/client-side-contextual-encoding-for.html.  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
6. Limit the usage of dynamic untrusted data to right side operations.  And be aware of data which may be passed to the application which look like code (eg. &amp;lt;code&amp;gt;location&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;eval()&amp;lt;/code&amp;gt;).  (Achim)&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 var x = “&amp;lt;%=properly encoded data for flow%&amp;gt;”;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you want to change different object attributes based on user input use a level of indirection.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Instead of: &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 window[userData] = “moreUserData”;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Do the following instead:&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 if (userData===”location”) {&lt;br /&gt;
    window.location = “static/path/or/properly/url/encoded/value”;&lt;br /&gt;
 }&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
7. When URL encoding in DOM be aware of character set issues as the character set in JavaScript DOM is not clearly defined (Mike Samuel).&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
8. Limit access to properties objects when using object[x] accessors. (Mike Samuel).  In other words use a level of indirection between untrusted input and specified object properties.&amp;lt;br/&amp;gt;&lt;br /&gt;
Here is an example of the problem when using map types:&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 var myMapType = {};&lt;br /&gt;
 myMapType[&amp;lt;%=untrustedData%&amp;gt;] = “moreUntrustedData”;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Although the developer writing the code above was trying to add additional keyed elements to the &amp;lt;code&amp;gt;myMapType&amp;lt;/code&amp;gt; object.  This could be used by an attacker to subvert internal and external attributes of the &amp;lt;code&amp;gt;myMapType&amp;lt;/code&amp;gt; object.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
9. Run your JavaScript in a ECMAScript 5 canopy or sand box to make it harder for your JavaScript API to be compromised (Gareth Heyes and John Stevens).&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
10. Don’t &amp;lt;code&amp;gt;eval()&amp;lt;/code&amp;gt; JSON to convert it to native JavaScript objects.  Instead use &amp;lt;code&amp;gt;JSON.toJSON()&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;JSON.parse()&amp;lt;/code&amp;gt; (Chris Schmidt).&lt;br /&gt;
&lt;br /&gt;
=  Common Problems Associated with Mitgating DOM Based XSS =&lt;br /&gt;
==Complex Contexts==&lt;br /&gt;
In many cases the context isn’t always strait forward to discern.&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 &amp;lt;a href=”javascript:myFunction(‘&amp;lt;%=untrustedData%&amp;gt;’, 'test');”&amp;gt;Click Me&amp;lt;/a&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;script&amp;gt;&lt;br /&gt;
 Function myFunction (url,name) {&lt;br /&gt;
     window.location = url;&lt;br /&gt;
 }&lt;br /&gt;
 &amp;lt;/script&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the above example, untrusted data started in the rendering URL context (&amp;lt;code&amp;gt;href&amp;lt;/code&amp;gt; attribute of an &amp;lt;code&amp;gt;&amp;lt;a&amp;gt;&amp;lt;/code&amp;gt; tag) then changed to a JavaScript execution context (&amp;lt;code&amp;gt;javascript:&amp;lt;/code&amp;gt; protocol handler) which passed the untrusted data to an execution URL subcontext (&amp;lt;code&amp;gt;window.location&amp;lt;/code&amp;gt; of myFunction).  Because the data was introduced in JavaScript code and passed to a URL subcontext the appropriate server-side encoding would be the following:&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 &amp;lt;a href=”javascript:myFunction(‘&amp;lt;%=Encoder.encodeForJS( &amp;amp;#x21a9;&lt;br /&gt;
               Encoder.encodeForURL(untrustedData))%&amp;gt;’, 'test');”&amp;gt;Click Me&amp;lt;/a&amp;gt;&lt;br /&gt;
 …&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Or if you were using ECMAScript 5 with an immutable JavaScript client-side encoding libraries you could do the following:&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 &amp;amp;lt;!--server side URL encoding has been removed.  Now only JavaScript encoding on server side. --&amp;gt;&lt;br /&gt;
 &amp;lt;a href=”javascript:myFunction(‘&amp;lt;%=Encoder.encodeForJS(untrustedData)%&amp;gt;’, 'test');”&amp;gt;Click Me&amp;lt;/a&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;script&amp;gt;&lt;br /&gt;
 Function myFunction (url,name) {&lt;br /&gt;
     var encodedURL = ESAPI4JS.encodeForURL(url);  //URL encoding using client-side scripts&lt;br /&gt;
     window.location = encodedURL;&lt;br /&gt;
 }&lt;br /&gt;
 &amp;lt;/script&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Insonsistencies of Encoding Libraries ==&lt;br /&gt;
There are a number of open source encoding libraries out there:&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#ESAPI&lt;br /&gt;
#Apache Commons String Utils&lt;br /&gt;
#Jtidy&lt;br /&gt;
#Your company’s custom implementation.&lt;br /&gt;
&lt;br /&gt;
Some work on a black list others ignore important characters like “&amp;lt;” and “&amp;gt;”.  ESAPI is one of the few which work on a whitelist and encode all non-alpha numeric characters.&lt;br /&gt;
It is important to use an encoding library which understands which characters can be used to exploit vulnerabilies in their respective contexts.&lt;br /&gt;
But there are misconceptions abound related to proper encoding. &lt;br /&gt;
&lt;br /&gt;
==Encoding Misconceptions==&lt;br /&gt;
Many security training curriculums and papers advocate the blind usage of HTML encoding to resolve XSS.  This logically seems to be prudent advice as the JavaScript parser does not understand HTML encoding.  However, if the pages returned from your web application utilize a content type of “text/xhtml” or the file type extension of “*.xhtml” then HML encoding may not work to mitigate against XSS.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example: &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 &amp;lt;script&amp;gt;&lt;br /&gt;
 &amp;amp;amp;#x61;lert(1);&lt;br /&gt;
 &amp;lt;/script&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The HTML encoded value above is still executable.  If that isn’t enough to keep in mind, you have to remember that encodings are lost when you retrieve them using the value attribute of a DOM element. &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Let’s look at the sample page and script:&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 &amp;lt;form name=”myForm” …&amp;gt;&lt;br /&gt;
   &amp;lt;input type=”text” name=”lName” value=”&amp;lt;%=Encoder.encodeForHTML(last_name)%&amp;gt;”&amp;gt;&lt;br /&gt;
 …&lt;br /&gt;
 &amp;lt;/form&amp;gt;&lt;br /&gt;
 &amp;lt;script&amp;gt;&lt;br /&gt;
 var x = document.myForm.lName.value;  //when the value is retrieved the encoding is reversed&lt;br /&gt;
 document.writeln(x);  //any code passed into lName is now executable.&lt;br /&gt;
 &amp;lt;/script&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Finally there is the problem that certain methods in JavaScript which are usually safe can be unsafe in certain contexts.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Usually Safe Methods==&lt;br /&gt;
&lt;br /&gt;
One example of an attribute which is usually safe is innerText.  Some papers or guides advocate its use as an alternative to innerHTML to mitigate against XSS in innerHTML.  However, depending on the tag which innerText is applied, code can be executed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 &amp;lt;script&amp;gt;&lt;br /&gt;
 var tag = document.createElement(“script”);&lt;br /&gt;
 tag.innerText = “&amp;lt;%=untrustedData%&amp;gt;”;  //executes code&lt;br /&gt;
 &amp;lt;/script&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Authors and Contributing Editors  =&lt;br /&gt;
&lt;br /&gt;
Jim Manico - jim[at]owasp.org &lt;br /&gt;
&lt;br /&gt;
Abraham Kang - abraham.kang[at]owasp.org&lt;br /&gt;
&lt;br /&gt;
Gareth (Gaz) Heyes&lt;br /&gt;
&lt;br /&gt;
Stefano Di Paola&lt;br /&gt;
&lt;br /&gt;
[[User:Achim| Achim Hoffmann]] [mailto:achim@owasp.org| achim_@_owasp.org]&lt;br /&gt;
&lt;br /&gt;
Robert (RSnake) Hansen&lt;br /&gt;
&lt;br /&gt;
Mario Heiderich&lt;br /&gt;
&lt;br /&gt;
John Steven&lt;br /&gt;
&lt;br /&gt;
Chris (Chris BEF) Schmidt&lt;br /&gt;
&lt;br /&gt;
Mike Samuel&lt;br /&gt;
&lt;br /&gt;
Jeremy Long&lt;br /&gt;
&lt;br /&gt;
Edwardo (SirDarkCat) Alberto Vela Nava&lt;br /&gt;
&lt;br /&gt;
Jeff Williams - jeff.williams[at]owasp.org &lt;br /&gt;
&lt;br /&gt;
Erlend Oftedal&lt;br /&gt;
&lt;br /&gt;
{{Cheatsheet_Navigation}}&lt;br /&gt;
&lt;br /&gt;
[[Category:How To]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Cheatsheets]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=113199</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=113199"/>
				<updated>2011-06-29T20:36:38Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Next Meeting */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra =Come see us at a chapter meeting, jump on our Google Group, or email any of us directly.&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board ===&lt;br /&gt;
Previously having had a Chapter Leader, then a Chapter &amp;quot;Program Committee&amp;quot;, the chapter is now run by a full board (alphabetical order):&lt;br /&gt;
&lt;br /&gt;
* Jeremy Long&lt;br /&gt;
* Jack Mannino&lt;br /&gt;
* John Steven - Board Chair&lt;br /&gt;
* Ben Tomhave&lt;br /&gt;
&lt;br /&gt;
Board member responsibilities include:&lt;br /&gt;
&amp;lt;pre style=&amp;quot;white-space: pre-wrap;&amp;quot;&amp;gt;&lt;br /&gt;
   * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics&lt;br /&gt;
   * Recruiting OWASP membership&lt;br /&gt;
   * Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
   * Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
   * Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
   * Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
   * Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations&lt;br /&gt;
   * Collecting and auditing use of chapter funds&lt;br /&gt;
   * Voting on chapter matters&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
For more information on how the board was elected and what it's responsibilities are, please see:&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;authkey=CIS9zFM Chapter Board Election]&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=https://groups.google.com/forum/#!forum/owasp-nova|emailarchives=https://groups.google.com/forum/#!forum/owasp-nova}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month.&lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' July 7th, 2011 @ 6pm&lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.cigital.com Cigital], Suite 400 21351 Ridgetop Circle, Dulles, VA, 20166&lt;br /&gt;
&lt;br /&gt;
'''Food Sponsor:''' TBD&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Topic of the Month: iGoat - Ken Van Wyk&lt;br /&gt;
&lt;br /&gt;
==========================================================&lt;br /&gt;
I'll start by discussing briefly some of the underlying platform weaknesses on &lt;br /&gt;
iOS, and how the developer has to work around those weaknesses in order &lt;br /&gt;
to create reasonably secure apps. Next, I'll describe where iGoat can fit into &lt;br /&gt;
that as a learning tool for iOS developers to really understand the platform &lt;br /&gt;
issues they face. I'll demonstrate iGoat and step through a couple of the &lt;br /&gt;
exercises to illustrate how it works. Lastly, I'll show the internals of iGoat to &lt;br /&gt;
illustrate how others can easily add new lessons into iGoat.&lt;br /&gt;
&lt;br /&gt;
https://www.owasp.org/index.php/OWASP_iGoat_Project&lt;br /&gt;
&lt;br /&gt;
==========================================================&lt;br /&gt;
&lt;br /&gt;
* Firetalks! :)&lt;br /&gt;
** Others!&lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== May 2011 ===&lt;br /&gt;
'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm &lt;br /&gt;
'''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190&lt;br /&gt;
'''Food Sponsor:''' Akamai&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
  * News / Updates&lt;br /&gt;
  * 2011 Election (voice vote on the entire slate)&lt;br /&gt;
  * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 &amp;quot;Broken Authentication and Session Management&amp;quot;]&lt;br /&gt;
  * Speaker: Steve Witmer on A3 from the &amp;quot;breakers&amp;quot; perspective&lt;br /&gt;
  * Speaker: ??? on A3 from the &amp;quot;fixers/defenders&amp;quot; perspective&lt;br /&gt;
  * Firetalks! :)&lt;br /&gt;
  * '''Update:''' All election candidates were elected by voice vote. &lt;br /&gt;
     * Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;authkey=CIS9zFM '11 Chapter Board Election Material]&lt;br /&gt;
&lt;br /&gt;
=== April 2011 ===&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
'''Food Sponsor:''' [https://www.cigital.com Cigital]&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
  * News / Updates&lt;br /&gt;
  * 2011 Election&lt;br /&gt;
  * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson ([https://www.owasp.org/images/9/92/Xssnotfriend-edited.pptx PPTX] or [https://www.owasp.org/images/0/06/Xssnotfriend-edited.pdf PDF])&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
=== OWASP NoVa Members On Twitter ===&lt;br /&gt;
&lt;br /&gt;
John Steven [http://twitter.com/m1splacedsoul http://twitter.com/m1splacedsoul]&lt;br /&gt;
&lt;br /&gt;
Jack Mannino [http://twitter.com/jack_mannino http://twitter.com/jack_mannino]&lt;br /&gt;
&lt;br /&gt;
Ben Tomhave [http://twitter.com/falconsview http://twitter.com/falconsview]&lt;br /&gt;
&lt;br /&gt;
Ken Johnson [http://twitter.com/cktricky http://twitter.com/cktricky]&lt;br /&gt;
&lt;br /&gt;
Mike Smith [http://twitter.com/rybolov http://twitter.com/rybolov]&lt;br /&gt;
&lt;br /&gt;
Trevor Hawthorn [http://twitter.com/packetwerks http://twitter.com/packetwerks]&lt;br /&gt;
&lt;br /&gt;
Joey Tyson [http://twitter.com/theharmonyguy http://twitter.com/theharmonyguy]&lt;br /&gt;
&lt;br /&gt;
Jeremy Long [http://twitter.com/long_twit http://twitter.com/long_twit]&lt;br /&gt;
&lt;br /&gt;
Ari Elias-Bachrach [http://twitter.com/angelofsecurity http://twitter.com/angelofsecurity]&lt;br /&gt;
&lt;br /&gt;
Venkat Sundaram [http://twitter.com/Vnk3889 http://twitter.com/Vnk3889]&lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=112075</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=112075"/>
				<updated>2011-06-13T16:44:53Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra =Come see us at a chapter meeting, jump on our Google Group, or email any of us directly.&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board ===&lt;br /&gt;
Previously having had a Chapter Leader, then a Chapter &amp;quot;Program Committee&amp;quot;, the chapter is now run by a full board (alphabetical order):&lt;br /&gt;
&lt;br /&gt;
* Jeremy Long&lt;br /&gt;
* Jack Mannino&lt;br /&gt;
* John Steven - Board Chair&lt;br /&gt;
* Ben Tomhave&lt;br /&gt;
&lt;br /&gt;
Board member responsibilities include:&lt;br /&gt;
&amp;lt;pre style=&amp;quot;white-space: pre-wrap;&amp;quot;&amp;gt;&lt;br /&gt;
   * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics&lt;br /&gt;
   * Recruiting OWASP membership&lt;br /&gt;
   * Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
   * Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
   * Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
   * Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
   * Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations&lt;br /&gt;
   * Collecting and auditing use of chapter funds&lt;br /&gt;
   * Voting on chapter matters&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
For more information on how the board was elected and what it's responsibilities are, please see:&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;authkey=CIS9zFM Chapter Board Election]&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=https://groups.google.com/forum/#!forum/owasp-nova|emailarchives=https://groups.google.com/forum/#!forum/owasp-nova}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month.&lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)&lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190&lt;br /&gt;
&lt;br /&gt;
'''Food Sponsor:''' The College Board&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 &amp;quot;Insecure Direct Object References&amp;quot;]&lt;br /&gt;
* College Board Speaker: &amp;quot;Attack-in-Depth:  Exploits of the OWASP Top Ten in Action&amp;quot;&lt;br /&gt;
* Firetalks! :)&lt;br /&gt;
** Jack Mannino: &amp;quot;Android Security 101&amp;quot;&lt;br /&gt;
** Others!&lt;br /&gt;
&lt;br /&gt;
'''[http://owaspnova060911.eventbrite.com/ Please RSVP]'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== May 2011 ===&lt;br /&gt;
'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm &lt;br /&gt;
'''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190&lt;br /&gt;
'''Food Sponsor:''' Akamai&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
  * News / Updates&lt;br /&gt;
  * 2011 Election (voice vote on the entire slate)&lt;br /&gt;
  * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 &amp;quot;Broken Authentication and Session Management&amp;quot;]&lt;br /&gt;
  * Speaker: Steve Witmer on A3 from the &amp;quot;breakers&amp;quot; perspective&lt;br /&gt;
  * Speaker: ??? on A3 from the &amp;quot;fixers/defenders&amp;quot; perspective&lt;br /&gt;
  * Firetalks! :)&lt;br /&gt;
  * '''Update:''' All election candidates were elected by voice vote. &lt;br /&gt;
     * Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;authkey=CIS9zFM '11 Chapter Board Election Material]&lt;br /&gt;
&lt;br /&gt;
=== April 2011 ===&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
'''Food Sponsor:''' [https://www.cigital.com Cigital]&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
  * News / Updates&lt;br /&gt;
  * 2011 Election&lt;br /&gt;
  * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson ([https://www.owasp.org/images/9/92/Xssnotfriend-edited.pptx PPTX] or [https://www.owasp.org/images/0/06/Xssnotfriend-edited.pdf PDF])&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=112074</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=112074"/>
				<updated>2011-06-13T16:40:04Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=&lt;br /&gt;
=== Chapter Board ===&lt;br /&gt;
Previously having had a Chapter Leader, then a Chapter &amp;quot;Program Committee&amp;quot;, the chapter is now run by a full board (alphabetical order):&lt;br /&gt;
&lt;br /&gt;
* Jeremy Long&lt;br /&gt;
* Jack Mannino&lt;br /&gt;
* John Steven - Board Chair&lt;br /&gt;
* Ben Tomhave&lt;br /&gt;
&lt;br /&gt;
Board member responsibilities include:&lt;br /&gt;
&amp;lt;pre style=&amp;quot;white-space: pre-wrap;&amp;quot;&amp;gt;&lt;br /&gt;
   * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics&lt;br /&gt;
   * Recruiting OWASP membership&lt;br /&gt;
   * Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
   * Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
   * Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
   * Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
   * Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations&lt;br /&gt;
   * Collecting and auditing use of chapter funds&lt;br /&gt;
   * Voting on chapter matters&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
For more information on how the board was elected and what it's responsibilities are, please see:&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;authkey=CIS9zFM Chapter Board Election]&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month.&lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)&lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190&lt;br /&gt;
&lt;br /&gt;
'''Food Sponsor:''' The College Board&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 &amp;quot;Insecure Direct Object References&amp;quot;]&lt;br /&gt;
* College Board Speaker: &amp;quot;Attack-in-Depth:  Exploits of the OWASP Top Ten in Action&amp;quot;&lt;br /&gt;
* Firetalks! :)&lt;br /&gt;
** Jack Mannino: &amp;quot;Android Security 101&amp;quot;&lt;br /&gt;
** Others!&lt;br /&gt;
&lt;br /&gt;
'''[http://owaspnova060911.eventbrite.com/ Please RSVP]'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== May 2011 ===&lt;br /&gt;
'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm &lt;br /&gt;
'''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190&lt;br /&gt;
'''Food Sponsor:''' Akamai&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
  * News / Updates&lt;br /&gt;
  * 2011 Election (voice vote on the entire slate)&lt;br /&gt;
  * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 &amp;quot;Broken Authentication and Session Management&amp;quot;]&lt;br /&gt;
  * Speaker: Steve Witmer on A3 from the &amp;quot;breakers&amp;quot; perspective&lt;br /&gt;
  * Speaker: ??? on A3 from the &amp;quot;fixers/defenders&amp;quot; perspective&lt;br /&gt;
  * Firetalks! :)&lt;br /&gt;
  * '''Update:''' All election candidates were elected by voice vote. &lt;br /&gt;
     * Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;authkey=CIS9zFM '11 Chapter Board Election Material]&lt;br /&gt;
&lt;br /&gt;
=== April 2011 ===&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
'''Food Sponsor:''' [https://www.cigital.com Cigital]&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
  * News / Updates&lt;br /&gt;
  * 2011 Election&lt;br /&gt;
  * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson ([https://www.owasp.org/images/9/92/Xssnotfriend-edited.pptx PPTX] or [https://www.owasp.org/images/0/06/Xssnotfriend-edited.pdf PDF])&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=112073</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=112073"/>
				<updated>2011-06-13T16:07:29Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* May 2011 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month.&lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)&lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190&lt;br /&gt;
&lt;br /&gt;
'''Food Sponsor:''' The College Board&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 &amp;quot;Insecure Direct Object References&amp;quot;]&lt;br /&gt;
* College Board Speaker: &amp;quot;Attack-in-Depth:  Exploits of the OWASP Top Ten in Action&amp;quot;&lt;br /&gt;
* Firetalks! :)&lt;br /&gt;
** Jack Mannino: &amp;quot;Android Security 101&amp;quot;&lt;br /&gt;
** Others!&lt;br /&gt;
&lt;br /&gt;
'''[http://owaspnova060911.eventbrite.com/ Please RSVP]'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== May 2011 ===&lt;br /&gt;
'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm &lt;br /&gt;
'''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190&lt;br /&gt;
'''Food Sponsor:''' Akamai&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
  * News / Updates&lt;br /&gt;
  * 2011 Election (voice vote on the entire slate)&lt;br /&gt;
  * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 &amp;quot;Broken Authentication and Session Management&amp;quot;]&lt;br /&gt;
  * Speaker: Steve Witmer on A3 from the &amp;quot;breakers&amp;quot; perspective&lt;br /&gt;
  * Speaker: ??? on A3 from the &amp;quot;fixers/defenders&amp;quot; perspective&lt;br /&gt;
  * Firetalks! :)&lt;br /&gt;
  * '''Update:''' All election candidates were elected by voice vote. &lt;br /&gt;
     * Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&amp;amp;authkey=CIS9zFM '11 Chapter Board Election Material]&lt;br /&gt;
&lt;br /&gt;
=== April 2011 ===&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
'''Food Sponsor:''' [https://www.cigital.com Cigital]&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
  * News / Updates&lt;br /&gt;
  * 2011 Election&lt;br /&gt;
  * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson ([https://www.owasp.org/images/9/92/Xssnotfriend-edited.pptx PPTX] or [https://www.owasp.org/images/0/06/Xssnotfriend-edited.pdf PDF])&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=112072</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=112072"/>
				<updated>2011-06-13T16:04:17Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month.&lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)&lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190&lt;br /&gt;
&lt;br /&gt;
'''Food Sponsor:''' The College Board&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 &amp;quot;Insecure Direct Object References&amp;quot;]&lt;br /&gt;
* College Board Speaker: &amp;quot;Attack-in-Depth:  Exploits of the OWASP Top Ten in Action&amp;quot;&lt;br /&gt;
* Firetalks! :)&lt;br /&gt;
** Jack Mannino: &amp;quot;Android Security 101&amp;quot;&lt;br /&gt;
** Others!&lt;br /&gt;
&lt;br /&gt;
'''[http://owaspnova060911.eventbrite.com/ Please RSVP]'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== May 2011 ===&lt;br /&gt;
'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm &lt;br /&gt;
'''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190&lt;br /&gt;
'''Food Sponsor:''' Akamai&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
  * News / Updates&lt;br /&gt;
  * 2011 Election (voice vote on the entire slate)&lt;br /&gt;
  * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 &amp;quot;Broken Authentication and Session Management&amp;quot;]&lt;br /&gt;
  * Speaker: Steve Witmer on A3 from the &amp;quot;breakers&amp;quot; perspective&lt;br /&gt;
  * Speaker: ??? on A3 from the &amp;quot;fixers/defenders&amp;quot; perspective&lt;br /&gt;
  * Firetalks! :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== April 2011 ===&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
'''Food Sponsor:''' [https://www.cigital.com Cigital]&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
  * News / Updates&lt;br /&gt;
  * 2011 Election&lt;br /&gt;
  * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson ([https://www.owasp.org/images/9/92/Xssnotfriend-edited.pptx PPTX] or [https://www.owasp.org/images/0/06/Xssnotfriend-edited.pdf PDF])&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=112071</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=112071"/>
				<updated>2011-06-13T16:03:39Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Letter from Chapter President - John Steven */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== '11 Election  ====&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board Responsibilities ===&lt;br /&gt;
&lt;br /&gt;
* '''Board Member''' Three (3) - OWASP NoVA Chapter Board Members will be verified OWASP members, in good standing, dedicated to direction and governance of the chapter. Responsibilities will include:&lt;br /&gt;
  * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics &lt;br /&gt;
  * Recruiting OWASP membership&lt;br /&gt;
  * Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
  * Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
  * Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
  * Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
  * Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations &lt;br /&gt;
  * Collecting and auditing use of chapter funds&lt;br /&gt;
  * Voting on chapter matters&lt;br /&gt;
&lt;br /&gt;
* '''Board Chairperson''' (1) - OWASP NoVA Chapter Board Chairperson will be a verified OWASP member, in good standing, dedicated to the direction and governance of the chapter. Responsibilities will include those of a board member. In addition, the chairperson will:&lt;br /&gt;
  * Defer to, facilitate, and support the activities and projects of the chapter board and its membership&lt;br /&gt;
  * Represent chapter in OWASP forums, such as the global summit&lt;br /&gt;
  * In conjunction with OWASP NoVA Board Members, set annual chapter mission&lt;br /&gt;
&lt;br /&gt;
All board members should be prepared to:&lt;br /&gt;
  * Devote approximately 4 hrs every two weeks to chapter business&lt;br /&gt;
  * Stand for election every twenty-four (24) months &lt;br /&gt;
  * Remain absolutely vendor neutral and&lt;br /&gt;
  * Uphold the OWASP principals and code of ethics.&lt;br /&gt;
&lt;br /&gt;
=== Election Procedures ===&lt;br /&gt;
'''Proof of Eligibility'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Candidates wishing to stand for election, will verify their eligibility along with posting their intentions in the section below. Eligibility will be verified through the following means:&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;List your name&lt;br /&gt;
&amp;lt;LI&amp;gt;List your OWASP Member ID (available here: [http://spreadsheets.google.com/a/owasp.org/pub?key=p6IFyntQTi7sxa2Xjx191BA Individual Member Roster]). Individual membership not required for election, but strongly recommended in order to 'lead by example'. Those seeking membership can find more information [http://www.owasp.org/index.php/Membership here]&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Indicate what city and town you live in (We'll only consider local members, but you may live in WV, VA, MD, or DC)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsement from someone else in the chapter&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Time table'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will announce their intentions at our next Chapter meeting, April 7, 2011 @ 6pm. Candidates unable to appear in person can announce their intentions through editing the wiki. If you'd like, I (John) can read something on your behalf at the meeting.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will be asked to give a brief (5 minute) talk discussing their intentions for candidacy. Candidates will also announce the position for which they're running.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;A vote will be conducted during our May chapter meeting&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;The ''final deadline for candidacy'' will be &amp;quot;close of business&amp;quot; on Friday, April 8th, 2011 (6pm EDT).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Voting'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
The election procedure will be as follows:&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Votes will be cast at our May 4th, 2011 chapter meeting, promptly @ 6pm.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Chapter participants must be present in person to vote.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Absentee voting will be allowed in the case participants can not be present on the 4th, due to medical, travel, or other reasons. Absentee voters must contact both [mailto:John.Steven@owasp.org John Steven] and [mailto:benjamin.tomhave@owasp.org Ben Tomhave] with your intention to absentee vote no later than April 29th, 2011 @ 6pm.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Votes will be counted during the May 4th meeting, and an announcement made as to the winner at the meeting's end.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Candidates ===&lt;br /&gt;
&lt;br /&gt;
'''John Steven'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;OWASP Member ID: (68NSRT2PSVV)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Position: Board Chairperson&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Sterling, VA&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsed by: Jeremy Long (68NRW3GS8RN), Ben Tomhave (4HNL4UGE8KP)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Purpose: Grow chapter membership &amp;amp; participation with a keen focus on technical depth of presentations and material.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Jack Mannino'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;OWASP Member ID: (67324580)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Position: Board Member&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Northern VA&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsed by: John Steven (68NSRT2PSVV), Ben Tomhave (4HNL4UGE8KP)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Purpose: Ensure that the chapter remains vendor-neutral, increase collaboration between chapter members, and promote new technical initiatives within our chapter. &amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Ben Tomhave'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;OWASP Member ID: (4HNL4UGE8KP)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Position: Board Member&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Northern VA&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsed by: John Steven (68NSRT2PSVV), Jack Mannino (67324580)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Purpose: To continue growing chapter membership and participation through maintaining regularly scheduled meetings, ensuring high-quality talk/presentation content, helping facilitate meeting logistics, and by representing the chapter in Global matters (e.g. Global Summit, Global Conferences Committee).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Jeremy Long'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;OWASP Member ID: (68NRW3GS8RN)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Position: Board Member&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Northern VA&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsed by: John Steven (68NSRT2PSVV), Ben Tomhave (4HNL4UGE8KP)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Purpose: To help grow chapter membership, ensure presentations are vendor neutral stance with sufficient technical depth, and to assist in organizing regularly scheduled meetings.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month.&lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)&lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190&lt;br /&gt;
&lt;br /&gt;
'''Food Sponsor:''' The College Board&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
* News / Updates&lt;br /&gt;
* Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 &amp;quot;Insecure Direct Object References&amp;quot;]&lt;br /&gt;
* College Board Speaker: &amp;quot;Attack-in-Depth:  Exploits of the OWASP Top Ten in Action&amp;quot;&lt;br /&gt;
* Firetalks! :)&lt;br /&gt;
** Jack Mannino: &amp;quot;Android Security 101&amp;quot;&lt;br /&gt;
** Others!&lt;br /&gt;
&lt;br /&gt;
'''[http://owaspnova060911.eventbrite.com/ Please RSVP]'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== May 2011 ===&lt;br /&gt;
'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm &lt;br /&gt;
'''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190&lt;br /&gt;
'''Food Sponsor:''' Akamai&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
  * News / Updates&lt;br /&gt;
  * 2011 Election (voice vote on the entire slate)&lt;br /&gt;
  * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 &amp;quot;Broken Authentication and Session Management&amp;quot;]&lt;br /&gt;
  * Speaker: Steve Witmer on A3 from the &amp;quot;breakers&amp;quot; perspective&lt;br /&gt;
  * Speaker: ??? on A3 from the &amp;quot;fixers/defenders&amp;quot; perspective&lt;br /&gt;
  * Firetalks! :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== April 2011 ===&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
'''Food Sponsor:''' [https://www.cigital.com Cigital]&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
  * News / Updates&lt;br /&gt;
  * 2011 Election&lt;br /&gt;
  * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson ([https://www.owasp.org/images/9/92/Xssnotfriend-edited.pptx PPTX] or [https://www.owasp.org/images/0/06/Xssnotfriend-edited.pdf PDF])&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=ESAPI_Summit&amp;diff=111581</id>
		<title>ESAPI Summit</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=ESAPI_Summit&amp;diff=111581"/>
				<updated>2011-06-02T16:57:48Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Attending the ESAPI Summit */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summit 2011 ==&lt;br /&gt;
&lt;br /&gt;
=== Summit Overview ===&lt;br /&gt;
&lt;br /&gt;
The ESAPI Summit will be held on &lt;br /&gt;
&lt;br /&gt;
=== Agenda ===&lt;br /&gt;
&lt;br /&gt;
* 09:00 - 09:30 Mission Briefing&lt;br /&gt;
** Review Project Definition and Mission Statement (update if necc.)&lt;br /&gt;
* 09:30 - 10:30 Brain Dump&lt;br /&gt;
** Get everyones &amp;quot;big-picture&amp;quot; ideas up on the board&lt;br /&gt;
** Brief statement about each, this should be a fast-paced Mind-Mapping Exercise aimed to get as many ideas as we can on the board as quickly as possible&lt;br /&gt;
* 10:30 - 10:45 Break time&lt;br /&gt;
** Good job, get some coffee and some air and get prepared for the real work.&lt;br /&gt;
* 10:45 - 12:00 Bug Hunt&lt;br /&gt;
** Review the list of existing ESAPI Bugs, assign a champion to them, and prioritize per champion&lt;br /&gt;
* 12:00 - 13:00 Lunch - Open Conversation&lt;br /&gt;
** Lunch to be provided by OWASP/ESAPI &lt;br /&gt;
* 13:00 - 15:00 Where do we go now?&lt;br /&gt;
** Now that the bugs are fresh in our heads, let's revisit our master wish-list from earlier and prioritize future enhancements, lay them out into a version roadmap (not a calendar roadmap). Some of these enhancements will likely jump out as high-priority and others as nice-to-haves. It should also be remembered, that a version roadmap is a organic document, it will constantly change and evolve to meet the demands of our users. This is just a first step in getting such a roadmap in place. &lt;br /&gt;
* 15:00 - 15:15 Break time&lt;br /&gt;
** Get some air, there is sure to be some great debate to reflect on&lt;br /&gt;
* 15:15 - 16:00 Formally define the following policies&lt;br /&gt;
** Becoming a Committer&lt;br /&gt;
** Submitting Contributed Components&lt;br /&gt;
** Reporting Security Vulnerabilities&lt;br /&gt;
* 16:00 - 18:00 Aligning the ESAPI Projects&lt;br /&gt;
** How do we bring all of the implementations into alignment as far as the API is concerned&lt;br /&gt;
** How do we ensure that all implements adhere to the contract of the API&lt;br /&gt;
** What level of adherement to the specification do we enforce to &amp;quot;sign off&amp;quot; on various implementations&lt;br /&gt;
&lt;br /&gt;
=== Deliverables ===&lt;br /&gt;
&lt;br /&gt;
* [[ESAPI Roadmap]]&lt;br /&gt;
* [[How to become a committer]]&lt;br /&gt;
* [[How to submit contributions]]&lt;br /&gt;
* [[How to report security vulnerabilities]]&lt;br /&gt;
* [[ESAPI Cross Platform Specification]]&lt;br /&gt;
&lt;br /&gt;
=== Attending the ESAPI Summit ===&lt;br /&gt;
&lt;br /&gt;
If you are planning to attend this summit, please list your name below so that we can ensure that we have adequate space and materials for everyone.&lt;br /&gt;
&lt;br /&gt;
* [[User:Chris Schmidt|Chris Schmidt]] - Meeting Leader&lt;br /&gt;
* [[User:jmanico|Jim Manico]] - ESAPI Project Manager&lt;br /&gt;
* [[User:John Steven|jOHN Steven]] - Cigital Principal, ESAPI Malcontent&lt;br /&gt;
&lt;br /&gt;
== Summit 2008 ==&lt;br /&gt;
&lt;br /&gt;
=== Summit Overview ===&lt;br /&gt;
&lt;br /&gt;
The first OWASP ESAPI Summit was held December 9-11, 2008. It was hosted by Aspect Security in their Columbia, MD office.&lt;br /&gt;
&lt;br /&gt;
The following were the attendees of the Summit:&lt;br /&gt;
&lt;br /&gt;
*[[User:Jeff Williams|Jeff Williams]], Aspect Security - [[ESAPI|ESAPI Project Lead]]&lt;br /&gt;
*[[User:Wichers|Dave Wichers]], Aspect Security - [http://code.google.com/p/owasp-esapi-java/ ESAPI Java Committer]&lt;br /&gt;
*Ron Monzillo, Sun Microsystems - [http://java.sun.com/javaee/security/ Java EE Security Architect] &lt;br /&gt;
*[[User:Arshan|Arshan Dabirsiaghi]], Aspect Security - [[:Category:Intrinsic_Security_Working_Group|OWASP Intrisic Security Working Group Chair]]&lt;br /&gt;
*[[User:Jerryhoff|Jerry Hoff]], Aspect Security&lt;br /&gt;
*[[User:Mikehfauzy|Mike Fauzy]], Aspect Security&lt;br /&gt;
*[[User:Kevin.Fealey|Kevin Fealey]], Aspect Security - [[ESAPI Swingset|ESAPI Swingset Lead]]&lt;br /&gt;
*[[User:Jmanico|Jim Manico]], Aspect Security - [http://code.google.com/p/owasp-esapi-java/ ESAPI Java Committer]&lt;br /&gt;
*Steve Lavenhar, Booz Allen Hamilton&lt;br /&gt;
*Lian Jin, Booz Allen Hamilton&lt;br /&gt;
*John Steven, Cigital, Technical Director&lt;br /&gt;
*Joel Winstead, Cigital&lt;br /&gt;
*Alex Smolen, Foundstone - [[.NET ESAPI | ESAPI .NET Lead]]&lt;br /&gt;
*Andy Miller, Lockheed Martin&lt;br /&gt;
*John Munsch, Lockheed Martin&lt;br /&gt;
*Steve Christey, MITRE - [http://cve.mitre.org CVE]/[http://cwe.mitre.org CWE] Project Lead&lt;br /&gt;
&lt;br /&gt;
The following pages contain our thoughts/results from the summit.&lt;br /&gt;
&lt;br /&gt;
Summary: TODO&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
&lt;br /&gt;
* [[ESAPI Charter]]&lt;br /&gt;
* [[ESAPI Roadmap]]&lt;br /&gt;
* [[ESAPI Adoption Strategy]]&lt;br /&gt;
* [[ESAPI Framework Strategy]]&lt;br /&gt;
* [[ESAPI Assurance]]&lt;br /&gt;
* [[ESAPI Documentation]]&lt;br /&gt;
* [[ESAPI Marketing]]&lt;br /&gt;
* [[ESAPI Tooling]]&lt;br /&gt;
* [[ESAPI Static Analysis Support]]&lt;br /&gt;
* [[ESAPI Performance]]&lt;br /&gt;
* [[ESAPI Internationalization]]&lt;br /&gt;
* [[ESAPI Installation]]&lt;br /&gt;
&lt;br /&gt;
=== Design ===&lt;br /&gt;
&lt;br /&gt;
* [[ESAPI API]]&lt;br /&gt;
&lt;br /&gt;
=== Features ===&lt;br /&gt;
&lt;br /&gt;
* [[ESAPI Validation]]&lt;br /&gt;
* [[ESAPI Canonicalization]]&lt;br /&gt;
* [[ESAPI Encoding]]&lt;br /&gt;
* [[ESAPI Authentication]]&lt;br /&gt;
* [[ESAPI Session Management]]&lt;br /&gt;
* [[ESAPI Access Control]]&lt;br /&gt;
* [[ESAPI Encryption]]&lt;br /&gt;
* [[ESAPI Randomizer]]&lt;br /&gt;
* [[ESAPI Error Handling]]&lt;br /&gt;
* [[ESAPI Logging]]&lt;br /&gt;
* [[ESAPI Intrusion Detection]]&lt;br /&gt;
* [[ESAPI HTTP Protection]]&lt;br /&gt;
* [[ESAPI Utilities]]&lt;br /&gt;
* [[ESAPI Filters]]&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
[[Category:OWASP Enterprise Security API]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=108277</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=108277"/>
				<updated>2011-04-06T14:31:57Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== '11 Election  ====&lt;br /&gt;
&lt;br /&gt;
===  Letter from Chapter President - John Steven  ===&lt;br /&gt;
All,&lt;br /&gt;
&lt;br /&gt;
I'm proud of how much the Northern Virginia OWASP Chapter has grown in the past two years.  We've increased membership and attendance, and been able to provide you, our constituency, some interesting speakers, panels, and presentations. A single chapter lead has always headed our chapter but last year we saw enough participation and activity we felt the need to add a program committee. Now, we've reached a size where we'd benefit from more leadership and governance.&lt;br /&gt;
&lt;br /&gt;
As you familiarize yourself with OWASP you'll notice two principal memes:&lt;br /&gt;
&lt;br /&gt;
* Conduct operations in as open, transparent, &amp;amp; democratic a manner as possible&lt;br /&gt;
* Prefer progress to discussion--support engaged participants that produce results over promise &lt;br /&gt;
&lt;br /&gt;
To provide better leadership and governance within the two principals' vein, I'm establishing a chapter board to be made of three (3) individuals that share responsibilities described below by the &amp;quot;Chapter Board Responsibilities&amp;quot; section. A fourth chair-person of the board position will be established as well to facilitate overall chapter direction and chapter interaction with global OWASP governing bodies. This chair-person position will replace my current position and as such I will step down and stand for election myself. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;del&amp;gt;I'm going to restrict board membership to verified [http://www.owasp.org/index.php/Membership OWASP Members] but otherwise &amp;lt;/del&amp;gt; anyone and everyone should feel free to run. Procedures for candidacy and election are described by the &amp;quot;Election Procedures&amp;quot; section below. We plan to organize a campaign period in April and conduct the board election during our May chapter meeting.  Board members make a special commitment to facilitate the chapter's logistics, while growing its membership and attendance. &lt;br /&gt;
&lt;br /&gt;
Beyond elected board members, everybody and anybody should feel free to participate in our Northern Virginia OWASP chapter in any capacity they seem beneficial. I encourage individuals to attend chapter meetings, network, explore and consume OWASP resources voraciously. Likewise, I encourage anyone to &amp;quot;take the reigns&amp;quot; and speak, organize, contribute, and direct our chapter as they see fit. As a open, transparent, and member-driven community, OWASP does not require individuals to attain any status or rank before contributing, as long as contributions meet our [http://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project code of ethics]. Indeed, OWASP strives to be a meritocracy. Our new board, once elected, will strive to provide an environment in which all members feel welcome, able, and supported in providing what contributions they can.&lt;br /&gt;
&lt;br /&gt;
So, please join me in participating in our up-and-coming campaign and election proceedings. With your help, I am confident that the Northern Virginia Chapter can take even greater strides towards helping this area's professionals better address our application security challenges,&lt;br /&gt;
&lt;br /&gt;
-jOHN&amp;lt;br&amp;gt;&lt;br /&gt;
John.Steven@owasp.org&amp;lt;br&amp;gt;&lt;br /&gt;
Northern Virginia OWASP Chapter President,&amp;lt;br&amp;gt;&lt;br /&gt;
Phone: 703.727.4034&amp;lt;br&amp;gt;&lt;br /&gt;
Web: http://goo.gl/Y5d2y&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board Responsibilities ===&lt;br /&gt;
&lt;br /&gt;
* '''Board Member''' Three (3) - OWASP NoVA Chapter Board Members will be verified OWASP members, in good standing, dedicated to direction and governance of the chapter. Responsibilities will include:&lt;br /&gt;
  * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics &lt;br /&gt;
  * Recruiting OWASP membership&lt;br /&gt;
  * Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
  * Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
  * Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
  * Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
  * Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations &lt;br /&gt;
  * Collecting and auditing use of chapter funds&lt;br /&gt;
  * Voting on chapter matters&lt;br /&gt;
&lt;br /&gt;
* '''Board Chairperson''' (1) - OWASP NoVA Chapter Board Chairperson will be a verified OWASP member, in good standing, dedicated to the direction and governance of the chapter. Responsibilities will include those of a board member. In addition, the chairperson will:&lt;br /&gt;
  * Defer to, facilitate, and support the activities and projects of the chapter board and its membership&lt;br /&gt;
  * Represent chapter in OWASP forums, such as the global summit&lt;br /&gt;
  * In conjunction with OWASP NoVA Board Members, set annual chapter mission&lt;br /&gt;
&lt;br /&gt;
All board members should be prepared to:&lt;br /&gt;
  * Devote approximately 4 hrs every two weeks to chapter business&lt;br /&gt;
  * Stand for election every twenty-four (24) months &lt;br /&gt;
  * Remain absolutely vendor neutral and&lt;br /&gt;
  * Uphold the OWASP principals and code of ethics.&lt;br /&gt;
&lt;br /&gt;
=== Election Procedures ===&lt;br /&gt;
'''Proof of Eligibility'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Candidates wishing to stand for election, will verify their eligibility along with posting their intentions in the section below. Eligibility will be verified through the following means:&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;List your name&lt;br /&gt;
&amp;lt;LI&amp;gt;List your OWASP Member ID (available here: [http://spreadsheets.google.com/a/owasp.org/pub?key=p6IFyntQTi7sxa2Xjx191BA Individual Member Roster]). Individual membership not required for election, but strongly recommended in order to 'lead by example'. Those seeking membership can find more information [http://www.owasp.org/index.php/Membership here]&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Indicate what city and town you live in (We'll only consider local members, but you may live in WV, VA, MD, or DC)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsement from someone else in the chapter&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Time table'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will announce their intentions at our next Chapter meeting, April 7, 2011 @ 6pm. Candidates unable to appear in person can announce their intentions through editing the wiki. If you'd like, I (John) can read something on your behalf at the meeting.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will be asked to give a brief (5 minute) talk discussing their intentions for candidacy. Candidates will also announce the position for which they're running.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;A vote will be conducted during our May chapter meeting&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;The ''final deadline for candidacy'' will be &amp;quot;close of business&amp;quot; on Friday, April 8th, 2011 (6pm EDT).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Voting'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
The election procedure will be as follows:&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Votes will be cast at our May 4th, 2011 chapter meeting, promptly @ 6pm.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Chapter participants must be present in person to vote.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Absentee voting will be allowed in the case participants can not be present on the 4th, due to medical, travel, or other reasons. Absentee voters must contact both [mailto:John.Steven@owasp.org John Steven] and [mailto:benjamin.tomhave@owasp.org Ben Tomhave] with your intention to absentee vote no later than April 29th, 2011 @ 6pm.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Votes will be counted during the May 4th meeting, and an announcement made as to the winner at the meeting's end.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Candidates ===&lt;br /&gt;
&lt;br /&gt;
'''John Steven'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;OWASP Member ID: (68NSRT2PSVV)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Position: Board Chairperson&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Sterling, VA&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsed by: Jeremy Long (68NRW3GS8RN), Ben Tomhave (4HNL4UGE8KP)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Purpose: Grow chapter membership &amp;amp; participation with a keen focus on technical depth of presentations and material.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Jack Mannino'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;OWASP Member ID: (67324580)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Position: Board Member&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Northern VA&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsed by: John Steven (68NSRT2PSVV), Ben Tomhave (4HNL4UGE8KP)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Purpose: Ensure that the chapter remains vendor-neutral, increase collaboration between chapter members, and promote new technical initiatives within our chapter. &amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Ben Tomhave'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;OWASP Member ID: (4HNL4UGE8KP)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Position: Board Member&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Northern VA&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsed by: John Steven (68NSRT2PSVV), Jack Mannino (67324580)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Purpose: To continue growing chapter membership and participation through maintaining regularly scheduled meetings, ensuring high-quality talk/presentation content, helping facilitate meeting logistics, and by representing the chapter in Global matters (e.g. Global Summit, Global Conferences Committee).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Jeremy Long'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;OWASP Member ID: (68NRW3GS8RN)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Position: Board Member&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Northern VA&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsed by: John Steven (68NSRT2PSVV), Ben Tomhave (4HNL4UGE8KP)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Purpose: To help grow chapter membership, ensure presentations are vendor neutral stance with sufficient technical depth, and to assist in organizing regularly scheduled meetings.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month.&lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
'''Food Sponsor:''' [https://www.cigital.com Cigital]&lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
  * 2011 Election&lt;br /&gt;
  * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
'''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]''' &lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Global_Education_Committee_-_Application_7&amp;diff=107506</id>
		<title>Global Education Committee - Application 7</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Global_Education_Committee_-_Application_7&amp;diff=107506"/>
				<updated>2011-03-24T17:11:04Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&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;Dr. A.L. Gottlieb.&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;|Coordinator/facility host for N. Virginia, OWASP Presenter.&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 Education Committee&lt;br /&gt;
 |}&lt;br /&gt;
----&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;|Benjamin Tomhave&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|OWASP NoVA Program Committee, OWASP GCC member (pending final board approval)&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|Tony's contributions to OWASP NoVA have been outstanding! He has helped host several chapter meetings, has presented in the past, will be presenting again in April 2011, and is overall a strong supporter of OWASP Education initiatives.&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;|&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;|'''3'''&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|Dan Cornell&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|San Antonio Chapter Leader, Global Membership Committee Chair&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|Every time I have been to the OWASP NoVA chapter Tony has been an active and valuable contributor. The Global Education Committee would benefit from his perspective and enthusiasm.&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;| John Steven&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;| NoVA Chapter Lead&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;| Hell hath no fury like Tony on a mission to educate.&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;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107460</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107460"/>
				<updated>2011-03-24T12:53:58Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Candidates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== '11 Election  ====&lt;br /&gt;
&lt;br /&gt;
===  Letter from Chapter President - John Steven  ===&lt;br /&gt;
All,&lt;br /&gt;
&lt;br /&gt;
I'm proud of how much the Northern Virginia OWASP Chapter has grown in the past two years.  We've increased membership and attendance, and been able to provide you, our constituency, some interesting speakers, panels, and presentations. A single chapter lead has always headed our chapter but last year we saw enough participation and activity we felt the need to add a program committee. Now, we've reached a size where we'd benefit from more leadership and governance.&lt;br /&gt;
&lt;br /&gt;
As you familiarize yourself with OWASP you'll notice two principal memes:&lt;br /&gt;
&lt;br /&gt;
* Conduct operations in as open, transparent, &amp;amp; democratic a manner as possible&lt;br /&gt;
* Prefer progress to discussion--support engaged participants that produce results over promise &lt;br /&gt;
&lt;br /&gt;
To provide better leadership and governance within the two principals' vein, I'm establishing a chapter board to be made of three (3) individuals that share responsibilities described below by the &amp;quot;Chapter Board Responsibilities&amp;quot; section. A fourth chair-person of the board position will be established as well to facilitate overall chapter direction and chapter interaction with global OWASP governing bodies. This chair-person position will replace my current position and as such I will step down and stand for election myself. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;del&amp;gt;I'm going to restrict board membership to verified [http://www.owasp.org/index.php/Membership OWASP Members] but otherwise &amp;lt;/del&amp;gt; anyone and everyone should feel free to run. Procedures for candidacy and election are described by the &amp;quot;Election Procedures&amp;quot; section below. We plan to organize a campaign period in April and conduct the board election during our May chapter meeting.  Board members make a special commitment to facilitate the chapter's logistics, while growing its membership and attendance. &lt;br /&gt;
&lt;br /&gt;
Beyond elected board members, everybody and anybody should feel free to participate in our Northern Virginia OWASP chapter in any capacity they seem beneficial. I encourage individuals to attend chapter meetings, network, explore and consume OWASP resources voraciously. Likewise, I encourage anyone to &amp;quot;take the reigns&amp;quot; and speak, organize, contribute, and direct our chapter as they see fit. As a open, transparent, and member-driven community, OWASP does not require individuals to attain any status or rank before contributing, as long as contributions meet our [http://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project code of ethics]. Indeed, OWASP strives to be a meritocracy. Our new board, once elected, will strive to provide an environment in which all members feel welcome, able, and supported in providing what contributions they can.&lt;br /&gt;
&lt;br /&gt;
So, please join me in participating in our up-and-coming campaign and election proceedings. With your help, I am confident that the Northern Virginia Chapter can take even greater strides towards helping this area's professionals better address our application security challenges,&lt;br /&gt;
&lt;br /&gt;
-jOHN&amp;lt;br&amp;gt;&lt;br /&gt;
John.Steven@owasp.org&amp;lt;br&amp;gt;&lt;br /&gt;
Northern Virginia OWASP Chapter President,&amp;lt;br&amp;gt;&lt;br /&gt;
Phone: 703.727.4034&amp;lt;br&amp;gt;&lt;br /&gt;
Web: http://goo.gl/Y5d2y&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board Responsibilities ===&lt;br /&gt;
&lt;br /&gt;
* '''Board Member''' Three (3) - OWASP NoVA Chapter Board Members will be verified OWASP members, in good standing, dedicated to direction and governance of the chapter. Responsibilities will include:&lt;br /&gt;
  * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics &lt;br /&gt;
  * Recruiting OWASP membership&lt;br /&gt;
  * Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
  * Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
  * Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
  * Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
  * Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations &lt;br /&gt;
  * Collecting and auditing use of chapter funds&lt;br /&gt;
  * Voting on chapter matters&lt;br /&gt;
&lt;br /&gt;
* '''Board Chairperson''' (1) - OWASP NoVA Chapter Board Chairperson will be a verified OWASP member, in good standing, dedicated to the direction and governance of the chapter. Responsibilities will include those of a board member. In addition, the chairperson will:&lt;br /&gt;
  * Defer to, facilitate, and support the activities and projects of the chapter board and its membership&lt;br /&gt;
  * Represent chapter in OWASP forums, such as the global summit&lt;br /&gt;
  * In conjunction with OWASP NoVA Board Members, set annual chapter mission&lt;br /&gt;
&lt;br /&gt;
All board members should be prepared to:&lt;br /&gt;
  * Devote approximately 4 hrs every two weeks to chapter business&lt;br /&gt;
  * Stand for election every twenty-four (24) months &lt;br /&gt;
  * Remain absolutely vendor neutral and&lt;br /&gt;
  * Uphold the OWASP principals and code of ethics.&lt;br /&gt;
&lt;br /&gt;
=== Election Procedures ===&lt;br /&gt;
'''Proof of Eligibility'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Candidates wishing to stand for election, will verify their eligibility along with posting their intentions in the section below. Eligibility will be verified through the following means:&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;List your name&lt;br /&gt;
&amp;lt;LI&amp;gt;List your OWASP Member ID (available here: [http://spreadsheets.google.com/a/owasp.org/pub?key=p6IFyntQTi7sxa2Xjx191BA Individual Member Roster]). Individual membership not required for election, but strongly recommended in order to 'lead by example'. Those seeking membership can find more information [http://www.owasp.org/index.php/Membership here]&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Indicate what city and town you live in (We'll only consider local members, but you may live in WV, VA, MD, or DC)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsement from someone else in the chapter&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Time table'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will announce their intentions at our next Chapter meeting, April 7, 2011 @ 6pm. Candidates unable to appear in person can announce their intentions through editing the wiki. If you'd like, I (John) can read something on your behalf at the meeting.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will be asked to give a brief (5 minute) talk discussing their intentions for candidacy. Candidates will also announce the position for which they're running.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;A vote will be conducted during our May chapter meeting&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;The ''final deadline for candidacy'' will be &amp;quot;close of business&amp;quot; on Friday, April 8th, 2011 (6pm EDT).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Voting'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
The election procedure will be as follows:&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Votes will be cast at our May 4th, 2011 chapter meeting, promptly @ 6pm.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Chapter participants must be present in person to vote.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Absentee voting will be allowed in the case participants can not be present on the 4th, due to medical, travel, or other reasons. Absentee voters must contact both [mailto:John.Steven@owasp.org John Steven] and [mailto:benjamin.tomhave@owasp.org Ben Tomhave] with your intention to absentee vote no later than April 29th, 2011 @ 6pm.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Votes will be counted during the May 4th meeting, and an announcement made as to the winner at the meeting's end.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Candidates ===&lt;br /&gt;
&lt;br /&gt;
'''John Steven'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;OWASP Member ID: (68NSRT2PSVV)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Position: Board Chairperson&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Sterling, VA&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsed by: Jeremy Long (68NRW3GS8RN), Ben Tomhave (4HNL4UGE8KP)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Purpose: Grow chapter membership &amp;amp; participation with a keen focus on technical depth of presentations and material.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Jack Mannino'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;OWASP Member ID: (67324580)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Position: Board Member&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Northern VA&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsed by: John Steven (68NSRT2PSVV), Ben Tomhave (4HNL4UGE8KP)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Purpose: Ensure that the chapter remains vendor-neutral, increase collaboration between chapter members, and promote new technical initiatives within our chapter. &amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Ben Tomhave'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;OWASP Member ID: (4HNL4UGE8KP)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Position: Board Member&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Northern VA&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsed by: John Steven (68NSRT2PSVV), Jack Mannino (67324580)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Purpose: To continue growing chapter membership and participation through maintaining regularly scheduled meetings, ensuring high-quality talk/presentation content, helping facilitate meeting logistics, and by representing the chapter in Global matters (e.g. Global Summit, Global Conferences Committee).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Jeremy Long'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;OWASP Member ID: (68NRW3GS8RN)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Position: Board Member&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Northern VA&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsed by: John Steven (68NSRT2PSVV)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Purpose: To help grow chapter membership, ensure presentations are vendor neutral stance with sufficient technical depth, and to assist in organizing regularly scheduled meetings.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month.&lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
  * 2011 Election&lt;br /&gt;
  * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
'''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]''' &lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107413</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107413"/>
				<updated>2011-03-23T14:59:44Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Candidates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== '11 Election  ====&lt;br /&gt;
&lt;br /&gt;
===  Letter from Chapter President - John Steven  ===&lt;br /&gt;
All,&lt;br /&gt;
&lt;br /&gt;
I'm proud of how much the Northern Virginia OWASP Chapter has grown in the past two years.  We've increased membership and attendance, and been able to provide you, our constituency, some interesting speakers, panels, and presentations. A single chapter lead has always headed our chapter but last year we saw enough participation and activity we felt the need to add a program committee. Now, we've reached a size where we'd benefit from more leadership and governance.&lt;br /&gt;
&lt;br /&gt;
As you familiarize yourself with OWASP you'll notice two principal memes:&lt;br /&gt;
&lt;br /&gt;
* Conduct operations in as open, transparent, &amp;amp; democratic a manner as possible&lt;br /&gt;
* Prefer progress to discussion--support engaged participants that produce results over promise &lt;br /&gt;
&lt;br /&gt;
To provide better leadership and governance within the two principals' vein, I'm establishing a chapter board to be made of three (3) individuals that share responsibilities described below by the &amp;quot;Chapter Board Responsibilities&amp;quot; section. A fourth chair-person of the board position will be established as well to facilitate overall chapter direction and chapter interaction with global OWASP governing bodies. This chair-person position will replace my current position and as such I will step down and stand for election myself. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;del&amp;gt;I'm going to restrict board membership to verified [http://www.owasp.org/index.php/Membership OWASP Members] but otherwise &amp;lt;/del&amp;gt; anyone and everyone should feel free to run. Procedures for candidacy and election are described by the &amp;quot;Election Procedures&amp;quot; section below. We plan to organize a campaign period in April and conduct the board election during our May chapter meeting.  Board members make a special commitment to facilitate the chapter's logistics, while growing its membership and attendance. &lt;br /&gt;
&lt;br /&gt;
Beyond elected board members, everybody and anybody should feel free to participate in our Northern Virginia OWASP chapter in any capacity they seem beneficial. I encourage individuals to attend chapter meetings, network, explore and consume OWASP resources voraciously. Likewise, I encourage anyone to &amp;quot;take the reigns&amp;quot; and speak, organize, contribute, and direct our chapter as they see fit. As a open, transparent, and member-driven community, OWASP does not require individuals to attain any status or rank before contributing, as long as contributions meet our [http://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project code of ethics]. Indeed, OWASP strives to be a meritocracy. Our new board, once elected, will strive to provide an environment in which all members feel welcome, able, and supported in providing what contributions they can.&lt;br /&gt;
&lt;br /&gt;
So, please join me in participating in our up-and-coming campaign and election proceedings. With your help, I am confident that the Northern Virginia Chapter can take even greater strides towards helping this area's professionals better address our application security challenges,&lt;br /&gt;
&lt;br /&gt;
-jOHN&amp;lt;br&amp;gt;&lt;br /&gt;
John.Steven@owasp.org&amp;lt;br&amp;gt;&lt;br /&gt;
Northern Virginia OWASP Chapter President,&amp;lt;br&amp;gt;&lt;br /&gt;
Phone: 703.727.4034&amp;lt;br&amp;gt;&lt;br /&gt;
Web: http://goo.gl/Y5d2y&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board Responsibilities ===&lt;br /&gt;
&lt;br /&gt;
* '''Board Member''' Three (3) - OWASP NoVA Chapter Board Members will be verified OWASP members, in good standing, dedicated to direction and governance of the chapter. Responsibilities will include:&lt;br /&gt;
  * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics &lt;br /&gt;
  * Recruiting OWASP membership&lt;br /&gt;
  * Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
  * Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
  * Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
  * Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
  * Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations &lt;br /&gt;
  * Collecting and auditing use of chapter funds&lt;br /&gt;
  * Voting on chapter matters&lt;br /&gt;
&lt;br /&gt;
* '''Board Chairperson''' (1) - OWASP NoVA Chapter Board Chairperson will be a verified OWASP member, in good standing, dedicated to the direction and governance of the chapter. Responsibilities will include those of a board member. In addition, the chairperson will:&lt;br /&gt;
  * Defer to, facilitate, and support the activities and projects of the chapter board and its membership&lt;br /&gt;
  * Represent chapter in OWASP forums, such as the global summit&lt;br /&gt;
  * In conjunction with OWASP NoVA Board Members, set annual chapter mission&lt;br /&gt;
&lt;br /&gt;
All board members should be prepared to:&lt;br /&gt;
  * Devote approximately 4 hrs every two weeks to chapter business&lt;br /&gt;
  * Stand for election every twenty-four (24) months &lt;br /&gt;
  * Remain absolutely vendor neutral and&lt;br /&gt;
  * Uphold the OWASP principals and code of ethics.&lt;br /&gt;
&lt;br /&gt;
=== Election Procedures ===&lt;br /&gt;
'''Proof of Eligibility'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Candidates wishing to stand for election, will verify their eligibility along with posting their intentions in the section below. Eligibility will be verified through the following means:&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;List your name&lt;br /&gt;
&amp;lt;LI&amp;gt;List your OWASP Member ID (available here: [http://spreadsheets.google.com/a/owasp.org/pub?key=p6IFyntQTi7sxa2Xjx191BA Individual Member Roster]). Individual membership not required for election, but strongly recommended in order to 'lead by example'. Those seeking membership can find more information [http://www.owasp.org/index.php/Membership here]&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Indicate what city and town you live in (We'll only consider local members, but you may live in WV, VA, MD, or DC)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsement from someone else in the chapter&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Time table'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will announce their intentions at our next Chapter meeting, April 7, 2011 @ 6pm. Candidates unable to appear in person can announce their intentions through editing the wiki. If you'd like, I (John) can read something on your behalf at the meeting.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will be asked to give a brief (5 minute) talk discussing their intentions for candidacy. Candidates will also announce the position for which they're running.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;A vote will be conducted during our May chapter meeting&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;The ''final deadline for candidacy'' will be &amp;quot;close of business&amp;quot; on Friday, April 8th, 2011 (6pm EDT).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Voting'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
The election procedure will be as follows:&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Votes will be cast at our May 4th, 2011 chapter meeting, promptly @ 6pm.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Chapter participants must be present in person to vote.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Absentee voting will be allowed in the case participants can not be present on the 4th, due to medical, travel, or other reasons. Absentee voters must contact both [mailto:John.Steven@owasp.org John Steven] and [mailto:benjamin.tomhave@owasp.org Ben Tomhave] with your intention to absentee vote no later than April 29th, 2011 @ 6pm.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Votes will be counted during the May 4th meeting, and an announcement made as to the winner at the meeting's end.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Candidates ===&lt;br /&gt;
&lt;br /&gt;
'''John Steven'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;OWASP Member ID: (68NSRT2PSVV)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Position: Board Chairperson&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Sterling, VA&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsed by: Jeremy Long (68NRW3GS8RN), Ben Tomhave (4HNL4UGE8KP)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Purpose: Grow chapter membership &amp;amp; participation with a keen focus on technical depth of presentations and material.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Jack Mannino'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;OWASP Member ID: (67324580)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Position: Board Member&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Northern VA&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsed by: John Steven (68NSRT2PSVV), Ben Tomhave (4HNL4UGE8KP)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Purpose: Ensure that the chapter remains vendor-neutral, increase collaboration between chapter members, and promote new technical initiatives within our chapter. &amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Ben Tomhave'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;OWASP Member ID: (4HNL4UGE8KP)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Position: Board Member&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Northern VA&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsed by: John Steven (68NSRT2PSVV)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Purpose: To continue growing chapter membership and participation through maintaining regularly scheduled meetings, ensuring high-quality talk/presentation content, helping facilitate meeting logistics, and by representing the chapter in Global matters (e.g. Global Summit, Global Conferences Committee).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month.&lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
  * News / Updates&lt;br /&gt;
  * 2011 Election&lt;br /&gt;
  * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
'''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]''' &lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107251</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107251"/>
				<updated>2011-03-21T16:28:48Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Candidates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== '11 Election  ====&lt;br /&gt;
&lt;br /&gt;
===  Letter from Chapter President - John Steven  ===&lt;br /&gt;
All,&lt;br /&gt;
&lt;br /&gt;
I'm proud of how much the Northern Virginia OWASP Chapter has grown in the past two years.  We've increased membership and attendance, and been able to provide you, our constituency, some interesting speakers, panels, and presentations. A single chapter lead has always headed our chapter but last year we saw enough participation and activity we felt the need to add a program committee. Now, we've reached a size where we'd benefit from more leadership and governance.&lt;br /&gt;
&lt;br /&gt;
As you familiarize yourself with OWASP you'll notice two principal memes:&lt;br /&gt;
&lt;br /&gt;
* Conduct operations in as open, transparent, &amp;amp; democratic a manner as possible&lt;br /&gt;
* Prefer progress to discussion--support engaged participants that produce results over promise &lt;br /&gt;
&lt;br /&gt;
To provide better leadership and governance within the two principals' vein, I'm establishing a chapter board to be made of three (3) individuals that share responsibilities described below by the &amp;quot;Chapter Board Responsibilities&amp;quot; section. A fourth chair-person of the board position will be established as well to facilitate overall chapter direction and chapter interaction with global OWASP governing bodies. This chair-person position will replace my current position and as such I will step down and stand for election myself. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;del&amp;gt;I'm going to restrict board membership to verified [http://www.owasp.org/index.php/Membership OWASP Members] but otherwise &amp;lt;/del&amp;gt; anyone and everyone should feel free to run. Procedures for candidacy and election are described by the &amp;quot;Election Procedures&amp;quot; section below. We plan to organize a campaign period in April and conduct the board election during our May chapter meeting.  Board members make a special commitment to facilitate the chapter's logistics, while growing its membership and attendance. &lt;br /&gt;
&lt;br /&gt;
Beyond elected board members, everybody and anybody should feel free to participate in our Northern Virginia OWASP chapter in any capacity they seem beneficial. I encourage individuals to attend chapter meetings, network, explore and consume OWASP resources voraciously. Likewise, I encourage anyone to &amp;quot;take the reigns&amp;quot; and speak, organize, contribute, and direct our chapter as they see fit. As a open, transparent, and member-driven community, OWASP does not require individuals to attain any status or rank before contributing, as long as contributions meet our [http://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project code of ethics]. Indeed, OWASP strives to be a meritocracy. Our new board, once elected, will strive to provide an environment in which all members feel welcome, able, and supported in providing what contributions they can.&lt;br /&gt;
&lt;br /&gt;
So, please join me in participating in our up-and-coming campaign and election proceedings. With your help, I am confident that the Northern Virginia Chapter can take even greater strides towards helping this area's professionals better address our application security challenges,&lt;br /&gt;
&lt;br /&gt;
-jOHN&amp;lt;br&amp;gt;&lt;br /&gt;
John.Steven@owasp.org&amp;lt;br&amp;gt;&lt;br /&gt;
Northern Virginia OWASP Chapter President,&amp;lt;br&amp;gt;&lt;br /&gt;
Phone: 703.727.4034&amp;lt;br&amp;gt;&lt;br /&gt;
Web: http://goo.gl/Y5d2y&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board Responsibilities ===&lt;br /&gt;
&lt;br /&gt;
* '''Board Member''' Three (3) - OWASP NoVA Chapter Board Members will be verified OWASP members, in good standing, dedicated to direction and governance of the chapter. Responsibilities will include:&lt;br /&gt;
&lt;br /&gt;
* Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics &lt;br /&gt;
* Recruiting OWASP membership&lt;br /&gt;
* Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
* Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
* Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
* Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
* Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations &lt;br /&gt;
* Collecting and auditing use of chapter funds&lt;br /&gt;
* Voting on chapter matters&lt;br /&gt;
&lt;br /&gt;
* '''Board Chairperson''' (1) - OWASP NoVA Chapter Board Chairperson will be a verified OWASP member, in good standing, dedicated to the direction and governance of the chapter. Responsibilities will include those of a board member. In addition, the chairperson will:&lt;br /&gt;
&lt;br /&gt;
* Defer to, facilitate, and support the activities and projects of the chapter board and its membership&lt;br /&gt;
* Represent chapter in OWASP forums, such as the global summit&lt;br /&gt;
* In conjunction with OWASP NoVA Board Members, set annual chapter mission&lt;br /&gt;
&lt;br /&gt;
Board members should be prepared to:&lt;br /&gt;
&lt;br /&gt;
* Devote approximately 4 hrs every two weeks to chapter business&lt;br /&gt;
* Stand for election every twenty-four (24) months &lt;br /&gt;
* Remain absolutely vendor neutral and&lt;br /&gt;
* Uphold the OWASP principals and code of ethics.&lt;br /&gt;
&lt;br /&gt;
=== Election Procedures ===&lt;br /&gt;
'''Proof of Eligibility'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Candidates wishing to stand for election, will verify their eligibility along with posting their intentions in the section below. Eligibility will be verified through the following means:&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;List your name&lt;br /&gt;
&amp;lt;LI&amp;gt;List your OWASP member ID (available here: [http://spreadsheets.google.com/a/owasp.org/pub?key=p6IFyntQTi7sxa2Xjx191BA Individual Member Roster]). Individual membership not required for election, but strongly recommended in order to 'lead by example'. Those seeking membership can find more information [http://www.owasp.org/index.php/Membership here]&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Indicate what city and town you live in (We'll only consider local members, but you may live in WV, VA, MD, or DC)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsement from someone else in the chapter&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Time table'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will announce their intentions at our next Chapter meeting, April 7, 2011 @ 6pm. Candidates unable to appear in person can announce their intentions through editing the wiki. If you'd like, I can read something on your behalf at the meeting.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will be asked to give a brief (5 minute) talk discussing their intentions for candidacy.Candidates will also announce the position for which they're running.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;A vote will be conducted during our May chapter meeting&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;The deadline for candidacy will be the meeting's end, April 7th, 2011, @9pm.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Voting'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
The election procedure will be as follows:&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Votes will be cast at our May 4th, 2011 chapter meeting, promptly @ 6pm.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Chapter participants must be present in person to vote.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Absentee voting will be allowed in the case participants can not be present on the 4th, due to medical, travel, or other reasons. Absentee voters must contact both John Steven and Ben Tomhave with your intention to absentee vote no later than April 29th, 2011 @ 6pm.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Votes will be counted during the May 4th meeting, and an announcement made as to the winner at the meeting's end.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Candidates ===&lt;br /&gt;
&lt;br /&gt;
'''John Steven'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;OWASP Member ID: (68NSRT2PSVV)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Position: Board Chairperson&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Sterling, VA&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsed by: Jeremy Long (68NRW3GS8RN)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Purpose: Grow chapter membership &amp;amp; participation with a keen focus on technical depth of presentations and material.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month.&lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
'''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]''' &lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107250</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107250"/>
				<updated>2011-03-21T16:27:31Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Candidates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== '11 Election  ====&lt;br /&gt;
&lt;br /&gt;
===  Letter from Chapter President - John Steven  ===&lt;br /&gt;
All,&lt;br /&gt;
&lt;br /&gt;
I'm proud of how much the Northern Virginia OWASP Chapter has grown in the past two years.  We've increased membership and attendance, and been able to provide you, our constituency, some interesting speakers, panels, and presentations. A single chapter lead has always headed our chapter but last year we saw enough participation and activity we felt the need to add a program committee. Now, we've reached a size where we'd benefit from more leadership and governance.&lt;br /&gt;
&lt;br /&gt;
As you familiarize yourself with OWASP you'll notice two principal memes:&lt;br /&gt;
&lt;br /&gt;
* Conduct operations in as open, transparent, &amp;amp; democratic a manner as possible&lt;br /&gt;
* Prefer progress to discussion--support engaged participants that produce results over promise &lt;br /&gt;
&lt;br /&gt;
To provide better leadership and governance within the two principals' vein, I'm establishing a chapter board to be made of three (3) individuals that share responsibilities described below by the &amp;quot;Chapter Board Responsibilities&amp;quot; section. A fourth chair-person of the board position will be established as well to facilitate overall chapter direction and chapter interaction with global OWASP governing bodies. This chair-person position will replace my current position and as such I will step down and stand for election myself. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;del&amp;gt;I'm going to restrict board membership to verified [http://www.owasp.org/index.php/Membership OWASP Members] but otherwise &amp;lt;/del&amp;gt; anyone and everyone should feel free to run. Procedures for candidacy and election are described by the &amp;quot;Election Procedures&amp;quot; section below. We plan to organize a campaign period in April and conduct the board election during our May chapter meeting.  Board members make a special commitment to facilitate the chapter's logistics, while growing its membership and attendance. &lt;br /&gt;
&lt;br /&gt;
Beyond elected board members, everybody and anybody should feel free to participate in our Northern Virginia OWASP chapter in any capacity they seem beneficial. I encourage individuals to attend chapter meetings, network, explore and consume OWASP resources voraciously. Likewise, I encourage anyone to &amp;quot;take the reigns&amp;quot; and speak, organize, contribute, and direct our chapter as they see fit. As a open, transparent, and member-driven community, OWASP does not require individuals to attain any status or rank before contributing, as long as contributions meet our [http://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project code of ethics]. Indeed, OWASP strives to be a meritocracy. Our new board, once elected, will strive to provide an environment in which all members feel welcome, able, and supported in providing what contributions they can.&lt;br /&gt;
&lt;br /&gt;
So, please join me in participating in our up-and-coming campaign and election proceedings. With your help, I am confident that the Northern Virginia Chapter can take even greater strides towards helping this area's professionals better address our application security challenges,&lt;br /&gt;
&lt;br /&gt;
-jOHN&amp;lt;br&amp;gt;&lt;br /&gt;
John.Steven@owasp.org&amp;lt;br&amp;gt;&lt;br /&gt;
Northern Virginia OWASP Chapter President,&amp;lt;br&amp;gt;&lt;br /&gt;
Phone: 703.727.4034&amp;lt;br&amp;gt;&lt;br /&gt;
Web: http://goo.gl/Y5d2y&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board Responsibilities ===&lt;br /&gt;
&lt;br /&gt;
* '''Board Member''' Three (3) - OWASP NoVA Chapter Board Members will be verified OWASP members, in good standing, dedicated to direction and governance of the chapter. Responsibilities will include:&lt;br /&gt;
&lt;br /&gt;
* Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics &lt;br /&gt;
* Recruiting OWASP membership&lt;br /&gt;
* Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
* Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
* Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
* Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
* Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations &lt;br /&gt;
* Collecting and auditing use of chapter funds&lt;br /&gt;
* Voting on chapter matters&lt;br /&gt;
&lt;br /&gt;
* '''Board Chairperson''' (1) - OWASP NoVA Chapter Board Chairperson will be a verified OWASP member, in good standing, dedicated to the direction and governance of the chapter. Responsibilities will include those of a board member. In addition, the chairperson will:&lt;br /&gt;
&lt;br /&gt;
* Defer to, facilitate, and support the activities and projects of the chapter board and its membership&lt;br /&gt;
* Represent chapter in OWASP forums, such as the global summit&lt;br /&gt;
* In conjunction with OWASP NoVA Board Members, set annual chapter mission&lt;br /&gt;
&lt;br /&gt;
Board members should be prepared to:&lt;br /&gt;
&lt;br /&gt;
* Devote approximately 4 hrs every two weeks to chapter business&lt;br /&gt;
* Stand for election every twenty-four (24) months &lt;br /&gt;
* Remain absolutely vendor neutral and&lt;br /&gt;
* Uphold the OWASP principals and code of ethics.&lt;br /&gt;
&lt;br /&gt;
=== Election Procedures ===&lt;br /&gt;
'''Proof of Eligibility'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Candidates wishing to stand for election, will verify their eligibility along with posting their intentions in the section below. Eligibility will be verified through the following means:&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;List your name&lt;br /&gt;
&amp;lt;LI&amp;gt;List your OWASP member ID (available here: [http://spreadsheets.google.com/a/owasp.org/pub?key=p6IFyntQTi7sxa2Xjx191BA Individual Member Roster]). Individual membership not required for election, but strongly recommended in order to 'lead by example'. Those seeking membership can find more information [http://www.owasp.org/index.php/Membership here]&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Indicate what city and town you live in (We'll only consider local members, but you may live in WV, VA, MD, or DC)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsement from someone else in the chapter&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Time table'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will announce their intentions at our next Chapter meeting, April 7, 2011 @ 6pm. Candidates unable to appear in person can announce their intentions through editing the wiki. If you'd like, I can read something on your behalf at the meeting.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will be asked to give a brief (5 minute) talk discussing their intentions for candidacy.Candidates will also announce the position for which they're running.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;A vote will be conducted during our May chapter meeting&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;The deadline for candidacy will be the meeting's end, April 7th, 2011, @9pm.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Voting'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
The election procedure will be as follows:&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Votes will be cast at our May 4th, 2011 chapter meeting, promptly @ 6pm.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Chapter participants must be present in person to vote.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Absentee voting will be allowed in the case participants can not be present on the 4th, due to medical, travel, or other reasons. Absentee voters must contact both John Steven and Ben Tomhave with your intention to absentee vote no later than April 29th, 2011 @ 6pm.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Votes will be counted during the May 4th meeting, and an announcement made as to the winner at the meeting's end.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Candidates ===&lt;br /&gt;
&lt;br /&gt;
'''John Steven'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;OWASP Member ID: (68NSRT2PSVV)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Position: Board Chairperson&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsed by: Jeremy Long (68NRW3GS8RN)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month.&lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
'''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]''' &lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107249</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107249"/>
				<updated>2011-03-21T16:24:40Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Election Procedures */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== '11 Election  ====&lt;br /&gt;
&lt;br /&gt;
===  Letter from Chapter President - John Steven  ===&lt;br /&gt;
All,&lt;br /&gt;
&lt;br /&gt;
I'm proud of how much the Northern Virginia OWASP Chapter has grown in the past two years.  We've increased membership and attendance, and been able to provide you, our constituency, some interesting speakers, panels, and presentations. A single chapter lead has always headed our chapter but last year we saw enough participation and activity we felt the need to add a program committee. Now, we've reached a size where we'd benefit from more leadership and governance.&lt;br /&gt;
&lt;br /&gt;
As you familiarize yourself with OWASP you'll notice two principal memes:&lt;br /&gt;
&lt;br /&gt;
* Conduct operations in as open, transparent, &amp;amp; democratic a manner as possible&lt;br /&gt;
* Prefer progress to discussion--support engaged participants that produce results over promise &lt;br /&gt;
&lt;br /&gt;
To provide better leadership and governance within the two principals' vein, I'm establishing a chapter board to be made of three (3) individuals that share responsibilities described below by the &amp;quot;Chapter Board Responsibilities&amp;quot; section. A fourth chair-person of the board position will be established as well to facilitate overall chapter direction and chapter interaction with global OWASP governing bodies. This chair-person position will replace my current position and as such I will step down and stand for election myself. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;del&amp;gt;I'm going to restrict board membership to verified [http://www.owasp.org/index.php/Membership OWASP Members] but otherwise &amp;lt;/del&amp;gt; anyone and everyone should feel free to run. Procedures for candidacy and election are described by the &amp;quot;Election Procedures&amp;quot; section below. We plan to organize a campaign period in April and conduct the board election during our May chapter meeting.  Board members make a special commitment to facilitate the chapter's logistics, while growing its membership and attendance. &lt;br /&gt;
&lt;br /&gt;
Beyond elected board members, everybody and anybody should feel free to participate in our Northern Virginia OWASP chapter in any capacity they seem beneficial. I encourage individuals to attend chapter meetings, network, explore and consume OWASP resources voraciously. Likewise, I encourage anyone to &amp;quot;take the reigns&amp;quot; and speak, organize, contribute, and direct our chapter as they see fit. As a open, transparent, and member-driven community, OWASP does not require individuals to attain any status or rank before contributing, as long as contributions meet our [http://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project code of ethics]. Indeed, OWASP strives to be a meritocracy. Our new board, once elected, will strive to provide an environment in which all members feel welcome, able, and supported in providing what contributions they can.&lt;br /&gt;
&lt;br /&gt;
So, please join me in participating in our up-and-coming campaign and election proceedings. With your help, I am confident that the Northern Virginia Chapter can take even greater strides towards helping this area's professionals better address our application security challenges,&lt;br /&gt;
&lt;br /&gt;
-jOHN&amp;lt;br&amp;gt;&lt;br /&gt;
John.Steven@owasp.org&amp;lt;br&amp;gt;&lt;br /&gt;
Northern Virginia OWASP Chapter President,&amp;lt;br&amp;gt;&lt;br /&gt;
Phone: 703.727.4034&amp;lt;br&amp;gt;&lt;br /&gt;
Web: http://goo.gl/Y5d2y&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board Responsibilities ===&lt;br /&gt;
&lt;br /&gt;
* '''Board Member''' Three (3) - OWASP NoVA Chapter Board Members will be verified OWASP members, in good standing, dedicated to direction and governance of the chapter. Responsibilities will include:&lt;br /&gt;
&lt;br /&gt;
* Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics &lt;br /&gt;
* Recruiting OWASP membership&lt;br /&gt;
* Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
* Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
* Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
* Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
* Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations &lt;br /&gt;
* Collecting and auditing use of chapter funds&lt;br /&gt;
* Voting on chapter matters&lt;br /&gt;
&lt;br /&gt;
* '''Board Chairperson''' (1) - OWASP NoVA Chapter Board Chairperson will be a verified OWASP member, in good standing, dedicated to the direction and governance of the chapter. Responsibilities will include those of a board member. In addition, the chairperson will:&lt;br /&gt;
&lt;br /&gt;
* Defer to, facilitate, and support the activities and projects of the chapter board and its membership&lt;br /&gt;
* Represent chapter in OWASP forums, such as the global summit&lt;br /&gt;
* In conjunction with OWASP NoVA Board Members, set annual chapter mission&lt;br /&gt;
&lt;br /&gt;
Board members should be prepared to:&lt;br /&gt;
&lt;br /&gt;
* Devote approximately 4 hrs every two weeks to chapter business&lt;br /&gt;
* Stand for election every twenty-four (24) months &lt;br /&gt;
* Remain absolutely vendor neutral and&lt;br /&gt;
* Uphold the OWASP principals and code of ethics.&lt;br /&gt;
&lt;br /&gt;
=== Election Procedures ===&lt;br /&gt;
'''Proof of Eligibility'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Candidates wishing to stand for election, will verify their eligibility along with posting their intentions in the section below. Eligibility will be verified through the following means:&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;List your name&lt;br /&gt;
&amp;lt;LI&amp;gt;List your OWASP member ID (available here: [http://spreadsheets.google.com/a/owasp.org/pub?key=p6IFyntQTi7sxa2Xjx191BA Individual Member Roster]). Individual membership not required for election, but strongly recommended in order to 'lead by example'. Those seeking membership can find more information [http://www.owasp.org/index.php/Membership here]&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Indicate what city and town you live in (We'll only consider local members, but you may live in WV, VA, MD, or DC)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsement from someone else in the chapter&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Time table'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will announce their intentions at our next Chapter meeting, April 7, 2011 @ 6pm. Candidates unable to appear in person can announce their intentions through editing the wiki. If you'd like, I can read something on your behalf at the meeting.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will be asked to give a brief (5 minute) talk discussing their intentions for candidacy.Candidates will also announce the position for which they're running.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;A vote will be conducted during our May chapter meeting&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;The deadline for candidacy will be the meeting's end, April 7th, 2011, @9pm.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Voting'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
The election procedure will be as follows:&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Votes will be cast at our May 4th, 2011 chapter meeting, promptly @ 6pm.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Chapter participants must be present in person to vote.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Absentee voting will be allowed in the case participants can not be present on the 4th, due to medical, travel, or other reasons. Absentee voters must contact both John Steven and Ben Tomhave with your intention to absentee vote no later than April 29th, 2011 @ 6pm.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Votes will be counted during the May 4th meeting, and an announcement made as to the winner at the meeting's end.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Candidates ===&lt;br /&gt;
TBD.&lt;br /&gt;
==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
'''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]''' &lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107248</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107248"/>
				<updated>2011-03-21T16:23:30Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Election Procedures */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== '11 Election  ====&lt;br /&gt;
&lt;br /&gt;
===  Letter from Chapter President - John Steven  ===&lt;br /&gt;
All,&lt;br /&gt;
&lt;br /&gt;
I'm proud of how much the Northern Virginia OWASP Chapter has grown in the past two years.  We've increased membership and attendance, and been able to provide you, our constituency, some interesting speakers, panels, and presentations. A single chapter lead has always headed our chapter but last year we saw enough participation and activity we felt the need to add a program committee. Now, we've reached a size where we'd benefit from more leadership and governance.&lt;br /&gt;
&lt;br /&gt;
As you familiarize yourself with OWASP you'll notice two principal memes:&lt;br /&gt;
&lt;br /&gt;
* Conduct operations in as open, transparent, &amp;amp; democratic a manner as possible&lt;br /&gt;
* Prefer progress to discussion--support engaged participants that produce results over promise &lt;br /&gt;
&lt;br /&gt;
To provide better leadership and governance within the two principals' vein, I'm establishing a chapter board to be made of three (3) individuals that share responsibilities described below by the &amp;quot;Chapter Board Responsibilities&amp;quot; section. A fourth chair-person of the board position will be established as well to facilitate overall chapter direction and chapter interaction with global OWASP governing bodies. This chair-person position will replace my current position and as such I will step down and stand for election myself. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;del&amp;gt;I'm going to restrict board membership to verified [http://www.owasp.org/index.php/Membership OWASP Members] but otherwise &amp;lt;/del&amp;gt; anyone and everyone should feel free to run. Procedures for candidacy and election are described by the &amp;quot;Election Procedures&amp;quot; section below. We plan to organize a campaign period in April and conduct the board election during our May chapter meeting.  Board members make a special commitment to facilitate the chapter's logistics, while growing its membership and attendance. &lt;br /&gt;
&lt;br /&gt;
Beyond elected board members, everybody and anybody should feel free to participate in our Northern Virginia OWASP chapter in any capacity they seem beneficial. I encourage individuals to attend chapter meetings, network, explore and consume OWASP resources voraciously. Likewise, I encourage anyone to &amp;quot;take the reigns&amp;quot; and speak, organize, contribute, and direct our chapter as they see fit. As a open, transparent, and member-driven community, OWASP does not require individuals to attain any status or rank before contributing, as long as contributions meet our [http://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project code of ethics]. Indeed, OWASP strives to be a meritocracy. Our new board, once elected, will strive to provide an environment in which all members feel welcome, able, and supported in providing what contributions they can.&lt;br /&gt;
&lt;br /&gt;
So, please join me in participating in our up-and-coming campaign and election proceedings. With your help, I am confident that the Northern Virginia Chapter can take even greater strides towards helping this area's professionals better address our application security challenges,&lt;br /&gt;
&lt;br /&gt;
-jOHN&amp;lt;br&amp;gt;&lt;br /&gt;
John.Steven@owasp.org&amp;lt;br&amp;gt;&lt;br /&gt;
Northern Virginia OWASP Chapter President,&amp;lt;br&amp;gt;&lt;br /&gt;
Phone: 703.727.4034&amp;lt;br&amp;gt;&lt;br /&gt;
Web: http://goo.gl/Y5d2y&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board Responsibilities ===&lt;br /&gt;
&lt;br /&gt;
* '''Board Member''' Three (3) - OWASP NoVA Chapter Board Members will be verified OWASP members, in good standing, dedicated to direction and governance of the chapter. Responsibilities will include:&lt;br /&gt;
&lt;br /&gt;
* Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics &lt;br /&gt;
* Recruiting OWASP membership&lt;br /&gt;
* Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
* Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
* Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
* Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
* Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations &lt;br /&gt;
* Collecting and auditing use of chapter funds&lt;br /&gt;
* Voting on chapter matters&lt;br /&gt;
&lt;br /&gt;
* '''Board Chairperson''' (1) - OWASP NoVA Chapter Board Chairperson will be a verified OWASP member, in good standing, dedicated to the direction and governance of the chapter. Responsibilities will include those of a board member. In addition, the chairperson will:&lt;br /&gt;
&lt;br /&gt;
* Defer to, facilitate, and support the activities and projects of the chapter board and its membership&lt;br /&gt;
* Represent chapter in OWASP forums, such as the global summit&lt;br /&gt;
* In conjunction with OWASP NoVA Board Members, set annual chapter mission&lt;br /&gt;
&lt;br /&gt;
Board members should be prepared to:&lt;br /&gt;
&lt;br /&gt;
* Devote approximately 4 hrs every two weeks to chapter business&lt;br /&gt;
* Stand for election every twenty-four (24) months &lt;br /&gt;
* Remain absolutely vendor neutral and&lt;br /&gt;
* Uphold the OWASP principals and code of ethics.&lt;br /&gt;
&lt;br /&gt;
=== Election Procedures ===&lt;br /&gt;
'''Proof of Eligibility'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Candidates wishing to stand for election, will verify their eligibility along with posting their intentions in the section below. Eligibility will be verified through the following means:&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;List your name&lt;br /&gt;
&amp;lt;LI&amp;gt;List your OWASP member ID (available here: [http://spreadsheets.google.com/a/owasp.org/pub?key=p6IFyntQTi7sxa2Xjx191BA Individual Member Roster]). Individual membership not required for election, but strongly recommended in order to 'lead by example'. Those seeking membership can find more information [http://www.owasp.org/index.php/Membership here]&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Indicate what city and town you live in (We'll only consider local members, but you may live in WV, VA, MD, or DC)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsement from someone else in the chapter&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Time table'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will announce their intentions at our next Chapter meeting, April 7, 2011 @ 6pm. Candidates unable to appear in person can announce their intentions through editing the wiki. If you'd like, I can read something on your behalf at the meeting.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will be asked to give a brief (5 minute) talk discussing their intentions for candidacy.Candidates will also announce the position for which they're running.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;A vote will be conducted during our May chapter meeting&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;The deadline for candidacy will be the meeting's end, April 7th, 2011, @9pm.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Voting'''&lt;br /&gt;
The election procedure will be as follows:&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Votes will be cast at our May 4th, 2011 chapter meeting, promptly @ 6pm.&amp;lt;LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Chapter participants must be present in person to vote.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Absentee voting will be allowed in the case participants can not be present on the 4th, due to medical, travel, or other reasons. Absentee voters must contact both John Steven and Ben Tomhave with your intention to absentee vote no later than April 29th, 2011 @ 6pm.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Votes will be counted during the May 4th meeting, and an announcement made as to the winner at the meeting's end.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Candidates ===&lt;br /&gt;
TBD.&lt;br /&gt;
==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
'''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]''' &lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107208</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107208"/>
				<updated>2011-03-20T01:54:05Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Election Procedures */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== '11 Election  ====&lt;br /&gt;
&lt;br /&gt;
===  Letter from Chapter President - John Steven  ===&lt;br /&gt;
All,&lt;br /&gt;
&lt;br /&gt;
I'm proud of how much the Northern Virginia OWASP Chapter has grown in the past two years.  We've increased membership and attendance, and been able to provide you, our constituency, some interesting speakers, panels, and presentations. A single chapter lead has always headed our chapter but last year we saw enough participation and activity we felt the need to add a program committee. Now, we've reached a size where we'd benefit from more leadership and governance.&lt;br /&gt;
&lt;br /&gt;
As you familiarize yourself with OWASP you'll notice two principal memes:&lt;br /&gt;
&lt;br /&gt;
* Conduct operations in as open, transparent, &amp;amp; democratic a manner as possible&lt;br /&gt;
* Prefer progress to discussion--support engaged participants that produce results over promise &lt;br /&gt;
&lt;br /&gt;
To provide better leadership and governance within the two principals' vein, I'm establishing a chapter board to be made of three (3) individuals that share responsibilities described below by the &amp;quot;Chapter Board Responsibilities&amp;quot; section. A fourth chair-person of the board position will be established as well to facilitate overall chapter direction and chapter interaction with global OWASP governing bodies. This chair-person position will replace my current position and as such I will step down and stand for election myself. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;del&amp;gt;I'm going to restrict board membership to verified [http://www.owasp.org/index.php/Membership OWASP Members] but otherwise &amp;lt;/del&amp;gt; anyone and everyone should feel free to run. Procedures for candidacy and election are described by the &amp;quot;Election Procedures&amp;quot; section below. We plan to organize a campaign period in April and conduct the board election during our May chapter meeting.  Board members make a special commitment to facilitate the chapter's logistics, while growing its membership and attendance. &lt;br /&gt;
&lt;br /&gt;
Beyond elected board members, everybody and anybody should feel free to participate in our Northern Virginia OWASP chapter in any capacity they seem beneficial. I encourage individuals to attend chapter meetings, network, explore and consume OWASP resources voraciously. Likewise, I encourage anyone to &amp;quot;take the reigns&amp;quot; and speak, organize, contribute, and direct our chapter as they see fit. As a open, transparent, and member-driven community, OWASP does not require individuals to attain any status or rank before contributing, as long as contributions meet our [http://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project code of ethics]. Indeed, OWASP strives to be a meritocracy. Our new board, once elected, will strive to provide an environment in which all members feel welcome, able, and supported in providing what contributions they can.&lt;br /&gt;
&lt;br /&gt;
So, please join me in participating in our up-and-coming campaign and election proceedings. With your help, I am confident that the Northern Virginia Chapter can take even greater strides towards helping this area's professionals better address our application security challenges,&lt;br /&gt;
&lt;br /&gt;
-jOHN&amp;lt;br&amp;gt;&lt;br /&gt;
John.Steven@owasp.org&amp;lt;br&amp;gt;&lt;br /&gt;
Northern Virginia OWASP Chapter President,&amp;lt;br&amp;gt;&lt;br /&gt;
Phone: 703.727.4034&amp;lt;br&amp;gt;&lt;br /&gt;
Web: http://goo.gl/Y5d2y&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board Responsibilities ===&lt;br /&gt;
&lt;br /&gt;
* '''Board Member''' Three (3) - OWASP NoVA Chapter Board Members will be verified OWASP members, in good standing, dedicated to direction and governance of the chapter. Responsibilities will include:&lt;br /&gt;
&lt;br /&gt;
* Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics &lt;br /&gt;
* Recruiting OWASP membership&lt;br /&gt;
* Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
* Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
* Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
* Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
* Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations &lt;br /&gt;
* Collecting and auditing use of chapter funds&lt;br /&gt;
* Voting on chapter matters&lt;br /&gt;
&lt;br /&gt;
* '''Board Chairperson''' (1) - OWASP NoVA Chapter Board Chairperson will be a verified OWASP member, in good standing, dedicated to the direction and governance of the chapter. Responsibilities will include those of a board member. In addition, the chairperson will:&lt;br /&gt;
&lt;br /&gt;
* Defer to, facilitate, and support the activities and projects of the chapter board and its membership&lt;br /&gt;
* Represent chapter in OWASP forums, such as the global summit&lt;br /&gt;
* In conjunction with OWASP NoVA Board Members, set annual chapter mission&lt;br /&gt;
&lt;br /&gt;
Board members should be prepared to:&lt;br /&gt;
&lt;br /&gt;
* Devote approximately 4 hrs every two weeks to chapter business&lt;br /&gt;
* Stand for election every twenty-four (24) months &lt;br /&gt;
* Remain absolutely vendor neutral and&lt;br /&gt;
* Uphold the OWASP principals and code of ethics.&lt;br /&gt;
&lt;br /&gt;
=== Election Procedures ===&lt;br /&gt;
'''Proof of Eligibility'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Candidates wishing to stand for election, will verify their eligibility along with posting their intentions in the section below. Eligibility will be verified through the following means:&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;List your name&lt;br /&gt;
&amp;lt;LI&amp;gt;List your OWASP member ID (available here: [http://spreadsheets.google.com/a/owasp.org/pub?key=p6IFyntQTi7sxa2Xjx191BA Individual Member Roster]). Individual membership not required for election, but strongly recommended in order to 'lead by example'. Those seeking membership can find more information [http://www.owasp.org/index.php/Membership here]&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Indicate what city and town you live in (We'll only consider local members, but you may live in WV, VA, MD, or DC)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsement from someone else in the chapter&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Time table'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;The deadline for announcing candidacy is our next Chapter meeting, April 7, 2011 @ 6pm. Candidates unable to appear in person can announce their intentions through editing the wiki. If you'd like, I can read something on your behalf at the meeting.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will be asked to give a brief (5 minute) talk discussing their intentions for candidacy.Candidates will also announce the position for which they're running.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;A vote will be conducted during our May chapter meeting&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Candidates ===&lt;br /&gt;
TBD.&lt;br /&gt;
==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
'''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]''' &lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107188</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107188"/>
				<updated>2011-03-18T18:46:21Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Letter from Chapter President - John Steven */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== '11 Election  ====&lt;br /&gt;
&lt;br /&gt;
===  Letter from Chapter President - John Steven  ===&lt;br /&gt;
All,&lt;br /&gt;
&lt;br /&gt;
I'm proud of how much the Northern Virginia OWASP Chapter has grown in the past two years.  We've increased membership and attendance, and been able to provide you, our constituency, some interesting speakers, panels, and presentations. A single chapter lead has always headed our chapter but last year we saw enough participation and activity we felt the need to add a program committee. Now, we've reached a size where we'd benefit from more leadership and governance.&lt;br /&gt;
&lt;br /&gt;
As you familiarize yourself with OWASP you'll notice two principal memes:&lt;br /&gt;
&lt;br /&gt;
* Conduct operations in as open, transparent, &amp;amp; democratic a manner as possible&lt;br /&gt;
* Prefer progress to discussion--support engaged participants that produce results over promise &lt;br /&gt;
&lt;br /&gt;
To provide better leadership and governance within the two principals' vein, I'm establishing a chapter board to be made of three (3) individuals that share responsibilities described below by the &amp;quot;Chapter Board Responsibilities&amp;quot; section. A fourth chair-person of the board position will be established as well to facilitate overall chapter direction and chapter interaction with global OWASP governing bodies. This chair-person position will replace my current position and as such I will step down and stand for election myself. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;del&amp;gt;I'm going to restrict board membership to verified [http://www.owasp.org/index.php/Membership OWASP Members] but otherwise &amp;lt;/del&amp;gt; anyone and everyone should feel free to run. Procedures for candidacy and election are described by the &amp;quot;Election Procedures&amp;quot; section below. We plan to organize a campaign period in April and conduct the board election during our May chapter meeting.  Board members make a special commitment to facilitate the chapter's logistics, while growing its membership and attendance. &lt;br /&gt;
&lt;br /&gt;
Beyond elected board members, everybody and anybody should feel free to participate in our Northern Virginia OWASP chapter in any capacity they seem beneficial. I encourage individuals to attend chapter meetings, network, explore and consume OWASP resources voraciously. Likewise, I encourage anyone to &amp;quot;take the reigns&amp;quot; and speak, organize, contribute, and direct our chapter as they see fit. As a open, transparent, and member-driven community, OWASP does not require individuals to attain any status or rank before contributing, as long as contributions meet our [http://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project code of ethics]. Indeed, OWASP strives to be a meritocracy. Our new board, once elected, will strive to provide an environment in which all members feel welcome, able, and supported in providing what contributions they can.&lt;br /&gt;
&lt;br /&gt;
So, please join me in participating in our up-and-coming campaign and election proceedings. With your help, I am confident that the Northern Virginia Chapter can take even greater strides towards helping this area's professionals better address our application security challenges,&lt;br /&gt;
&lt;br /&gt;
-jOHN&amp;lt;br&amp;gt;&lt;br /&gt;
John.Steven@owasp.org&amp;lt;br&amp;gt;&lt;br /&gt;
Northern Virginia OWASP Chapter President,&amp;lt;br&amp;gt;&lt;br /&gt;
Phone: 703.727.4034&amp;lt;br&amp;gt;&lt;br /&gt;
Web: http://goo.gl/Y5d2y&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board Responsibilities ===&lt;br /&gt;
&lt;br /&gt;
* '''Board Member''' Three (3) - OWASP NoVA Chapter Board Members will be verified OWASP members, in good standing, dedicated to direction and governance of the chapter. Responsibilities will include:&lt;br /&gt;
&lt;br /&gt;
* Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics &lt;br /&gt;
* Recruiting OWASP membership&lt;br /&gt;
* Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
* Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
* Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
* Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
* Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations &lt;br /&gt;
* Collecting and auditing use of chapter funds&lt;br /&gt;
* Voting on chapter matters&lt;br /&gt;
&lt;br /&gt;
* '''Board Chairperson''' (1) - OWASP NoVA Chapter Board Chairperson will be a verified OWASP member, in good standing, dedicated to the direction and governance of the chapter. Responsibilities will include those of a board member. In addition, the chairperson will:&lt;br /&gt;
&lt;br /&gt;
* Defer to, facilitate, and support the activities and projects of the chapter board and its membership&lt;br /&gt;
* Represent chapter in OWASP forums, such as the global summit&lt;br /&gt;
* In conjunction with OWASP NoVA Board Members, set annual chapter mission&lt;br /&gt;
&lt;br /&gt;
Board members should be prepared to:&lt;br /&gt;
&lt;br /&gt;
* Devote approximately 4 hrs every two weeks to chapter business&lt;br /&gt;
* Stand for election every twenty-four (24) months &lt;br /&gt;
* Remain absolutely vendor neutral and&lt;br /&gt;
* Uphold the OWASP principals and code of ethics.&lt;br /&gt;
&lt;br /&gt;
=== Election Procedures ===&lt;br /&gt;
'''Proof of Eligibility'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Candidates wishing to stand for election, will verify their eligibility along with posting their intentions in the section below. Eligibility will be verified through the following means:&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;List your name&lt;br /&gt;
&amp;lt;LI&amp;gt;List your OWASP member ID (available here: [http://spreadsheets.google.com/a/owasp.org/pub?key=p6IFyntQTi7sxa2Xjx191BA Individual Member Roster]). Individual membership not required for election, but strongly recommended in order to 'lead by example'. Those seeking membership can find more information [http://www.owasp.org/index.php/Membership here]&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Indicate what city and town you live in (We'll only consider local members, but you may live in WV, VA, MD, or DC)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsement from someone else in the chapter&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Time table'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;The deadline for announcing candidacy is our next Chapter meeting, April 7, 2011 @ 6pm. Candidates unable to appear in person can announce their intentions through editing the wiki. If you'd like, I can read something on your behalf at the meeting.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will be asked to give a brief (5 minute) talk discussing their intentions for candidacy.Candidates will also announce the position for which they're running.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;A vote will be conducted during our Monday chapter meeting&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Candidates ===&lt;br /&gt;
TBD.&lt;br /&gt;
==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
'''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]''' &lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107187</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107187"/>
				<updated>2011-03-18T18:45:21Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Election Procedures */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== '11 Election  ====&lt;br /&gt;
&lt;br /&gt;
===  Letter from Chapter President - John Steven  ===&lt;br /&gt;
All,&lt;br /&gt;
&lt;br /&gt;
I'm proud of how much the Northern Virginia OWASP Chapter has grown in the past two years.  We've increased membership and attendance, and been able to provide you, our constituency, some interesting speakers, panels, and presentations. A single chapter lead has always headed our chapter but last year we saw enough participation and activity we felt the need to add a program committee. Now, we've reached a size where we'd benefit from more leadership and governance.&lt;br /&gt;
&lt;br /&gt;
As you familiarize yourself with OWASP you'll notice two principal memes:&lt;br /&gt;
&lt;br /&gt;
* Conduct operations in as open, transparent, &amp;amp; democratic a manner as possible&lt;br /&gt;
* Prefer progress to discussion--support engaged participants that produce results over promise &lt;br /&gt;
&lt;br /&gt;
To provide better leadership and governance within the two principals' vein, I'm establishing a chapter board to be made of three (3) individuals that share responsibilities described below by the &amp;quot;Chapter Board Responsibilities&amp;quot; section. A fourth chair-person of the board position will be established as well to facilitate overall chapter direction and chapter interaction with global OWASP governing bodies. This chair-person position will replace my current position and as such I will step down and stand for election myself. &lt;br /&gt;
&lt;br /&gt;
I'm going to restrict board membership to verified [http://www.owasp.org/index.php/Membership OWASP Members] but otherwise anyone and everyone should feel free to run. Procedures for candidacy and election are described by the &amp;quot;Election Procedures&amp;quot; section below. We plan to organize a campaign period in April and conduct the board election during our May chapter meeting.  Board members make a special commitment to facilitate the chapter's logistics, while growing its membership and attendance. &lt;br /&gt;
&lt;br /&gt;
Beyond elected board members, everybody and anybody should feel free to participate in our Northern Virginia OWASP chapter in any capacity they seem beneficial. I encourage individuals to attend chapter meetings, network, explore and consume OWASP resources voraciously. Likewise, I encourage anyone to &amp;quot;take the reigns&amp;quot; and speak, organize, contribute, and direct our chapter as they see fit. As a open, transparent, and member-driven community, OWASP does not require individuals to attain any status or rank before contributing, as long as contributions meet our [http://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project code of ethics]. Indeed, OWASP strives to be a meritocracy. Our new board, once elected, will strive to provide an environment in which all members feel welcome, able, and supported in providing what contributions they can.&lt;br /&gt;
&lt;br /&gt;
So, please join me in participating in our up-and-coming campaign and election proceedings. With your help, I am confident that the Northern Virginia Chapter can take even greater strides towards helping this area's professionals better address our application security challenges,&lt;br /&gt;
&lt;br /&gt;
-jOHN&amp;lt;br&amp;gt;&lt;br /&gt;
John.Steven@owasp.org&amp;lt;br&amp;gt;&lt;br /&gt;
Northern Virginia OWASP Chapter President,&amp;lt;br&amp;gt;&lt;br /&gt;
Phone: 703.727.4034&amp;lt;br&amp;gt;&lt;br /&gt;
Web: http://goo.gl/Y5d2y&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board Responsibilities ===&lt;br /&gt;
&lt;br /&gt;
* '''Board Member''' Three (3) - OWASP NoVA Chapter Board Members will be verified OWASP members, in good standing, dedicated to direction and governance of the chapter. Responsibilities will include:&lt;br /&gt;
&lt;br /&gt;
* Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics &lt;br /&gt;
* Recruiting OWASP membership&lt;br /&gt;
* Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
* Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
* Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
* Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
* Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations &lt;br /&gt;
* Collecting and auditing use of chapter funds&lt;br /&gt;
* Voting on chapter matters&lt;br /&gt;
&lt;br /&gt;
* '''Board Chairperson''' (1) - OWASP NoVA Chapter Board Chairperson will be a verified OWASP member, in good standing, dedicated to the direction and governance of the chapter. Responsibilities will include those of a board member. In addition, the chairperson will:&lt;br /&gt;
&lt;br /&gt;
* Defer to, facilitate, and support the activities and projects of the chapter board and its membership&lt;br /&gt;
* Represent chapter in OWASP forums, such as the global summit&lt;br /&gt;
* In conjunction with OWASP NoVA Board Members, set annual chapter mission&lt;br /&gt;
&lt;br /&gt;
Board members should be prepared to:&lt;br /&gt;
&lt;br /&gt;
* Devote approximately 4 hrs every two weeks to chapter business&lt;br /&gt;
* Stand for election every twenty-four (24) months &lt;br /&gt;
* Remain absolutely vendor neutral and&lt;br /&gt;
* Uphold the OWASP principals and code of ethics.&lt;br /&gt;
&lt;br /&gt;
=== Election Procedures ===&lt;br /&gt;
'''Proof of Eligibility'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Candidates wishing to stand for election, will verify their eligibility along with posting their intentions in the section below. Eligibility will be verified through the following means:&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;List your name&lt;br /&gt;
&amp;lt;LI&amp;gt;List your OWASP member ID (available here: [http://spreadsheets.google.com/a/owasp.org/pub?key=p6IFyntQTi7sxa2Xjx191BA Individual Member Roster]). Individual membership not required for election, but strongly recommended in order to 'lead by example'. Those seeking membership can find more information [http://www.owasp.org/index.php/Membership here]&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Indicate what city and town you live in (We'll only consider local members, but you may live in WV, VA, MD, or DC)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsement from someone else in the chapter&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Time table'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;The deadline for announcing candidacy is our next Chapter meeting, April 7, 2011 @ 6pm. Candidates unable to appear in person can announce their intentions through editing the wiki. If you'd like, I can read something on your behalf at the meeting.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will be asked to give a brief (5 minute) talk discussing their intentions for candidacy.Candidates will also announce the position for which they're running.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;A vote will be conducted during our Monday chapter meeting&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Candidates ===&lt;br /&gt;
TBD.&lt;br /&gt;
==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
'''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]''' &lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107160</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107160"/>
				<updated>2011-03-18T14:44:21Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Election Procedures */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== '11 Election  ====&lt;br /&gt;
&lt;br /&gt;
===  Letter from Chapter President - John Steven  ===&lt;br /&gt;
All,&lt;br /&gt;
&lt;br /&gt;
I'm proud of how much the Northern Virginia OWASP Chapter has grown in the past two years.  We've increased membership and attendance, and been able to provide you, our constituency, some interesting speakers, panels, and presentations. A single chapter lead has always headed our chapter but last year we saw enough participation and activity we felt the need to add a program committee. Now, we've reached a size where we'd benefit from more leadership and governance.&lt;br /&gt;
&lt;br /&gt;
As you familiarize yourself with OWASP you'll notice two principal memes:&lt;br /&gt;
&lt;br /&gt;
* Conduct operations in as open, transparent, &amp;amp; democratic a manner as possible&lt;br /&gt;
* Prefer progress to discussion--support engaged participants that produce results over promise &lt;br /&gt;
&lt;br /&gt;
To provide better leadership and governance within the two principals' vein, I'm establishing a chapter board to be made of three (3) individuals that share responsibilities described below by the &amp;quot;Chapter Board Responsibilities&amp;quot; section. A fourth chair-person of the board position will be established as well to facilitate overall chapter direction and chapter interaction with global OWASP governing bodies. This chair-person position will replace my current position and as such I will step down and stand for election myself. &lt;br /&gt;
&lt;br /&gt;
I'm going to restrict board membership to verified [http://www.owasp.org/index.php/Membership OWASP Members] but otherwise anyone and everyone should feel free to run. Procedures for candidacy and election are described by the &amp;quot;Election Procedures&amp;quot; section below. We plan to organize a campaign period in April and conduct the board election during our May chapter meeting.  Board members make a special commitment to facilitate the chapter's logistics, while growing its membership and attendance. &lt;br /&gt;
&lt;br /&gt;
Beyond elected board members, everybody and anybody should feel free to participate in our Northern Virginia OWASP chapter in any capacity they seem beneficial. I encourage individuals to attend chapter meetings, network, explore and consume OWASP resources voraciously. Likewise, I encourage anyone to &amp;quot;take the reigns&amp;quot; and speak, organize, contribute, and direct our chapter as they see fit. As a open, transparent, and member-driven community, OWASP does not require individuals to attain any status or rank before contributing, as long as contributions meet our [http://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project code of ethics]. Indeed, OWASP strives to be a meritocracy. Our new board, once elected, will strive to provide an environment in which all members feel welcome, able, and supported in providing what contributions they can.&lt;br /&gt;
&lt;br /&gt;
So, please join me in participating in our up-and-coming campaign and election proceedings. With your help, I am confident that the Northern Virginia Chapter can take even greater strides towards helping this area's professionals better address our application security challenges,&lt;br /&gt;
&lt;br /&gt;
-jOHN&amp;lt;br&amp;gt;&lt;br /&gt;
John.Steven@owasp.org&amp;lt;br&amp;gt;&lt;br /&gt;
Northern Virginia OWASP Chapter President,&amp;lt;br&amp;gt;&lt;br /&gt;
Phone: 703.727.4034&amp;lt;br&amp;gt;&lt;br /&gt;
Web: http://goo.gl/Y5d2y&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board Responsibilities ===&lt;br /&gt;
&lt;br /&gt;
* '''Board Member''' Three (3) - OWASP NoVA Chapter Board Members will be verified OWASP members, in good standing, dedicated to direction and governance of the chapter. Responsibilities will include:&lt;br /&gt;
&lt;br /&gt;
* Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics &lt;br /&gt;
* Recruiting OWASP membership&lt;br /&gt;
* Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
* Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
* Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
* Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
* Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations &lt;br /&gt;
* Collecting and auditing use of chapter funds&lt;br /&gt;
* Voting on chapter matters&lt;br /&gt;
&lt;br /&gt;
* '''Board Chairperson''' (1) - OWASP NoVA Chapter Board Chairperson will be a verified OWASP member, in good standing, dedicated to the direction and governance of the chapter. Responsibilities will include those of a board member. In addition, the chairperson will:&lt;br /&gt;
&lt;br /&gt;
* Defer to, facilitate, and support the activities and projects of the chapter board and its membership&lt;br /&gt;
* Represent chapter in OWASP forums, such as the global summit&lt;br /&gt;
* In conjunction with OWASP NoVA Board Members, set annual chapter mission&lt;br /&gt;
&lt;br /&gt;
Board members should be prepared to:&lt;br /&gt;
&lt;br /&gt;
* Devote approximately 4 hrs every two weeks to chapter business&lt;br /&gt;
* Stand for election every twenty-four (24) months &lt;br /&gt;
* Remain absolutely vendor neutral and&lt;br /&gt;
* Uphold the OWASP principals and code of ethics.&lt;br /&gt;
&lt;br /&gt;
=== Election Procedures ===&lt;br /&gt;
'''Proof of Eligibility'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Candidates wishing to stand for election, will verify their eligibility along with posting their intentions in the section below. Eligibility will be verified through the following means:&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;List your name&lt;br /&gt;
&amp;lt;LI&amp;gt;List your OWASP member ID (available here: [http://spreadsheets.google.com/a/owasp.org/pub?key=p6IFyntQTi7sxa2Xjx191BA Individual Member Roster]). Individuals seeking membership can find more information [http://www.owasp.org/index.php/Membership here]&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Indicate what city and town you live in (We'll only consider local members, but you may live in WV, VA, MD, or DC)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsement from someone else in the chapter&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Time table'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;The deadline for announcing candidacy is our next Chapter meeting, April 7, 2011 @ 6pm. Candidates unable to appear in person can announce their intentions through editing the wiki. If you'd like, I can read something on your behalf at the meeting.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will be asked to give a brief (5 minute) talk discussing their intentions for candidacy.Candidates will also announce the position for which they're running.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;A vote will be conducted during our Monday chapter meeting&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Candidates ===&lt;br /&gt;
TBD.&lt;br /&gt;
==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
'''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]''' &lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107159</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107159"/>
				<updated>2011-03-18T14:43:02Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Election Procedures */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== '11 Election  ====&lt;br /&gt;
&lt;br /&gt;
===  Letter from Chapter President - John Steven  ===&lt;br /&gt;
All,&lt;br /&gt;
&lt;br /&gt;
I'm proud of how much the Northern Virginia OWASP Chapter has grown in the past two years.  We've increased membership and attendance, and been able to provide you, our constituency, some interesting speakers, panels, and presentations. A single chapter lead has always headed our chapter but last year we saw enough participation and activity we felt the need to add a program committee. Now, we've reached a size where we'd benefit from more leadership and governance.&lt;br /&gt;
&lt;br /&gt;
As you familiarize yourself with OWASP you'll notice two principal memes:&lt;br /&gt;
&lt;br /&gt;
* Conduct operations in as open, transparent, &amp;amp; democratic a manner as possible&lt;br /&gt;
* Prefer progress to discussion--support engaged participants that produce results over promise &lt;br /&gt;
&lt;br /&gt;
To provide better leadership and governance within the two principals' vein, I'm establishing a chapter board to be made of three (3) individuals that share responsibilities described below by the &amp;quot;Chapter Board Responsibilities&amp;quot; section. A fourth chair-person of the board position will be established as well to facilitate overall chapter direction and chapter interaction with global OWASP governing bodies. This chair-person position will replace my current position and as such I will step down and stand for election myself. &lt;br /&gt;
&lt;br /&gt;
I'm going to restrict board membership to verified [http://www.owasp.org/index.php/Membership OWASP Members] but otherwise anyone and everyone should feel free to run. Procedures for candidacy and election are described by the &amp;quot;Election Procedures&amp;quot; section below. We plan to organize a campaign period in April and conduct the board election during our May chapter meeting.  Board members make a special commitment to facilitate the chapter's logistics, while growing its membership and attendance. &lt;br /&gt;
&lt;br /&gt;
Beyond elected board members, everybody and anybody should feel free to participate in our Northern Virginia OWASP chapter in any capacity they seem beneficial. I encourage individuals to attend chapter meetings, network, explore and consume OWASP resources voraciously. Likewise, I encourage anyone to &amp;quot;take the reigns&amp;quot; and speak, organize, contribute, and direct our chapter as they see fit. As a open, transparent, and member-driven community, OWASP does not require individuals to attain any status or rank before contributing, as long as contributions meet our [http://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project code of ethics]. Indeed, OWASP strives to be a meritocracy. Our new board, once elected, will strive to provide an environment in which all members feel welcome, able, and supported in providing what contributions they can.&lt;br /&gt;
&lt;br /&gt;
So, please join me in participating in our up-and-coming campaign and election proceedings. With your help, I am confident that the Northern Virginia Chapter can take even greater strides towards helping this area's professionals better address our application security challenges,&lt;br /&gt;
&lt;br /&gt;
-jOHN&amp;lt;br&amp;gt;&lt;br /&gt;
John.Steven@owasp.org&amp;lt;br&amp;gt;&lt;br /&gt;
Northern Virginia OWASP Chapter President,&amp;lt;br&amp;gt;&lt;br /&gt;
Phone: 703.727.4034&amp;lt;br&amp;gt;&lt;br /&gt;
Web: http://goo.gl/Y5d2y&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board Responsibilities ===&lt;br /&gt;
&lt;br /&gt;
* '''Board Member''' Three (3) - OWASP NoVA Chapter Board Members will be verified OWASP members, in good standing, dedicated to direction and governance of the chapter. Responsibilities will include:&lt;br /&gt;
&lt;br /&gt;
* Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics &lt;br /&gt;
* Recruiting OWASP membership&lt;br /&gt;
* Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
* Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
* Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
* Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
* Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations &lt;br /&gt;
* Collecting and auditing use of chapter funds&lt;br /&gt;
* Voting on chapter matters&lt;br /&gt;
&lt;br /&gt;
* '''Board Chairperson''' (1) - OWASP NoVA Chapter Board Chairperson will be a verified OWASP member, in good standing, dedicated to the direction and governance of the chapter. Responsibilities will include those of a board member. In addition, the chairperson will:&lt;br /&gt;
&lt;br /&gt;
* Defer to, facilitate, and support the activities and projects of the chapter board and its membership&lt;br /&gt;
* Represent chapter in OWASP forums, such as the global summit&lt;br /&gt;
* In conjunction with OWASP NoVA Board Members, set annual chapter mission&lt;br /&gt;
&lt;br /&gt;
Board members should be prepared to:&lt;br /&gt;
&lt;br /&gt;
* Devote approximately 4 hrs every two weeks to chapter business&lt;br /&gt;
* Stand for election every twenty-four (24) months &lt;br /&gt;
* Remain absolutely vendor neutral and&lt;br /&gt;
* Uphold the OWASP principals and code of ethics.&lt;br /&gt;
&lt;br /&gt;
=== Election Procedures ===&lt;br /&gt;
'''Proof of Eligibility'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Candidates wishing to stand for election, will verify their eligibility along with posting their intentions in the section below. Eligibility will be verified through the following means:&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;List your name&lt;br /&gt;
&amp;lt;LI&amp;gt;List your OWASP member ID (available here: [http://spreadsheets.google.com/a/owasp.org/pub?key=p6IFyntQTi7sxa2Xjx191BA Individual Member Roster]). Individuals seeking membership can find more information [http://www.owasp.org/index.php/Membership here]&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Indicate what city and town you live in (We'll only consider local members, but you may live in WV, VA, MD, or DC)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsement from someone else in the chapter&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Time table'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;The deadline for announcing candidacy is our next Chapter meeting, April 7, 2011 @ 6pm. Candidates unable to appear in person can announce their intentions through editing the wiki. If you'd like, I can read something on your behalf at the meeting.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will be asked to give a brief (5 minute) talk discussing their intentions for candidacy.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;A vote will be conducted during out Monday chapter meeting&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Candidates ===&lt;br /&gt;
TBD.&lt;br /&gt;
==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
'''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]''' &lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107158</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107158"/>
				<updated>2011-03-18T14:42:43Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Election Procedures */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== '11 Election  ====&lt;br /&gt;
&lt;br /&gt;
===  Letter from Chapter President - John Steven  ===&lt;br /&gt;
All,&lt;br /&gt;
&lt;br /&gt;
I'm proud of how much the Northern Virginia OWASP Chapter has grown in the past two years.  We've increased membership and attendance, and been able to provide you, our constituency, some interesting speakers, panels, and presentations. A single chapter lead has always headed our chapter but last year we saw enough participation and activity we felt the need to add a program committee. Now, we've reached a size where we'd benefit from more leadership and governance.&lt;br /&gt;
&lt;br /&gt;
As you familiarize yourself with OWASP you'll notice two principal memes:&lt;br /&gt;
&lt;br /&gt;
* Conduct operations in as open, transparent, &amp;amp; democratic a manner as possible&lt;br /&gt;
* Prefer progress to discussion--support engaged participants that produce results over promise &lt;br /&gt;
&lt;br /&gt;
To provide better leadership and governance within the two principals' vein, I'm establishing a chapter board to be made of three (3) individuals that share responsibilities described below by the &amp;quot;Chapter Board Responsibilities&amp;quot; section. A fourth chair-person of the board position will be established as well to facilitate overall chapter direction and chapter interaction with global OWASP governing bodies. This chair-person position will replace my current position and as such I will step down and stand for election myself. &lt;br /&gt;
&lt;br /&gt;
I'm going to restrict board membership to verified [http://www.owasp.org/index.php/Membership OWASP Members] but otherwise anyone and everyone should feel free to run. Procedures for candidacy and election are described by the &amp;quot;Election Procedures&amp;quot; section below. We plan to organize a campaign period in April and conduct the board election during our May chapter meeting.  Board members make a special commitment to facilitate the chapter's logistics, while growing its membership and attendance. &lt;br /&gt;
&lt;br /&gt;
Beyond elected board members, everybody and anybody should feel free to participate in our Northern Virginia OWASP chapter in any capacity they seem beneficial. I encourage individuals to attend chapter meetings, network, explore and consume OWASP resources voraciously. Likewise, I encourage anyone to &amp;quot;take the reigns&amp;quot; and speak, organize, contribute, and direct our chapter as they see fit. As a open, transparent, and member-driven community, OWASP does not require individuals to attain any status or rank before contributing, as long as contributions meet our [http://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project code of ethics]. Indeed, OWASP strives to be a meritocracy. Our new board, once elected, will strive to provide an environment in which all members feel welcome, able, and supported in providing what contributions they can.&lt;br /&gt;
&lt;br /&gt;
So, please join me in participating in our up-and-coming campaign and election proceedings. With your help, I am confident that the Northern Virginia Chapter can take even greater strides towards helping this area's professionals better address our application security challenges,&lt;br /&gt;
&lt;br /&gt;
-jOHN&amp;lt;br&amp;gt;&lt;br /&gt;
John.Steven@owasp.org&amp;lt;br&amp;gt;&lt;br /&gt;
Northern Virginia OWASP Chapter President,&amp;lt;br&amp;gt;&lt;br /&gt;
Phone: 703.727.4034&amp;lt;br&amp;gt;&lt;br /&gt;
Web: http://goo.gl/Y5d2y&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board Responsibilities ===&lt;br /&gt;
&lt;br /&gt;
* '''Board Member''' Three (3) - OWASP NoVA Chapter Board Members will be verified OWASP members, in good standing, dedicated to direction and governance of the chapter. Responsibilities will include:&lt;br /&gt;
&lt;br /&gt;
* Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics &lt;br /&gt;
* Recruiting OWASP membership&lt;br /&gt;
* Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
* Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
* Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
* Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
* Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations &lt;br /&gt;
* Collecting and auditing use of chapter funds&lt;br /&gt;
* Voting on chapter matters&lt;br /&gt;
&lt;br /&gt;
* '''Board Chairperson''' (1) - OWASP NoVA Chapter Board Chairperson will be a verified OWASP member, in good standing, dedicated to the direction and governance of the chapter. Responsibilities will include those of a board member. In addition, the chairperson will:&lt;br /&gt;
&lt;br /&gt;
* Defer to, facilitate, and support the activities and projects of the chapter board and its membership&lt;br /&gt;
* Represent chapter in OWASP forums, such as the global summit&lt;br /&gt;
* In conjunction with OWASP NoVA Board Members, set annual chapter mission&lt;br /&gt;
&lt;br /&gt;
Board members should be prepared to:&lt;br /&gt;
&lt;br /&gt;
* Devote approximately 4 hrs every two weeks to chapter business&lt;br /&gt;
* Stand for election every twenty-four (24) months &lt;br /&gt;
* Remain absolutely vendor neutral and&lt;br /&gt;
* Uphold the OWASP principals and code of ethics.&lt;br /&gt;
&lt;br /&gt;
=== Election Procedures ===&lt;br /&gt;
'''Proof of Eligibility'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Candidates wishing to stand for election, will verify their eligibility along with posting their intentions in the section below. Eligibility will be verified through the following means:&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;List your name&lt;br /&gt;
&amp;lt;LI&amp;gt;List your OWASP member ID (available here: [http://spreadsheets.google.com/a/owasp.org/pub?key=p6IFyntQTi7sxa2Xjx191BA Individual Member Roster]). Individuals seeking membership can find more information [http://www.owasp.org/index.php/Membership here]&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Indicate what city and town you live in (We'll only consider local members, but you may live in WV, VA, MD, or DC)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsement from someone else in the chapter&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Time table'''&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;The deadline for announcing candidacy is our next Chapter meeting, April 7, 2011 @ 6pm. Candidates unable to appear in person can announce their intentions through editing the wiki. If you'd like, I can read something on your behalf at the meeting.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Candidates will be asked to give a brief (5 minute) talk discussing their intentions for candidacy.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;A vote will be conducted during out Monday chapter meeting&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Candidates ===&lt;br /&gt;
TBD.&lt;br /&gt;
==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
'''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]''' &lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107157</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107157"/>
				<updated>2011-03-18T14:38:28Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Election Procedures */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== '11 Election  ====&lt;br /&gt;
&lt;br /&gt;
===  Letter from Chapter President - John Steven  ===&lt;br /&gt;
All,&lt;br /&gt;
&lt;br /&gt;
I'm proud of how much the Northern Virginia OWASP Chapter has grown in the past two years.  We've increased membership and attendance, and been able to provide you, our constituency, some interesting speakers, panels, and presentations. A single chapter lead has always headed our chapter but last year we saw enough participation and activity we felt the need to add a program committee. Now, we've reached a size where we'd benefit from more leadership and governance.&lt;br /&gt;
&lt;br /&gt;
As you familiarize yourself with OWASP you'll notice two principal memes:&lt;br /&gt;
&lt;br /&gt;
* Conduct operations in as open, transparent, &amp;amp; democratic a manner as possible&lt;br /&gt;
* Prefer progress to discussion--support engaged participants that produce results over promise &lt;br /&gt;
&lt;br /&gt;
To provide better leadership and governance within the two principals' vein, I'm establishing a chapter board to be made of three (3) individuals that share responsibilities described below by the &amp;quot;Chapter Board Responsibilities&amp;quot; section. A fourth chair-person of the board position will be established as well to facilitate overall chapter direction and chapter interaction with global OWASP governing bodies. This chair-person position will replace my current position and as such I will step down and stand for election myself. &lt;br /&gt;
&lt;br /&gt;
I'm going to restrict board membership to verified [http://www.owasp.org/index.php/Membership OWASP Members] but otherwise anyone and everyone should feel free to run. Procedures for candidacy and election are described by the &amp;quot;Election Procedures&amp;quot; section below. We plan to organize a campaign period in April and conduct the board election during our May chapter meeting.  Board members make a special commitment to facilitate the chapter's logistics, while growing its membership and attendance. &lt;br /&gt;
&lt;br /&gt;
Beyond elected board members, everybody and anybody should feel free to participate in our Northern Virginia OWASP chapter in any capacity they seem beneficial. I encourage individuals to attend chapter meetings, network, explore and consume OWASP resources voraciously. Likewise, I encourage anyone to &amp;quot;take the reigns&amp;quot; and speak, organize, contribute, and direct our chapter as they see fit. As a open, transparent, and member-driven community, OWASP does not require individuals to attain any status or rank before contributing, as long as contributions meet our [http://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project code of ethics]. Indeed, OWASP strives to be a meritocracy. Our new board, once elected, will strive to provide an environment in which all members feel welcome, able, and supported in providing what contributions they can.&lt;br /&gt;
&lt;br /&gt;
So, please join me in participating in our up-and-coming campaign and election proceedings. With your help, I am confident that the Northern Virginia Chapter can take even greater strides towards helping this area's professionals better address our application security challenges,&lt;br /&gt;
&lt;br /&gt;
-jOHN&amp;lt;br&amp;gt;&lt;br /&gt;
John.Steven@owasp.org&amp;lt;br&amp;gt;&lt;br /&gt;
Northern Virginia OWASP Chapter President,&amp;lt;br&amp;gt;&lt;br /&gt;
Phone: 703.727.4034&amp;lt;br&amp;gt;&lt;br /&gt;
Web: http://goo.gl/Y5d2y&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board Responsibilities ===&lt;br /&gt;
&lt;br /&gt;
* '''Board Member''' Three (3) - OWASP NoVA Chapter Board Members will be verified OWASP members, in good standing, dedicated to direction and governance of the chapter. Responsibilities will include:&lt;br /&gt;
&lt;br /&gt;
* Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics &lt;br /&gt;
* Recruiting OWASP membership&lt;br /&gt;
* Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
* Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
* Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
* Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
* Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations &lt;br /&gt;
* Collecting and auditing use of chapter funds&lt;br /&gt;
* Voting on chapter matters&lt;br /&gt;
&lt;br /&gt;
* '''Board Chairperson''' (1) - OWASP NoVA Chapter Board Chairperson will be a verified OWASP member, in good standing, dedicated to the direction and governance of the chapter. Responsibilities will include those of a board member. In addition, the chairperson will:&lt;br /&gt;
&lt;br /&gt;
* Defer to, facilitate, and support the activities and projects of the chapter board and its membership&lt;br /&gt;
* Represent chapter in OWASP forums, such as the global summit&lt;br /&gt;
* In conjunction with OWASP NoVA Board Members, set annual chapter mission&lt;br /&gt;
&lt;br /&gt;
Board members should be prepared to:&lt;br /&gt;
&lt;br /&gt;
* Devote approximately 4 hrs every two weeks to chapter business&lt;br /&gt;
* Stand for election every twenty-four (24) months &lt;br /&gt;
* Remain absolutely vendor neutral and&lt;br /&gt;
* Uphold the OWASP principals and code of ethics.&lt;br /&gt;
&lt;br /&gt;
=== Election Procedures ===&lt;br /&gt;
'''Proof of Eligibility'''&lt;br /&gt;
Candidates wishing to stand for election, will verify their eligibility along with posting their intentions in the section below. Eligibility will be verified through the following means:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;List your name&lt;br /&gt;
&amp;lt;LI&amp;gt;List your OWASP member ID (available here: [http://spreadsheets.google.com/a/owasp.org/pub?key=p6IFyntQTi7sxa2Xjx191BA Individual Member Roster]). Individuals seeking membership can find more information [http://www.owasp.org/index.php/Membership here]&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Indicate what city and town you live in (We'll only consider local members, but you may live in WV, VA, MD, or DC)&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Endorsement from someone else in the chapter&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Candidates ===&lt;br /&gt;
TBD.&lt;br /&gt;
==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
'''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]''' &lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107040</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107040"/>
				<updated>2011-03-17T02:51:40Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Letter from Chapter President - John Steven */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== '11 Election  ====&lt;br /&gt;
&lt;br /&gt;
===  Letter from Chapter President - John Steven  ===&lt;br /&gt;
All,&lt;br /&gt;
&lt;br /&gt;
I'm proud of how much the Northern Virginia OWASP Chapter has grown in the past two years.  We've increased membership and attendance, and been able to provide you, our constituency, some interesting speakers, panels, and presentations. A single chapter lead has always headed our chapter but last year we saw enough participation and activity we felt the need to add a program committee. Now, we've reached a size where we'd benefit from more leadership and governance.&lt;br /&gt;
&lt;br /&gt;
As you familiarize yourself with OWASP you'll notice two principal memes:&lt;br /&gt;
&lt;br /&gt;
* Conduct operations in as open, transparent, &amp;amp; democratic a manner as possible&lt;br /&gt;
* Prefer progress to discussion--support engaged participants that produce results over promise &lt;br /&gt;
&lt;br /&gt;
To provide better leadership and governance within the two principals' vein, I'm establishing a chapter board to be made of three (3) individuals that share responsibilities described below by the &amp;quot;Chapter Board Responsibilities&amp;quot; section. A fourth chair-person of the board position will be established as well to facilitate overall chapter direction and chapter interaction with global OWASP governing bodies. This chair-person position will replace my current position and as such I will step down and stand for election myself. &lt;br /&gt;
&lt;br /&gt;
I'm going to restrict board membership to verified [http://www.owasp.org/index.php/Membership OWASP Members] but otherwise anyone and everyone should feel free to run. Procedures for candidacy and election are described by the &amp;quot;Election Procedures&amp;quot; section below. We plan to organize a campaign period in April and conduct the board election during our May chapter meeting.  Board members make a special commitment to facilitate the chapter's logistics, while growing its membership and attendance. &lt;br /&gt;
&lt;br /&gt;
Beyond elected board members, everybody and anybody should feel free to participate in our Northern Virginia OWASP chapter in any capacity they seem beneficial. I encourage individuals to attend chapter meetings, network, explore and consume OWASP resources voraciously. Likewise, I encourage anyone to &amp;quot;take the reigns&amp;quot; and speak, organize, contribute, and direct our chapter as they see fit. As a open, transparent, and member-driven community, OWASP does not require individuals to attain any status or rank before contributing, as long as contributions meet our [http://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project code of ethics]. Indeed, OWASP strives to be a meritocracy. Our new board, once elected, will strive to provide an environment in which all members feel welcome, able, and supported in providing what contributions they can.&lt;br /&gt;
&lt;br /&gt;
So, please join me in participating in our up-and-coming campaign and election proceedings. With your help, I am confident that the Northern Virginia Chapter can take even greater strides towards helping this area's professionals better address our application security challenges,&lt;br /&gt;
&lt;br /&gt;
-jOHN&amp;lt;br&amp;gt;&lt;br /&gt;
John.Steven@owasp.org&amp;lt;br&amp;gt;&lt;br /&gt;
Northern Virginia OWASP Chapter President,&amp;lt;br&amp;gt;&lt;br /&gt;
Phone: 703.727.4034&amp;lt;br&amp;gt;&lt;br /&gt;
Web: http://goo.gl/Y5d2y&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board Responsibilities ===&lt;br /&gt;
&lt;br /&gt;
* '''Board Member''' Three (3) - OWASP NoVA Chapter Board Members will be verified OWASP members, in good standing, dedicated to direction and governance of the chapter. Responsibilities will include:&lt;br /&gt;
&lt;br /&gt;
* Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics &lt;br /&gt;
* Recruiting OWASP membership&lt;br /&gt;
* Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
* Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
* Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
* Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
* Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations &lt;br /&gt;
* Collecting and auditing use of chapter funds&lt;br /&gt;
* Voting on chapter matters&lt;br /&gt;
&lt;br /&gt;
* '''Board Chairperson''' (1) - OWASP NoVA Chapter Board Chairperson will be a verified OWASP member, in good standing, dedicated to the direction and governance of the chapter. Responsibilities will include those of a board member. In addition, the chairperson will:&lt;br /&gt;
&lt;br /&gt;
* Defer to, facilitate, and support the activities and projects of the chapter board and its membership&lt;br /&gt;
* Represent chapter in OWASP forums, such as the global summit&lt;br /&gt;
* In conjunction with OWASP NoVA Board Members, set annual chapter mission&lt;br /&gt;
&lt;br /&gt;
Board members should be prepared to:&lt;br /&gt;
&lt;br /&gt;
* Devote approximately 4 hrs every two weeks to chapter business&lt;br /&gt;
* Stand for election every twenty-four (24) months &lt;br /&gt;
* Remain absolutely vendor neutral and&lt;br /&gt;
* Uphold the OWASP principals and code of ethics.&lt;br /&gt;
&lt;br /&gt;
=== Election Procedures ===&lt;br /&gt;
TBD.&lt;br /&gt;
&lt;br /&gt;
=== Candidates ===&lt;br /&gt;
TBD.&lt;br /&gt;
==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
'''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]''' &lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107037</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107037"/>
				<updated>2011-03-17T02:45:51Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: /* Chapter Board Responsibilities */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== '11 Election  ====&lt;br /&gt;
&lt;br /&gt;
===  Letter from Chapter President - John Steven  ===&lt;br /&gt;
All,&lt;br /&gt;
&lt;br /&gt;
I'm proud of how much the Northern Virginia OWASP Chapter has grown in the past two years.  We've increased membership and attendance, and been able to provide you, our constituency, some interesting speakers, panels, and presentations. A single chapter lead has always headed our chapter but last year we saw enough participation and activity we felt the need to add a program committee. Now, we've reached a size where we'd benefit from more leadership and governance.&lt;br /&gt;
&lt;br /&gt;
As you familiarize yourself with OWASP you'll notice two principal memes:&lt;br /&gt;
&lt;br /&gt;
* Conduct operations in as open, transparent, &amp;amp; democratic a manner as possible&lt;br /&gt;
* Prefer progress to discussion--support engaged participants that produce results over promise &lt;br /&gt;
&lt;br /&gt;
To provide better leadership and governance within the two principals' vein, I'm establishing a chapter board to be made of three (3) individuals that share responsibilities described below by the &amp;quot;Chapter Board Responsibilities&amp;quot; section. A fourth chair-person of the board position will be established as well to facilitate overall chapter direction and chapter interaction with global OWASP governing bodies. This chair-person position will replace my current position and as such I will step down and stand for election myself. &lt;br /&gt;
&lt;br /&gt;
I'm going to restrict board membership to verified [http://www.owasp.org/index.php/Membership OWASP Members] but otherwise anyone and everyone should feel free to run. Procedures for candidacy and election are described by the &amp;quot;Election Procedures&amp;quot; section below. We plan to organize a campaign period in April and conduct the board election during our May chapter meeting.  Board members make a special commitment to facilitate the chapter's logistics, while growing its membership and attendance. &lt;br /&gt;
&lt;br /&gt;
Beyond elected board members, everybody and anybody should feel free to participate in our Northern Virginia OWASP chapter in any capacity they seem beneficial. I encourage individuals to attend chapter meetings, network, explore and consume OWASP resources voraciously. Likewise, I encourage anyone to &amp;quot;take the reigns&amp;quot; and speak, organize, contribute, and direct our chapter as they see fit. As a open, transparent, and member-driven community, OWASP does not require individuals to attain any status or rank before contributing, as long as contributions meet our [http://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project code of ethics]. Indeed, OWASP strives to be a meritocracy. Our new board, once elected, will strive to provide an environment in which all members feel welcome, able, and supported in providing what contributions they can.&lt;br /&gt;
&lt;br /&gt;
So, please join me in participating in our up-and-coming campaign and election proceedings. With your help, I am confident that the Northern Virginia Chapter can take even greater strides towards helping this area's professionals better address our application security challenges,&lt;br /&gt;
&lt;br /&gt;
-jOHN&amp;lt;br&amp;gt;&lt;br /&gt;
John.Steven@owasp.org&amp;lt;br&amp;gt;&lt;br /&gt;
Northern Virginia OWASP Chapter President,&amp;lt;br&amp;gt;&lt;br /&gt;
Senior Director, Cigital Inc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board Responsibilities ===&lt;br /&gt;
&lt;br /&gt;
* '''Board Member''' Three (3) - OWASP NoVA Chapter Board Members will be verified OWASP members, in good standing, dedicated to direction and governance of the chapter. Responsibilities will include:&lt;br /&gt;
&lt;br /&gt;
* Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics &lt;br /&gt;
* Recruiting OWASP membership&lt;br /&gt;
* Driving OWASP NoVA Chapter attendance and involvement&lt;br /&gt;
* Deferring to, facilitating, and supporting the activities and projects of chapter membership&lt;br /&gt;
* Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions&lt;br /&gt;
* Scouting, clearing, and scheduling chapter meeting venues and catering&lt;br /&gt;
* Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations &lt;br /&gt;
* Collecting and auditing use of chapter funds&lt;br /&gt;
* Voting on chapter matters&lt;br /&gt;
&lt;br /&gt;
* '''Board Chairperson''' (1) - OWASP NoVA Chapter Board Chairperson will be a verified OWASP member, in good standing, dedicated to the direction and governance of the chapter. Responsibilities will include those of a board member. In addition, the chairperson will:&lt;br /&gt;
&lt;br /&gt;
* Defer to, facilitate, and support the activities and projects of the chapter board and its membership&lt;br /&gt;
* Represent chapter in OWASP forums, such as the global summit&lt;br /&gt;
* In conjunction with OWASP NoVA Board Members, set annual chapter mission&lt;br /&gt;
&lt;br /&gt;
Board members should be prepared to:&lt;br /&gt;
&lt;br /&gt;
* Devote approximately 4 hrs every two weeks to chapter business&lt;br /&gt;
* Stand for election every twenty-four (24) months &lt;br /&gt;
* Remain absolutely vendor neutral and&lt;br /&gt;
* Uphold the OWASP principals and code of ethics.&lt;br /&gt;
&lt;br /&gt;
=== Election Procedures ===&lt;br /&gt;
TBD.&lt;br /&gt;
&lt;br /&gt;
=== Candidates ===&lt;br /&gt;
TBD.&lt;br /&gt;
==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
'''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]''' &lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107032</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107032"/>
				<updated>2011-03-17T02:25:08Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== '11 Election  ====&lt;br /&gt;
&lt;br /&gt;
===  Letter from Chapter President - John Steven  ===&lt;br /&gt;
All,&lt;br /&gt;
&lt;br /&gt;
I'm proud of how much the Northern Virginia OWASP Chapter has grown in the past two years.  We've increased membership and attendance, and been able to provide you, our constituency, some interesting speakers, panels, and presentations. A single chapter lead has always headed our chapter but last year we saw enough participation and activity we felt the need to add a program committee. Now, we've reached a size where we'd benefit from more leadership and governance.&lt;br /&gt;
&lt;br /&gt;
As you familiarize yourself with OWASP you'll notice two principal memes:&lt;br /&gt;
&lt;br /&gt;
* Conduct operations in as open, transparent, &amp;amp; democratic a manner as possible&lt;br /&gt;
* Prefer progress to discussion--support engaged participants that produce results over promise &lt;br /&gt;
&lt;br /&gt;
To provide better leadership and governance within the two principals' vein, I'm establishing a chapter board to be made of three (3) individuals that share responsibilities described below by the &amp;quot;Chapter Board Responsibilities&amp;quot; section. A fourth chair-person of the board position will be established as well to facilitate overall chapter direction and chapter interaction with global OWASP governing bodies. This chair-person position will replace my current position and as such I will step down and stand for election myself. &lt;br /&gt;
&lt;br /&gt;
I'm going to restrict board membership to verified [http://www.owasp.org/index.php/Membership OWASP Members] but otherwise anyone and everyone should feel free to run. Procedures for candidacy and election are described by the &amp;quot;Election Procedures&amp;quot; section below. We plan to organize a campaign period in April and conduct the board election during our May chapter meeting.  Board members make a special commitment to facilitate the chapter's logistics, while growing its membership and attendance. &lt;br /&gt;
&lt;br /&gt;
Beyond elected board members, everybody and anybody should feel free to participate in our Northern Virginia OWASP chapter in any capacity they seem beneficial. I encourage individuals to attend chapter meetings, network, explore and consume OWASP resources voraciously. Likewise, I encourage anyone to &amp;quot;take the reigns&amp;quot; and speak, organize, contribute, and direct our chapter as they see fit. As a open, transparent, and member-driven community, OWASP does not require individuals to attain any status or rank before contributing, as long as contributions meet our [http://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project code of ethics]. Indeed, OWASP strives to be a meritocracy. Our new board, once elected, will strive to provide an environment in which all members feel welcome, able, and supported in providing what contributions they can.&lt;br /&gt;
&lt;br /&gt;
So, please join me in participating in our up-and-coming campaign and election proceedings. With your help, I am confident that the Northern Virginia Chapter can take even greater strides towards helping this area's professionals better address our application security challenges,&lt;br /&gt;
&lt;br /&gt;
-jOHN&amp;lt;br&amp;gt;&lt;br /&gt;
John.Steven@owasp.org&amp;lt;br&amp;gt;&lt;br /&gt;
Northern Virginia OWASP Chapter President,&amp;lt;br&amp;gt;&lt;br /&gt;
Senior Director, Cigital Inc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board Responsibilities ===&lt;br /&gt;
TBD.&lt;br /&gt;
&lt;br /&gt;
=== Election Procedures ===&lt;br /&gt;
TBD.&lt;br /&gt;
&lt;br /&gt;
=== Candidates ===&lt;br /&gt;
TBD.&lt;br /&gt;
==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
'''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]''' &lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107021</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=107021"/>
				<updated>2011-03-16T20:32:23Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== '11 Election  ====&lt;br /&gt;
&lt;br /&gt;
===  Letter from Chapter President - John Steven  ===&lt;br /&gt;
&lt;br /&gt;
=== Chapter Board Responsibilities ===&lt;br /&gt;
&amp;lt;A NAME=&amp;quot;Responsibilities&amp;quot; /&amp;gt;&lt;br /&gt;
TBD.&lt;br /&gt;
&lt;br /&gt;
=== Election Procedures ===&lt;br /&gt;
&amp;lt;A NAME=&amp;quot;Responsibilities&amp;quot; /&amp;gt;&lt;br /&gt;
TBD.&lt;br /&gt;
&lt;br /&gt;
=== Candidates ===&lt;br /&gt;
&amp;lt;A NAME=&amp;quot;Candidates&amp;quot; /&amp;gt;&lt;br /&gt;
TBD.&lt;br /&gt;
&lt;br /&gt;
==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
'''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]''' &lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Virginia&amp;diff=106713</id>
		<title>Virginia</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Virginia&amp;diff=106713"/>
				<updated>2011-03-13T20:00:51Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== About  ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-nova.JPG|right|275px|Owasp-nova.JPG]]The '''OWASP Northern VA Local Chapter''' meetings are FREE and OPEN to anyone interested in learning more about application security. We encourage individuals to provide knowledge transfer via hands-on training and presentations of specific OWASP projects and research topics and sharing SDLC knowledge. &lt;br /&gt;
&lt;br /&gt;
We the encourage vendor-agnostic presentations to utilize the OWASP Powerpoint template when applicable and individual volunteerism to enable perpetual growth. As a 501(3)c non-profit association donations of meeting space or refreshments sponsorship is encouraged, simply contact the local chapter leaders listed on this page to discuss. Prior to participating with OWASP please review the Chapter Rules. &lt;br /&gt;
&lt;br /&gt;
The chapter is committed to providing an engaging experience for a variety of audience types ranging from local students and those beginning in app-sec, to those experienced and accomplished professionals who are looking for competent collaborators for OWASP-related projects. To this end, we will continue to conduct both monthly chapter meetings as well as out-of-band curricula, on application security topics. &lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Virginia|extra=The chapter leader is [mailto:John.Steven@owasp.org John Steven].&lt;br /&gt;
&lt;br /&gt;
=== Program Committee ===&lt;br /&gt;
The OWASP NoVA Chapter Program Committee aims to:&lt;br /&gt;
&lt;br /&gt;
Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency. &lt;br /&gt;
&lt;br /&gt;
Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.&lt;br /&gt;
&lt;br /&gt;
In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:&lt;br /&gt;
&lt;br /&gt;
* Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.&lt;br /&gt;
* Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material&lt;br /&gt;
* Design, document, and implement a chapter participant &amp;quot;speaker survey&amp;quot; / voting mechanism&lt;br /&gt;
* Implement a &amp;quot;speaker survey&amp;quot; results display on the OWASP Wiki for the broader OWASP community to consume&lt;br /&gt;
*  Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)&lt;br /&gt;
&lt;br /&gt;
|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} &lt;br /&gt;
&lt;br /&gt;
You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. &lt;br /&gt;
&lt;br /&gt;
==== Schedule  ====&lt;br /&gt;
&lt;br /&gt;
Meetings are (generally) held the first Thursday of the month. &lt;br /&gt;
&lt;br /&gt;
=== Next Meeting  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' April 7, 2011 @ 6pm &lt;br /&gt;
&lt;br /&gt;
'''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 &lt;br /&gt;
&lt;br /&gt;
'''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 &amp;quot;Cross-Site Scripting (XSS)&amp;quot;]&lt;br /&gt;
  * Preso:&amp;quot;Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform&amp;quot; by Joey Tyson&lt;br /&gt;
  * Preso:“XSS Remediation” by Cassia Martin&lt;br /&gt;
  * Preso:&amp;quot;Growing the secure application developer community through expanded curricula&amp;quot; by Tony Gottlieb&lt;br /&gt;
  * FireTalks (bring it!)&lt;br /&gt;
&lt;br /&gt;
'''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]''' &lt;br /&gt;
&lt;br /&gt;
Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Speakers  ===&lt;br /&gt;
&lt;br /&gt;
'''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement &lt;br /&gt;
&lt;br /&gt;
If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. &lt;br /&gt;
&lt;br /&gt;
[http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&amp;amp;ctz=America/New_York View the OWASP NoVA Chapter Calendar]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Past meetings  ====&lt;br /&gt;
&lt;br /&gt;
=== March 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review&lt;br /&gt;
   * Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 &amp;quot;Injection&amp;quot;]&lt;br /&gt;
  * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== February 2011  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' February 3, 2011 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * News / Updates&lt;br /&gt;
   * Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]&lt;br /&gt;
  * Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2&lt;br /&gt;
   * Briefing: Training/Preso Plan for the Year&lt;br /&gt;
&lt;br /&gt;
=== December 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' December 2, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA&amp;lt;br&amp;gt; '''AGENDA:''' &lt;br /&gt;
&lt;br /&gt;
   * 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)&lt;br /&gt;
   * Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)&lt;br /&gt;
   * Social / Networking (BYOB!)&lt;br /&gt;
&lt;br /&gt;
=== November 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time:''' November 4, 2010 @ 6pm&amp;lt;br&amp;gt; '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA&amp;lt;br&amp;gt; '''Speaker:''' Ben Tomhave&amp;lt;br&amp;gt; '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform&amp;lt;br&amp;gt; '''Description:''' What we're doing today is not working and isn't sustainable. The fundamental culture of the average business does not encourage making good security decisions. Software shops continue to focus on functionality and timelines, neglecting information security. In spite of regulations like PCI and HIPAA+HITECH, which are levying fines against organizations for their security failures, the tipping point has clearly not been reached to cause meaningful change. Much of this problem can be attributed to the excessive use of negative incentives (sticks) instead of providing positive incentives (carrots) that inspire better decision making and motivate true change. Fortunately, it's not too late to change tactics and start achieving demonstrable success.&amp;lt;br&amp;gt; '''Speaker Bio:''' Ben Tomhave is a Senior Security Analyst with Gemini Security Solutions in Chantilly, VA, specializing in solutions architecture, security planning, program development and management, and other strategic security solutions. He holds a MS in Engineering Management with an Information Security Management concentration from The George Washington University and is a CISSP. &lt;br /&gt;
&lt;br /&gt;
=== June 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/&amp;lt;br&amp;gt; '''TOPIC''': Risk Management - Time to blow it up and start over?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''DESCRIPTION''':&lt;br /&gt;
&lt;br /&gt;
A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. &amp;quot;Now that the industry is trying to formalize the concept of risk management into neat little compartments like standards (ISO 27005/31000), certifications (CRISC) and products (GRC) guess what? We're doing it wrong. Fundamentally wrong. This talk will discuss why all this current risk management stuff is goofy and what sort of alternatives we have that might help us understand our ability to protect, our tendency towards failure, and how to match that up with what management will stomach.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Slides are available from: http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''SPECIAL SPEAKER''':&lt;br /&gt;
&lt;br /&gt;
[http://twitter.com/tiffanyrad Tiffany Rad] provided an overview and update on [http://twitter.com/reversespace Reverse Space] in Herndon, VA. For more information, or to help out, please join the [http://groups.google.com/group/ReverseSpace Reverse Space Google Group].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== May 2010  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode&amp;lt;br&amp;gt; '''TITLE''': State of Software Security ([[Image:State of Software Security-Ennis.ppsx.zip]])&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
A discussion of the current state of software security based on the compiled findings by Veracode from the dynamic and static code analysis they have performed for customers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== September 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time&amp;lt;br&amp;gt; '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Fortify 360&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
We're pleased to invite you to our next week's OWASP Session (Thursday September 17th). We will be hosting a presentation, demo and hands on session of Fortify 360 (http://www.fortify.com). Fortify 360 includes Fortify SCA (Source Code Analyzer) and the Fortify 360 Server which is Fortify's solution for an enterprise deployment of SCA. The session will start with a presentation by Fortify engineers, followed by a demo and finally a hands on session where the audience will be free to install Fortify SCA on the machine and try it the SCA tool on a sample application that we will provide. The audience will also be introduced with the Fortify 360 Server and try some of the enterprise level features such as collaborative code review, metrics and so on. Bring your laptop if you want to try Fortify 360!&lt;br /&gt;
&lt;br /&gt;
The target audience is anyone interested in Secure Code Review with a Static Analysis tool at the desktop level and/or enterprise level. We will need to register visitors before hand...please email wade.woolwine@owasp.org for registration and confirm attendance. Pizza and refreshments will be served.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''DATE''': Thursday, September 3, 2009. 6:00pm.&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Conducting Application Assessment&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER''': Jeremy Epstein, SRI&amp;lt;br&amp;gt; '''DESCRIPTION''': &lt;br /&gt;
&lt;br /&gt;
After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with &amp;quot;hanging chads&amp;quot;. Once problems with those systems started appearing, many localities started moving to optical scan, which was used by a majority of US voters in the 2008 election. There are other technologies in use around the country, including lever machines, vote-by-mail, vote-by-phone, and Internet voting. What are the tradeoffs among these technologies? Particularly relevant to OWASP, what are the security issues associated with different types of equipment, and what measures do vendors of voting equipment use to try to address the security problems? Are software security problems important, or can non-technical measures protect against them? In this talk, we'll discuss a wide variety of voting technologies, and their pros and cons from both a technical and societal perspective.&lt;br /&gt;
&lt;br /&gt;
'''ABOUT THE SPEAKER''': &lt;br /&gt;
&lt;br /&gt;
Jeremy Epstein is Senior Computer Scientist at SRI International. His background includes more than 20 years experience in computer security research, product development, and consulting. Prior to joining SRI International, he was Principal Consultant with Cigital, and before that spent nine years as Senior Director of Product Security at Software AG, an international business software company. Within the area of voting systems, Jeremy has been involved for over five years in voting technology and advocacy, both as an employee and as an independent consultant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== July 2009  ===&lt;br /&gt;
&lt;br /&gt;
'''DATE''': July 9th 6pm-9pm EST&amp;lt;br&amp;gt; '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171&amp;lt;br&amp;gt; '''TOPIC''': &amp;quot;Ounce's 02&amp;quot;&amp;lt;br&amp;gt; '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.&amp;lt;br&amp;gt; '''DESCRIPTION''': So what is O2? &lt;br /&gt;
&lt;br /&gt;
Well in my mind O2 is a combination of advanced tools (Technology) which are designed to be used on a particular way (Process) by knowledgeable Individuals (People) &lt;br /&gt;
&lt;br /&gt;
Think about it as a Fighter Jet who is able to go very fast, has tons of controls, needs to be piloted by somebody who knows what they are doing and needs to have a purpose (i.e. mission). &lt;br /&gt;
&lt;br /&gt;
Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review. &lt;br /&gt;
&lt;br /&gt;
Now, here is the catch, this version is NOT for the faint-of-heart. I designed this to suit my needs, which although are the same as most other security consultants, have its own particularities&amp;amp;nbsp;:) &lt;br /&gt;
&lt;br /&gt;
The whole model of O2 development is based around the concept of automating a security consultant’s brain, so I basically ensure that the main O2 Developer (Dinis Cruz) has a very good understanding of the feature requirements of the targeted Security Consultant (Dinis Cruz)&amp;amp;nbsp;:) . And this proved (even to my surprise) spectacularly productive, since suddenly I (i.e. the security consultant) didn't had to wait months for new features to be added to its toolkit. If there was something that needed to be added, it would just be added in days or hours. &lt;br /&gt;
&lt;br /&gt;
=== June 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''&amp;lt;br&amp;gt; Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''&amp;lt;br&amp;gt;'' &lt;br /&gt;
&lt;br /&gt;
Gary McGraw talked about the experience he, Sammy Migues, and Brian Chess gained conducting a survey of some of America's top Software Security groups. Study results are available under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Share Alike license] at [http://www.bsi-mm.com www.bsi-mm.com]. Gary described the common structural elements and activities of successful software security programs, present the maturity model that resulted from survey data, and discuss lessons learned from listening to those leading these groups. &lt;br /&gt;
&lt;br /&gt;
Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group. &lt;br /&gt;
&lt;br /&gt;
Download presentation notes at: [http://www.owasp.org/images/0/03/JMR-Economics_of_Security_Goups.ppt The Economic Advantages of a Resilient Supply Chain- Software Security] &lt;br /&gt;
&lt;br /&gt;
=== May 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''&amp;lt;br&amp;gt; Later, a panel: &lt;br /&gt;
&lt;br /&gt;
*Steven Lavenhar, Booz Allen Hamilton; &lt;br /&gt;
*Eric Dalci, Cigital Inc.&lt;br /&gt;
&lt;br /&gt;
Panel moderated by John Steven &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This session is an introductory to Static Analysis. This session presents the different types of analysis used by today's Static Analysis tools. Examples of direct application to find vulnerabilities will be shown (ex: Data Flow Analysis, Semantic, Control Flow, etc.). Current limitations of Static Analysis will also be exposed. This session is tool agnostic, but will cover the approach taken by various leading commercial (as well as open-source) tools. &lt;br /&gt;
&lt;br /&gt;
Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis] &lt;br /&gt;
&lt;br /&gt;
=== April 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''&amp;lt;br&amp;gt; Jeremiah Spoke on (what he and colleagues determined were the) top ten web hacking techniques of 2008. This talk was a preview of his RSA '09 talk.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Later, &lt;br /&gt;
&lt;br /&gt;
*Nate Miller, Stratum Security; &lt;br /&gt;
*Jeremiah Grossman, Whitehat Security; &lt;br /&gt;
*Tom Brennan, Whitehat Security; and &lt;br /&gt;
*Wade Woolwine, AOL&lt;br /&gt;
&lt;br /&gt;
served as penetration testing panels answering questions posed and moderated by Ken Van Wyk. &lt;br /&gt;
&lt;br /&gt;
=== February 2009  ===&lt;br /&gt;
&lt;br /&gt;
''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity''' &lt;br /&gt;
&lt;br /&gt;
Identification of web application vulnerabilities is only half the battle with remediation efforts as the other. Let's face the facts, there are many real world business scenarios where it is not possible to update web application code in either a timely manner or at all. This is where the tactical use-case of implementing a web application firewall to address identified issues proves its worth. &lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of the recommended practices for utilizing a web application firewall for virtual patching. After discussing the framework to use, we will then present a very interesting OWASP Summer of Code Project where the challenge was to attempt to mitigate as many of the OWASP WebGoat vulnerabilities as possible using the open source ModSecurity web application firewall. During the talk, we will discuss both WebGoat and ModSecurity and provide in-depth walk-throughs of some of the complex fixes. Examples will include addressing not only attacks but the underlying vulnerabilities, using data persistence for multiple-step processes, content injection and even examples of the new LUA programming language API. The goal of this talk is to both highlight cutting edge mitigation options using a web application firewall and to show how it can effectively be used by security consultants who traditionally could only offer source code fixes. &lt;br /&gt;
&lt;br /&gt;
Ryan C. Barnett is the Director of Application Security Research at Breach Security and leads Breach Security Labs. He is also a Faculty Member for the SANS Institute, Team Lead for the Center for Internet Security Apache Benchmark Project and a Member of the Web Application Security Consortium where he leads the Distributed Open Proxy Honeypot Project. Mr. Barnett has also authored a web security book for Addison/Wesley Publishing entitled &amp;quot;Preventing Web Attacks with Apache.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
(This talk is a preview of Ryan's talk at Blackhat Federal the following week - see https://www.blackhat.com/html/bh-dc-09/bh-dc-09-speakers.html#Barnett ) &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]] &lt;br /&gt;
&lt;br /&gt;
''John Steven, Cigital'': '''Moving Beyond Top N Lists''' &lt;br /&gt;
&lt;br /&gt;
Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Cigital published an article: The Top 11 Reasons Why Top 10 (or 25) Lists Don’t Work. Yet, these lists are a staple of conference abstracts, industry best practice lists, and the like. Are they good or bad? We’ll explore how to get beyond the Top 10 (or 25) list in making your software security effort real. &lt;br /&gt;
&lt;br /&gt;
John is Senior Director, Advanced Technology Consulting at Cigital. His experience includes research in static code analysis and hands-on architecture and implementation of high-performance, scalable Java EE systems. John has provided security consulting services to a broad variety of commercial clients including two of the largest trading platforms in the world and has advised America's largest internet provider in the Midwest on security and forensics. John led the development of Cigital's architectural analysis methodology and its approach to deploying enterprise software security frameworks. He has demonstrated success in building Cigital's intellectual property for providing cutting-edge security. He brings this experience and a track record of effective strategic innovation to clients seeking to change, whether to adopt more cutting-edge approaches, or to solidify ROI. John currently chairs the SD Best Practices security track and co-edits the building security in department of IEEE's Security and Privacy magazine. John has served on numerous conference panels regarding software security, wireless security and Java EE system development. He holds a B.S. in Computer Engineering and an M.S. in Computer Science from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
=== January 2009  ===&lt;br /&gt;
&lt;br /&gt;
To kick off 2009, our January meeting featured a discussion of the relationship between application security and CMMI, and an overview of the OWASP ASVS project. &lt;br /&gt;
&lt;br /&gt;
''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI''' &lt;br /&gt;
&lt;br /&gt;
Addressing new and complex threats and IT security challenges requires repeatable, reliable, rapid, and cost effective solutions. To implement these solutions, organizations have begun to align their security improvement efforts with their system and software development practices. During a “Birds of a Feather” at the March 2007 SEPG, a group of industry representatives initiated an effort which led to the definition of assurance practices that can be applied in the context of the CMMI. This presentation will provide an understanding how applying the assurance practices in the context of security contribute to the overall increased quality of products and services, illustrate how the a focus on assurance in the context of CMMI practices is related to application security practices, and present and approach to evaluate and improve the repeatability and reliability of assurance practices. &lt;br /&gt;
&lt;br /&gt;
Michele Moss, CISSP, is a security engineer with more than 12 years of experience in process improvement. She specializes in integrating assurance processes and practices into project lifecycles. Michele is the Co-Chair of the DHS Software Assurance Working Group on Processes &amp;amp;amp; Practices. She has assisted numerous organizations with maturing their information technology, information assurance, project management, and support practices through the use of the capability maturity models including the CMMI, and the SSE-CMM. She is one of the key contributors in an effort to apply an assurance focus to CMMI. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS''' &lt;br /&gt;
&lt;br /&gt;
The primary aim of the OWASP ASVS Project is to normalize the range of coverage and level of rigor available in the market when it comes to performing application-level security verification. The goal is to create a set of commercially-workable open standards that are tailored to specific web-based technologies. &lt;br /&gt;
&lt;br /&gt;
Mike Boberski works at Booz Allen Hamilton. He has a background in application security and the use of cryptography by applications. He is experienced in trusted product evaluation, security-related software development and integration, and cryptomodule testing. For OWASP, he is the project lead and a co-author of the OWASP Application Security Verification Standard, the first OWASP standard. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]] &lt;br /&gt;
&lt;br /&gt;
=== November 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our November 2008 meeting, we had two great presentations on software assurance and security testing. &lt;br /&gt;
&lt;br /&gt;
''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance''' &lt;br /&gt;
&lt;br /&gt;
Nadya's presentation will provide an update on the Software Assurance Forum efforts to establish a comprehensive framework for software assurance (SwA) and security measurement. The Framework addresses measuring achievement of SwA goals and objectives within the context of individual projects, programs, or enterprises. It targets a variety of audiences including executives, developers, vendors, suppliers, and buyers. The Framework leverages existing measurement methodologies, including Practical Software and System Measurement (PSM); CMMI Goal, Question, Indicator, Measure (GQ(I)M); NIST SP 800-55 Rev1; and ISO/IEC 27004 and identifies commonalities among the methodologies to help organizations integrate SwA measurement in their overall measurement efforts cost-effectively and as seamlessly as possible, rather than establish a standalone SwA measurement effort within an organization. The presentation will provide an update on the SwA Forum Measurement Working Group work, present the current version of the Framework and underlying measures development and implementation processes, and propose example SwA measures applicable to a variety of SwA stakeholders. The presentation will update the group on the latest NIST and ISO standards on information security measurement that are being integrated into the Framework as the standards are being developed. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Paco Hope, Cigital'': '''The Web Security Testing Cookbook''' &lt;br /&gt;
&lt;br /&gt;
The Web Security Testing Cookbook (O'Reilly &amp;amp;amp; Associates, October 2008) gives developers and testers the tools they need to make security testing a regular part of their development lifecycle. Its recipe style approach covers manual, exploratory testing as well automated techniques that you can make part of your unit tests or regression cycle. The recipes cover the basics like observing messages between clients and servers, to multi-phase tests that script the login and execution of web application features. This book complements many of the security texts in the market that tell you what a vulnerability is, but not how to systematically test it day in and day out. Leverage the recipes in this book to add significant security coverage to your testing without adding significant time and cost to your effort. &lt;br /&gt;
&lt;br /&gt;
Congratulations to Tim Bond who won an autographed copy of Paco's book. Get your copy here [[http://www.amazon.com/Security-Testing-Cookbook-Paco-Hope/dp/0596514832]] &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf]] &lt;br /&gt;
&lt;br /&gt;
=== October 2008  ===&lt;br /&gt;
&lt;br /&gt;
For our October 2008 meeting, we had two fascinating talks relating to forensics. &lt;br /&gt;
&lt;br /&gt;
''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats''' &lt;br /&gt;
&lt;br /&gt;
Dave Merkel is Vice President of Products at Mandiant, a leading provider of information security services, education and products. Mr. Merkel has worked in the information security and incident response industry for over 10 years. His background includes service as a federal agent in the US Air Force and over 7 years experience directing security operations at America Online. He currently oversees the product business at Mandiant, and is in charge of building Mandiant Intelligent Response - an enterprise incident response solution. But no, he won't be selling you anything today. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf]] &lt;br /&gt;
&lt;br /&gt;
''Inno Eroraha, NetSecurity'': '''[Responding to the Digital Crime Scene: Gathering Volatile Data''' &lt;br /&gt;
&lt;br /&gt;
Inno Eroraha is the founder and chief strategist of NetSecurity Corporation, a company that provides digital forensics, hands-on security consulting, and Hands-on How-To® training solutions that are high-quality, timely, and customer-focused. In this role, Mr. Eroraha helps clients plan, formulate, and execute the best security and forensics strategy that aligns with their business goals and priorities. He has consulted with Fortune 500 companies, IRS, DHS, VA, DoD, and other entities. &lt;br /&gt;
&lt;br /&gt;
Slides available: [[http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf] ] &lt;br /&gt;
&lt;br /&gt;
=== History ===&lt;br /&gt;
&lt;br /&gt;
The original DC Chapter was founded in June 2004 by [mailto:jeff.williams@owasp.org Jeff Williams] and has had members from Virginia to Delaware. In April 2005 a new chapter, OWASP Washington VA Local Chapter, was formed and the DC Chapter was renamed to DC-Maryland. The two are sister chapters and include common members and shared discourse. The chapters meet in opposite halves of the month to facilitate this relationship. &lt;br /&gt;
&lt;br /&gt;
==== Chapter Groups  ====&lt;br /&gt;
&lt;br /&gt;
Within the chapter, various common interests spring up. We've created Google groups to manage collaboration amongst participants for these topics. Feel free to join and participate in: &lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/novaowasp_threatmodeling  Threat Modeling] &lt;br /&gt;
*[http://groups.google.com/group/novaowasp_mobile  Mobile] &lt;br /&gt;
&lt;br /&gt;
==== Knowledge  ====&lt;br /&gt;
&lt;br /&gt;
The Northern Virginia (NoVA) chapter is committed to compiling resources on interesting and valuable topic areas. We hope that this structure helps you access information pertinent to your tasks at hand as you move through a secure application development life cycle. Currently, our topic areas of focus include activities such as: &lt;br /&gt;
&lt;br /&gt;
*Threat Modeling &lt;br /&gt;
*[[Code Review and Static Analysis with tools]] &lt;br /&gt;
*Penetration Testing and Dynamic Analysis tools &lt;br /&gt;
*Monitoring/Dynamic patching (WAFs)&lt;br /&gt;
&lt;br /&gt;
Certain projects our members are involved in cross-cut these activities, providing value throughout. They include: &lt;br /&gt;
&lt;br /&gt;
*ASVS&lt;br /&gt;
&lt;br /&gt;
=== Static Analysis Curriculum  ===&lt;br /&gt;
&lt;br /&gt;
*For an introduction to the OWASP Static Analysis (SA) Track goals, objectives, and session roadmap, please see [http://www.owasp.org/index.php/Image:OWASP_NoVA_SA_Track_Final_20090408.ppt this presentation].&lt;br /&gt;
&lt;br /&gt;
The following is the agenda of the OWASP Static Analysis track roadmap for the [http://www.owasp.org/index.php/Virginia_(Northern_Virginia) Northern Virginia Chapter]. &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]] &lt;br /&gt;
&lt;br /&gt;
'''Contacts'''&amp;lt;br&amp;gt; Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== Flash Talk Resources  ===&lt;br /&gt;
&lt;br /&gt;
Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] &amp;lt;br&amp;gt; [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information &amp;lt;br&amp;gt; Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;paypal&amp;gt;Northern Virginia&amp;lt;/paypal&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Virginia]] [[Category:Washington,_DC]]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Global_Conferences_Committee_-_Application_9&amp;diff=105629</id>
		<title>Global Conferences Committee - Application 9</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Global_Conferences_Committee_-_Application_9&amp;diff=105629"/>
				<updated>2011-02-23T13:08:32Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &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;Benjamin (Ben) Tomhave&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 NoVA Program Committee member, OWASP Summit 2011 attendee&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;
&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;|Dan Cornell&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|Global Membership Committee Chair&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|Ben's involvement in the OWASP NoVA chapter as well as his outreach to other organizations such as Security BSides make him an excellent candidate to be on the Global Conference Committee.&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;|John Steven&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|NoVA Chapter President&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|Ben's work in the chapter has been exemplary and he has concrete, practical, and good ideas.&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>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User:John_Steven&amp;diff=103569</id>
		<title>User:John Steven</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User:John_Steven&amp;diff=103569"/>
				<updated>2011-02-06T02:05:07Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: Created page with &amp;quot;John leads the Virginia OWASP Northern Virginia (NoVA) chapter. Follow the chapter on [http://www.twitter.com/OWASPNoVA OWASPNoVA]   &amp;lt;br&amp;gt; '''Projects'''   John has:   *Contri...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;John leads the [[Virginia OWASP Northern Virginia (NoVA) chapter]]. Follow the chapter on [http://www.twitter.com/OWASPNoVA OWASPNoVA] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''Projects''' &lt;br /&gt;
&lt;br /&gt;
John has: &lt;br /&gt;
&lt;br /&gt;
*Contributed to&amp;amp;nbsp; [[O2]] &lt;br /&gt;
*Created the [http://www.owasp.org/index.php/Category:Summit_2011_OWASP_Secure_Coding_Workshop_Track Secure Coding Workshop]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; '''Professional''' &lt;br /&gt;
&lt;br /&gt;
John Steven is Senior Director of Advanced Technology Consulting at Cigital with over a decade of hands-on experience in software security. John's expertise runs the gamut of software security from threat modeling and architectural risk analysis, through static analysis (with an emphasis on automation), to security testing. As a consultant, John has provided strategic direction as a trusted adviser to many multi-national corporations. John's keen interest in automation keeps Cigital technology at the cutting edge. He has served as co-editor of the Building Security In department of IEEE Security &amp;amp;amp; Privacy magazine and speaks with regularity at conferences and trade shows. John holds a B.S. in Computer Engineering and an M.S. in Computer Science both from Case Western Reserve University. &lt;br /&gt;
&lt;br /&gt;
'''Resources''' &lt;br /&gt;
&lt;br /&gt;
*[http://www.cigital.com/justiceleague/author/jOHN/ Cigital Blog] &lt;br /&gt;
*[http://codepoetic.blogspot.com Development Blog] &lt;br /&gt;
*[http://www.twitter.com/m1splacedsoul Twitter]&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Summit_2011_Working_Sessions/Session054&amp;diff=103568</id>
		<title>Summit 2011 Working Sessions/Session054</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Summit_2011_Working_Sessions/Session054&amp;diff=103568"/>
				<updated>2011-02-06T01:44:31Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Template:&amp;lt;includeonly&amp;gt;{{{1}}}&amp;lt;/includeonly&amp;gt;&amp;lt;noinclude&amp;gt;Summit 2011 Working Sessions test tab&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name1 = John Steven&lt;br /&gt;
| summit_session_attendee_email1 = John.Steven@owasp.org &lt;br /&gt;
| summit_session_attendee_username1 = John Steven&lt;br /&gt;
| summit_session_attendee_company1= Cigital&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed1=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name2 = &lt;br /&gt;
| summit_session_attendee_email2 = &lt;br /&gt;
| summit_session_attendee_username2 = &lt;br /&gt;
| summit_session_attendee_company2=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed2=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name3 = &lt;br /&gt;
| summit_session_attendee_email3 = &lt;br /&gt;
| summit_session_attendee_username3 = &lt;br /&gt;
| summit_session_attendee_company3=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed3=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name4 = &lt;br /&gt;
| summit_session_attendee_email4 = &lt;br /&gt;
| summit_session_attendee_username4 = &lt;br /&gt;
| summit_session_attendee_company4=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed4=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name5 = &lt;br /&gt;
| summit_session_attendee_email5 = &lt;br /&gt;
| summit_session_attendee_username5 = &lt;br /&gt;
| summit_session_attendee_company5=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed5=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name6 = &lt;br /&gt;
| summit_session_attendee_email6 = &lt;br /&gt;
| summit_session_attendee_username6 = &lt;br /&gt;
| summit_session_attendee_company6=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed6=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name7 = &lt;br /&gt;
| summit_session_attendee_email7 = &lt;br /&gt;
| summit_session_attendee_username7 = &lt;br /&gt;
| summit_session_attendee_company7=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed7=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name8 = &lt;br /&gt;
| summit_session_attendee_email8 = &lt;br /&gt;
| summit_session_attendee_username8 = &lt;br /&gt;
| summit_session_attendee_company8=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed8=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name9 = &lt;br /&gt;
| summit_session_attendee_email9 = &lt;br /&gt;
| summit_session_attendee_username9 = &lt;br /&gt;
| summit_session_attendee_company9=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed9=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name10 = &lt;br /&gt;
| summit_session_attendee_email10 = &lt;br /&gt;
| summit_session_attendee_username10 = &lt;br /&gt;
| summit_session_attendee_company10=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed10=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name11 = &lt;br /&gt;
| summit_session_attendee_email11 = &lt;br /&gt;
| summit_session_attendee_username11 = &lt;br /&gt;
| summit_session_attendee_company11=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed11=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name12 = &lt;br /&gt;
| summit_session_attendee_email12 = &lt;br /&gt;
| summit_session_attendee_username12 = &lt;br /&gt;
| summit_session_attendee_company12=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed12=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name13 = &lt;br /&gt;
| summit_session_attendee_email13 = &lt;br /&gt;
| summit_session_attendee_username13 = &lt;br /&gt;
| summit_session_attendee_company13=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed13=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name14 = &lt;br /&gt;
| summit_session_attendee_email14 = &lt;br /&gt;
| summit_session_attendee_username14 = &lt;br /&gt;
| summit_session_attendee_company14=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed14= &lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name15 = &lt;br /&gt;
| summit_session_attendee_email15 = &lt;br /&gt;
| summit_session_attendee_username15 = &lt;br /&gt;
| summit_session_attendee_company15=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed15=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name16 = &lt;br /&gt;
| summit_session_attendee_email16 = &lt;br /&gt;
| summit_session_attendee_username16 = &lt;br /&gt;
| summit_session_attendee_company16=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed16=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name17 = &lt;br /&gt;
| summit_session_attendee_email17 = &lt;br /&gt;
| summit_session_attendee_username17 = &lt;br /&gt;
| summit_session_attendee_company17=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed17=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name18 = &lt;br /&gt;
| summit_session_attendee_email18 = &lt;br /&gt;
| summit_session_attendee_username18 = &lt;br /&gt;
| summit_session_attendee_company18=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed18=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name19 = &lt;br /&gt;
| summit_session_attendee_email19 = &lt;br /&gt;
| summit_session_attendee_username19 = &lt;br /&gt;
| summit_session_attendee_company19=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed19=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name20 = &lt;br /&gt;
| summit_session_attendee_email20 = &lt;br /&gt;
| summit_session_attendee_username20 = &lt;br /&gt;
| summit_session_attendee_company20=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed20=&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| summit_track_logo = [[Image:T._global_committees.jpg]]&lt;br /&gt;
| summit_ws_logo = [[Image:WS._global_commitee.jpg‎]]&lt;br /&gt;
| summit_session_name = Board Structure&lt;br /&gt;
| summit_session_url = http://www.owasp.org/index.php?title=Summit_2011_Working_Sessions/Session054&lt;br /&gt;
| mailing_list =&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| short_working_session_description= &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| related_project_name1 = &lt;br /&gt;
| related_project_url_1 = &lt;br /&gt;
&lt;br /&gt;
| related_project_name2 = &lt;br /&gt;
| related_project_url_2 = &lt;br /&gt;
&lt;br /&gt;
| related_project_name3 = &lt;br /&gt;
| related_project_url_3 = &lt;br /&gt;
&lt;br /&gt;
| related_project_name4 = &lt;br /&gt;
| related_project_url_4 = &lt;br /&gt;
&lt;br /&gt;
| related_project_name5 = &lt;br /&gt;
| related_project_url_5 = &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| summit_session_objective_name1= &lt;br /&gt;
&lt;br /&gt;
| summit_session_objective_name2 = &lt;br /&gt;
&lt;br /&gt;
| summit_session_objective_name3 = &lt;br /&gt;
&lt;br /&gt;
| summit_session_objective_name4 = &lt;br /&gt;
&lt;br /&gt;
| summit_session_objective_name5 =  &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| working_session_date_and_time = &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| discussion_model = participants and attendees&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| operational_resources = Projector, whiteboards, markers, Internet connectivity, power&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| working_session_additional_details = &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|summit_session_deliverable_name1 = &lt;br /&gt;
&lt;br /&gt;
|summit_session_deliverable_name2 = &lt;br /&gt;
&lt;br /&gt;
|summit_session_deliverable_name3 = &lt;br /&gt;
&lt;br /&gt;
|summit_session_deliverable_name4 = &lt;br /&gt;
&lt;br /&gt;
|summit_session_deliverable_name5 = &lt;br /&gt;
&lt;br /&gt;
|summit_session_deliverable_name6 = &lt;br /&gt;
&lt;br /&gt;
|summit_session_deliverable_name7 = &lt;br /&gt;
&lt;br /&gt;
|summit_session_deliverable_name8 =  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| summit_session_leader_name1 = &lt;br /&gt;
| summit_session_leader_email1 = &lt;br /&gt;
| summit_session_leader_username1 = &lt;br /&gt;
&lt;br /&gt;
| summit_session_leader_name2 = &lt;br /&gt;
| summit_session_leader_email2 = &lt;br /&gt;
| summit_session_leader_username2 = &lt;br /&gt;
&lt;br /&gt;
| summit_session_leader_name3 = &lt;br /&gt;
| summit_session_leader_email3 = &lt;br /&gt;
| summit_session_leader_username3 = &lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| operational_leader_name1 =&lt;br /&gt;
| operational_leader_email1 =&lt;br /&gt;
| operational_leader_username1 = &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| meeting_notes = &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| session_name_mask = &amp;lt;!--Please replace DO NOT EDIT this string --&amp;gt; Session054&lt;br /&gt;
| session_home_page = &amp;lt;!--Please replace DO NOT EDIT this string --&amp;gt; Summit_2011_Working_Sessions/Session054&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Summit_2011_Working_Sessions/Session028&amp;diff=103081</id>
		<title>Summit 2011 Working Sessions/Session028</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Summit_2011_Working_Sessions/Session028&amp;diff=103081"/>
				<updated>2011-02-02T17:12:17Z</updated>
		
		<summary type="html">&lt;p&gt;John Steven: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Template:&amp;lt;includeonly&amp;gt;{{{1}}}&amp;lt;/includeonly&amp;gt;&amp;lt;noinclude&amp;gt;Summit 2011 Working Sessions test tab&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name1 = Elke Roth-Mandutz&lt;br /&gt;
| summit_session_attendee_email1 = elke.roth-mandutz@ohm-hochschule.de&lt;br /&gt;
| summit_session_attendee_username1 = &lt;br /&gt;
| summit_session_attendee_company1= GSO-University of Applied Sciences&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed1=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name2 = &lt;br /&gt;
| summit_session_attendee_email2 = &lt;br /&gt;
| summit_session_attendee_username2 = &lt;br /&gt;
| summit_session_attendee_company2=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed2=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name3 = Chris Schmidt&lt;br /&gt;
| summit_session_attendee_email3 = chris.schmidt@owasp.org&lt;br /&gt;
| summit_session_attendee_username3 = &lt;br /&gt;
| summit_session_attendee_company3=Aspect Security&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed3=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name4 = Justin Clarke&lt;br /&gt;
| summit_session_attendee_email4 = justin.clarke@owasp.org&lt;br /&gt;
| summit_session_attendee_username4 = &lt;br /&gt;
| summit_session_attendee_company4=Gotham Digital Science&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed4=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name5 = &lt;br /&gt;
| summit_session_attendee_email5 = &lt;br /&gt;
| summit_session_attendee_username5 = &lt;br /&gt;
| summit_session_attendee_company5=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed5=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name6 = &lt;br /&gt;
| summit_session_attendee_email6 = &lt;br /&gt;
| summit_session_attendee_username6 = &lt;br /&gt;
| summit_session_attendee_company6=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed6=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name7 = &lt;br /&gt;
| summit_session_attendee_email7 = &lt;br /&gt;
| summit_session_attendee_username7 = &lt;br /&gt;
| summit_session_attendee_company7=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed7=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name8 = &lt;br /&gt;
| summit_session_attendee_email8 = &lt;br /&gt;
| summit_session_attendee_username8 = &lt;br /&gt;
| summit_session_attendee_company8=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed8=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name9 = &lt;br /&gt;
| summit_session_attendee_email9 = &lt;br /&gt;
| summit_session_attendee_username9 = &lt;br /&gt;
| summit_session_attendee_company9=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed9=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name10 = &lt;br /&gt;
| summit_session_attendee_email10 = &lt;br /&gt;
| summit_session_attendee_username10 = &lt;br /&gt;
| summit_session_attendee_company10=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed10=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name11 = &lt;br /&gt;
| summit_session_attendee_email11 = &lt;br /&gt;
| summit_session_attendee_username11 = &lt;br /&gt;
| summit_session_attendee_company11=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed11=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name12 = &lt;br /&gt;
| summit_session_attendee_email12 = &lt;br /&gt;
| summit_session_attendee_username12 = &lt;br /&gt;
| summit_session_attendee_company12=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed12=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name13 = &lt;br /&gt;
| summit_session_attendee_email13 = &lt;br /&gt;
| summit_session_attendee_username13 = &lt;br /&gt;
| summit_session_attendee_company13=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed13=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name14 = &lt;br /&gt;
| summit_session_attendee_email14 = &lt;br /&gt;
| summit_session_attendee_username14 = &lt;br /&gt;
| summit_session_attendee_company14=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed14= &lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name15 = &lt;br /&gt;
| summit_session_attendee_email15 = &lt;br /&gt;
| summit_session_attendee_username15 = &lt;br /&gt;
| summit_session_attendee_company15=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed15=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name16 = &lt;br /&gt;
| summit_session_attendee_email16 = &lt;br /&gt;
| summit_session_attendee_username16 = &lt;br /&gt;
| summit_session_attendee_company16=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed16=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name17 = &lt;br /&gt;
| summit_session_attendee_email17 = &lt;br /&gt;
| summit_session_attendee_username17 = &lt;br /&gt;
| summit_session_attendee_company17=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed17=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name18 = &lt;br /&gt;
| summit_session_attendee_email18 = &lt;br /&gt;
| summit_session_attendee_username18 = &lt;br /&gt;
| summit_session_attendee_company18=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed18=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name19 = &lt;br /&gt;
| summit_session_attendee_email19 = &lt;br /&gt;
| summit_session_attendee_username19 = &lt;br /&gt;
| summit_session_attendee_company19=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed19=&lt;br /&gt;
&lt;br /&gt;
| summit_session_attendee_name20 = &lt;br /&gt;
| summit_session_attendee_email20 = &lt;br /&gt;
| summit_session_attendee_username20 = &lt;br /&gt;
| summit_session_attendee_company20=&lt;br /&gt;
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed20=&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| summit_track_logo = [[Image:T._secure_coding.jpg]]&lt;br /&gt;
| summit_ws_logo = [[Image:WS._secure_coding.jpg]]&lt;br /&gt;
| summit_session_name = Protecting Information Stored Client-Side&lt;br /&gt;
| summit_session_url = http://www.owasp.org/index.php/Summit_2011_Working_Sessions/Session028&lt;br /&gt;
| mailing_list =&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| short_working_session_description=This section will focus on providing mechanisms for protecting important or sensitive data applications and services need to store client-side. Contexts this section aims to cover include:&lt;br /&gt;
&lt;br /&gt;
* Personal or user-specific information&lt;br /&gt;
* Application-specific information (tokens, secrets)&lt;br /&gt;
* Key configuration data, other EIS/service information&lt;br /&gt;
&lt;br /&gt;
For the purpose of the Portugal Summit, the session will focus on development within a &amp;quot;classic&amp;quot; N-tier Java application environment. &lt;br /&gt;
 &lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| related_project_name1 = &lt;br /&gt;
| related_project_url_1 = &lt;br /&gt;
&lt;br /&gt;
| related_project_name2 = &lt;br /&gt;
| related_project_url_2 = &lt;br /&gt;
&lt;br /&gt;
| related_project_name3 = &lt;br /&gt;
| related_project_url_3 = &lt;br /&gt;
&lt;br /&gt;
| related_project_name4 = &lt;br /&gt;
| related_project_url_4 = &lt;br /&gt;
&lt;br /&gt;
| related_project_name5 = &lt;br /&gt;
| related_project_url_5 = &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| summit_session_objective_name1= Produce an informal threat model for each development scenario &lt;br /&gt;
&lt;br /&gt;
| summit_session_objective_name2 = Impart clear and simple shared understanding of threats associated with each development scenario (and dispel common misunderstandings/idioms)  &lt;br /&gt;
&lt;br /&gt;
| summit_session_objective_name3 = Define solution that resists defined attacks&lt;br /&gt;
&lt;br /&gt;
| summit_session_objective_name4 = Deliver solution implementation (snippets) to https://code.google.com/p/secure-coding-workshop/&lt;br /&gt;
&lt;br /&gt;
| summit_session_objective_name5 =  &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| working_session_date_and_time = &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| discussion_model = participants and attendees&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| operational_resources = Projector, whiteboards, markers, Internet connectivity, power&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| working_session_additional_details = Within the N-tier Java environment, the session will tackle the following development scenarios:&lt;br /&gt;
&lt;br /&gt;
1) - Coat Check&lt;br /&gt;
* Removing information from a client&lt;br /&gt;
* Server-side storage, memento pattern&lt;br /&gt;
* Solving scale issues&lt;br /&gt;
2) - Purse&lt;br /&gt;
* Storing app-important information (like a purse)&lt;br /&gt;
* Resisting attack with augmented plain-text storage!&lt;br /&gt;
* Supporting back, reload, etc.&lt;br /&gt;
* Patterns &amp;amp; design for anti-tampering protocols&lt;br /&gt;
3) - Nuclear Briefcase&lt;br /&gt;
* Sensitive, opaque information&lt;br /&gt;
* Shuttling information between 3rd parties&lt;br /&gt;
&lt;br /&gt;
Future summits will address the following two contexts as well: &lt;br /&gt;
&lt;br /&gt;
* Phones (ios, Android)&lt;br /&gt;
* RIA &lt;br /&gt;
&lt;br /&gt;
However, for the purpose of this coming session, we will only conduct planning and 'homework assignments' for these contexts in the next session (likely Minnesota). &lt;br /&gt;
&lt;br /&gt;
The session will work each of the three above development scenarios within the n-tier environment using the following work stream: &lt;br /&gt;
&lt;br /&gt;
* Define problem&lt;br /&gt;
* Conduct Cigital-style Threat Model (TM) exercise&lt;br /&gt;
* Co-design solution based on particular threats and attack vectors&lt;br /&gt;
* Implement solution within provided sample application-ette&lt;br /&gt;
* Discuss testing and verification strategies for solution.&lt;br /&gt;
&lt;br /&gt;
Participants will be taken through the above work stream, an abbreviated 'build security in' process designed to focus on implementation (rather than documentation or assurance), to restructure applications to demonstrate security patterns, integrate existing security functionality, or build security controls as necessary. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|summit_session_deliverable_name1 = (see objectives) Threat Models&lt;br /&gt;
|summit_session_deliverable_name2 = (see objectives) Code Snippets&lt;br /&gt;
&lt;br /&gt;
|summit_session_deliverable_name3 = Plan and Extra-summit work-items for exercises in Phone and RIA  contexts during next summit &lt;br /&gt;
&lt;br /&gt;
|summit_session_deliverable_name4 = &lt;br /&gt;
&lt;br /&gt;
|summit_session_deliverable_name5 = &lt;br /&gt;
&lt;br /&gt;
|summit_session_deliverable_name6 = &lt;br /&gt;
&lt;br /&gt;
|summit_session_deliverable_name7 = &lt;br /&gt;
&lt;br /&gt;
|summit_session_deliverable_name8 = &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| summit_session_leader_name1 = John Steven&lt;br /&gt;
| summit_session_leader_email1 = John.Steven@owasp.org&lt;br /&gt;
&lt;br /&gt;
| summit_session_leader_name2 = &lt;br /&gt;
| summit_session_leader_email2 = &lt;br /&gt;
| summit_session_leader_username2 = &lt;br /&gt;
&lt;br /&gt;
| summit_session_leader_name3 = &lt;br /&gt;
| summit_session_leader_email3 = &lt;br /&gt;
| summit_session_leader_username3 = &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| operational_leader_name1 =&lt;br /&gt;
| operational_leader_email1 =&lt;br /&gt;
| operational_leader_username1 = &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| meeting_notes = &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| session_name_mask = &amp;lt;!--Please replace DO NOT EDIT this string --&amp;gt; Session028&lt;br /&gt;
| session_home_page = &amp;lt;!--Please replace DO NOT EDIT this string --&amp;gt; Summit_2011_Working_Sessions/Session028&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>John Steven</name></author>	</entry>

	</feed>