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 Proactive Controls"
m |
m |
||
| Line 158: | Line 158: | ||
= Users = | = Users = | ||
| + | |||
| + | ''"Giving them guidance that was practical was challenging. The OWASP Top 10 Proactive Controls helped a lot."'' | ||
| + | —Michael Leung. Management consultant with Canadian Cybersecurity Inc. | ||
== Disclaimer == | == Disclaimer == | ||
Organizations listed are not accredited by OWASP. Neither their products or services have been endorsed by OWASP. | Organizations listed are not accredited by OWASP. Neither their products or services have been endorsed by OWASP. | ||
== How to get listed == | == How to get listed == | ||
| − | Please let us know how your organization is using OWASP Top 10 Proactive Controls. Include your name, organization's name, and brief description of how you use the project. The project lead can be reached here. | + | Please let us know how your organization is using OWASP Top 10 Proactive Controls. Include your name, organization's name, and brief description of how you use the project. The project lead can be reached [mailto:katy.anton@owasp.org here]. |
= Formal Numbering = | = Formal Numbering = | ||
Revision as of 14:33, 21 September 2018
OWASP Top 10 Proactive Controls 2018Software developers are the foundation of any application. In order to achieve secure software, developers must be supported and helped by the organization they author code for. As software developers author the code that makes up a web application, they need to embrace and practice a wide variety of secure coding techniques. All tiers of a web application, the user interface, the business logic, the controller, the database code and more – all need to be developed with security in mind. This can be a very difficult task and developers are often set up for failure. Most developers did not learn about secure coding or crypto in school. The languages and frameworks that developers use to build web applications are often lacking critical core controls or are insecure by default in some way. It is also very rare when organizations provide developers with prescriptive requirements that guide them down the path of secure software. And even when they do, there may be security flaws inherent in the requirements and designs. When it comes to software, developers are often set up to lose the security game. The OWASP Top Ten Proactive Controls 2018 is a list of security techniques that should be included in every software development project. They are ordered by order of importance, with control number 1 being the most important. This document was written by developers for developers to assist those new to secure development.
LicensingThe OWASP Proactive Controls document is free to use under the Creative Commons ShareAlike 3 License. |
What is This?The OWASP Top Ten Proactive Controls describes the most important control and control categories that every architect and developer should absolutely, 100% include in every project. PresentationUse the extensive project presentation that expands on the information in the document. Project LeadersKey Contributors
Related Projects |
Quick Access
Translations
Latest News and Events
Please see the News tab for more. ArchiveMailing ListKeep up-to-date, participate or ask questions via the Project Email List. Classifications
| |||||||
