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 "Category:OWASP CSRFGuard Project"

From OWASP
Jump to: navigation, search
(→‎Related Projects)
(→‎Classifications: Added stage and category)
 
(19 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
 
=Main=
 
=Main=
  
−
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
+
<div style="width:100%;height:90px;border:0,margin:0;overflow: hidden;">[[File: flagship_big.jpg|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Flagship_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 20: Line 21:
 
OWASP CSRFGuard implements a variant of the synchronizer token pattern to mitigate the risk of CSRF attacks. In order to implement this pattern, CSRFGuard must offer the capability to place the CSRF prevention token within the HTML produced by the protected web application. CSRFGuard 3 provides developers more fine grain control over the injection of the token. Developers can inject the token in their HTML using either dynamic JavaScript DOM manipulation or a JSP tag library. CSRFGuard no longer intercepts and modifies the HttpServletResponse object as was done in previous releases. The currently available token injection strategies are designed to make the integration of CSRFGuard more feasible and scalable within current enterprise web applications. Developers are encouraged to make use of both the JavaScript DOM Manipulation and the JSP tag library strategies for a complete token injection strategy. The JavaScript DOM Manipulation strategy is ideal as it is automated and requires minimal effort on behalf of the developer. In the event the JavaScript solution is insufficient within a particular application context, developers should leverage the JSP tag library. The purpose of this article is to describe the token injection strategies offered by OWASP CSRFGuard 3.
 
OWASP CSRFGuard implements a variant of the synchronizer token pattern to mitigate the risk of CSRF attacks. In order to implement this pattern, CSRFGuard must offer the capability to place the CSRF prevention token within the HTML produced by the protected web application. CSRFGuard 3 provides developers more fine grain control over the injection of the token. Developers can inject the token in their HTML using either dynamic JavaScript DOM manipulation or a JSP tag library. CSRFGuard no longer intercepts and modifies the HttpServletResponse object as was done in previous releases. The currently available token injection strategies are designed to make the integration of CSRFGuard more feasible and scalable within current enterprise web applications. Developers are encouraged to make use of both the JavaScript DOM Manipulation and the JSP tag library strategies for a complete token injection strategy. The JavaScript DOM Manipulation strategy is ideal as it is automated and requires minimal effort on behalf of the developer. In the event the JavaScript solution is insufficient within a particular application context, developers should leverage the JSP tag library. The purpose of this article is to describe the token injection strategies offered by OWASP CSRFGuard 3.
  
−
==== JavaScript DOM Manipulation ===
+
==== JavaScript DOM Manipulation ====
  
 
OWASP CSRFGuard 3 supports the ability to dynamically inject CSRF prevention tokens throughout the DOM currently loaded in the user's browser. This strategy is extremely valuable with regards to server-side performance as it simply requires the serving of a dynamic JavaScript file. There is little to no performance hit when the fetched dynamic JavaScript updates the browser's DOM. Making use of the JavaScript token injection solution requires the developer map a Servlet and place a JavaScript HTML tag within all pages sending requests to protected application resources. Developers are strongly encouraged to leverage the JavaScript token injection strategy by default. This strategy requires minimal effort on behalf of the developer as most of the token injection logic is automated. In the event that the JavaScript automated solution may be insufficient for a specific application context, developers should leverage the OWASP CSRFGuard JSP tag library.
 
OWASP CSRFGuard 3 supports the ability to dynamically inject CSRF prevention tokens throughout the DOM currently loaded in the user's browser. This strategy is extremely valuable with regards to server-side performance as it simply requires the serving of a dynamic JavaScript file. There is little to no performance hit when the fetched dynamic JavaScript updates the browser's DOM. Making use of the JavaScript token injection solution requires the developer map a Servlet and place a JavaScript HTML tag within all pages sending requests to protected application resources. Developers are strongly encouraged to leverage the JavaScript token injection strategy by default. This strategy requires minimal effort on behalf of the developer as most of the token injection logic is automated. In the event that the JavaScript automated solution may be insufficient for a specific application context, developers should leverage the OWASP CSRFGuard JSP tag library.
Line 36: Line 37:
 
* A JavaEE Filter and exposes various automated and manual ways to integrate per-session or pseudo-per-request tokens into HTML.  
 
* A JavaEE Filter and exposes various automated and manual ways to integrate per-session or pseudo-per-request tokens into HTML.  
  
−
==Licensing==
+
 
−
The CSRFGuard project is run by Azzeddine RAMRAMI. He can be contacted at azzeddine.ramrami AT owasp.org. CSRFGuard distributions are currently maintained on GitHub.
+
== Ohloh ==
 +
 
 +
*https://www.ohloh.net/p/OWASP-CSRFGuard
 +
 
 +
| valign="top"  style="padding-left:25px;width:200px;" |
 +
 
 +
 
 +
== In Print ==
 +
 
 +
This project can be purchased as a print on demand book from Lulu.com
 +
 
 +
==Classifications==
 +
 
 +
  {| width="200" cellpadding="2"
 +
  |-
 +
  | align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-flagship-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Flagship_Projects]]
 +
  | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]] 
 +
  |-
 +
  | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]]
 +
  |-
 +
  | colspan="2" align="center"  | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]
 +
  |-
 +
  | colspan="2" align="center"  | [[File:Project_Type_Files_CODE.jpg|link=]]
 +
  |}
 +
 
 +
