|
|
| Line 47: |
Line 47: |
| | *[https://lists.owasp.org/mailman/listinfo/owasp-esapi-ruby esapi-ruby mailing list] | | *[https://lists.owasp.org/mailman/listinfo/owasp-esapi-ruby esapi-ruby mailing list] |
| | *[https://lists.owasp.org/mailman/listinfo/owasp-esapi-swingset esapi-swingset mailing list] | | *[https://lists.owasp.org/mailman/listinfo/owasp-esapi-swingset esapi-swingset mailing list] |
| | + | |
| | + | IRC Chat |
| | + | |
| | + | If you would rather chat with us about your problem or thoughts - you can join us in our IRC channel using an [http://www.google.com/search?q=irc+client IRC Client] or using FreeNode's [http://webchat.freenode.net WebChat] client. |
| | + | |
| | + | *Server: irc.freenode.net |
| | + | *Channel: #esapi |
| | | | |
| | | | | | |
Revision as of 05:47, 17 June 2011
Home
|
|
|
|
ESAPI (The OWASP Enterprise Security API) is a free, open source, web application security control library that makes it easier for programmers to write lower-risk applications. The ESAPI libraries are designed to make it easier for programmers to retrofit security into existing applications. The ESAPI libraries also serve as a solid foundation for new development.
Allowing for language-specific differences, all OWASP ESAPI versions have the same basic design:
- There is a set of security control interfaces. They define for example types of parameters that are passed to types of security controls.
- There is a reference implementation for each security control. The logic is not organization‐specific and the logic is not application‐specific. An example: string‐based input validation.
- 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. An example: enterprise authentication.
This project source code is licensed under the BSD license, which is very permissive and about as close to public domain as is possible. The project documentation is licensed under the Creative Commons license. You can use or modify ESAPI however you want, even include it in commercial products.
The following organizations are a few of the many organizations that are starting to adopt ESAPI to secure their web applications: American Express, Apache Foundation, Booz Allen Hamilton, Aspect Security, Foundstone(McAfee), The Hartford, Infinite Campus, Lockheed Martin, MITRE, U.S. Navy - SPAWAR, The World Bank, SANS Institute.
Please let us know how your organization is using OWASP ESAPI. Include your name, organization's name, and brief description of how you are using it. The project lead can be reached here. The project maintainer can be reached here.
|
|
|
|
|
|
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 subscribe to one of the lists below.
IRC Chat
If you would rather chat with us about your problem or thoughts - you can join us in our IRC channel using an IRC Client or using FreeNode's WebChat client.
- Server: irc.freenode.net
- Channel: #esapi
|
Got developer cycles?
 ESAPI Coding
The ESAPI project is always on the lookout for volunteers who are interested in contributing developer cycles.
|
Related resources
 OWASP Cheat Sheet Series
|
Downloads
|
|
|
|
 1. About ESAPI
 2. Get ESAPI
|
 3. Learn ESAPI
- ESAPI design patterns (not language-specific): (PDF, Word, PPT)
- The ESAPI Swingset sample application demonstrates how to leverage ESAPI to protect a web application.
- LAMP should be spelled LAMPE (PDF)
- ESAPI for Java interface documentation (JavaDocs)
- ESAPI for PHP interface documentation (phpdoc)
|
Here's what I did with ESAPI
- I used ESAPI for Java with Google AppEngine. I used it for simple validation and encoding. --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. --Mike
- I used ESAPI for Java’s "Logger" control to make it easier for a US Government customer to meet C&A requirements. --Dave
- I used ESAPI for Java to build a low risk web application that was over 250,000+ lines of code in size. --Jim
- I used ESAPI for Java's "Authenticator" to replace a spaghetti-like mechanism in a legacy financial services web application. In hindsight I should have used the application-specific "Adapter" pattern mentioned by Mike above. The organization also uses the ESAPI Encryptor as an interface to a hardware security module. --Roman
- I use ESAPI for Java to educate developers about application security principals at several of the world’s largest organizations. --Jim
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.
Java EE
PROJECT INFO
What does this OWASP project offer you?
|
RELEASE(S) INFO
What does this OWASP project release offer you?
|
| what
|
is this project?
|
| OWASP ESAPI for Java EE
Purpose: This is the Java EE language version of OWASP ESAPI. The ESAPI for Java EE is the baseline ESAPI design.
License: BSD license
|
| who
|
is working on this project?
|
Project Leader: Kevin Wall & Matt Seil @
Project Maintainer: ESAPI-Dev mailing list @
Project Contributor(s):
|
| how
|
can you learn more?
|
| Project Pamphlet: N/A
3x slide Project Presentation: N/A
Mailing list: Subscribe or read the archives
Project Roadmap: N/A
Main links:
Project Health:  Not Reviewed (Provisional)
To be reviewed under Assessment Criteria v2.0
|
|
|
| Key Contacts
|
|
- Contact Kevin Wall & Matt Seil @ to contribute, review or sponsor this project
- Contact the GPC to report a problem or concern about this project or to update information.
|
|
|
.NET
PROJECT INFO
What does this OWASP project offer you?
|
| what
|
is this project?
|
| OWASP ESAPI for .NET
Purpose: This is the .NET language version of OWASP ESAPI.
License: BSD license
|
| who
|
is working on this project?
|
Project Leader: None
Project Maintainer: Michael Weber @
Project Contributor(s):
|
| how
|
can you learn more?
|
| Project Pamphlet: N/A
3x slide Project Presentation: N/A
Mailing list: Subscribe or read the archives
Project Roadmap: N/A
Main links:
Project Health: Not Reviewed (Provisional)
To be reviewed under Assessment Criteria v2.0
|
|
|
| Key Contacts
|
|
- Contact None to contribute, review or sponsor this project
- Contact the GPC to report a problem or concern about this project or to update information.
|
|
|
Classic ASP
PROJECT INFO
What does this OWASP project offer you?
|
| what
|
is this project?
|
| OWASP ESAPI for Classic ASP
Purpose: This is the Microsoft Classic ASP 3.x language version of OWASP ESAPI.
- The current release of this project is not suitable for production use
License: BSD license
|
| who
|
is working on this project?
|
Project Leader: Juan Carlos Calderon @
Project Maintainer: Juan Carlos Calderon @
Project Contributor(s): N/A
|
| how
|
can you learn more?
|
| Project Pamphlet: N/A
3x slide Project Presentation: N/A
Mailing list: Subscribe or read the archives
Project Roadmap: [[:ESAPI for Classic ASP is currently "mounted" on ESAPI for .NET using interop, however the prevalence of random errors in the technology had make it non usable in real world. Starting on December 2010, the API will be re-written completely to ActiveX objects to avoid any issue related to interop and to other dependencies (.NET Framework) | To view, click here]]
Main links:
Project Health: Not Reviewed (Provisional)
To be reviewed under Assessment Criteria v2.0
|
|
|
| Key Contacts
|
|
- Contact Juan Carlos Calderon @ to contribute, review or sponsor this project
- Contact the GPC to report a problem or concern about this project or to update information.
|
|
|
PHP
PROJECT INFO
What does this OWASP project offer you?
|
| what
|
is this project?
|
| OWASP ESAPI for PHP
Purpose: This is the PHP language version of OWASP ESAPI.
- The current release of this project is not suitable for production use
License: BSD license
|
| who
|
is working on this project?
|
Project Leader: Andrew van der Stock @
Project Maintainer:
Project Contributor(s):
|
| how
|
can you learn more?
|
| Project Pamphlet: N/A
3x slide Project Presentation: N/A
Mailing list: Subscribe or read the archives
Project Roadmap: N/A
Main links:
Project Health: Not Reviewed (Provisional)
To be reviewed under Assessment Criteria v2.0
|
|
|
| Key Contacts
|
|
- Contact Andrew van der Stock @ to contribute, review or sponsor this project
- Contact the GPC to report a problem or concern about this project or to update information.
|
|
|
ColdFusion/CFML
PROJECT INFO
What does this OWASP project offer you?
|
| what
|
is this project?
|
| OWASP ESAPI for ColdFusion/CFML
Purpose: This is the ColdFusion/CFML language version of OWASP ESAPI.
License: BSD license
|
| who
|
is working on this project?
|
Project Leader: Jason Dean @
Project Maintainer:
Project Contributor(s):
|
| how
|
can you learn more?
|
| Project Pamphlet: N/A
3x slide Project Presentation: N/A
Mailing list: N/A
Project Roadmap: N/A
Main links:
Project Health: Not Reviewed (Provisional)
To be reviewed under Assessment Criteria v2.0
|
|
|
| Key Contacts
|
|
- Contact Jason Dean @ to contribute, review or sponsor this project
- Contact the GPC to report a problem or concern about this project or to update information.
|
|
|
Python
PROJECT INFO
What does this OWASP project offer you?
|
| what
|
is this project?
|
| OWASP ESAPI for Python
Purpose: This is the Python language version of OWASP ESAPI.
- The current release of this project is not suitable for production use
License: BSD license
|
| who
|
is working on this project?
|
Project Leader: Craig Younkins @
Project Maintainer:
Project Contributor(s): N/A
|
| how
|
can you learn more?
|
| Project Pamphlet: N/A
3x slide Project Presentation: N/A
Mailing list: N/A
Project Roadmap: N/A
Main links:
Project Health: Not Reviewed (Provisional)
To be reviewed under Assessment Criteria v2.0
|
|
|
| Key Contacts
|
|
- Contact Craig Younkins @ to contribute, review or sponsor this project
- Contact the GPC to report a problem or concern about this project or to update information.
|
|
|
JavaScript
PROJECT INFO
What does this OWASP project offer you?
|
| what
|
is this project?
|
| OWASP ESAPI for JavaScript
Purpose: This is the JavaScript language version of OWASP ESAPI.
- The current release of this project is not suitable for production use
License: BSD license
|
| who
|
is working on this project?
|
Project Leader: Chris Schmidt
Project Maintainer:
Project Contributor(s): N/A
|
| how
|
can you learn more?
|
| Project Pamphlet: N/A
3x slide Project Presentation: N/A
Mailing list: N/A
Project Roadmap: N/A
Main links:
Project Health: Not Reviewed (Provisional)
To be reviewed under Assessment Criteria v2.0
|
|
|
| Key Contacts
|
|
- Contact Chris Schmidt to contribute, review or sponsor this project
- Contact the GPC to report a problem or concern about this project or to update information.
|
|
|
Objective C
PROJECT INFO
What does this OWASP project offer you?
|
RELEASE(S) INFO
What releases are available for this project?
|
| what
|
is this project?
|
| Name: OWASP ESAPI Objective - C Project (home page)
|
Purpose: The OWASP ESAPI Objective-C is the Objective-C (Cocoa) implementation of ESAPI.
- The current release of this project is not suitable for production use
|
| License: BSD License
|
| who
|
is working on this project?
|
| Project Leader(s):
|
| how
|
can you learn more?
|
| Project Pamphlet: Not Yet Created
|
| Project Presentation:
|
| Mailing list: Mailing List Archives
|
| Project Roadmap: View
|
| Main links:
|
| Key Contacts
|
|
|
|
|
|
Force.com
PROJECT INFO
What does this OWASP project offer you?
|
| what
|
is this project?
|
| OWASP ESAPI for Force.com
Purpose: This is the Force.com language version of OWASP ESAPI.
- The current release of this project is suitable for production use
License: New BSD license
|
| who
|
is working on this project?
|
Project Leader: Yoel Gluck (securecloud .at. salesforce.com)
Project Maintainer: Jonathan Rico
Project Contributor(s): N/A
|
| how
|
can you learn more?
|
| Project Pamphlet: N/A
3x slide Project Presentation: N/A
Mailing list: N/A
Project Roadmap: N/A
Main links:
Project Health: Not Reviewed (Provisional)
To be reviewed under Assessment Criteria v2.0
|
|
|
| Key Contacts
|
|
|
|
|
|
Ruby
PROJECT INFO
What does this OWASP project offer you?
|
RELEASE(S) INFO
What releases are available for this project?
|
| what
|
is this project?
|
| Name: Owasp Esapi Ruby (home page)
|
| Purpose: The Owasp Esapi Ruby is a port for outstanding release quality Owasp Esapi project to the Ruby programming language. The idea is to build a Ruby gem (the standard ruby library archive format) containing the Esapi concepts implemented in Ruby classes so people using Ruby in their Rails application can have security into them.
|
| License: BSD license
|
| who
|
is working on this project?
|
| Project Leader(s):
|
| Project Contributor(s):
|
| how
|
can you learn more?
|
| Project Pamphlet: Not Yet Created
|
| Project Presentation:
|
| Mailing list: Mailing List Archives
|
| Project Roadmap: View
|
| Main links:
|
| Key Contacts
|
|
|
|
|
| current release
|
|
|
| Owasp Esapi Ruby v0.30.0 - March 2011 - (download)
|
Release description:
- The OWASP Esapi Ruby gem will require at least version 1.9.2 of Ruby interpreter to make sure to have full advantages of the newer language APIs. In particular version 1.9.2 introduces radical changes in the following areas:
- Regular expression engine (to be written)
- UTF-8 support
- Unicode support in 1.9.2 is much better and provides better support for character set encoding/decoding
- All strings have an additional chunk of info attached: Encoding
- String#size takes encoding into account – returns the encoded character count
- You can get the raw datasize
- Indexed access is by encoded data – characters, not bytes
- You can change encoding by force but it doesn’t convert the data
- Dates and Time
- From “Programming Ruby 1.9“
- “As of Ruby 1.9.2, the range of dates that can be represented is no longer limited by the under- lying operating system’s time representation (so there’s no year 2038 problem). As a result, the year passed to the methods gm, local, new, mktime, and utc must now include the century—a year of 90 now represents 90 and not 1990.“
|
| Rating: Not Reviewed - Assessment Details
|
|
|
| last reviewed release
|
| Not Yet Reviewed
|
|
|
Swingset
The ESAPI Swingset Project divides itself into sub-projects, i.e., Swingset Interactive and Swingset Demo.
Project Details
PROJECT INFO
What does this OWASP project offer you?
|
| what
|
is this project?
|
| OWASP Enterprise Security API
Purpose: ESAPI (The OWASP Enterprise Security API) is a free, open source, web application security control library that makes it easier for programmers to write lower-risk applications. The ESAPI libraries are designed to make it easier for programmers to retrofit security into existing applications. The ESAPI libraries also serve as a solid foundation for new development. Allowing for language-specific differences, all OWASP ESAPI versions have the same basic design:
- There is a set of security control interfaces. They define for example types of parameters that are passed to types of security controls.
- There is a reference implementation for each security control. The logic is not organization‐specific and the logic is not application‐specific. An example: string‐based input validation.
- 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. An example: enterprise authentication.
License: BSD license
|
| who
|
is working on this project?
|
Project Leader: Kevin W. Wall and Matt Seil @
Project Maintainer:
Project Contributor(s):
- Jeremiah J. Stacey
- Chris Schmidt @
- Jeff Williams
- Dave Wichers
- John Steven
|
| how
|
can you learn more?
|
| Project Pamphlet: View
3x slide Project Presentation: View
Mailing list: Subscribe or read the archives
Project Roadmap: N/A
Main links:
Project Health: Not Reviewed (Provisional)
To be reviewed under Assessment Criteria v2.0
|
|
|
| Key Contacts
|
|
- Contact Kevin W. Wall and Matt Seil @ to contribute, review or sponsor this project
- Contact the GPC to report a problem or concern about this project or to update information.
|
|
|
Pages in category "OWASP Enterprise Security API"
The following 27 pages are in this category, out of 27 total.
ESAPI Terminology
