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-2017 Foreword"
(Created page with "{{Top_10_2017:TopTemplate |usenext=2017NextLink |next={{Top_10:LanguageFile|text=introduction|language=en|year=2017|language=en}} |useprev=Nothing |prev= |year=...") |
m (Editorial changes, added a Link to SAMM) |
||
| (11 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ | + | {{Top_10_2013:TopTemplate |
| − | + | |useprev=2017PrevLink | |
| − | + | |prev={{Top_10:LanguageFile|text=tableOfContents|year=2017|language=en}} | |
| − | + | |usenext=2017NextLink | |
| − | + | |next={{Top_10:LanguageFile|text=introduction|year=2017|language=en}} | |
| − | + | |year=2017 | |
| − | + | |language=en | |
}} | }} | ||
| + | <!--- Foreword ---> | ||
| + | {{Top_10:SubsectionTableBeginTemplate|type=main}}{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstWhole|title=Foreword|year=2017|language=en}} | ||
| + | Insecure software is undermining our financial, healthcare, defense, energy, and other critical infrastructure. As our software becomes increasingly complex, and connected, the difficulty of achieving application security increases exponentially. The rapid pace of modern software development processes makes the most common risks essential to discover and resolve quickly and accurately. We can no longer afford to tolerate relatively simple security problems like those presented in this OWASP Top 10. | ||
| − | + | A great deal of feedback was received during the creation of the OWASP Top 10 - 2017, more than for any other equivalent OWASP effort. This shows how much passion the community has for the OWASP Top 10, and thus how critical it is for OWASP to get the Top 10 right for the majority of use cases. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | Although the original goal of the OWASP Top 10 project was simply to raise awareness amongst developers and managers, it has become <i>the</i> de facto application security standard. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | the | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | In this release, issues and recommendations are written concisely and in a testable way to assist with the adoption of the OWASP Top 10 in application security programs. We encourage large and high performing organizations to use the <u>[[ASVS|OWASP Application Security Verification Standard (ASVS)]]</u> if a true standard is required, but for most, the OWASP Top 10 is a great start on the application security journey. | |
| − | |||
| − | the | ||
| − | |||
| − | |||
| − | + | We have written up a range of suggested next steps for different users of the OWASP Top 10, including <b><u>[[{{Top_10:LanguageFile|text=documentRootTop10New|language=en|year=2017 }}_{{Top_10:LanguageFile|text=whatsNextforDevelopers|language=en}}|{{Top_10:LanguageFile|text=whatsNextforDevelopers|language=en}}]]</u></b>, <b><u>[[{{Top_10:LanguageFile|text=documentRootTop10New|language=en|year=2017 }}_{{Top_10:LanguageFile|text=whatsNextforSecurityTesters|language=en}}|{{Top_10:LanguageFile|text=whatsNextforSecurityTesters|language=en}}]]</u></b>, <b><u>[[{{Top_10:LanguageFile|text=documentRootTop10New|language=en|year=2017 }}_{{Top_10:LanguageFile|text=whatsNextforOrganizations|language=en}}|{{Top_10:LanguageFile|text=whatsNextforOrganizations|language=en}}]]</u></b>, which is suitable for CIOs and CISOs, and <b><u>[[{{Top_10:LanguageFile|text=documentRootTop10New|language=en|year=2017 }}_{{Top_10:LanguageFile|text=whatsNextforApplicationManagers|language=en}}|{{Top_10:LanguageFile|text=whatsNextforApplicationManagers|language=en}}]]</u></b>, which is suitable for application managers or anyone responsible for the lifecycle of the application. | |
| − | |||
| − | |||
| − | and | ||
| − | |||
| − | |||
| − | |||
| − | + | In the long term, we encourage all software development teams and organizations to create an application security program that is compatible with your culture and technology. These programs come in all shapes and sizes. Leverage your organization's existing strengths to measure and improve your application security program using the <u>[[OWASP_SAMM_Project|Software Assurance Maturity Model]]</u>. | |
| − | security | ||
| − | your | ||
| − | |||
| + | 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 at our GitHub project repository: | ||
| + | * <u>[https://github.com/OWASP/Top10/issues https://github.com/OWASP/Top10/issues]</u> | ||
| + | You can find the OWASP Top 10 project and translations here: | ||
| + | * <u>[[top10|https://www.owasp.org/index.php/top10]]</u> | ||
| + | Lastly, we wish to thank the founding leadership of the OWASP Top 10 project, Dave Wichers and Jeff Williams, for all their efforts, and believing in us to get this finished with the community's help. Thank you! | ||
| + | * Andrew van der Stock | ||
| + | * Brian Glas | ||
| + | * Neil Smithline | ||
| + | * Torsten Gigler | ||
| − | {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position= | + | {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=whole|title=Project Sponsorship|year=2017|language=en}} |
| + | Thanks to <u>[https://www.autodesk.com Autodesk]</u> for sponsoring the OWASP Top 10 - 2017. | ||
| − | + | Organizations and individuals that have provided vulnerability prevalence data or other assistance are listed on the <b><u>[[{{Top_10:LanguageFile|text=documentRootTop10New|language=en|year=2017 }}_{{Top_10:LanguageFile|text=acknowledgements|language=en}}|{{Top_10:LanguageFile|text=acknowledgements|language=en}}]]</u></b> page. | |
| − | + | {{Top_10_2013:BottomAdvancedTemplate | |
| − | + | |type=box | |
| − | + | |useprev=2017PrevLink | |
| − | + | |prev={{Top_10:LanguageFile|text=tableOfContents|year=2017|language=en}} | |
| − | + | |usenext=2017NextLink | |
| − | + | |next={{Top_10:LanguageFile|text=introduction|year=2017|language=en}} | |
| − | + | |year=2017 | |
| − | + | |language=en | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | {{ | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
}} | }} | ||
<!-- [[Category:OWASP Top Ten Project]] --> | <!-- [[Category:OWASP Top Ten Project]] --> | ||
Latest revision as of 22:40, 19 December 2017
|
Foreword
Insecure software is undermining our financial, healthcare, defense, energy, and other critical infrastructure. As our software becomes increasingly complex, and connected, the difficulty of achieving application security increases exponentially. The rapid pace of modern software development processes makes the most common risks essential to discover and resolve quickly and accurately. We can no longer afford to tolerate relatively simple security problems like those presented in this OWASP Top 10. A great deal of feedback was received during the creation of the OWASP Top 10 - 2017, more than for any other equivalent OWASP effort. This shows how much passion the community has for the OWASP Top 10, and thus how critical it is for OWASP to get the Top 10 right for the majority of use cases. Although the original goal of the OWASP Top 10 project was simply to raise awareness amongst developers and managers, it has become the de facto application security standard. In this release, issues and recommendations are written concisely and in a testable way to assist with the adoption of the OWASP Top 10 in application security programs. We encourage large and high performing organizations to use the OWASP Application Security Verification Standard (ASVS) if a true standard is required, but for most, the OWASP Top 10 is a great start on the application security journey. We have written up a range of suggested next steps for different users of the OWASP Top 10, including What's Next for Developers, What's Next for Security Testers, What's Next for Organizations, which is suitable for CIOs and CISOs, and What's Next for Application Managers, which is suitable for application managers or anyone responsible for the lifecycle of the application. In the long term, we encourage all software development teams and organizations to create an application security program that is compatible with your culture and technology. These programs come in all shapes and sizes. Leverage your organization's existing strengths to measure and improve your application security program using the Software Assurance Maturity Model. 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 at our GitHub project repository: You can find the OWASP Top 10 project and translations here: Lastly, we wish to thank the founding leadership of the OWASP Top 10 project, Dave Wichers and Jeff Williams, for all their efforts, and believing in us to get this finished with the community's help. Thank you!
| |
|
Project Sponsorship
Thanks to Autodesk for sponsoring the OWASP Top 10 - 2017. Organizations and individuals that have provided vulnerability prevalence data or other assistance are listed on the Acknowledgements page. |
