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 "Top 10 2013"
m (deleted a doubled 'language' paramater (avoids 'Category: Pages using duplicate arguments in template calls')) |
|||
(20 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
− | + | {{Top_10_2013:TopTemplate | |
− | {{ | + | |usenext=2013NextLink |
+ | |next={{Top_10:LanguageFile|text=introduction|year=2013|language=en}} | ||
+ | |useprev=Nothing | ||
+ | |prev= | ||
+ | |year=2013 | ||
+ | |language=en | ||
+ | }} | ||
− | {{Top_10_2010: | + | {{Top_10:SubsectionTableBeginTemplate|type=main}}{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstLeft|title={{Top_10:LanguageFile|text=foreword}}|year=2013|language=en}} |
− | + | Insecure software is undermining our financial, healthcare, | |
− | + | defense, energy, and other critical infrastructure. As our | |
− | + | digital infrastructure gets increasingly complex and | |
+ | interconnected, the difficulty of achieving application | ||
+ | security increases exponentially. We can no longer afford to | ||
+ | tolerate relatively simple security problems like those | ||
+ | presented in this OWASP Top 10. | ||
+ | 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 standards, books, tools, and organizations, including | ||
+ | MITRE, PCI DSS, DISA, FTC, and [[Industry:Citations|many more]]. This release of | ||
+ | the OWASP Top 10 marks this project’s tenth anniversary of | ||
+ | raising awareness of the importance of application security | ||
+ | risks. The OWASP Top 10 was first released in 2003, with | ||
+ | minor updates in 2004 and 2007. The 2010 version was | ||
+ | revamped to prioritize by risk, not just prevalence. This 2013 | ||
+ | edition follows the same approach. | ||
− | + | We encourage you to use the Top 10 to get your organization | |
− | + | started with application security. Developers can learn from | |
− | + | the mistakes of other organizations. Executives should start | |
− | + | thinking about how to manage the risk that software | |
− | + | applications create in their enterprise. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | In the long term, we encourage you to create an application | |
+ | security program that is compatible with your culture and | ||
+ | technology. These programs come in all shapes and sizes, | ||
+ | and you should avoid attempting to do everything prescribed | ||
+ | by some process model. Instead, leverage your | ||
+ | organization’s existing strengths to do and measure what | ||
+ | works for you. | ||
− | + | We hope that the OWASP Top 10 is useful to your application | |
+ | security efforts. Please don’t hesitate to contact OWASP with | ||
+ | your questions, comments, and ideas, either publicly to | ||
+ | [mailto:owasp-[email protected] [email protected]] or privately to [mailto:[email protected] [email protected]]. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | {{Top_10_2010: | + | {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=right|title={{Top_10:LanguageFile|text=aboutOWASP}}|year=2013|language=en}} |
− | {{Top_10_2010: | ||
− | |||
− | |||
− | {{ | ||
− | |||
− | |||
− | {{ | + | The Open Web Application Security Project (OWASP) is an open community dedicated to enabling organizations to develop, purchase, and maintain applications that can be trusted. At OWASP you’ll find free and open … |
+ | |||
+ | * Application security tools and standards | ||
+ | * Complete books on application security testing, secure code development, and secure code review | ||
+ | * Standard security controls and libraries | ||
+ | * [https://www.owasp.org/index.php/Category:OWASP_Chapter Local chapters worldwide] | ||
+ | * Cutting edge research | ||
+ | * [https://www.owasp.org/index.php/Category:OWASP_AppSec_Conference Extensive conferences worldwide] | ||
+ | * Mailing lists | ||
+ | |||
+ | Learn more at: [https://www.owasp.org/ https://www.owasp.org] | ||
+ | |||
+ | All of the OWASP tools, documents, forums, and chapters are | ||
+ | free and open to anyone interested in improving application | ||
+ | security. We advocate approaching application security as a | ||
+ | people, process, and technology problem, because the most | ||
+ | effective approaches to application security require | ||
+ | improvements in all of these areas. | ||
+ | |||
+ | OWASP is a new kind of organization. Our freedom from | ||
+ | commercial pressures allows us to provide unbiased, practical, | ||
+ | cost-effective information about application security. OWASP | ||
+ | is not affiliated with any technology company, although we | ||
+ | support the informed use of commercial security technology. | ||
+ | Similar to many open source software projects, OWASP | ||
+ | produces many types of materials in a collaborative, open way. | ||
+ | |||
+ | The OWASP Foundation is the non-profit entity that ensures | ||
+ | the project’s long-term success. Almost everyone associated | ||
+ | with OWASP is a volunteer, including the OWASP Board, | ||
+ | Global Committees, Chapter Leaders, Project Leaders, and | ||
+ | project members. We support innovative security research | ||
+ | with grants and infrastructure. | ||
+ | |||
+ | |||
+ | Come join us! | ||
+ | </td></tr></table> | ||
+ | {{Top_10_2013:BottomTemplate | ||
+ | |usenext=2013NextLink | ||
+ | |next={{Top_10:LanguageFile|text=introduction|year=2013|language=en}} | ||
+ | |useprev=Nothing | ||
+ | |prev= | ||
+ | |year=2013 | ||
+ | |language=en | ||
+ | }} | ||
[[Category:OWASP Top Ten Project]] | [[Category:OWASP Top Ten Project]] |
Latest revision as of 20:28, 23 April 2017
NOTE: THIS IS NOT THE LATEST VERSION. Please visit the OWASP Top 10 project page to find the latest edition.
Foreword
Insecure software is undermining our financial, healthcare, defense, energy, and other critical infrastructure. As our digital infrastructure gets increasingly complex and interconnected, the difficulty of achieving application security increases exponentially. We can no longer afford to tolerate relatively simple security problems like those presented in this OWASP Top 10. 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 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 tenth anniversary of raising awareness of the importance of application security risks. The OWASP Top 10 was first released in 2003, with minor updates in 2004 and 2007. The 2010 version was revamped to prioritize by risk, not just prevalence. This 2013 edition follows the same approach. We encourage you to use the Top 10 to get your organization started with application security. Developers can learn from the mistakes of other organizations. Executives should start thinking about how to manage the risk that software applications create in their enterprise. In the long term, we encourage you to create an application security program that is compatible with your culture and technology. These programs come in all shapes and sizes, and you should avoid attempting to do everything prescribed by some process model. Instead, leverage your organization’s existing strengths to do and measure what works for you. We hope that the OWASP Top 10 is useful to your application security efforts. Please don’t hesitate to contact OWASP with your questions, comments, and ideas, either publicly to [email protected] or privately to [email protected].
|
About OWASP
The Open Web Application Security Project (OWASP) is an open community dedicated to enabling organizations to develop, purchase, and maintain applications that can be trusted. At OWASP you’ll find free and open …
Learn more at: https://www.owasp.org All of the OWASP tools, documents, forums, and chapters are free and open to anyone interested in improving application security. We advocate approaching application security as a people, process, and technology problem, because the most effective approaches to application security require improvements in all of these areas. OWASP is a new kind of organization. Our freedom from commercial pressures allows us to provide unbiased, practical, cost-effective information about application security. OWASP is not affiliated with any technology company, although we support the informed use of commercial security technology. Similar to many open source software projects, OWASP produces many types of materials in a collaborative, open way. The OWASP Foundation is the non-profit entity that ensures the project’s long-term success. Almost everyone associated with OWASP is a volunteer, including the OWASP Board, Global Committees, Chapter Leaders, Project Leaders, and project members. We support innovative security research with grants and infrastructure.
|
![CC-by-sa-3 0-88x31.png](/images/6/64/CC-by-sa-3_0-88x31.png)