[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-571462-105":3,"detail-sidebar-cat-1-en-105":81,"doc-detail-571462-en":126},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":74,"head_meta":76,"extra_data":78,"updated_unix":80},105,"en","owasp-top-ten-proactive-controls-project-v-30-foreword-aim-objectif","OWASP Top Ten Proactive Controls Project - v 3.0 - Foreword - Aim & Objectif","","OWASP Top Ten Proactive Controls Project presents a proactive, developer-focused set of security techniques intended for every software development effort. The foreword explains why insecure software threatens critical infrastructure as digital systems grow more complex and interconnected. The document’s aim is to raise awareness by outlining the most important application-security concerns, encouraging early and consistent application of each control throughout development. It also describes the document structure and how the Top 10 list is prioritized and created.",{"@graph":14,"@context":73},[15,34,56],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/template/","Template",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/template/presentations/","Presentations",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/template/owasp-top-ten-proactive-controls-project-v-30-foreword-aim-objectif/571462/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/owasp-top-ten-proactive-controls-project-v-30-foreword-aim-objectif/571462.png","ImageObject",442,249,{"name":42,"@type":43},"Ben ","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-24","2026-10-13",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",5,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"What is the purpose of the OWASP Top Ten Proactive Controls project?","Question",{"text":63,"@type":64},"It aims to raise awareness about application security by describing the most important areas of concern developers should know, encouraging the use of the proactive controls to start secure development.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"How are the Top 10 Proactive Controls prioritized?",{"text":68,"@type":64},"The list is ordered by importance, with item 1 being the most important.",{"name":70,"@type":61,"acceptedAnswer":71},"Who is the primary audience for this document?",{"text":72,"@type":64},"The document is primarily written for developers, while development managers, product owners, QA professionals, program managers, and others involved in building software can also benefit.","https://schema.org",{"og:url":32,"og:type":75,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":77,"canonical":32},"index,follow",{"doc_id":79,"site_id":7},571462,1792253241,{"code":4,"msg":82,"data":83},"success",[84,88,93,98,103,108,113,118,122],{"id":85,"doc_module":22,"doc_module_name":25,"category_name":29,"show_sort_weight":86,"slug":87},11,90,"presentations",{"id":89,"doc_module":22,"doc_module_name":25,"category_name":90,"show_sort_weight":91,"slug":92},12,"Resumes",80,"resumes",{"id":94,"doc_module":22,"doc_module_name":25,"category_name":95,"show_sort_weight":96,"slug":97},14,"Invoices",70,"invoices",{"id":99,"doc_module":22,"doc_module_name":25,"category_name":100,"show_sort_weight":101,"slug":102},15,"Posters",60,"posters",{"id":104,"doc_module":22,"doc_module_name":25,"category_name":105,"show_sort_weight":106,"slug":107},16,"Social Media",50,"social-media",{"id":109,"doc_module":22,"doc_module_name":25,"category_name":110,"show_sort_weight":111,"slug":112},17,"Forms",40,"forms",{"id":114,"doc_module":22,"doc_module_name":25,"category_name":115,"show_sort_weight":116,"slug":117},18,"Letters",30,"letters",{"id":119,"doc_module":22,"doc_module_name":25,"category_name":120,"show_sort_weight":55,"slug":121},21,"Paper Templates","papers-templates",{"id":123,"doc_module":22,"doc_module_name":25,"category_name":124,"show_sort_weight":4,"slug":125},158,"General","general-158",{"code":4,"msg":82,"data":127},{"doc_id":79,"user_id":128,"nickname":42,"user_avatar":129,"doc_module":22,"category_id":85,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":111,"language":135,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":136,"faqs":137,"seo_title":138,"seo_description":12,"update_tm":139,"read_time":94},2336478951081,"https://ap-avatar.wpscdn.com/davatar_276721f389ce27ea32af1340a28f341c","OWASP Top Ten Proactive Controls Project  \nAbout OWASP  \nThe Open Web Application Security Project (OWASP) is a 501c3 non for profit educational charity dedicated to enabling organizations to design, develop, acquire, operate, and maintain secure software. All OWASP tools, documents, forums, and chapters are free and open to anyone interested in improving application security. We can be found at [www.owasp.org](www.owasp.org).  \nOWASP is a new kind of organization. Our freedom from commercial pressures allows us to provide unbiased, practical, cost effective information about application security.  \nOWASP is not affiliated with any technology company. Similar to many open source software projects, OWASP produces many types of materials in a collaborative and open way. The OWASP Foundation is a not-for-profit entity that ensures the project's long-term success.  \nv 3.0 © 2002-2018 OWASP Foundation This document is licensed under the Creative Commons Attribution-ShareAlike 3.0 license. 2  \nOWASP Top Ten Proactive Controls Project  \nFOREWORD  \nInsecure software is undermining our financial, healthcare, defense, energy, and other critical infrastructure worldwide. As our digital, global 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.  \nAIM & OBJECT IF  \nThe goal of the OWASP Top 10 Proactive Controls project (OPC) is to raise awareness about application security by describing the most important areas of concern that software developers must be aware of. We encourage you to use the OWASP Proactive Controls to get your developers started with application security. Developers can learn from the mistakes of other organizations. We hope that the OWASP Proactive Controls is useful to your efforts in building secure software.  \nCALL TO ACTION  \nPlease don’t hesitate to contact the OWASP Proactive Control project with your questions, comments, and ideas, either publicly to our email list or [privately to](privately to jim@owasp.org)[ jim@owasp.org](privately to jim@owasp.org).  \nCOPYRIGHT AND LICENSE  \nThis document is released under the Creative Commons Attribution ShareAlike 3.0 license. For any reuse or distribution, you must make it clear to others the license terms of this work.  \nPROJECT LEADERS  \nKaty Anton  \nCONTRIBUTORS  \nChris Romeo Dave Ferguson  \nColin Watson  \nJim Bird  \nDan Anderson Josh Grossman Rick Mitchell  \nJim Manico  \nDavid Cybuck Osama Elnaggar And many more…  \nv 3.0 © 2002-2018 OWASP Foundation This document is licensed under the Creative Commons Attribution-ShareAlike 3.0 license. 3  \nOWASP Top Ten Proactive Controls Project  \nDOCUMENT STRUCTURE  \nThis document is structured as a list of security controls. Each control is described as follows:  \nOWASP Proactive Controls v 3.0  \nCx: Control Name  \nDescription  \n| \u003Cbr>\u003Cbr>_________________________________________\u003Cbr>\u003Cbr>__________________________________\u003Cbr>\u003Cbr>Implementation | A detailed description of the control including some best practices to consider. |\n| --- | --- |\n| \u003Cbr>|  |\n\n__________________________  \nVulnerabilities Prevented  \n•    \n•     \nReferences  \n•    \n•     \nTools  \n•   \n_____________  \n•    \nImplementation best practicesand examples to illustrate how to implement each control.  \nList of prevented vulnerabilities or risks addressed (OWASP TOP 10 Risk, CWE, etc. )  \nList of references for further study (OWASP Cheat sheet, Security Hardening Guidelines, etc. )  \nSet of tools/projects to easily introduce/integrate security controls into your software.  \nv 3.0 © 2002-2018 OWASP Foundation This document is licensed under the Creative Commons Attribution-ShareAlike 3.0 license. 4  \nOWASP Top Ten Proactive Controls Project  \nINTRODUCTION  \nThe OWASP Top Ten Proactive Controls 2018 is a list of security techniques that should be considered for every software development project. This document is w","cbCaiaZXCS1KCRdi","https://ap.wps.com/l/cbCaiaZXCS1KCRdi","pdf",2822842,"English","# Foreword\n# Aim & Objectif\n# Call to Action\n# Copyright and License\n# Project Leaders\n# Contributors\n# Document Structure\n# Introduction\n## The Top 10 Proactive Controls\n## How this List Was Created\n# Target Audience\n# How to Use this Document","[{\"question\":\"What is the purpose of the OWASP Top Ten Proactive Controls project?\",\"answer\":\"It aims to raise awareness about application security by describing the most important areas of concern developers should know, encouraging the use of the proactive controls to start secure development.\"},{\"question\":\"How are the Top 10 Proactive Controls prioritized?\",\"answer\":\"The list is ordered by importance, with item 1 being the most important.\"},{\"question\":\"Who is the primary audience for this document?\",\"answer\":\"The document is primarily written for developers, while development managers, product owners, QA professionals, program managers, and others involved in building software can also benefit.\"}]","OWASP Top Ten Proactive Controls Project - v 3.0 - Foreword - Aim & Objectif | PDF",1791918770]