GPN16:OWASP ProActive Controls: Unterschied zwischen den Versionen

aus dem Wiki des Entropia e.V., CCC Karlsruhe
K (Fahrplanbot tut Dinge)
K (Video added)
 
Zeile 1: Zeile 1:
 
{{#ev:mediacccde|https://media.ccc.de/browse/conferences/gpn/gpn16/gpn16-7644-owasp_proactive_controls.html||right}}
Ein Vortrag von Ives Laaf auf der [[GPN16]].
Ein Vortrag von Ives Laaf auf der [[GPN16]].



Aktuelle Version vom 25. Juni 2016, 14:52 Uhr

Ein Vortrag von Ives Laaf auf der GPN16.

Vorstellung der OWASP ProActive Controls

Software 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 2016 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.

Links