|}
 +
 
 +
= Licensing =
  
 
OWASP CSRFGuard 3.1 is offered under the BSD license
 
OWASP CSRFGuard 3.1 is offered under the BSD license
Line 43: Line 71:
 
| 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;" |
  
−
== Presentation & Manual ==
+
= Presentation & Manual =
  
 
Link to presentation
 
Link to presentation
Line 49: Line 77:
 
https://www.owasp.org/index.php/CSRFGuard_3_Token_Injection
 
https://www.owasp.org/index.php/CSRFGuard_3_Token_Injection
  
−
== Project Leader ==
+
= Project Leader =
  
−
The CSRFGuard project is run by Azzeddine RAMRAMI. He can be contacted at azzeddine.ramrami AT owasp.org.
+
The CSRFGuard project is run by [mailto:azzeddine.ramrami(at)owasp.org Azzeddine RAMRAMI].
 +
 
 +
The project co-leader is [mailto:sebastien.gioria(at)owasp.org Sébastien Gioria].
 +
 
 +
With the active participation of:
 +
  [mailto:ahamednafeez(at)gmail.com  Ahamed Nafeez] : Security Tester & Bug Finder
 +
  [mailto:Trent.schmidt(at)gmail.com Trent Schmidt] : Release & Maven Central helper
  
 
== Related Projects ==
 
== Related Projects ==
Line 62: Line 96:
 
:*https://www.owasp.org/index.php/CSRFProtector_Project - CSRF Protector Project - Implements new Anti CSRF method in web applications
 
:*https://www.owasp.org/index.php/CSRFProtector_Project - CSRF Protector Project - Implements new Anti CSRF method in web applications
  
−
== Ohloh ==
+
= Source Code Download =
  
−
*https://www.ohloh.net/p/OWASP-CSRFGuard
+
Download and build the latest source code from GitHub :
  
−
| valign="top"  style="padding-left:25px;width:200px;" |
+
* https://github.com/aramrami/OWASP-CSRFGuard
  
−
== Quick Download ==
+
Download and build the latest source code from GitHub - https://github.com/aramrami/OWASP-CSRFGuard-3
  
−
Download and build the latest source code from GitHub :
+
[[CSRFGuard_Deprecated_Releases | Deprecated Releases]] - article containing several download references to deprecated and officially unsupported releases
 +
 
 +
== CSRFGuard Binary in Maven Central ==
  
