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 "Guidelines of OWASP"
From OWASP
Dinis.cruz (talk | contribs) (→guidelines of OWASP) |
Dinis.cruz (talk | contribs) (→guidelines of OWASP) |
||
| Line 12: | Line 12: | ||
* Don't create Web Applications that have the OWASP Top Vulnerabilities | * Don't create Web Applications that have the OWASP Top Vulnerabilities | ||
* Have an SDL as defined by the OpenSAMM project | * Have an SDL as defined by the OpenSAMM project | ||
| − | * All developers should program in the nude at least 1 day/week | + | * All developers should program in the nude at least 1 day/week (Stephen de Vries idea, designed to help developers have more empathy with the 'nude state' of the applications they are developing) |
=== References=== | === References=== | ||
Revision as of 09:35, 25 September 2013
Section 2.7.4 item c) from the REGULATIONS document (which is aimed at laying down technical specifications for online collection systems pursuant to Regulation (EU) No 211/2011 of the European Parliament and of the Council on the citizens’ initiative), says that:
- Proper security configuration is in place, which requires, at least, that:
- ...
- e) security settings in the development frameworks and libraries are configured in accordance with best practices, such as the guidelines of OWASP."
So what does guidelines of OWASP actually means? This page aims at answering that question
guidelines of OWASP
- Don't create Web Applications that have the OWASP Top Vulnerabilities
- Have an SDL as defined by the OpenSAMM project
- All developers should program in the nude at least 1 day/week (Stephen de Vries idea, designed to help developers have more empathy with the 'nude state' of the applications they are developing)
References
- EU Regulations PDF
- Guidelines of OWASP - Blog post
