This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "Chicago"

From OWASP
Jump to: navigation, search
 
(161 intermediate revisions by 15 users not shown)
Line 1: Line 1:
== Welcome to the OWASP Chicago Local Chapter ==
+
{{Chapter Template|chaptername=Chicago|extra=The chapter leaders are [mailto:[email protected] Michael Allen] and [mailto:[email protected] Adam Lewis].
 +
|meetupurl=https://www.meetup.com/OWASP-Chicago-Chapter/|region=United States}}
  
Anyone in our area interested in information security is welcome to attend. Our meetings are informal and encourage open discussion of all aspects of application security. We invite attendees to give short presentations about specific topics.
+
Everyone is welcome to join us at our chapter meetings.
  
If you have any questions about the Chicago chapter, please send an email to our chapter leaders, [mailto:[email protected] Joe Bernik], [mailto:[email protected] Cory Scott], or [mailto:[email protected] Jason Witty.]
+
[[Category:OWASP Chapter]]
 
 
The Chicago chapter is sponsored by LaSalle Bank[http://www.LaSalleBank.com/]
 
 
 
== Next Meeting ==
 
  
The next Quarterly Chicago OWASP Chapter meeting will be held on September 5th, 2007 at 6PM CST.  
+
If you're interested in speaking, sponsoring or hosting an event, [mailto:[email protected] please contact us].
 +
<br/>
 +
= General Information =
  
We hope to see you at the ABN AMRO Plaza at 540 W. Madison, Downtown Chicago, 23rd floor.  Please RSVP to jason{AT}wittys.com by Monday 09/03/2007 if you plan to attend. Your name will need to be entered into the building's security system in order to gain access to the meeting.  
+
Anyone in our area interested in application security is welcome to attend. Our meetings are informal and encourage open discussion of all aspects of application security. We invite attendees to give short presentations about specific topics.
  
'''Agenda:'''
+
Follow (and/or DM us) on Twitter: [https://twitter.com/owaspchicago @owaspchicago]<br>
 +
LinkedIn: https://www.linkedin.com/groups/4049846<br/>
 +
Chat with us on SLACK.  https://owasp.slack.com/
 +
<br/>
 +
<br/>
  
6:00 Refreshments and Networking<BR>
+
Interesting in being a sponsor or presenting at an event?  Contact us at info@owasp-chicago.org
6:30 Andre Gironda - Automated Thrash Testing<BR>
 
7:15 Yet to be Named Presentation<BR>
 
  
'''Presentation Abstracts'''
 
  
'''Andre Gironda - Automated Thrash Testing'''<br/ >
 
Andre Gironda is a member of the OWASP Tools Project team.  He recently made contributions to the OWASP Top Ten 2007, and has spoken at local OWASP events on topics ranging from automated scanning tools to problems with trusting the same-origin policy.  After building the [http://www.owasp.org/index.php/Phoenix/Tools Phoenix Tools page] - a long list of mostly free tools sorted by classification - he intends to get the word out about both automated and manual tools/techniques that can really make a difference when testing web applications for security.
 
  
Automated Thrash Testing introduces some novel ways of accurately testing both server-side and client-side web applications according to simple standards with simple tools that can be used by both penetration testers and developers.  The [http://en.wikipedia.org/wiki/Thrash_%2528computer_science%2529 "thrash"] component means to test extensively and with completeness.  The problem for thrash testing completeness is to measure test coverage.  Test coverage of any web application should be accurately gauged by the amount of web surface area covered (pages, links, elements), as well as the actual code coverage itself.
+
__NOTOC__
 
+
<headertabs />
As of today, web applications on the client-side have not been sufficiently tested.  Protocol drivers, found in all generations of webapp scanners, aren't capable of testing client-side code - partly due to their reliance on [http://en.wikipedia.org/wiki/Domain-specific_programming_language domain-specific frameworks].  Application drivers had to be created to include all of the application functionality of a modern browser.  Some new tools have even been built into the browser itself.  This leads to another problem of using a different tool for every browser.  The most recent application drivers have been built to work with multiple browsers in a more standardized way, allowing for better automation in testing.
 
 
 
Automated Thrash Testing is meant to be a call to action for a web application vulnerability scanner standard.  Compare to similar work by Sutton, Greene, and Amini in [http://www.ddj.com/dept/security/200001745?_requestid=894432 Requirements for Effective Fuzzing].  It is planned to encompass the entirety of OWASP Top Ten 2007 and WASC TC v2, but the focus of the talk is on how the tools and methods should work - not which attack vectors they should include or how those specific attacks function.
 
 
 
== Presentation Archives ==
 
 
 
'''[http://wittys.com/owasp/OWASP_Chicago_Thomas_Ptacek.pdf]Webapps In Name Only'''
 
Thomas Ptacek, Matasano Security
 
 
 
Where modern network architecture meets legacy application design, we get "The Port 80 Problem": vendors wrapping every conceivable network protocol in a series of POSTs and calling them "safe". These "Webapps In Name Only" are a nightmare for application security specialists.
 
 
 
In this talk, we'll discuss, with case studies, how tools from protocol reverse engineering can be brought to bear on web application security, covering the following areas:
 
 
 
- Locating and Decompiling Java and .NET Code
 
- Structure and Interpretation of Binary Protocols in HTTP
 
- Protocol Debugging Tools
 
- Web App Crypto Tricks
 
 
 
'''[http://wittys.com/owasp/cscott-Stronger%20Web%20Authentication-v1.0.ppt]Token-less strong authentication for web applications: A Security Review'''
 
Cory Scott, ABN AMRO
 
 
 
A short presentation on the threat models and attack vectors for token-less schemes used to reduce the risk of password-only authentication, but yet do not implement "true" two-factor technologies for logistical costs or user acceptance reasons. We'll go over how device fingerprinting and IP geo-location work and discuss the pros and cons of the solutions.
 
[[Category:OWASP Chapter]]
 

Latest revision as of 09:33, 1 July 2019

OWASP Chicago

Welcome to the Chicago chapter homepage. The chapter leaders are Michael Allen and Adam Lewis.

Upcoming Events

Meetup_logo3.jpg Chicago Schedule of Events

Participation

OWASP Foundation (Overview Slides) is a professional association of global members and is open to anyone interested in learning more about software security. Local chapters are run independently and guided by the Chapter_Leader_Handbook. As a 501(c)(3) non-profit professional association your support and sponsorship of any meeting venue and/or refreshments is tax-deductible. Financial contributions should only be made online using the authorized online chapter donation button. To be a SPEAKER at ANY OWASP Chapter in the world simply review the speaker agreement and then contact the local chapter leader with details of what OWASP PROJECT, independent research or related software security topic you would like to present on.

Sponsorship/Membership

Btn donate SM.gif 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? Join Now BlueIcon.JPG

Everyone is welcome to join us at our chapter meetings.

If you're interested in speaking, sponsoring or hosting an event, please contact us.

General Information

Anyone in our area interested in application security is welcome to attend. Our meetings are informal and encourage open discussion of all aspects of application security. We invite attendees to give short presentations about specific topics.

Follow (and/or DM us) on Twitter: @owaspchicago
LinkedIn: https://www.linkedin.com/groups/4049846
Chat with us on SLACK. https://owasp.slack.com/

Interesting in being a sponsor or presenting at an event? Contact us at [email protected]