This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Category:OWASP Project"
From OWASP
| Line 11: | Line 11: | ||
A list of '''Projects''' that have been identified as '''orphaned''' ones has been set up. Please [[:Category:OWASP Orphaned Projects|glance at it]] and see you find interest in leading any of them. <br><br> | A list of '''Projects''' that have been identified as '''orphaned''' ones has been set up. Please [[:Category:OWASP Orphaned Projects|glance at it]] and see you find interest in leading any of them. <br><br> | ||
| − | <paypal>OWASP Projects</paypal> | + | <paypal>OWASP Projects</paypal> |
==== Release Quality Projects ==== | ==== Release Quality Projects ==== | ||
| Line 20: | Line 20: | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
| − | ! width="50%" | Tools | + | ! width="50%" | Tools |
! Documentation | ! Documentation | ||
|- valign="top" | |- valign="top" | ||
| Line 68: | Line 68: | ||
:this Project is the one and only source of information about Rails security topics. (Assessment Criteria v1.0) | :this Project is the one and only source of information about Rails security topics. (Assessment Criteria v1.0) | ||
| − | ;[[OWASP Secure Coding Practices - Quick Reference Guide|OWASP Secure Coding Practices - Quick Reference Guide]] | + | ;[[OWASP Secure Coding Practices - Quick Reference Guide|OWASP Secure Coding Practices - Quick Reference Guide]] |
:this document provides a quick high level reference for secure coding practices. It is technology agnostic and defines a set of general software security coding practices, in a checklist format, that can be integrated into the development lifecycle. (Assessment Criteria v2.0) | :this document provides a quick high level reference for secure coding practices. It is technology agnostic and defines a set of general software security coding practices, in a checklist format, that can be integrated into the development lifecycle. (Assessment Criteria v2.0) | ||
| Line 107: | Line 107: | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
| − | ! width="50%" | Tools | + | ! width="50%" | Tools |
! Documentation | ! Documentation | ||
|- valign="top" | |- valign="top" | ||
| Line 192: | Line 192: | ||
;[[:Category:OWASP Tools Project|OWASP Tools Project]] | ;[[:Category:OWASP Tools Project|OWASP Tools Project]] | ||
| − | :The OWASP Tools Project has been created to provide unbiased, practical information and guidance about application security tools that are used to detect vulnerabilities or to protect against vulnerabilities. The goal of this project is to identify any available tools, categorise them and rate them according to a predefind criteria to assess their effectiveness. | + | :The OWASP Tools Project has been created to provide unbiased, practical information and guidance about application security tools that are used to detect vulnerabilities or to protect against vulnerabilities. The goal of this project is to identify any available tools, categorise them and rate them according to a predefind criteria to assess their effectiveness. |
<br> '''LIFE CYCLE:<br><br>''' | <br> '''LIFE CYCLE:<br><br>''' | ||
| Line 219: | Line 219: | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
| − | ! width="50%" | Tools | + | ! width="50%" | Tools |
! Documentation | ! Documentation | ||
|- valign="top" | |- valign="top" | ||
| | | | ||
| − | ;[[:OWASP Alchemist Project|OWASP Alchemist Project]] | + | ;[[:OWASP Alchemist Project|OWASP Alchemist Project]] |
| − | : this project enables a software development team in realization of highly secure and defensible application with built-in defences/controls against security‐related design, coding and implementation flaws. (Assessment Criteria v2.0) | + | :this project enables a software development team in realization of highly secure and defensible application with built-in defences/controls against security‐related design, coding and implementation flaws. (Assessment Criteria v2.0) |
;[[:Category:OWASP Application Security Tool Benchmarking Environment and Site Generator Refresh Project|OWASP Application Security Tool Benchmarking Environment and Site Generator Refresh Project]] | ;[[:Category:OWASP Application Security Tool Benchmarking Environment and Site Generator Refresh Project|OWASP Application Security Tool Benchmarking Environment and Site Generator Refresh Project]] | ||
:The idea is to split destination web application technology from the three reusable libraries: library of navigational elements, library of vulnerabilities and library of language constructs. (Assessment Criteria v1.0) | :The idea is to split destination web application technology from the three reusable libraries: library of navigational elements, library of vulnerabilities and library of language constructs. (Assessment Criteria v1.0) | ||
| − | ;[[:OWASP Broken Web Applications Project|OWASP Broken Web Applications Project]] | + | ;[[:OWASP Broken Web Applications Project|OWASP Broken Web Applications Project]] |
:a collection of vulnerable web applications that is distributed on a Virtual Machine. (Assessment Criteria v2.0) | :a collection of vulnerable web applications that is distributed on a Virtual Machine. (Assessment Criteria v2.0) | ||
| Line 253: | Line 253: | ||
:This tool is an encoder, decoder, converter, transformer, calculator, for various codings used in the wild wide web. (Assessment Criteria v1.0) | :This tool is an encoder, decoder, converter, transformer, calculator, for various codings used in the wild wide web. (Assessment Criteria v1.0) | ||
| − | ;[[ESAPI Swingset|OWASP ESAPI Swingset Project]] | + | ;[[ESAPI Swingset|OWASP ESAPI Swingset Project]] |
| − | :the ESAPI Swingset is a web application which demonstrates common security vulnerabilities and asks users to secure the application against these vulnerabilities using the ESAPI library. (Assessment Criteria v2.0) | + | :the ESAPI Swingset is a web application which demonstrates common security vulnerabilities and asks users to secure the application against these vulnerabilities using the ESAPI library. (Assessment Criteria v2.0) |
| − | ;[[:Category:OWASP Favicon Database Project|OWASP Favicon Database Project]] | + | ;[[:Category:OWASP Favicon Database Project|OWASP Favicon Database Project]] |
:software enumeration via favicon.ico (Assessment Criteria v2.0) | :software enumeration via favicon.ico (Assessment Criteria v2.0) | ||
| − | ;[[:OWASP HTTP Post Tool|OWASP HTTP Post Tool]] | + | ;[[:OWASP HTTP Post Tool|OWASP HTTP Post Tool]] |
| − | :Assessment Criteria v2.0) | + | :a tool for the purpose of performing web application security assessment around the availability concerns Assessment Criteria v2.0) |
;[[:Category:OWASP Insecure Web App Project|OWASP Insecure Web App Project]] | ;[[:Category:OWASP Insecure Web App Project|OWASP Insecure Web App Project]] | ||
| Line 283: | Line 283: | ||
:is secure by default centralised input/output validation library which combines security rules and business rules as well as escaping in the output level. (Assessment Criteria v1.0) | :is secure by default centralised input/output validation library which combines security rules and business rules as well as escaping in the output level. (Assessment Criteria v1.0) | ||
| − | ;[[:OWASP O2 Platform|OWASP O2 Platform]] | + | ;[[:OWASP O2 Platform|OWASP O2 Platform]] |
| − | :this project is a collection of Open Source modules that help Web Application Security Professionals to maximize their efforts and quickly obtain high visibility into an application's security profile (Assessment Criteria v2.0) | + | :this project is a collection of Open Source modules that help Web Application Security Professionals to maximize their efforts and quickly obtain high visibility into an application's security profile (Assessment Criteria v2.0) |
;[[:Category:OWASP Open Review Project|OWASP Open Review Project (ORPRO)]] | ;[[:Category:OWASP Open Review Project|OWASP Open Review Project (ORPRO)]] | ||
| Line 326: | Line 326: | ||
;[[:OWASP Zed Attack Proxy Project|OWASP Zed Attack Proxy Project]] | ;[[:OWASP Zed Attack Proxy Project|OWASP Zed Attack Proxy Project]] | ||
| − | :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 a new to penetration testing. ZAP provides automated scanners as well as a set of tools that allow you to find security vulnerabilities manually. | + | :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 a new to penetration testing. ZAP provides automated scanners as well as a set of tools that allow you to find security vulnerabilities manually. (Assessment Criteria v1.0) |
| | | | ||
| Line 335: | Line 335: | ||
:identify and provide a set of application security metrics that have been found by contributors to be effective in measuring application security (Assessment Criteria v2.0) | :identify and provide a set of application security metrics that have been found by contributors to be effective in measuring application security (Assessment Criteria v2.0) | ||
| − | ;[[:OWASP Application Security Program for Manager|OWASP Application Security Program for Manager]] | + | ;[[:OWASP Application Security Program for Manager|OWASP Application Security Program for Manager]] |
| − | :create an OWASP Roadmap for the world wide Companies Type. (Assessment Criteria v2.0) | + | :create an OWASP Roadmap for the world wide Companies Type. (Assessment Criteria v2.0) |
| − | ;[[:OWASP Application Security Skills Assessment |OWASP Application Security Skills Assessment]] | + | ;[[:OWASP Application Security Skills Assessment|OWASP Application Security Skills Assessment]] |
:Help individuals understand their strengths and weaknesses in specific application security skills. (Assessment Criteria v2.0) | :Help individuals understand their strengths and weaknesses in specific application security skills. (Assessment Criteria v2.0) | ||
| Line 356: | Line 356: | ||
;[[:Category:OWASP Book Cover & Sleeve Design|OWASP Book Cover & Sleeve Design]] | ;[[:Category:OWASP Book Cover & Sleeve Design|OWASP Book Cover & Sleeve Design]] | ||
| − | :this is a project of corporate design to develop a scalable book cover series strategy and a Book Sleeve. (Assessment Criteria v1.0) | + | :this is a project of corporate design to develop a scalable book cover series strategy and a Book Sleeve. (Assessment Criteria v1.0) |
;[[:OWASP Browser Security Project|OWASP Browser Security Project]] | ;[[:OWASP Browser Security Project|OWASP Browser Security Project]] | ||
| − | : To be definied (Assessment Criteria v2.0) | + | :To be definied (Assessment Criteria v2.0) |
;[[:Category:OWASP Boot Camp Project|OWASP Boot Camp Project]] | ;[[:Category:OWASP Boot Camp Project|OWASP Boot Camp Project]] | ||
| Line 380: | Line 380: | ||
:(Assessment Criteria v2.0) | :(Assessment Criteria v2.0) | ||
| − | ;[[:Category:OWASP CBT Project|Computer Based Training Project (OWASP CBT Project)]] | + | ;[[:Category:OWASP CBT Project|Computer Based Training Project (OWASP CBT Project)]] |
:the goal of this project is to provide computer based training on OWASP security related initiatives. (Assessment Criteria v2.0) | :the goal of this project is to provide computer based training on OWASP security related initiatives. (Assessment Criteria v2.0) | ||
| Line 390: | Line 390: | ||
:The goal of the project is to maintain a list of top 10 security risks faced with the Cloud Computing and SaaS Models. (Assessment Criteria v2.0) | :The goal of the project is to maintain a list of top 10 security risks faced with the Cloud Computing and SaaS Models. (Assessment Criteria v2.0) | ||
| − | ;[[:OWASP Enterprise Application Security Project|OWASP Enterprise Application Security Project]] | + | ;[[:OWASP Enterprise Application Security Project|OWASP Enterprise Application Security Project]] |
| − | : provides guidance to people involved in the procurement, design, implementation or sign-off of large scale (ie 'Enterprise') applications. (Assessment Criteria v2.0) | + | :provides guidance to people involved in the procurement, design, implementation or sign-off of large scale (ie 'Enterprise') applications. (Assessment Criteria v2.0) |
;[[:OWASP Fiddler Addons for Security Testing Project|OWASP Fiddler Addons for Security Testing Project]] | ;[[:OWASP Fiddler Addons for Security Testing Project|OWASP Fiddler Addons for Security Testing Project]] | ||
| Line 402: | Line 402: | ||
:a project to collect, share and compose statements used as code injections like SQL, SSI, XSS, Formatstring and as well directory traversal statements. (Assessment Criteria v1.0) | :a project to collect, share and compose statements used as code injections like SQL, SSI, XSS, Formatstring and as well directory traversal statements. (Assessment Criteria v1.0) | ||
| − | ;[[:OWASP Hungarian Translation Project|OWASP Hungarian Translation Project]] | + | ;[[:OWASP Hungarian Translation Project|OWASP Hungarian Translation Project]] |
:we plan to translate OWASP material that we consider fundamental (ASVS, Bulding Guide, Testing Guide, Top 10) first, and move on later. (Assessment Criteria v2.0) | :we plan to translate OWASP material that we consider fundamental (ASVS, Bulding Guide, Testing Guide, Top 10) first, and move on later. (Assessment Criteria v2.0) | ||
| Line 429: | Line 429: | ||
:a project to learn how companies are working to create a positive security approach on their own resources and use this knowledge to create a set of control, marketing and awareness tools that will be available to promote and construct a positive approach to security worldwide (Assessment Criteria v1.0) | :a project to learn how companies are working to create a positive security approach on their own resources and use this knowledge to create a set of control, marketing and awareness tools that will be available to promote and construct a positive approach to security worldwide (Assessment Criteria v1.0) | ||
| − | ;[[OWASP RFP-Criteria|OWASP Request for Proposal]] | + | ;[[OWASP RFP-Criteria|OWASP Request for Proposal]] |
:a project that is intended to provide a list of questions to consider when seeking a dynamic application security service provider. (Assessment Criteria v2.0) | :a project that is intended to provide a list of questions to consider when seeking a dynamic application security service provider. (Assessment Criteria v2.0) | ||
| Line 435: | Line 435: | ||
:a project that is intended to be the first step towards integrating security requirements in academic course curriculum (Assessment Criteria v1.0) | :a project that is intended to be the first step towards integrating security requirements in academic course curriculum (Assessment Criteria v1.0) | ||
| − | ;[[:OWASP Secure Web Application Framework Manifesto]] | + | ;[[:OWASP Secure Web Application Framework Manifesto]] |
:this project is a document detailing a specific set of security requirements for developers of web application frameworks to adhere to. (Assessment Criteria v2.0) | :this project is a document detailing a specific set of security requirements for developers of web application frameworks to adhere to. (Assessment Criteria v2.0) | ||
| Line 441: | Line 441: | ||
:a to be a design-time security reference for developers implementing common patterns independent of specific platforms and frameworks (Assessment Criteria v2.0) | :a to be a design-time security reference for developers implementing common patterns independent of specific platforms and frameworks (Assessment Criteria v2.0) | ||
| − | ;[[:Category:OWASP Security Assurance Testing of Virtual Worlds Project|OWASP Security Assurance Testing of Virtual Worlds Project]] | + | ;[[:Category:OWASP Security Assurance Testing of Virtual Worlds Project|OWASP Security Assurance Testing of Virtual Worlds Project]] |
| − | : a testing framework specific to Virtual World related applications (MMORGs) and environments (Assessment Criteria v2.0) | + | :a testing framework specific to Virtual World related applications (MMORGs) and environments (Assessment Criteria v2.0) |
;[[:Category:OWASP Security Spending Benchmarks|OWASP Security Spending Benchmarks]] | ;[[:Category:OWASP Security Spending Benchmarks|OWASP Security Spending Benchmarks]] | ||
| Line 450: | Line 450: | ||
:this project is committed to building a usable framework to help organizations formulate and implement a strategy for application security that's tailored to the specific business risks facing the organization. | :this project is committed to building a usable framework to help organizations formulate and implement a strategy for application security that's tailored to the specific business risks facing the organization. | ||
| − | ;[[OWASP Uniform Reporting Guidelines|OWASP Uniform Reporting Guidelines]] | + | ;[[OWASP Uniform Reporting Guidelines|OWASP Uniform Reporting Guidelines]] |
:this project will complement the OWASP testing guide as well as the OWASP RFP Template. This is going to be a reporting template for vulnerability findings which will be free, base on industry best practices and hopefully will become the defacto standard. (Assessment Criteria v2.0) | :this project will complement the OWASP testing guide as well as the OWASP RFP Template. This is going to be a reporting template for vulnerability findings which will be free, base on industry best practices and hopefully will become the defacto standard. (Assessment Criteria v2.0) | ||
| Line 468: | Line 468: | ||
:a project to define evaluation criteria for XML Security Gateways (Assessment Criteria v1.0) | :a project to define evaluation criteria for XML Security Gateways (Assessment Criteria v1.0) | ||
| − | ;[[Security Ecosystem Project|OWASP Security Ecosystem Project]] | + | ;[[Security Ecosystem Project|OWASP Security Ecosystem Project]] |
| − | : nobody (and no company) can build secure software by themselves. We have seen that vulnerability research can help to drive security forward in companies, but it’s a painful process. We envision a partnership between technology platform vendors and a thriving ecosystem focused on the security of their technology. (Assessment Criteria v2.0) | + | :nobody (and no company) can build secure software by themselves. We have seen that vulnerability research can help to drive security forward in companies, but it’s a painful process. We envision a partnership between technology platform vendors and a thriving ecosystem focused on the security of their technology. (Assessment Criteria v2.0) |
;[[:Category:OWASP Speakers Project|OWASP Speakers Project]] | ;[[:Category:OWASP Speakers Project|OWASP Speakers Project]] | ||
| Line 483: | Line 483: | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
| − | ! width="50%" | Tools | + | ! width="50%" | Tools |
! Documentation | ! Documentation | ||
|- valign="top" | |- valign="top" | ||
| Line 490: | Line 490: | ||
:a JavaScript based web application security testing suite | :a JavaScript based web application security testing suite | ||
| − | ;[[:Category:OWASP CSRFGuard Project|OWASP CSRFGuard Project]] | + | ;[[:Category:OWASP CSRFGuard Project|OWASP CSRFGuard Project]] |
| − | :this is a "reference implementation". Developers are encouraged to leverage more tightly integrated solutions for performance (ex: speed of parsing HTML) and technical (ex: AJAX requests) challenges. | + | :this is a "reference implementation". Developers are encouraged to leverage more tightly integrated solutions for performance (ex: speed of parsing HTML) and technical (ex: AJAX requests) challenges. |
;[[:Category:OWASP Google Hacking Project|OWASP Google Hacking Project]] | ;[[:Category:OWASP Google Hacking Project|OWASP Google Hacking Project]] | ||
| − | :Google SOAP Search API with Perl | + | :Google SOAP Search API with Perl |
;[[:Category:OWASP Interceptor Project|OWASP Interceptor Project]] | ;[[:Category:OWASP Interceptor Project|OWASP Interceptor Project]] | ||
| Line 500: | Line 500: | ||
| | | | ||
| − | |||
;[[:OWASP Corporate Application Security Rating Guide|OWASP Corporate Application Security Rating Guide]] | ;[[:OWASP Corporate Application Security Rating Guide|OWASP Corporate Application Security Rating Guide]] | ||
:This project will organize and structure publicly available data that large companies will share of the lessons learned about how to organize an application security initiative, best practices for training and testing, and more. | :This project will organize and structure publicly available data that large companies will share of the lessons learned about how to organize an application security initiative, best practices for training and testing, and more. | ||
| Line 508: | Line 507: | ||
|} | |} | ||
| − | __NOTOC__ <headertabs /> | + | |
| + | __NOTOC__ <headertabs /> | ||
{{PutInCategory}} | {{PutInCategory}} | ||
Revision as of 17:24, 22 November 2010
An OWASP project is a collection of related tasks that have a defined roadmap and team members. OWASP project leaders are responsible for defining the vision, roadmap, and tasks for the project. The project leader also promotes the project and builds the team. Tools and documents are organized into the following categories:
- PROTECT - These are tools and documents that can be used to guard against security-related design and implementation flaws.
- DETECT - These are tools and documents that can be used to find security-related design and implementation flaws.
- LIFE CYCLE - These are tools and documents that can be used to add security-related activities into the Software Development Life Cycle (SDLC).
If you would like to start a new project please review the How to Start an OWASP Project guide. Please contact the Global Project Committee members to discuss project ideas and how they might fit into OWASP. All OWASP projects must be free and open and have their homepage on the OWASP portal. You can read all the guidelines in the Project Assessment Criteria.
Every project has an associated mail list. You can view all the lists, examine their archives, and subscribe to any of them on the OWASP Project Mailing Lists page.
A list of Projects that have been identified as orphaned ones has been set up. Please glance at it and see you find interest in leading any of them.
<paypal>OWASP Projects</paypal>
Release Quality Projects
- Release quality projects are generally the level of quality of professional tools or documents.
- Projects are listed below.
| Tools | Documentation |
|---|---|
|
PROTECT:
|
PROTECT:
|
Beta Status Projects
- Beta quality projects are complete and ready to use with documentation.
- Projects are listed below.
| Tools | Documentation |
|---|---|
|
PROTECT:
|
PROTECT:
|
Alpha Status Projects
- Alpha quality projects are generally usable but may lack documentation or quality review.
- Projects are listed below.
| Tools | Documentation |
|---|---|
|
(Assessment Criteria v1.0)
(Assessment Criteria v1.0)
|
Inactive Projects
- Inactive projects are unrated projects (projects that have not reached any one of Alpha, Beta, or Release status) which may have been abandoned. Efforts are being made to contact project leads to determine status and plans for future work.
- Projects are listed below.
| Tools | Documentation |
|---|---|
|
|
How to add a new OWASP Project article
You can follow the instructions to make a new OWASP Project article. Please use the appropriate structure and follow the Tutorial. Be sure to paste the following at the end of your article to make it show up in the OWASP Project category:
[[Category:OWASP Project]]
Subcategories
This category has the following 132 subcategories, out of 132 total.
A
B
C
D
E
F
G
H
I
J
L
M
N
O
P
R
S
T
V
W
X
Y
Pages in category "OWASP Project"
The following 200 pages are in this category, out of 419 total.
(previous page) (next page)A
B
C
- Classic ASP Security Project
- GPC Project Details/OWASP Cloud ‐ 10 Project
- GPC Project Details/OWASP Code Crawler
- Code review
- OWASP Codes of Conduct
- Collaborate
- OWASP Common Numbering Project
- GPC Project Details/OWASP CBT Project
- Cornucopia - Ecommerce Website Edition - Wiki Deck
- OWASP Corporate Application Security Rating Guide
- OWASP Cross-Site Request Forgery Research Pool
- OWASP CSRFGuard Project/es
- CSRFProtector Project
E
G
H
J
M
O
- O-Saft
- O-Saft/Documentation
- OWASP O2 Platform Project - Project Identification
- Octoms
- Opa
- Projects/Opa
- OWASP OVAL Content Project
- OWASP - Cyber Security in the Boardroom
- OWASP 1-Liner
- OWASP A&D Project
- OWASP Academy Portal Project
- OWASP AJAX Crawling Tool
- OWASP Amass Project
- OWASP Androick Project
- OWASP Anti-Ransomware Guide Project
- OWASP API Security Project
- OWASP APK DISSECTOR
- OWASP Application Fuzzing Framework Project
- OWASP Application Security Curriculum
- OWASP Application Security Guide For CISOs Project
- OWASP Application Security Guide For CISOs Project v2
- OWASP Application Security Program Quick Start Guide Project
- OWASP AppSec Designer Security Functional Requirements & Countermeasures Libraries
- OWASP AppSec Pipeline
- OWASP Appsec Tutorial Series
- OWASP AppSensor Handbook
- OWASP AppSensor Project
- OWASP ASP.NET MVC Boilerplate Project
- OWASP Assimilation Project
- OWASP ASVS Assessment tool
- OWASP Attack Surface Detector Project
- OWASP Auth
- OWASP Automated Threats to Web Applications
- OWASP Autosploit Project
- OWASP Barbarus
- OWASP Basic Expression & Lexicon Variation Algorithms (BELVA) Project
- OWASP Best Practices in Vulnerability Disclosure and Bug Bounty Programs
- OWASP Broken Web Applications Project
- OWASP Browser Security Project
- OWASP Bug Logging Tool
- OWASP Bywaf Project
- OWASP Cheat Sheet Series
- OWASP Chinese Project
- OWASP CISO Survey Project
- OWASP Click Me Project
- OWASP Cloud Security Mentor
- OWASP Cloud Security Project
- OWASP Cloud Testing Guide
- OWASP Cloud-Native Application Security Top 10
- OWASP Code Project Template
- OWASP Code Pulse Project
- OWASP Container Security Verification Standard (CSVS)
- OWASP Cornucopia
- OWASP Counter Project
- OWASP Crossword of the Month
- OWASP Crowdtesting
- OWASP Cyber Defense Matrix
- OWASP D4N155
- OWASP Damn Vulnerable Crypto Wallet
- OWASP Damn Vulnerable Web Sockets (DVWS)
- OWASP DeepViolet TLS/SSL Scanner
- OWASP DefectDojo Project
- OWASP Dependency Check
- OWASP Dependency Track Project
- OWASP Desktop Goat and Top 5 Project
- OWASP DevSecOps Maturity Model
- OWASP DevSlop Project
- OWASP Documentation Project Template
- OWASP Droid Fusion
- OWASP Droid10 Project
- OWASP DVSA
- OWASP Ecuador
- OWASP EJSF Project
- OWASP Embedded Application Security
- OWASP Encoder Comparison Reference Project
- OWASP Example Incubator
- OWASP Excess XSS Project
- OWASP Faux Bank Project
- OWASP File Hash Repository
- OWASP Financial Information Exchange Security Project
- OWASP Find Security Bugs
- OWASP Focus
- OWASP Framework Security Project
- OWASP Game Security Framework Project
- OWASP Global Chapter Meetings Project
- OWASP Glue Tool Project
- OWASP Go Secure Coding Practices Guide
- OWASP Good Component Practices Project
- OWASP Google Assistant
- OWASP Guide Project
- OWASP H2H Tool Project
- OWASP HA Vulnerability Scanner Project
- OWASP Hackademic Challenges Project
- OWASP Hacking Lab
- OWASP Hacking-the Pentest Tutor Game
- OWASP Hive Project
- OWASP Honeypot Project
- OWASP ICS / SCADA Security Project
- OWASP iGoat Tool Project
- OWASP iMAS iOS Mobile Application Security Project
- OWASP Incident Response Project
- OWASP Information Security Metrics Bank
- OWASP Insecure Web Components Project
- OWASP Intelligent Intrusion Detection System
- OWASP Internet of Things Project
- OWASP IOT Analytics 4Industry4
- OWASP iSABEL Proxy Server
- OWASP ISO IEC 27034 Application Security Controls Project
- OWASP ISO Project
- OWASP Java Encoder Project
- OWASP Java File I O Security Project
- OWASP Java J2EE Secure Development Curriculum
- OWASP Java Uncertain Form Submit Prevention
- OWASP JavaScript Sandboxes
- OWASP JAWS Project
- OWASP JOTP Project
- OWASP JSEC CVE Details
- OWASP JSON Sanitizer
- OWASP Jupiter
- OWASP KALP Mobile Project
- OWASP Kates Project
- OWASP Knowledge Based Authentication Performance Metrics Project
- OWASP Knowledge Graph
- OWASP LAPSE Project
- OWASP Learning Platform Project
- OWASP Lock It
- OWASP Logging
- OWASP LWAF
