|
|
| (95 intermediate revisions by 11 users not shown) |
| Line 1: |
Line 1: |
| − | ==== '11 Election ====
| |
| − |
| |
| − | === Letter from Chapter President - John Steven ===
| |
| − | All,
| |
| − |
| |
| − | I'm proud of how much the Northern Virginia OWASP Chapter has grown in the past two years. We've increased membership and attendance, and been able to provide you, our constituency, some interesting speakers, panels, and presentations. A single chapter lead has always headed our chapter but last year we saw enough participation and activity we felt the need to add a program committee. Now, we've reached a size where we'd benefit from more leadership and governance.
| |
| − |
| |
| − | As you familiarize yourself with OWASP you'll notice two principal memes:
| |
| − |
| |
| − | * Conduct operations in as open, transparent, & democratic a manner as possible
| |
| − | * Prefer progress to discussion--support engaged participants that produce results over promise
| |
| − |
| |
| − | To provide better leadership and governance within the two principals' vein, I'm establishing a chapter board to be made of three (3) individuals that share responsibilities described below by the "Chapter Board Responsibilities" section. A fourth chair-person of the board position will be established as well to facilitate overall chapter direction and chapter interaction with global OWASP governing bodies. This chair-person position will replace my current position and as such I will step down and stand for election myself.
| |
| − |
| |
| − | <del>I'm going to restrict board membership to verified [http://www.owasp.org/index.php/Membership OWASP Members] but otherwise </del> anyone and everyone should feel free to run. Procedures for candidacy and election are described by the "Election Procedures" section below. We plan to organize a campaign period in April and conduct the board election during our May chapter meeting. Board members make a special commitment to facilitate the chapter's logistics, while growing its membership and attendance.
| |
| − |
| |
| − | Beyond elected board members, everybody and anybody should feel free to participate in our Northern Virginia OWASP chapter in any capacity they seem beneficial. I encourage individuals to attend chapter meetings, network, explore and consume OWASP resources voraciously. Likewise, I encourage anyone to "take the reigns" and speak, organize, contribute, and direct our chapter as they see fit. As a open, transparent, and member-driven community, OWASP does not require individuals to attain any status or rank before contributing, as long as contributions meet our [http://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project code of ethics]. Indeed, OWASP strives to be a meritocracy. Our new board, once elected, will strive to provide an environment in which all members feel welcome, able, and supported in providing what contributions they can.
| |
| − |
| |
| − | So, please join me in participating in our up-and-coming campaign and election proceedings. With your help, I am confident that the Northern Virginia Chapter can take even greater strides towards helping this area's professionals better address our application security challenges,
| |
| − |
| |
| − | -jOHN<br>
| |
| − | | |
| − | Northern Virginia OWASP Chapter President,<br>
| |
| − | Phone: 703.727.4034<br>
| |
| − | Web: http://goo.gl/Y5d2y<br>
| |
| − |
| |
| − | === Chapter Board Responsibilities ===
| |
| − |
| |
| − | * '''Board Member''' Three (3) - OWASP NoVA Chapter Board Members will be verified OWASP members, in good standing, dedicated to direction and governance of the chapter. Responsibilities will include:
| |
| − |
| |
| − | * 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
| |
| − |
| |
| − | * '''Board Chairperson''' (1) - OWASP NoVA Chapter Board Chairperson will be a verified OWASP member, in good standing, dedicated to the direction and governance of the chapter. Responsibilities will include those of a board member. In addition, the chairperson will:
| |
| − |
| |
| − | * Defer to, facilitate, and support the activities and projects of the chapter board and its membership
| |
| − | * Represent chapter in OWASP forums, such as the global summit
| |
| − | * In conjunction with OWASP NoVA Board Members, set annual chapter mission
| |
| − |
| |
| − | Board members should be prepared to:
| |
| − |
| |
| − | * Devote approximately 4 hrs every two weeks to chapter business
| |
| − | * Stand for election every twenty-four (24) months
| |
| − | * Remain absolutely vendor neutral and
| |
| − | * Uphold the OWASP principals and code of ethics.
| |
| − |
| |
| − | === Election Procedures ===
| |
| − | '''Proof of Eligibility'''
| |
| − | <p>
| |
| − | Candidates wishing to stand for election, will verify their eligibility along with posting their intentions in the section below. Eligibility will be verified through the following means:</p>
| |
| − |
| |
| − | <OL>
| |
| − | <LI>List your name
| |
| − | <LI>List your OWASP member ID (available here: [http://spreadsheets.google.com/a/owasp.org/pub?key=p6IFyntQTi7sxa2Xjx191BA Individual Member Roster]). Individual membership not required for election, but strongly recommended in order to 'lead by example'. Those seeking membership can find more information [http://www.owasp.org/index.php/Membership here]</LI>
| |
| − | <LI>Indicate what city and town you live in (We'll only consider local members, but you may live in WV, VA, MD, or DC)</LI>
| |
| − | <LI>Endorsement from someone else in the chapter</LI>
| |
| − | </OL>
| |
| − |
| |
| − | '''Time table'''
| |
| − | <p>
| |
| − | <UL>
| |
| − | <LI>Candidates will announce their intentions at our next Chapter meeting, April 7, 2011 @ 6pm. Candidates unable to appear in person can announce their intentions through editing the wiki. If you'd like, I can read something on your behalf at the meeting.</LI>
| |
| − | <LI>Candidates will be asked to give a brief (5 minute) talk discussing their intentions for candidacy.Candidates will also announce the position for which they're running.</LI>
| |
| − | <LI>A vote will be conducted during our May chapter meeting</LI>
| |
| − | <LI>The deadline for candidacy will be the meeting's end, April 7th, 2011, @9pm.</LI>
| |
| − | </UL>
| |
| − | </p>
| |
| − |
| |
| − | '''Voting'''
| |
| − | <p>
| |
| − | The election procedure will be as follows:
| |
| − | <UL>
| |
| − | <LI>Votes will be cast at our May 4th, 2011 chapter meeting, promptly @ 6pm.</LI>
| |
| − | <LI>Chapter participants must be present in person to vote.</LI>
| |
| − | <LI>Absentee voting will be allowed in the case participants can not be present on the 4th, due to medical, travel, or other reasons. Absentee voters must contact both John Steven and Ben Tomhave with your intention to absentee vote no later than April 29th, 2011 @ 6pm.</LI>
| |
| − | <LI>Votes will be counted during the May 4th meeting, and an announcement made as to the winner at the meeting's end.</LI>
| |
| − | </UL>
| |
| − | </p>
| |
| − |
| |
| − | === Candidates ===
| |
| − |
| |
| − | '''John Steven'''
| |
| − | <p>
| |
| − | <UL>
| |
| − | <LI>OWASP Member ID: (68NSRT2PSVV)</LI>
| |
| − | <LI>Position: Board Chairperson</LI>
| |
| − | <LI>Sterling, VA</LI>
| |
| − | <LI>Endorsed by: Jeremy Long (68NRW3GS8RN)</LI>
| |
| − | <LI>Purpose: Grow chapter membership & participation with a keen focus on technical depth of presentations and material.</LI>
| |
| − | </UL>
| |
| − | </p>
| |
| − |
| |
| − | '''Jack Mannino'''
| |
| − | <p>
| |
| − | <UL>
| |
| − | <LI>OWASP Member ID: (67324580)</LI>
| |
| − | <LI>Position: Board Member</LI>
| |
| − | <LI>Northern VA</LI>
| |
| − | <LI>Endorsed by: John Steven (68NSRT2PSVV)</LI>
| |
| − | <LI>Purpose: Ensure that the chapter remains vendor-neutral, increase collaboration between chapter members, and promote new technical initiatives within our chapter. </LI>
| |
| − | </UL>
| |
| − | </p>
| |
| | ==== About ==== | | ==== 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. | + | [[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. | | 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. |
| Line 116: |
Line 7: |
| | 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. | | 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= The chapter leader is [mailto:[email protected] John Steven]. | + | {{Chapter Template|chaptername=Northern Virginia|extra =Come see us at a chapter meeting, jump on our Google Group, or email any of us directly. |
| − | | |
| − | === Program Committee ===
| |
| − | The OWASP NoVA Chapter Program Committee aims to:
| |
| − | | |
| − | Actively shepherd speakers and and speaking process within the NoVA chapter in order to assure that chapter meetings provide maximum practical benefit to our constituency.
| |
| | | | |
| − | Benefit the broader OWASP community by creating and supporting a 'preferred speaker' list through explicitly gauging, documenting, and sharing speaker quality data gained through feedback from chapter participants.
| + | === Chapter Board === |
| | + | Previously having had a Chapter Leader, then a Chapter "Program Committee", the chapter is now run by a full board: |
| | | | |
| − | In pursuit of this charter, we will elect as many as five program committee members that will, over the course of 2010:
| + | * Abdullah Munawar - Board Chair |
| | + | * Ben Pick |
| | | | |
| − | * Create easy-to-apply vetting criteria from existing OWASP chapter guidance and ethics rules.
| + | Board member responsibilities include: |
| − | * Assure one program committee personnel applies vetting criteria to each-and-every proposed chapter speaker/material
| |
| − | * Design, document, and implement a chapter participant "speaker survey" / voting mechanism
| |
| − | * Implement a "speaker survey" results display on the OWASP Wiki for the broader OWASP community to consume
| |
| − | * Coordinate with other chapters to set up a 'preferred speaker' list that aggregates data about high-scoring speakers (for the OWASP on-the-move project)
| |
| | | | |
| − | |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-wash_dc_va|emailarchives=http://lists.owasp.org/pipermail/owasp-wash_dc_va}} | + | <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. | | You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. |
| − | | + | === Schedule === |
| − | ==== Schedule ====
| |
| | | | |
| | Meetings are (generally) held the first Thursday of the month. | | Meetings are (generally) held the first Thursday of the month. |
| | | | |
| − | === Next Meeting ===
| + | 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. |
| − | | |
| − | '''Date/Time:''' April 7, 2011 @ 6pm
| |
| − | | |
| − | '''Location Sponsor:''' [http://www.reversespace.com/ ReverseSpace], 13505 Dulles Technology Dr, Suite 3, Herndon, VA 20171
| |
| − | | |
| − | '''AGENDA:'''
| |
| − | | |
| − | * News / Updates
| |
| − | * 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
| |
| − | * Preso:“XSS Remediation” by Cassia Martin
| |
| − | * Preso:"Growing the secure application developer community through expanded curricula" by Tony Gottlieb
| |
| − | * FireTalks (bring it!)
| |
| − | | |
| − | '''[http://www.regonline.com/owaspnova-april2011 PLEASE RSVP]'''
| |
| − | | |
| − | Please check back for updates, join the mailing list, or follow us on Twitter ([http://twitter.com/OWASPNoVA/ @OWASPNoVA]).
| |
| − | | |
| − | ----
| |
| − | | |
| − | === Upcoming Speakers ===
| |
| − | | |
| − | '''NEWS:''' We will be spending the next few months doing a deep-dive into the OWASP Top 10 list. You will learn from these sessions what the problem is, how it's exploited, and how to mitigate the weakness. We anticipate this being at least 5 months of sessions. We will also potentially supplement
| |
| − | | |
| − | If you want to present, please contact [mailto:John.Steven@owasp.org John] or [mailto:benjamin.tomhave@owasp.org Ben]. We're very open to hearing from all our members. | |
| − | | |
| − | [http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&ctz=America/New_York View the OWASP NoVA Chapter Calendar]<br>
| |
| − | | |
| − | <br>
| |
| − | | |
| − | ----
| |
| − | | |
| − | ==== Past meetings ====
| |
| − | | |
| − | === March 2011 ===
| |
| − | | |
| − | '''Date/Time:''' March 3, 2011 @ 6pm '''Location Sponsor:''' [http://www.boozallen.com/ Booz Allen Hamilton], 13200 Woodland Park Road, Herndon, VA 20171 '''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
| |
| − | | |
| − | <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].
| |
| − | | |
| − | <br>
| |
| − | | |
| − | === 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 ([[Image:State of Software Security-Ennis.ppsx.zip]])<br> '''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 [email protected] 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.
| |
| − | | |
| − | <br>
| |
| − | | |
| − | === 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'''
| + | == Next Meeting == |
| | | | |
| − | 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.
| + | We'll post all meetings on the Meetup page below. |
| | | | |
| − | 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.
| + | We can also be contacted through the comment or messages systems on Meetup. |
| | | | |
| − | 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."
| + | For latest news check the meetup page here: [http://www.meetup.com/OWASP-Northern-Virginia-Chapter/ Meetup]. |
| | | | |
| − | (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 )
| + | === History === |
| − | | |
| − | 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: [[http://www.epsteinmania.com/owasp/Moss-AppSecurityAndCMMI.pdf]]
| |
| − | | |
| − | ''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: [[https://www.owasp.org/images/5/52/About_OWASP_ASVS_Web_Edition.ppt]]
| |
| − | | |
| − | === 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]]
| |
| − | | |
| − | ''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]]
| |
| − | | |
| − | === 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]]
| |
| − | | |
| − | ''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] ]
| |
| − | | |
| − | === History ===
| |
| | | | |
| | The original DC Chapter was founded in June 2004 by [mailto: [email protected] 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. | | The original DC Chapter was founded in June 2004 by [mailto: [email protected] 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 ====
| + | __NOTOC__ |
| − | | |
| − | 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]
| |
| − | | |
| − | ==== 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:[email protected] 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:Virginia]] [[Category:Washington,_DC]] | + | [[Category:OWASP Chapter]] |
| | + | [[Category:United States]] |
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.
Welcome to the Northern Virginia chapter homepage. Come see us at a chapter meeting, jump on our Google Group, or email any of us directly.
Previously having had a Chapter Leader, then a Chapter "Program Committee", the chapter is now run by a full board:
For more information on how the board was elected and what it's responsibilities are, please see: Chapter Board Election
We'll post all meetings on the Meetup page below.
to this chapter or become a local chapter supporter.
Or consider the value of Individual, Corporate, or Academic Supporter membership. Ready to become a member? 
