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"
(Added Users tab) |
m |
||
| Line 167: | Line 167: | ||
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''' | |
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:[email protected] 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:[email protected] here]. | ||
Revision as of 14:37, 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
| |||||||
OWASP Proactive Controls 2018 is currently available in the following formats.
- Top 10 Proactive Controls 2018 PDF version
- Top 10 Proactive Controls 2018 PPT download.
- Top 10 Proactive Controls 2018 DOCX download.
Wiki version- is currently work in progress .
- [9 May 2018] Featured in Developer's security guide: 50 online resources to shift left
- [7 May 2018] 3.0 released!
- [11 Aug 2017] Presented at Northeast PHP Conference
- [25 July 2017] Podcast about at OWASP Top 10 Proactive Controls
- [12 May 2017] Presented at AppSec EU'17 - Belfast
- [14 Feb 2017] Featured in Managing Cloud Infrastructure to Prevent Security Gaps
- [Feb 2017 ] Featured in "Application Security Program: Protect Against Data Breaches"
- [ 1 Oct 2016] Presented at PHPNW16
- [5 July 2016] Featured in Incorporating Security Best Practices into Agile Teams
- [June 2016 ] Featured in A Transformative Approach to Secure Systems Delivery
- [2 June 2016] Featured in DevOpsSec - Securing Software through Continuous Delivery
- [30 Apr 2016] Added Hebrew Translation for 2016 version
- [28 Apr 2016] Added Chinese Translations for 2016 version
- [12 Apr 2016] Added Hebrew translation for 2016 version
- [29 Feb 2016] Added Japanese Translation
- [14 Jan 2016] 2.0 released!
- [5 Dec 2015] Began final edit process for 2.0
- [29 Mar 2015] Added Hebrew Translation
- [27 Jan 2015] Added Top Ten Mapping
- [31 Oct 2014] Project presentation uploaded
- [10 Mar 2014] Request for review
- [04 Feb 2014] New Wiki Template!
- Michael Leung. Management consultant with Canadian Cybersecurity Inc.
- "Giving them guidance that was practical was challenging. The OWASP Top 10 Proactive Controls helped a lot."
Disclaimer
Organizations listed are not accredited by OWASP. Neither their products or services have been endorsed by OWASP.
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.
2018 Numbering
- OWASP-2018-C1: Define Security Requirements
- OWASP-2018-C2: Leverage Security Frameworks and Libraries
- OWASP-2018-C3: Secure Database Access
- OWASP-2018-C4: Encode and Escape Data
- OWASP-2018-C5: Validate All Inputs
- OWASP-2018-C6: Implement Digital Identity
- OWASP-2018-C7: Enforce Access Controls
- OWASP-2018-C8: Protect Data Everywhere
- OWASP-2018-C9: Implement Security Logging and Monitoring
- OWASP-2018-C10: Handle All Errors and Exceptions
2016 Numbering
- OWASP-2016-C1: Verify for Security Early and Often
- OWASP-2016-C2: Parameterize Queries
- OWASP-2016-C3: Encode Data
- OWASP-2016-C4: Validate All Inputs
- OWASP-2016-C5: Implement Identity and Authentication Controls
- OWASP-2016-C6: Implement Appropriate Access Controls
- OWASP-2016-C7: Protect Data
- OWASP-2016-C8: Implement Logging and Intrusion Detection
- OWASP-2016-C9: Leverage Security Frameworks and Libraries
- OWASP-2016-C10: Error and Exception Handling
2014 Numbering
- OWASP-2014-C1: Parameterize Queries
- OWASP-2014-C2: Encode Data
- OWASP-2014-C3: Validate All Inputs
- OWASP-2014-C4: Implement Appropriate Access Controls
- OWASP-2014-C5: Establish Identity and Authentication Controls
- OWASP-2014-C6: Protect Data and Privacy
- OWASP-2014-C7: Implement Logging, Error Handling and Intrusion Detection
- OWASP-2014-C8: Leverage Security Features of Frameworks and Security Libraries
- OWASP-2014-C9: Include Security-Specific Requirements
- OWASP-2014-C10: Design and Architect Security In
2016 Version
- Top 10 Proactive Controls 2016 Traditional Chinese Translation PDF Download
- Top 10 Proactive Controls 2016 Simplified Chinese Translation PDF Download
- Top 10 Proactive Controls 2016 Japanese Translation PDF Download
- Top 10 Proactive Controls 2016 Hebrew Translation PDF Download
2014 Version
- Hebrew and French translations of the Top 10 Proactive Controls 2014 can be found on the 2014 archive tab.
Welcome to the OWASP Top 10 Proactive Controls Project!
2018 Roadmap
- Create new PowerPoint and other artifacts for 2018 version (done)
- Create wiki for 2018 version (work in progress)
2016 Roadmap
- Create new PowerPoint and other artifacts for 2016 version (done)
- Proactive Control Mapping to Cheatsheet (done)
Status
- February 21, 2014 Moved 2014 info to archive tab
- January 15, 2016: 2016 Proactive Controls Released!
- August 6, 2015: Kickoff for 2.0 effort, in progress
- March 10, 2014: We released an early beta of this document to the OWASP leaders list for review and commentary.
- February 3, 2014: We are currently working towards a beta release of this document and have begun working with a designer for the final release PDF.
