This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit

Difference between revisions of "Category:OWASP Enterprise Security API"

Jump to: navigation, search
(Download Now)
(OWASP Enterprise Security API (ESAPI) Project)
Line 1: Line 1:
{{ infobox software
| logo                  = [[Image:MySQL.svg|180px]]
| developer              = [[MySQL AB]]
| released              = {{initial release|1995|05|23}}
| frequently updated    = yes
| programming language  = [[C (programming language)|C]], [[C++]]
| operating system      = [[Cross-platform]]
| language              = English
| genre                  = [[Relational database management system]]
| license                = [[GNU General Public License]] (version 2) or proprietary [[EULA]]
| website                =
=OWASP Enterprise Security API (ESAPI) Project=
=OWASP Enterprise Security API (ESAPI) Project=

Revision as of 13:37, 15 September 2008

Template:Infobox software

OWASP Enterprise Security API (ESAPI) Project

The ESAPI is a free and open collection of all the security methods that a developer needs to build a secure web application. You can just use the interfaces and build your own implementation using your company's infrastructure. Or, you can use the reference implementation as a starting point. In concept, the API is language independent. However, the first deliverables from the project are a Java API and a Java reference implementation. Efforts to build ESAPI in .NET and PHP are already underway.

Unfortunately, the available platforms, frameworks, and toolkits (Java EE, Struts, Spring, etc...) simply do not provide enough protection. This leaves developers with responsibility for designing and building security mechanisms. This reinventing the wheel for every application leads to wasted time and massive security holes.

The cost savings through reduced development time, and the increased security due to using heavily analyzed and carefully designed security methods provide developers with a massive advantage over organizations that are trying to deal with security using existing ad hoc secure coding techniques. This API is designed to automatically take care of many aspects of application security, making these issues invisible to the developers.

The OWASP ESAPI project is led by Jeff Williams, who serves as the volunteer chair of OWASP and is the CEO of Aspect Security. Jeff is a software developer who has specialized in application security since 1995. The ESAPI is the result of over a decade of code review and penetration testing of critical enterprise applications. If you'd like to volunteer to help on the project, you can contact him at

Download Now

This release is the first public release and will undoubtably undergo significant revision over the coming months. We are seeking organizations willing to pilot this ESAPI and work with us to make this library better. Please contact for more information. If you're interested in application security, please join the OWASP ESAPI mailing list and help make ESAPI better!

Latest Version (archive versions are posted in code repository)

Getting Started


The ESAPI architecture is very simple, just a collection of classes that encapsulate the key security operations most applications need. ESAPI is designed to make it easy to retrofit security into existing applications, as well as providing a solid foundation for new development. New development projects should consider integrating ESAPI into their framework to make even more of the security happen automatically. ESAPI comes with an ESAPI filter that minimizes the changes required to your base application.


The ESAPI covers most of the key security challenges facing application developers. ESAPI provides the capability for developers to create applications that are protected against almost all of the risks described in the OWASP Top Ten. Compare this coverage with automated scanning and static analysis tools, and then consider how your time is best spent.


There are two key parts to the ESAPI:

  • A set of interfaces
  • A reference implementation

By using the ESAPI, applications across an organization will be easier to develop, more consistent, and easier to update in a single place. The use of the ESAPI will make it much easier for static analysis tools to verify an application, as the ESAPI calls can be built into the ruleset.

Project Sponsors

The OWASP ESAPI project is sponsored by Aspect_logo.gif


This project is dual-licensed under GPL and BSD. Pick whichever one fits your corporate policy...[JFM]