−
* https://github.com/aramrami/OWASP-CSRFGuard-3
+
You can download a binary version from Maven Central here:
  
−
Download and build the latest source code from GitHub - https://github.com/aramrami/OWASP-CSRFGuard-3
+
* https://oss.sonatype.org/#nexus-search;gav~~csrfguard
  
−
[[CSRFGuard_Deprecated_Releases | Deprecated Releases]] - article containing several download references to deprecated and officially unsupported releases
+
Thanks to Trent Schmidt and Joel Orlina (JIRA) for there help.
  
 
== User Manual(s) ==
 
== User Manual(s) ==
  
 
[[CSRFGuard_3_User_Manual | OWASP CSRFGuard v3 ]] - series of articles describing the installation, configuration, and deployment of OWASP CSRFGuard v3.
 
[[CSRFGuard_3_User_Manual | OWASP CSRFGuard v3 ]] - series of articles describing the installation, configuration, and deployment of OWASP CSRFGuard v3.
−
== News and Events ==
+
= News and Events =
  
 
* [08 Fev 2014] A security fix has been published. See details on GitHub
 
* [08 Fev 2014] A security fix has been published. See details on GitHub
 
* [10 Feb 2014] Release 3.1 of CSRFGuard project is now available for download  
 
* [10 Feb 2014] Release 3.1 of CSRFGuard project is now available for download  
 
* [28 Jul 2014] A new Github repository called "OWASP CSRFGuard-3" with issues management has been created
 
* [28 Jul 2014] A new Github repository called "OWASP CSRFGuard-3" with issues management has been created
−
 
−
== In Print ==
 
−
 
−
This project can be purchased as a print on demand book from Lulu.com
 
−
 
−
==Classifications==
 
−
 
−
  {| width="200" cellpadding="2"
 
−
  |-
 
−
  | colspan="2" align="center"  | [[File:Project_Type_Files_CODE.jpg|link=]]
 
−
  |}
 
−
 
−
|}
 
−
 
 
=FAQs=
 
=FAQs=
  
Line 113: Line 135:
 
* Ahamed Nafeez, Security Engineer.  
 
* Ahamed Nafeez, Security Engineer.  
 
* Christa Erwin, Security, Programmer/Analyst.
 
* Christa Erwin, Security, Programmer/Analyst.
 +
* Trent Schmidt, Release & Maven Central helper
  
 
==Others==
 
==Others==
Line 143: Line 166:
  
 
[[Category:OWASP Project]]
 
[[Category:OWASP Project]]
 +
[[Category:SAMM-SA-2]]

Latest revision as of 20:19, 28 March 2016

Flagship big.jpg

OWASP CSRFGuard

Welcome to the home of the OWASP CSRFGuard Project! OWASP CSRFGuard is a library that implements a variant of the synchronizer token pattern to mitigate the risk of Cross-Site Request Forgery (CSRF) attacks.

Introduction

The OWASP CSRFGuard library is integrated through the use of a JavaEE Filter and exposes various automated and manual ways to integrate per-session or pseudo-per-request tokens into HTML.

Description

Overview

OWASP CSRFGuard implements a variant of the synchronizer token pattern to mitigate the risk of CSRF attacks. In order to implement this pattern, CSRFGuard must offer the capability to place the CSRF prevention token within the HTML produced by the protected web application. CSRFGuard 3 provides developers more fine grain control over the injection of the token. Developers can inject the token in their HTML using either dynamic JavaScript DOM manipulation or a JSP tag library. CSRFGuard no longer intercepts and modifies the HttpServletResponse object as was done in previous releases. The currently available token injection strategies are designed to make the integration of CSRFGuard more feasible and scalable within current enterprise web applications. Developers are encouraged to make use of both the JavaScript DOM Manipulation and the JSP tag library strategies for a complete token injection strategy. The JavaScript DOM Manipulation strategy is ideal as it is automated and requires minimal effort on behalf of the developer. In the event the JavaScript solution is insufficient within a particular application context, developers should leverage the JSP tag library. The purpose of this article is to describe the token injection strategies offered by OWASP CSRFGuard 3.

