Category:OWASP Enterprise Security API

Home
{| width="100%" ! width="33%" | ! width="33%" | ! width="33%" |
 * - valign="top"

Let's talk here
ESAPI Communities

Further development of ESAPI occurs through mailing list discussions and occasional workshops, and suggestions for improvement are welcome. For more information, please [mailto:jeff.williams@owasp.org contact us].


 * esapi-user mailing list (this is the main list)
 * esapi-dev mailing list
 * esapi-php mailing list
 * esapi-python mailing list
 * esapi-summit mailing list



Got developer cycles?
ESAPI Coding

The ESAPI project is always on the lookout for volunteers who are interested in contributing developer cycles.


 * ESAPI for PHP Developer Onboarding Instructions
 * ESAPI for other languages developer onboarding instructions -- coming soon!



Related resources
OWASP Resources


 * OWASP Top Ten
 * OWASP Application Security Verification Standard
 * OWASP Development Guide
 * OWASP Legal Project
 * SQL Injection Prevention Cheat Sheet
 * XSS (Cross Site Scripting) Prevention Cheat Sheet
 * OWASP Press Releases


 * }

Here's what I did with ESAPI

 * I used ESAPI for Java with Google AppEngine. I used it for simple validation and encoding. --[mailto:jeff.williams@owasp.org Jeff]


 * I used ESAPI for PHP with a custom web 2.0 corporate knowledge management application, made up of many open source and commercial applications integrated to work together. I added an organization- and application-specific "Adapter" control to wrap calls to the other ESAPI controls. --[mailto:mike.boberski@owasp.org Mike]


 * I used ESAPI for Java’s "Logger" control to make it easier for a US Government customer to meet C&A requirements. --[mailto:dave.wichers@owasp.org Dave]

Glossary
ESAPI Terminology


 * adapter - There are optionally your own implementations for each security control. There may be application logic contained in these classes which may be developed by or for your organization. The logic may be organization-specific and/or application-specific. There may be proprietary information or logic contained in these classes which may be developed by or for your organization.
 * built-in singleton design pattern - The "built-in" singleton design pattern refers to the replacement of security control reference implementations with your own implementations. ESAPI interfaces are otherwise left intact.
 * codec - ESAPI encoder/decoder reference implementations.
 * core - The ESAPI interfaces and reference implementations that are not intended to be replaced with enterprise-specific versions are called the ESAPI Core.
 * exception - ESAPI exception reference implementations.
 * extended factory design pattern - The "extended" factory design pattern refers to the addition of a new security control interface and corresponding implementation, which in turn calls ESAPI security control reference implementations and/or security control reference implementations that were replaced with your own implementations. The ESAPI locator class would be called in order to retrieve a singleton instance of your new security control, which in turn would call ESAPI security control reference implementations and/or security control reference implementations that were replaced with your own implementations.
 * extended singleton design pattern - The "extended" singleton pattern refers to the replacement of security control reference implementations with your own implementations and the addition/modification/subtraction of corresponding security control interfaces.
 * ES-enable (or ESAPI-enable) - Just as web applications and web services can be Public Key Infrastructure (PKI) enabled (PK-enabled) to perform for example certificate-based authentication, applications and services can be OWASP ESAPI-enabled (ES-enabled) to enable applications and services to protect themselves from attackers.
 * filter - In ESAPI for Java, there is additionally an HTTP filter that can be called separately from the other controls.
 * interfaces - There is a set of security control interfaces. There is no application logic contained in these interfaces. They define for example types of parameters that are passed to types of security controls. There is no proprietary information or logic contained in these interfaces.
 * locator - The ESAPI security control interfaces include an "ESAPI" class that is commonly referred to as a "locator" class. The ESAPI locator class is called in order to retrieve singleton instances of individual security controls, which are then called in order to perform security checks (such as performing an access control check) or that result in security effects (such as generating an audit record).
 * reference implementation - There is a reference implementation for each security control. There is application logic contained in these classes, i.e. contained in these interface implementations. However, the logic is not organization-specific and the logic is not application-specific. There is no proprietary information or logic contained in these reference implementation classes.
 * Web Application Firewall (WAF) - In ESAPI for Java, there is additionally a Web Application Firewall (WAF) that can be called separately from the other controls.

Project Details
''This project licensed under the BSD license, which is very permissive and about as close to public domain as is possible. You can use or modify ESAPI however you want, even include it in commercial products.''