OWASP Security Frameworks Project
OWASP Security Frameworks
The OWASP Security Frameworks Project is a series of design patterns that can be used by language designers and architects to create secure frameworks for developers, thereby relieving developers of the work of implementing security themselves.
Write a description that is just a few paragraphs long
This project is the outgrowth of several conversations I've had recently, and a presentation given at AppSec CA by Ken Johnson and Mike McCabe (both of whom are on board to help out). There will be some copying from other projects (like some of the cheat sheets), but ultimately our goal is to provide language independent advice targeted at enterprise architects and the people who design programming languages. The goal is to make security functionality a part of the framework that a developer builds upon, so that the developer doesn't have to do it him or herself.
The OWASP Security Framework is free to use. It is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.
What is the OWASP Security Frameworks Project?
OWASP Security Frameworks Project provides:
Link to presentation
News and Events
This project can be purchased as a print on demand book from Lulu.com
XXX is developed by a worldwide team of volunteers. The primary contributors to date have been:
As of February 2014, the priorities are:
The plan is to develop a series of documents that cover the various features an architecture should provide. For example we'll have a document on XSS prevention, database access, authentication, CSRF prevention, etc. Each one will contain the design patterns that should be implemented in order to provide those functions in a secure manner. They'll each be free standing documents which can eventually be combined together into one large pdf or book when we're "done".
Involvement in the development and promotion of XXX is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help:
| PROJECT INFO
What does this OWASP project offer you?
| RELEASE(S) INFO|
What releases are available for this project?