OWASP ASVS Assessment tool

Revision as of 09:05, 25 October 2014 by Johanna Curiel (talk | contribs)

Jump to: navigation, search
OWASP Project Header.jpg

OWASP ASVS Assessment Tool Project

OWASP ASVS Assessment Tool (OWAAT) helps in Web application verification conforming to the OWASP Application Security Verification Standard (ASVS) project.


OWASP ASVS Assessment Tool (OWAAT) designed to help in verifying the security of application with OWASP ASVS. An Initial Version of The OWAAT, Version 1.0, has been developed at Amirkabir University of Technology's Computer Emergency Response Team (APA). It coded in PHP and JavaScript and based on jQuery library.

  • Important features of the tool are as follow:
  • User management: It provides user management.
  • Verification methodology: It allows to modify verification method for each rule.
  • Assessment: It can be used when assessing the security of application with OWASP ASVS.
  • Task Assignment: It allows to assign assessment tasks to each user.
  • Reporting: It enables the creation of reports from assessment results.


OWAAT project is free to use. It is licensed under the GNU Affero General Public License version 3.0 (AGPLv3).

What is OWAAT

OWAAT is a Web-Based Assessment tool that helps in Web application verification conforming to the OWASP Application Security Verification Standard (ASVS) project.


Project Leader

Mahmoud Ghorbanzadeh (mailto: mdgh@aut.ac.ir)

Related Projects


Quick Download


News and Events


New projects.png Owasp-builders-small.png
Project Type Files CODE.jpg

Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. The point of a document like this are the answers. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'

How can I participate in your project?

All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

If I am not a programmer can I participate in your project?

Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.


The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project. Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project. Be sure to provide a link to a complete list of all the amazing people in your project's community as well.

The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project contributors is found here.

The first contributors to the project were:

A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership.

Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active.

As of October 2013, the priorities are:

  • Finish the referencing for each principle.
  • Update the Project Template.
  • Use the OWASP Press to develop a book.
  • Finish and publish the book on Lulu.

Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help:

  • Helping find references to some of the principles.
  • Project administration support.
  • Wiki editing support.
  • Writing support for the book.

This page is where you need to place your legacy project template page if your project was created before October 2013. To edit this page you will need to edit your project information template. You can typically find this page by following this address and substituting your project name where it says "OWASP_Example_Project". When in doubt, ask the OWASP Projects Manager. Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project

What does this OWASP project offer you?
What releases are available for this project?
what is this project?
Name: N/A
Purpose: N/A
License: N/A
who is working on this project?
Project Leader(s): N/A
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: N/A
Project Roadmap: Not Yet Created
Key Contacts
  • Contact the GPC to contribute to this project
  • Contact the GPC to review or sponsor this project
current release
last reviewed release

other releases