Category:OWASP Enterprise Security API

From OWASP

(Redirected from ESAPI)

About
FAQ
Java EE
.NET
Classic ASP
PHP
ColdFusion/CFML
Python
JavaScript
Haskell
News
Contributors/Users


OWASP Tools Project Enterprise Security API (ESAPI) OWASP Enterprise Security API Toolkits help software developers guard against security-related design and implementation flaws. Our motto is NO GUTS NO GLORY! How ESAPI Works Where To Go From Here Start Here Please take a brief moment to take this survey and let the ESAPI Development Team know how we are doing Click here to take survey	Sample Application - ESAPI Swingset The ESAPI Swingset sample application is under development. Many lessons have been completed that demonstrate how to leverage ESAPI to protect a web application. It also demonstrates the flaws web applications can have if they are not ESAPI-enabled.

OWASP Tools Project

Enterprise Security API (ESAPI)

OWASP Enterprise Security API Toolkits help software developers guard against security-related design and implementation flaws. Our motto is NO GUTS NO GLORY!

How ESAPI Works

Where To Go From Here

Start Here

Please take a brief moment to take this survey and let the ESAPI Development Team know how we are doing

Click here to take survey

Sample Application - ESAPI Swingset

The ESAPI Swingset sample application is under development.
- Many lessons have been completed that demonstrate how to leverage ESAPI to protect a web application.
- It also demonstrates the flaws web applications can have if they are not ESAPI-enabled.


Start Here 1. About ESAPI Introduction to ESAPI (PDF, Word) Project presentation (PowerPoint) Video presentation (YouTube) 2. Get ESAPI ESAPI for Java EE ESAPI for .NET ESAPI for Classic ASP ESAPI for PHP ESAPI for ColdFusion & CFML ESAPI for Python ESAPI for Haskell ESAPI for Javascript 3. Learn ESAPI ESAPI design patterns (not language-specific): (PDF, Word, PPT) ESAPI for .NET design notes (Blog) 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) Related Resources OWASP Top Ten OWASP Application Security Verification Standard XSS (Cross Site Scripting) Prevention Cheat Sheet	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 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? The ESAPI project is always on the lookout for volunteers who are interested in contributing developer cycles. ESAPI for PHP Developer Onboarding Instructions	Glossary 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.

.NET Edition of the OWASP ESAPI Toolkit - Version 0.2 is released

The .NET version of ESAPI is being lead by Alex Smolen. Feel free to contact him at (me AT AlexSmolen DOT com) for more information.
If you're interested in application security, please join the OWASP ESAPI mailing list and help make ESAPI better!

OWASP ESAPI - .NET Edition ReadMe

Release 0.2: August 2009

Welcome to the .NET Edition of OWASP ESAPI v0.2

This document provides information about the .NET Edition of OWASP ESAPI. The topics below cover system requirements, additional product information, and application notes.

The code for the ESAPI is currently in Google Code.

Download the latest .NET ESAPI library binary from Google Code here.

Download the latest .NET ESAPI documentation from Google Code here. It is a zipped .chm (help) file.

You can also browse the .NET ESAPI documentation here

To download and work with the source you must use an SVN tool.

AnkhSVN is a free SVN tool that integrates with Visual Studio. Point your SVN tool at http://owasp-esapi-dotnet.googlecode.com/svn/trunk. Anonymous checkout is supported.

You can also browse the source.

System Requirements

The solution is created with VS 2008 and .NET 3.5. However, the actual code should be compatible with .NET 2.0, so it should be simple to get the code to compile in most environments. Troubleshooting

Other Requirements

The .NET Edition of OWASP ESAPI includes a reference implementation which may be tailored or replaced, according to your organization's needs.

You must also download download and install the latest version of the AntiXss library.

Server Recommendations

None

Obtaining the .NET Edition of OWASP ESAPI

There are a couple of ways to get started with the .NET ESAPI.

If you simply want to start using the functionality, you can download the assembly from [ Google Code]. You will also need to add the appropriate configuration (see here).

You can download the solution from Google Code with SVN.

You will need to download and install the AntiXss library separately, in order to respect the code licensing.

The SwingSet application requires you to login - just register a username and go. You also need to supply a SMTP host in the web.config file in SwingSet in order to register a user, so that you can get an activation email. I might change this in the released version, since it's sort of a pain. You can just use the external SMTP server for an email account you own and use that - i.e.

   <mailSettings>
     <smtp from="dot-net-esapi@owasp.com">
       <network
            host="you fill this part in, for example d.mx.mail.yahoo.com for a yahoo.com mail account"
            port="25"
            />
     </smtp>
   </mailSettings>

OWASP ESAPI - .NET Edition Release Notes

Release 0.2

August 2009

Welcome to the .NET Edition of OWASP ESAPI v0.2

This document provides information about .NET Edition of OWASP ESAPI v0.2. Browse through the topics below to find out about new features, known issues and limitations for this release.

Information specific to the changes in this release are captured in this document set. For all other information and for feature details, see the ESAPI <version> programming manual.

New features

This release improve significanlty on the first release. The following components have been redesigned and reimplemented:

AccessController
AccessReferenceMap
Encoder
Encryptor
Esapi
HttpUtilities
IntrusionDetector
Logger
Randomizer
SecurityConfiguration
Validator

The SwingSet application has also been introduced, to demonstrate how to use the ESAPI as well as showcase other ASP.NET security best practices.

Fixed in this release

All components have been redesigned - there have been major changes since v0.1.

Known issues

Canonicalization support is incomplete - only some Codecs support decoding.
There are only a few ValidationRules.
AccessController implementation does not provide policy storage.

Upgrading from earlier releases

This version is an entirely different code base. Please completely upgrade all existing implementations.


Project Leader Jeff Williams Project Contributors Jim Manico (Project Manager) Dave Wichers Arshan Dabirsiaghi Jerry Hoff Chris Schmidt Kevin W. Wall Mike Boberski (Documentation Lead) The ESAPI project is sponsored by:	Users and Adopters 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 Galois Foundstone(McAfee) The Hartford Infinite Campus Lockheed Martin MITRE Nationwide Insurance 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.

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.

Pages in category "OWASP Enterprise Security API"

The following 23 pages are in this category, out of 23 total.

A

Agile Software Development: Don't Forget EVIL User Stories

C

E

E cont.

I

Injection Prevention Cheat Sheet

J

JavaEE Enterprise Security API 2 Release Notes

P

Category:OWASP Enterprise Security API

From OWASP

Start Here

Related Resources

Let's Talk Here

Got Developer Cycles?

Glossary

Pages in category "OWASP Enterprise Security API"

A

C

E

E cont.

I

J

P

S

T

U

X

Views

Personal tools

search

Navigation

Reference

Language

Toolbox