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 Security Frameworks Project"
(Created page with "=Main= <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">link=</div> {| style="padding: 0;margin:0;margin-top:10px;t...") |
|||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
=Main= | =Main= | ||
| − | + | <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> | |
| − | <div style="width:100%;height: | + | <div style="width:100%;height:100px;border:0,margin:0;overflow: hidden;">[[Image:OWASP Inactive Banner.jpg|800px| link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Inactive_Projects]] </div> |
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
| Line 12: | Line 12: | ||
==Introduction== | ==Introduction== | ||
| − | + | Providing a secure environment to a developer will lead to a more secure final product. Developers need to work in an environment which is secure by default and which relieves them of the burden of implementing their own security controls. That task often falls to the developers who create languages, or enterprise architects. We aim to create a library of design patterns and instructions that should be implemented by architects to create secure languages and environments for developers. | |
==Description== | ==Description== | ||
| − | + | The project aims to provide language independent advice targeted at enterprise architects and people who design programming languages. The intent is to make security functionality a part of the framework that a developer builds upon, so that the developer doesn't have to implement their own security functions. The ultimate goal is to have as much security as possible built into the programming environment so that developer mistakes and omissions are less likely to lead to security vulnerabilities. | |
==Licensing== | ==Licensing== | ||
| Line 23: | Line 23: | ||
| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" | | | valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" | | ||
| − | + | <!-- | |
== What is the OWASP Security Frameworks Project? == | == What is the OWASP Security Frameworks Project? == | ||
| Line 36: | Line 36: | ||
Link to presentation | Link to presentation | ||
| − | + | --> | |
== Project Leader == | == Project Leader == | ||
| − | Ari Elias-Bachrach | + | [[User:Ari_Elias-Bachrach|Ari Elias-Bachrach]] |
== Related Projects == | == Related Projects == | ||
| − | * [[ | + | * [[Cheat Sheets]] |
| − | + | * [[OWASP Framework Security Project]] | |
| − | |||
| valign="top" style="padding-left:25px;width:200px;" | | | valign="top" style="padding-left:25px;width:200px;" | | ||
| − | + | <!-- | |
== Quick Download == | == Quick Download == | ||
| − | * Link to page/download | + | * Link to page/download when ready |
| − | + | --> | |
== News and Events == | == News and Events == | ||
| − | * [ | + | * [22 Feb 2014] Project initiated |
| − | |||
| Line 83: | Line 81: | ||
|} | |} | ||
| − | = | + | =Security Frameworks= |
| − | + | List of guides: | |
| − | + | * [[Data Access Framework]] | |
| − | + | * Password Storage | |
| − | + | * Authentication Framework | |
| − | + | * [[Session Management Framework]] | |
| − | + | * Framework for Handling Output | |
| + | * [[Security Headers]] | ||
= Acknowledgements = | = Acknowledgements = | ||
==Volunteers== | ==Volunteers== | ||
| − | + | The OWASP security frameworks project is developed by a worldwide team of volunteers. The primary contributors to date have been: | |
| − | * | + | * Ari Elias-Bachrach |
| − | * | + | * Mike McCabe |
| + | * Ken Johnson | ||
==Others== | ==Others== | ||
| − | * | + | * your name here, just volunteer :-) |
| − | |||
= Road Map and Getting Involved = | = Road Map and Getting Involved = | ||
As of February 2014, the priorities are: | 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. | + | The plan is to develop a series of documents that cover the various features an architecture should provide. 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 | + | Involvement in the development and promotion of this project is actively encouraged! |
You do not have to be a security expert in order to contribute. | You do not have to be a security expert in order to contribute. | ||
Some of the ways you can help: | Some of the ways you can help: | ||
| − | * | + | * volunteer to write (or help write) a design pattern document |
| − | |||
Latest revision as of 05:15, 13 February 2016
OWASP Security FrameworksThe 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. IntroductionProviding a secure environment to a developer will lead to a more secure final product. Developers need to work in an environment which is secure by default and which relieves them of the burden of implementing their own security controls. That task often falls to the developers who create languages, or enterprise architects. We aim to create a library of design patterns and instructions that should be implemented by architects to create secure languages and environments for developers. DescriptionThe project aims to provide language independent advice targeted at enterprise architects and people who design programming languages. The intent is to make security functionality a part of the framework that a developer builds upon, so that the developer doesn't have to implement their own security functions. The ultimate goal is to have as much security as possible built into the programming environment so that developer mistakes and omissions are less likely to lead to security vulnerabilities. LicensingThe 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.
|
Project Leader
Related Projects |
News and Events
In PrintThis project can be purchased as a print on demand book from Lulu.com
Classifications
| |||||||
List of guides:
- Data Access Framework
- Password Storage
- Authentication Framework
- Session Management Framework
- Framework for Handling Output
- Security Headers
Volunteers
The OWASP security frameworks project is developed by a worldwide team of volunteers. The primary contributors to date have been:
- Ari Elias-Bachrach
- Mike McCabe
- Ken Johnson
Others
- your name here, just volunteer :-)
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. 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 this project is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help:
- volunteer to write (or help write) a design pattern document
| PROJECT INFO What does this OWASP project offer you? |
RELEASE(S) INFO What releases are available for this project? | |||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| |||||||||||||||||||||||||||||||||||
