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

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

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?

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]

@@ 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 take place on March 5th, 2008 at 6pm CDT.
-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
-/3/2008 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.
-===Agenda===
-:00 Refreshments and Networking<br>
+If you're interested in speaking, sponsoring or hosting an event, [mailto:[email protected] please contact us].
-:30 '''Integrating Security Into the QA Group''' - Taylor McKinley, Product Manager at Fortify Software<br>
+<br/>
-:10 '''Web app penetration testing with scripting languages''' - Mike Tracy, Security Consultant at Matasano Security
+= General Information =
-===Presentation abstracts===
+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.
-'''Integrating Security Into the QA Group'''
+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/>
-Until recently, Web Application Testing was left to security teams and ethical hackers who used advanced tools, such as Web application scanners, to analyze running Web applications. However, security groups are becoming overburdened by product releases, and many organizations are attempting to move security testing earlier in the development cycle. The QA group is a natural candidate, since it generally has the infrastructure in place to test applications for quality issues. However, for many organizations, integrating security into the QA group has been incredibly difficult. The process of running a security test is a learned skill, and not something one can teach a QA tester in a matter of days. On top of that, most security testing tools were designed for penetration testers (since they require an in-depth knowledge of application security theory) and are not generally usable by QA professionals. As a result, very few QA groups have successfully adopted security testing.
+Interesting in being a sponsor or presenting at an event?   Contact us at info@owasp-chicago.org
-This talk will focus on a new technique for allowing QA teams to participate in the security process without any additional work or expertise.
-'''Web app penetration testing with scripting languages'''
-We show how, with minimal scripting knowledge, using tools we're
+__NOTOC__
-developing in-house and releasing to the public, the
+<headertabs />
-browser/proxy/tool mechanisms we use to test web apps today can be
-enhanced. With a little scripting, your test tools can be customized
-to any project, handle Ajax sites, JSON documents, XML, and more.
-We introduce PenTestConsole, a set of Ruby classes wrapped around an HTML parser
-(Hpricot), an XML parser (REXML), a deep spider, a fuzzer and classes
-that provide http functionality that would normally be used in a
-vulnerability assessment tool (forms, parameters, header manipulation,
-character encoding etc.).  We started out by looking at URL transfer
-libraries (Curb Ruby bindings for libcurl and Ruby net/http), parsers
-(Hpricot) and fully blown scraping tools (like Mechanize) and decided to
-create something new.  We wanted a tool could range from fine-grained
-manipulation of user inputs to hit it with a hammer random acts of
-senseless garbage.  We also wanted to be able to do combinatoric input
-reduction (pairwise for example) and header manipulation and tie it
-right into the tool.
-We discuss how we leverage minimal programming effort to gain maximal
-improvement in testing, so that we're no longer held hostage by web app
-pen testing tools (no matter how good they are), and so that we can automate
-and accelerate tests.
-== Presentation Archives ==
-Automated Thrash Testing - Andre Gironda - Presentation slides [http://www.owasp.org/images/3/32/Auto-thrash-testing.pdf here]<BR>
-Defeating Information Leak Prevention - Eric Monti - Presentation slides [https://www.owasp.org/images/4/4a/OWASP-CHI07-Defeating_Extrusion_Detection.pdf here]<BR>
-'''[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]]

Difference between revisions of "Chicago"

Latest revision as of 09:33, 1 July 2019

OWASP Chicago

Upcoming Events

Participation

Sponsorship/Membership

General Information

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

Navigation

Reference

Tools