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 "CSRFGuard 3 User Manual"

From OWASP
Jump to: navigation, search
(Download)
 
(14 intermediate revisions by one other user not shown)
Line 7: Line 7:
 
Users can download the latest release of OWASP CSRFGuard using one of the following links:
 
Users can download the latest release of OWASP CSRFGuard using one of the following links:
  
:[TBD Latest Stable Binary] - download the latest stable binary and associated configuration files (recommended).
+
Download and build the source at - https://github.com/aramrami/OWASP-CSRFGuard
:[TBD Latest Stable Source] - download the latest stable archive of the project source code.
 
  
 
= Installation =
 
= Installation =
Line 15: Line 14:
  
 
:# Copy the Owasp.CsrfGuard.jar file to your application's classpath
 
:# Copy the Owasp.CsrfGuard.jar file to your application's classpath
:# Map the CsrfGuardFilter in your application's deployment descriptor (web.xml)
+
:# Declare CsrfGuard in your application's deployment descriptor (web.xml)
 
:# Configure the Owasp.CsrfGuard.properties file as you see fit
 
:# Configure the Owasp.CsrfGuard.properties file as you see fit
  
Line 33: Line 32:
 
= Token Injection =
 
= Token Injection =
  
JavaScript DOM Manipulation requires minimal effort on behalf of the developer and is ideal for most web based applications. The JSP tag library should be utilized in situations where the JavaScript DOM Manipulation token injection strategy is found to be technically insufficient. Together, the JavaScript DOM Manipulation and the JSP tag library provide strong and fine grain means of integrating CSRF prevention tokens within application presentation logic.
+
Users of OWASP CSRFGuard can inject prevention tokens into HTML using two strategies:
 +
 
 +
:* JavaScript DOM Manipulation - largely automated process requiring minimal effort and is ideal for most web applications
 +
:* JSP Tag Library - provides fine grained strategy ideal for situations where automated DOM manipulation is insufficient.
  
 
[[CSRFGuard_3_Token_Injection | Click here]] for more information regarding the injection of CSRF prevention tokens within your application.
 
[[CSRFGuard_3_Token_Injection | Click here]] for more information regarding the injection of CSRF prevention tokens within your application.
 +
 +
= Known Issues =
 +
 +
The following is a quick bulleted list of known issues within the current release:
 +
 +
:* No known way to inject CSRF prevention tokens into setters of document.location (ex: document.location="http://www.owasp.org";)
  
 
[[Category:OWASP_CSRFGuard_Project]]
 
[[Category:OWASP_CSRFGuard_Project]]

Latest revision as of 11:37, 23 January 2014

Overview

Welcome to the OWASP CSRFGuard 3 User Manual! The purpose of this article is to provide the user with guidance on obtaining, installing, deploying, and developing with the OWASP CSRFGuard library. The author's goal was to keep the User Manual informative, use to understand, and concise. If you find that one or more aspects of this document does not adhere to these goals, please me know at eric dot sheridan at owasp dot org.

Download

Users can download the latest release of OWASP CSRFGuard using one of the following links:

Download and build the source at - https://github.com/aramrami/OWASP-CSRFGuard

Installation

Installation of OWASP CSRFGuard 3 is very straight forward requiring three simple steps:

  1. Copy the Owasp.CsrfGuard.jar file to your application's classpath
  2. Declare CsrfGuard in your application's deployment descriptor (web.xml)
  3. Configure the Owasp.CsrfGuard.properties file as you see fit

Click here for more detailed information regarding the installation of OWASP CSRFGuard.

Configuration

The minimum configuration settings that users should review include:

  • Default new token landing page (org.owasp.csrfguard.NewTokenLandingPage)
  • Support for Ajax and XMLHttpRequest (org.owasp.csrfguard.Ajax)
  • URI resources that should not be protected (org.owasp.csrfguard.unprotected.*)
  • Actions executed when an attack is detected (org.owasp.csrfguard.action.*)

Click here for more information regarding the configuration of OWASP CSRFGuard.

Token Injection

Users of OWASP CSRFGuard can inject prevention tokens into HTML using two strategies:

  • JavaScript DOM Manipulation - largely automated process requiring minimal effort and is ideal for most web applications
  • JSP Tag Library - provides fine grained strategy ideal for situations where automated DOM manipulation is insufficient.

Click here for more information regarding the injection of CSRF prevention tokens within your application.

Known Issues

The following is a quick bulleted list of known issues within the current release:

  • No known way to inject CSRF prevention tokens into setters of document.location (ex: document.location="http://www.owasp.org";)