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 "OWASP Security JDIs Project"
From OWASP
Line 4: | Line 4: | ||
! width="500" align="center" | <br> | ! width="500" align="center" | <br> | ||
|- | |- | ||
− | | align="right" | [[Image:OWASP Inactive Banner.jpg|800px| link=https://www.owasp.org/index.php/ | + | | align="right" | [[Image:OWASP Inactive Banner.jpg|800px| link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Inactive_Projects]] |
| align="right" | | | align="right" | | ||
Revision as of 20:03, 23 January 2014
|
|
---|---|
![]() |
Overview
The aim of this project is to build up a collection of practical solutions to specific security problems.
Rather than give explanations of security issues and defensive techniques - something which is done by Cheat Sheets and HOWTOs - the JDIs will consist of detailed, explicit instructions addressing specific issues using specific technology.
Like recipes, a JDI may suit some tastes more than others and, again like recipes, there can be more than one JDI for the same problem.
The benefits will be
- practical, if limited, solutions for developers without them first having to become an expert in the problem space - something which time often does not permit
- usable code which can be a practical introduction to defensive technologies, such as ESAPI, AntiSamy, etc.
The project will
- endeavour to source a suitable solutions to specific, practical problems on request, and
- adopt solutions already developed by developers and/or security specialists which they would like to share.