JavaScript DOM Manipulation

OWASP CSRFGuard 3 supports the ability to dynamically inject CSRF prevention tokens throughout the DOM currently loaded in the user's browser. This strategy is extremely valuable with regards to server-side performance as it simply requires the serving of a dynamic JavaScript file. There is little to no performance hit when the fetched dynamic JavaScript updates the browser's DOM. Making use of the JavaScript token injection solution requires the developer map a Servlet and place a JavaScript HTML tag within all pages sending requests to protected application resources. Developers are strongly encouraged to leverage the JavaScript token injection strategy by default. This strategy requires minimal effort on behalf of the developer as most of the token injection logic is automated. In the event that the JavaScript automated solution may be insufficient for a specific application context, developers should leverage the OWASP CSRFGuard JSP tag library.

Note: Use of JavaScript DOM Manipulation is required for Ajax support.


CSRFGuard Architecture

What is CSRFGuard?

OWASP CSRFGuard provides:

  • A library that implements a variant of the synchronizer token pattern to mitigate the risk of Cross-Site Request Forgery (CSRF) attacks.
  • A JavaEE Filter and exposes various automated and manual ways to integrate per-session or pseudo-per-request tokens into HTML.


Ohloh


In Print

This project can be purchased as a print on demand book from Lulu.com

Classifications

Owasp-flagship-trans-85.png Owasp-builders-small.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Project Type Files CODE.jpg

OWASP CSRFGuard 3.1 is offered under the BSD license

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

The CSRFGuard project is run by Azzeddine RAMRAMI.

The project co-leader is Sébastien Gioria.

With the active participation of: 

 Ahamed Nafeez : Security Tester & Bug Finder
 Trent Schmidt : Release & Maven Central helper

Related Projects

Download and build the latest source code from GitHub :

Download and build the latest source code from GitHub - https://github.com/aramrami/OWASP-CSRFGuard-3

Deprecated Releases - article containing several download references to deprecated and officially unsupported releases

CSRFGuard Binary in Maven Central

You can download a binary version from Maven Central here:

Thanks to Trent Schmidt and Joel Orlina (JIRA) for there help.

User Manual(s)

OWASP CSRFGuard v3 - series of articles describing the installation, configuration, and deployment of OWASP CSRFGuard v3.

  • [08 Fev 2014] A security fix has been published. See details on GitHub
  • [10 Feb 2014] Release 3.1 of CSRFGuard project is now available for download
  • [28 Jul 2014] A new Github repository called "OWASP CSRFGuard-3" with issues management has been created

Here a complete CSRF attacks FAQ:

Volunteers

CSRFGuard is developed by a worldwide team of volunteers. The primary contributors to date have been:

  • Ahamed Nafeez, Security Engineer.
  • Christa Erwin, Security, Programmer/Analyst.
  • Trent Schmidt, Release & Maven Central helper

Others

  • Eric Sheridan was the original designer of CSRFGuard until 3.0 version.

As of CSRFGuard the priorities are:

  • Address any security vulnerabilities around javascript prototype hijacking
  • Support for Internet Explorer
  • Addressing outstanding issues listed in GitHub
  • Support for Multi-part requests
  • Add support for the 'Origin' header

Involvement in the development and promotion of CSRFGurd is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help:

  • Make fix to the actual version
  • Propose a security enhcement
  • Write a complete Architecture Folder for CSRFGurd
  • Add an IA engine to detect unknown attacks.


You can sign up for the OWASP CSRFGuard email list at https://lists.owasp.org/mailman/listinfo/owasp-csrfguard

Pages in category "OWASP CSRFGuard Project"

The following 4 pages are in this category, out of 4 total.

C

Retrieved from "https://wiki.owasp.org/index.php?title=Category:OWASP_CSRFGuard_Project&oldid=211961"