This project is helpful as basic reference material when performing such activities as threat modeling, security architecture review, security testing, code review, and metrics. We intend to... More > encourage understanding and consistency when discussing these basic foundational elements of application security. Security only works if people can make informed decisions about risk. The ASDR provides that basic information to help ensure all stakeholders are involved.
For more information please check the OWASP Foundation's website - OWASP Application Security Desk Reference (ASDR) Project.< Less
This project aims to improve and to collect the existent information about the backend security. The project is composed by three sections (security development, security hardening and security... More > testing). The aim is to define the guidelines for the companies and IT professionals working in the security field into processes development and back-end components management/testing in the enterprise architecture.
For more information, please check out the project home page at OWASP Backend Security Project.< Less
The last security guide for Rails was a great success, with a lot of more secure web applications and continued awareness in the community of security issues. The Ruby on Rails Security Project is... More > the one and only source of information about Rails security topics, and I keep the community up-to-date with blog posts and conference talks in Europe. The Guide and the Project has been mentioned in several Rails books and web-sites.
A lot has changed since the publishing of the first Guide. Some new security holes have been found, there are new advises and most importantly Rails version 2.0 has been released. The new Ruby on Rails Security Guide aims at providing an up-to-date coding and configuration guide for the Rails community.
For more information, please check out the project home page at OWASP Ruby on Rails Security Guide V2.< Less
The AppSensor document is a conceptual framework that offers prescriptive guidance to implement intrusion detection capabilities into existing application utilizing standard security controls and... More > recommendations for automated response policies based upon detected behaviour. When using AppSensor, an application will be able to identify malicious users within the application and eliminate the threat by taking response action such as logging out the user, locking the account or notifying an administrator.
An attacker often requires numerous probes and attack attempts in order to locate an exploitable vulnerability within the application. By using AppSensor it is possible to identify and eliminate the threat of an attacker before they are able to successfully identify an exploitable flaw.
For more information, please check out the project home page at OWASP AppSensor Project.< Less
The purpose of this project is to create custom Modsecurity rulesets that, in addition to the Core Set, will protect WebGoat 5.1 from as many of its vulnerabilities as possible (the goal is 90%)... More > without changing one line of source code. To ensure that it will be a complete 'no touch' on WebGoat and its environment, ModSecurity will be configured on Apache server as a remote proxy server. For those vulnerabilities that cannot be prevented (partially or not at all), I will document my efforts in attempting to protect them. Business logic vulnerabilities will be particularly challenging to solve.
For more information, please check out the project home page at OWASP Securing WebGoat using ModSecurity Project.< Less
The goal of the Top 10 project is to raise awareness about application security by identifying some of the most critical
risks facing organizations. The Top 10 project is referenced by many... More > standards, books, tools, and organizations, including MITRE, PCI DSS, DISA, FTC, and many more. This release of the OWASP Top 10 marks this project’s eighth year of raising awareness of the importance of application security risks. The OWASP Top 10 was first released in 2003, minor updates were made in 2004 and 2007, and this is the 2010 release.< Less
The primary aim of the OWASP Application Security Verification Standard (ASVS) Project is to normalize the range in the coverage and level of rigor available in the market when it comes to performing... More > application security verification using a commercially-workable open standard. This standard can be used to establish a level of confidence in the security of web applications and web services.
For more information, please check out the project home page at OWASP Application Security Verification Standard (ASVS) Project.< Less
The Code Review Guide is currently at release version 1.1 and the second best selling OWASP book in 2008. Many positive comments have been feedback regarding this initial version and believe... More > it’s a key enabler for the OWASP fight against software insecurity. It has even inspired individuals to build tools based on its information. The combination of a book on secure code review and tools to support such an activity is very powerful as it gives the developer community a place to start regarding secure application development.
Going forward I hope to further integrate with the ASVS and other guides such as the testing and ASDR guides shall be perfromed for version 2.0.
For more information, please check out the project home page at OWASP Code Review Guide V1.1.< Less