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
Line 20: Line 20:
 
Prior to discarding the request, CSRFGuard can be configured to take one or more actions such as logging aspects of the request and redirecting the user to a landing page.  
 
Prior to discarding the request, CSRFGuard can be configured to take one or more actions such as logging aspects of the request and redirecting the user to a landing page.  
 
The latest release enhances this strategy to support the optional verification of HTTP requests submitted using Ajax as well as the optional verification of referrer headers.
 
The latest release enhances this strategy to support the optional verification of HTTP requests submitted using Ajax as well as the optional verification of referrer headers.
 +
 +
[[File:CSRGuard.PNG]]
  
  

Revision as of 11:49, 16 February 2014

OWASP Project Header.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

When a user interacts with this HTML, CSRF prevention tokens (i.e. cryptographically random synchronizer tokens) are submitted with the corresponding HTTP request. It is the responsibility of OWASP CSRFGuard to ensure the token is present and is valid for the current HTTP request. Any attempt to submit a request to a protected resource without the correct corresponding token is viewed as a CSRF attack in progress and is discarded. Prior to discarding the request, CSRFGuard can be configured to take one or more actions such as logging aspects of the request and redirecting the user to a landing page. The latest release enhances this strategy to support the optional verification of HTTP requests submitted using Ajax as well as the optional verification of referrer headers.

CSRGuard.PNG


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.

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.

Presentation

Link to presentation

Project Leader

The CSRFGuard project is run by Azzeddine RAMRAMI. He can be contacted at azzeddine.ramrami AT owasp.org.

Related Projects

Quick Download

Download and build the latest source code from GitHub :

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

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

User Manual(s)

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

News and Events

  • [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


In Print

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

Classifications

Project Type Files CODE.jpg

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, a Security Engineer at Citrix Systems, where he works on end-to-end penetration testing to researching exotic security topics to creating threat models. He has an above average interest in client-side security and network security.

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.