|
|
| (143 intermediate revisions by 11 users not shown) |
| Line 1: |
Line 1: |
| − | ==== About ==== | + | ==== About ==== |
| − | [[Image:Owasp-nova.JPG|275px|right]]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. | + | [[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. | | 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}} |
| | | | |
| − | ===History=== | + | You may also want to follow [http://twitter.com/OWASPNoVA/ @OWASPNoVA] on Twitter. |
| − | 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. | + | === Schedule === |
| | | | |
| − | ==== Locations ====
| |
| − | '''If you plan to attend in person:'''
| |
| − |
| |
| − | Directions to Booz Allen's One Dulles facility:
| |
| − |
| |
| − | 13200 Woodland Park Road
| |
| − | Herndon, VA 20171
| |
| − |
| |
| − | From Tyson's Corner:
| |
| − |
| |
| − | * Take LEESBURG PIKE / VA-7 WEST
| |
| − | * Merge onto VA-267 WEST / DULLES TOLL ROAD (Portions Toll)
| |
| − | * Take the VA-657 Exit (Exit Number 10 towards Herndon / Chantilly)
| |
| − | * Take the ramp toward CHANTILLY
| |
| − | * Turn Left onto CENTERVILLE ROAD (at end of ramp)
| |
| − | * Turn Left onto WOODLAND PARK ROAD (less than 1⁄2 mile)
| |
| − | * End at 13200 WOODLAND PARK ROAD
| |
| − |
| |
| − | <br>'''If you plan to attend via Webinar:'''
| |
| − |
| |
| − | You can attend through [[OWASPNoVA WebEx]]
| |
| − |
| |
| − | ==== 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''': Thursday, June 3rd, 6pm Eastern Daylight Time<br> '''LOCATION''': Booz Allen Hamilton - 13200 Woodland Park Road Herndon, VA 20171<br> '''SPEAKER''': TBD<br> '''TOPIC''': TBD<br>
| |
| − | | |
| − | '''ABSTRACT''': TBD
| |
| − | | |
| − | '''INSTRUCTIONS''': RSVP through [mailto:[email protected]?Subject=OWASP%20RSVP Stan Wisseman] with “OWASP RSVP” in the subject. | |
| − | | |
| − | ----
| |
| − | | |
| − | ===== Upcoming Speakers =====
| |
| − | | |
| − | If you want to present, please contact [mailto:John.Steven@owasp.org John], [mailto:tomhave@secureconsulting.net Ben], or [mailto:wisseman_stan@bah.com Stan]. We're very open to hearing from all our members. | |
| − | | |
| − | Future speakers to include Gunnar Peterson and more.
| |
| − | | |
| − | [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>
| |
| − | | |
| − | | |
| − | ----
| |
| − | | |
| − | === Past meetings ===
| |
| − | '''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<br>
| |
| − | '''DESCRIPTION''':
| |
| − | <p>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.</p><BR>
| |
| − | | |
| − | '''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''':
| |
| − | <p> 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!</p> | |
| − | <p>
| |
| − | 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.</p><BR> | |
| − | | |
| − | '''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''':
| |
| − | <P>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.</p>
| |
| − | | |
| − | '''ABOUT THE SPEAKER''':
| |
| − | <p>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.</p><BR><BR>
| |
| − | | |
| − | == 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===
| |
| − | Questions related to this curriculum should be sent to [mailto:[email protected] John Steven], who is the Northern Virginia chapter leader. | |
| − | | |
| − | ===Registration===
| |
| − | Classroom’s size estimate for hands on: 30 stations max. Physical number of students can be larger as people may want to pair up. But we may have a hard limit of 40 students.
| |
| − | | |
| − | Registration for sessions will be on first come and first served basis. '''REGISTRATION IS OPEN!'''
| |
| − | | |
| − | Please send an email to [mailto:[email protected] John Steven] with your skill level with Statis Analysis tools, your motivation and '''the dates''' that you want to sign in for. | |
| − | Students are required to bring their own laptop. We ask to the students to bring their laptop in the hands on session, and to have software such as SSH pre-installed. Basic knowledge about code is also required in all sessions, except the last one.
| |
| − | | |
| − | ===Student’s prerequisites===
| |
| − | All students will need to bring their own laptop
| |
| − | | |
| − | 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>
| |
| − | PANEL: TBD<BR>
| |
| − | INSTRUCTIONS: RSVP through Stan Wisseman [email protected] with “OWASP RSVP” in the subject.<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.
| |
| − | | |
| − | * View the OWASP NoVA Chapter [http://www.google.com/calendar/hosted/owasp.org/embed?src=owasp.org_1ht5oegk8kd0dtat5cko71e7dc%40group.calendar.google.com&ctz=America/New_York Calendar ]
| |
| − | | |
| − | * The next meeting is '''Thursday, July 9th, 2009.'''
| |
| − | * Add July 9th to my [https://www.google.com/calendar/hosted/owasp.org/event?action=TEMPLATE&tmeid=azV2NGU4Zjc0M2w1a3NxMG4zam84cXZyMmcgb3dhc3Aub3JnXzFodDVvZWdrOGtkMGR0YXQ1Y2tvNzFlN2RjQGc&tmsrc=b3dhc3Aub3JnXzFodDVvZWdrOGtkMGR0YXQ1Y2tvNzFlN2RjQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20 Google Calendar], [https://cigital.webex.com/cigital/j.php?ED=124134682&UID=1012271922&ICS=MI&LD=1&RD=2&ST=1&SHA2=CWCN2pMk85HfkpUHyB/6CNfutu79JBWjL2LWsdybwEw= Exchange Calendar]
| |
| − | | |
| − | ==== 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
| |
| − | | |
| − | | |
| − | ==== Contributors and Sponsors ====
| |
| − | | |
| − | '''Chapter Leader'''
| |
| − | | |
| − | | |
| − | | |
| − | '''Refreshment Sponsors'''
| |
| | | | |
| − | [[Image:Cigital_OWASP.GIF]]
| + | == Next Meeting == |
| | | | |
| − | '''Facility Sponsors''' | + | We'll post all meetings on the Meetup page below. |
| | | | |
| − | [[Image:Bah-bw.JPG|215px]]
| + | 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]. |
| | | | |
| − | __NOTOC__
| + | === History === |
| − | <headertabs/>
| |
| − | <paypal>Northern Virginia</paypal>
| |
| | | | |
| − | ==Flash Talk Resources ==
| + | 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. |
| | | | |
| − | Chandu Ketkar on OFS. Download: [http://www.owasp.org/images/1/1c/OFS.pptx OFS Presentation.] <BR/>
| + | __NOTOC__ |
| − | [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/>
| |
| | | | |
| − | ==Knowledge==
| + | [[Category:OWASP Chapter]] |
| − | On the [[Knowledge]] page, you'll find links to this chapter's contributions organized by topic area.
| + | [[Category:United States]] |
| − |
| |
| − | [[Category:Virginia]] | |
| − | [[Category:Washington, DC]] | |
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? 
