OWASP Web Testing Environment Project

=Main= {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

OWASP WTE
OWASP WTE, or OWASP Web Testing Environment, is a collection of application security tools and documentation available in multiple formats such as VMs, Linux distribution packages, Cloud-based installations and ISO images.

Introduction
The OWASP WTE project is an enhancement of the original OWASP Live CD Project and expands the offering from a static Live CD ISO image to a collection of sub-projects. Its primary goal is to

"Make application security tools and documentation easily available and easy to use."

Description
At its heart, OWASP WTE is a collection of easy to use application security tools and documentation. WTE has a variety of ways to distribute them:
 * Virtual Machines for VMware, VirtualBox and Parallels
 * Invidividual Debian packages (.deb) which attempt to be Linux disto agnostic.
 * Tested against Ubuntu, Debian, Mint, Kali, etc.
 * A bootable ISO image
 * Hosted on various Cloud providers
 * Ala Carte mix-and-match installations for special purposes

The project is focused at providing a ready environment for testers, developers or trainers to learn, enhance, demonstrate or use their application security skills. It's been an active OWASP project since 2008 and has had over 300,000 downloads.

Beyond the collection of tools from OWASP and other security projects, OWASP WTE has begun producing and including its own security tools, especially where there were no existing tools which fit a particular need.

Licensing
OWASP WTE is free to use. Its licensing is dependant on several factors:
 * OWASP WTE created documenation is licensed under the Creative Commons Attribution-ShareAlike 3.0 license, so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.
 * OWASP WTE created software and tools are licensed under the GPLv3 or later license. You are free to use and modify this software as well as having the right to re-distribute this software as long as any changes you've made are contributed back to the project under the same license.  For questions, see the GPL FAQ
 * OWASP WTE packaged software and documentation is under the license of that project and/or software. The only licensing constraint required by OWASP WTE is that the software it makes packages of must be free to redistribute.

In short, you can use and share OWASP WTE as much as you want. The only time you may have an obligation is when you modify and redistribute OWASP WTE. If you are unsure, please ask the OWASP WTE Mail list


 * valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

What is WTE?
OWASP WTE provides:


 * Virtual Machines
 * VMware/Parallels .vmdk
 * VirtualBox .vdi
 * Open Virtualization Archive .ova
 * Linux Distribution packages
 * Debian .deb
 * RPM .rpm - coming soon
 * Cloud-based installations
 * ISO images

Presentation
OWASP WTE: Application Testing Your Way

Project Leader
Matt Tesauro

Related Projects

 * OWASP Live CD Project
 * OWASP ZAP

Ohloh

 * Coming Soon


 * valign="top" style="padding-left:25px;width:200px;" |

Quick Download

 * Downloads site

Email List
OWASP WTE Mail list

Code repository
Migration in progress Previous repository
 * GitHub
 * Google Code

News and Events

 * 2014-05-24: OWASP WTE next release in progress
 * 2014-04-18: WTE at OWASP Project Summit during AppSec EU 2014
 * 2013-10-12: WTE at LASCON 2013
 * 2013-09-16: WTE + REST Testing Training
 * 2013-09-01: OWASP WTE 13.09 released

Classifications

 * }

=FAQs=

Question: What is the login (aka username and password) for the VMs?

Answer:

The default username and password for the OWASP WTE VMs is owasp and owasp. Obviously, if you're going to run this for any period of time or in a situation more then a host-only VM, update the password for the owasp user to something long and random. Regrettably, I have to set something as a default and owasp/owasp seems like a sensible thing. The owasp user has sudo privileges if you need to do admin tasks, update software, etc.

Question: How to I update my OWASP WTE VM?

Answer

The OWASP WTE VMs ship with a OWASP WTE repository already configured. The same process you use to update the base OS (Xubuntu) will also update the OWASP WTE pacakges. Beyond the GUI tools, you can do the following in a terminal:

$ sudo apt-get update $ sudo apt-get upgrade

Question: What are the project's goals

Answer

The overarching goal for this project is to make application security tools and documentation easily available. I see this as a great complement to OWASP's goal to make application security visible.

The project has several other goals going forward:
 * 1) Provide a showcase for great OWASP tools and documentation
 * 2) Provide the best, freely distributable application security tools in an easy to use package
 * 3) Ensure that the tools provided are as easy to use as possible.
 * 4) Continue to add documentation and tools to the OWASP Live CD
 * 5) Continue to document how to use the tools and how the tool modules where created.
 * 6) Align the tools provided with the OWASP Testing Guide

There were also some design goals, particularly, this should be an environment which is
 * easy for the users to keep updated
 * easy for the project lead to keep updated
 * easy to produce releases
 * focused on just web application testing - not general Pen Testing.

(For general Pen Testing, the gold standard is Kali Linux.)

Original SoC Goals are still available for the curious.

= Acknowledgements =

Volunteers
OWASP WTE is developed by a worldwide team of volunteers. The primary contributors to date have been:


 * Kent Poots
 * Brad Causey
 * Drew Beebe
 * Nishi Kumar

Others

 * David Hughes
 * Simon Bennetts
 * Achim Hoffmann
 * Your name here!

Numerous others have provided feedback, suggestions, bugs and other assistance. If you've been missed, please email matt.tesauro [at] owasp [dot] org and let him know.

= Road Map and Getting Involved = As of May 2014, the priorities are:
 * Adding support for RPM packages
 * GPG signing all packages
 * More support for Cloud-based installations

Involvement in the development and promotion of OWASP WTE is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help:
 * Use WTE and submit bugs, suggestion, feedback
 * Suggest tools, docs or something else to add to the project
 * Blog/Tweet/shout about WTE
 * Make a video on using WTE and let the project know about it
 * Ping the OWASP WTE Mail list for more ideas or with a suggestion

=Project History=

The OWASP WTE project was originally started to update the previous OWASP Live CD 2007. The project met the September 15th, 2008 deadline for the OWASP Summer of Code (SoC) and produced its first release - the SoC release. Since the completion of the SoC, the project has made the following releases:


 * OWASP WTE Oct 2013
 * OWASP WTE Oct 2012
 * OWASP WTE Sept 2011
 * OWASP WTE Feb 2011
 * OWASP WTE Beta (January 2010)
 * the AppSec EU release (May, 2009)
 * the Portugal release (Dec 12, 2008)
 * the AustinTerrier release (Feb 10, 2009)

In addition to creating these releases of the OWASP Live CD/OWASP WTE, the maintainer has created a Linux package in Debian format (.deb) for each tool and the documentation included with OWASP WTE. This allows the WTE packages to be installed ala carte on Ubuntu, Debian, Mint, and other .deb based Linux distributions.

For historical purposes, the original application for the SoC is available here for the curious.

=Project About=