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
(Undo revision 151114 by Edwin Aldridge (talk)) |
m (→Overview) (Tag: Visual edit) |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | = | + | {| |
| + | |- | ||
| + | ! width="700" align="center" | <br> | ||
| + | ! width="500" align="center" | <br> | ||
| + | |- | ||
| + | | align="right" | [[Image:OWASP Inactive Banner.jpg|800px| link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Inactive_Projects]] | ||
| + | | align="right" | | ||
| − | == | + | |} |
| + | ==Overview== | ||
| − | The aim of this project is to build up a | + | The aim of this project is to build up a [[OWASP_Security_JDIs|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 - | + | Rather than give explanations of security issues and defensive techniques - something which is already done by Cheat Sheets and HOWTOs - |
the JDIs will consist of detailed, explicit instructions addressing specific issues using specific technology. | the JDIs will consist of detailed, explicit instructions addressing specific issues using specific technology. | ||
| Line 13: | Line 20: | ||
* 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 | * 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. | * usable code which can be a practical introduction to defensive technologies, such as ESAPI, AntiSamy, etc. | ||
| − | |||
| − | |||
| − | |||
The project will | The project will | ||
| Line 21: | Line 25: | ||
# adopt solutions already developed by developers and/or security specialists which they would like to share. | # adopt solutions already developed by developers and/or security specialists which they would like to share. | ||
| + | ==Project Pages== | ||
| − | + | [[OWASP_Security_JDIs| JDI Collection]] | |
| − | |||
| − | + | [[OWASP_Security_JDI_Process | Development Process]] | |
| − | |||
| − | + | [[OWASP_Security_JDI_Pro-forma | JDI Pro-forma]] | |
| − | |||
| + | [[Projects/OWASP_Security_JDIs_Project | OWASP Project Page]] | ||
| − | + | [[Projects/OWASP_Security_JDIs_Project/Roadmap | Roadmap]] | |
| − | |||
[[Category:OWASP Project]] | [[Category:OWASP Project]] | ||
| − | __NOTOC__ | + | __NOTOC__ |
Latest revision as of 18:02, 16 May 2017
| |
|
|---|---|
|
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 already 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.
