OWASP Zed Attack Proxy Project

= Main = The Zed Attack Proxy (ZAP) is an easy to use integrated penetration testing tool for finding vulnerabilities in web applications.

It is designed to be used by people with a wide range of security experience and as such is ideal for developers and functional testers who are new to penetration testing.

ZAP provides automated scanners as well as a set of tools that allow you to find security vulnerabilities manually.

''' News flash: Simon's slides from AppSec Ireland are now online. He will also be talking about ZAP at OWASP Manchester on 11th September '''

The current version of ZAP is 1.4.1.

ZAP is ideal for Security Regression Tests - see this video on Youtube

For more videos see the links on the wiki videos page.

Want a very quick introduction? See the project pamphlet.

For a slightly longer introduction see the project presentation.

For more details about ZAP, including the full user guide, see the wiki.

Zed Attack Proxy

= Screenshots =

= News = Latest News:


 * 2012/08/05 Version 1.4.1 released
 * 2012/07/08 Version 1.4.0.1 downloaded over 15,000 times
 * 2012/07/05 Python API released
 * 2012/06/15 ZAP accepted for the OWASP Project Reboot
 * 2012/06/13 Using ZAP for Security Regression tests video published
 * 2012/06/04 Version 1.4.0.1 downloaded over 10,000 times
 * 2012/05/28 Simon's Introduction to ZAP talk at App Sec USA becomes the most watched OWASP video on vimeo
 * 2012/04/23 3 ZAP related Google Summer of Code 2012 projects accepted. To find out how these are progressing please see their wiki pages.
 * 2012/04/23 OWASP ZAP SmartCard Project officially launched.
 * 2012/04/08 Version 1.4.0.1 released
 * 2012/02/10 Version 1.3.4 downloaded over 10,000 times
 * 2012/02/01 OWASP ZAP is named the Toolsmith Tool of the Year for 2011!

= Sponsors =

ZAP is developed by a worldwide team of volunteers.

But we have also been helped by many organizations, either either financially or by encouraging their employees to work on ZAP:

= Features = Some of ZAP's features:
 * OWASP
 * Mozilla
 * Sage
 * Google
 * Microsoft
 * Hacktics, Ernst & Young
 * Taddong
 * Denim Group
 * SecureIdeas
 * UtiliSec


 * Intercepting Proxy
 * Automated scanner
 * Passive scanner
 * Brute Force scanner
 * Spider
 * Fuzzer
 * Smartcard and Client Digital Certificates support
 * Port scanner
 * Dynamic SSL certificates
 * API
 * Beanshell integration

= Characteristics = Some of ZAP's characteristics:


 * Easy to install (just requires java 1.6)
 * Ease of use a priority
 * Comprehensive help pages
 * Fully internationalized
 * Under active development
 * Open source
 * Free (no paid for 'Pro' version)
 * Cross platform
 * Involvement actively encouraged

ZAP is a fork of the well regarded Paros Proxy.

= Languages =

ZAP supports the following languages:


 * English
 * Brazilian Portuguese
 * Chinese
 * Danish
 * French
 * German
 * Greek
 * Indonesian
 * Japanese
 * Persian
 * Polish
 * Spanish

Can you help improve these translations or add new ones? Please zaproxy-develop get in touch!

= Roadmap =

Release 2.0.0
The next release of ZAP will be a major release and include significant enhancements.

It will definitely include: And we are also hoping to include: Note that we dont have a release date for this yet, but the current 'finger in the air' plan is for sometime in autumn 2012.
 * A replacement for the 'standard' spider, c/o Google Summer of Code 2012
 * A new 'Ajax' spider, c/o Crawljax and Google Summer of Code 2012
 * Session awareness, c/o Google Summer of Code 2012
 * Web Socket support, c/o Google Summer of Code 2012
 * Session scope
 * Different modes (Safe, Protected and Standard)
 * A scripting console (with support for any language that conforms to JSR 223)
 * Enhancements and fixes logged on the issues page
 * An integrated extensions marketplace
 * Authentication handling
 * More API support
 * Fine grained scanning controls
 * Possibly even more enhancements, details TBA

Details of previous releases can be found here

= Get Involved =

Involvement in the development of ZAP is actively encouraged!

You do not have to be a security expert in order to contribute.

Some of the ways you can help:

Feature Requests
Please raise new feature requests as enhancement requests here: http://code.google.com/p/zaproxy/issues/list

If there are existing requests you are also interested in then please 'star' them - that way we can see which features people are most interested in and can prioritize them accordingly.

Feedback
Please use the zaproxy-develop Google Group for feedback:
 * What do like?
 * What don't you like?
 * What features could be made easier to use?
 * How could the help pages be improved?

Log issues
Have you had a problem using ZAP?

If so and its not already been logged then please report it

Localization
Are you fluent in another language? Can you help translate ZAP into that language?

If so then please get in touch.

Development
If you fancy having a go at adding functionality to ZAP then please get in touch via the zaproxy-develop Google Group.

Again, you do not have to be a security expert to contribute code - working on ZAP could be great way to learn more about web application security!

If you actively contribute to ZAP then you will be invited to join the project.

= Project About =