OWASP - User contributions [en]

HTTP Strict Transport Security

2014-07-10T13:55:27Z

User talk:Laurence Casey

2012-01-18T16:26:37Z

Laurence Casey:

Aspect Security, Inc.
http://www.aspectsecurity.com

= Home\TEST =

{| width="100%"
|-
! width="66%" |
! width="33%" |
|- valign="top"
|
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 [http://en.wikipedia.org/wiki/BSD_license BSD license], which is very permissive and about as close to public domain as is possible. The project documentation is licensed under the [http://creativecommons.org/licenses/by-sa/2.0/ 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: [http://www.americanexpress.com/ American Express], [http://www.apache.org/ Apache Foundation], [http://www.boozallen.com Booz Allen Hamilton], [http://www.aspectsecurity.com/ Aspect Security], [http://www.foundstone.com Foundstone(McAfee)], [http://www.thehartford.com/ The Hartford], [http://www.infinitecampus.com Infinite Campus], [http://www.lockheedmartin.com/ Lockheed Martin], [http://cwe.mitre.org/top25/index.html MITRE], [http://enterprise.spawar.navy.mil/ U.S. Navy - SPAWAR], [http://www.worldbank.org/ The World Bank], [http://www.sans.org/top25errors/ 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 [mailto:jeff.williams@owasp.org here]. The project maintainer can be reached [mailto:jim.manico@owasp.org here].

|
[[Image:Esapi-sponsors.PNG]]

|}

{| width="100%"
|-
! width="33%" |
! width="33%" |
! width="33%" |
|- valign="top"
|
== Let's talk here ==

[[Image:Asvs-bulb.jpg]]'''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.

*[https://lists.owasp.org/mailman/listinfo/esapi-dev esapi-dev mailing list (this is the main list)]
*[https://lists.owasp.org/mailman/listinfo/esapi-user esapi-user mailing list]
*[https://lists.owasp.org/mailman/listinfo/esapi-php esapi-php mailing list]
*[https://lists.owasp.org/mailman/listinfo/esapi-python esapi-python 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]
*[http://groups.google.com/group/cfesapi esapi-coldfusion 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

|

== Got developer cycles? ==

[[Image:Asvs-waiting.JPG]]'''ESAPI Coding'''

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

*[http://owasp-esapi-php.googlecode.com/files/esapi4php-contributing.pdf ESAPI for PHP Developer Onboarding Instructions]
*ESAPI for other languages developer onboarding instructions -- coming soon!

|
== Related resources ==

[[Image:Asvs-satellite.jpg]]'''OWASP Cheat Sheet Series'''

*[[SQL Injection Prevention Cheat Sheet]]
*[[XSS (Cross Site Scripting) Prevention Cheat Sheet]]
*[[Cryptographic Storage Cheat Sheet]]
*[[Authentication Cheat Sheet]]
*[[Cross-Site Request Forgery (CSRF) Prevention Cheat Sheet]]
*[[Transport Layer Protection Cheat Sheet]]

|}

= Downloads =

{| width="100%"
|-
! width="33%" |
! width="33%" |
|- valign="top"
|
[[Image:Asvs-step1.jpg]]'''1. About ESAPI'''

*Data sheet([http://www.owasp.org/images/8/81/Esapi-datasheet.pdf PDF],[http://www.owasp.org/images/3/32/Esapi-datasheet.doc Word])
*Project presentation ([http://owasp-esapi-java.googlecode.com/files/OWASP%20ESAPI.ppt PowerPoint])
*Video presentation ([http://www.youtube.com/watch?v=QAPD1jPn04g YouTube])

[[Image:Asvs-step2.jpg]]'''2. Get ESAPI'''

*[http://code.google.com/p/owasp-esapi-java/downloads/list ESAPI for Java Downloads]
*{{#switchtablink:.NET|ESAPI for .NET}} 
*{{#switchtablink:Classic ASP|ESAPI for Classic ASP}} 
*{{#switchtablink:PHP|ESAPI for PHP}} 
*{{#switchtablink:ColdFusion.2FCFML|ESAPI for ColdFusion & CFML}} 
*{{#switchtablink:Python|ESAPI for Python}} 
*[http://code.google.com/p/owasp-esapi-js/downloads/detail?name=esapi4js-0.1.3.zip ESAPI for Javascript] 

|
[[Image:Asvs-step3.jpg]]'''3. Learn ESAPI'''

*ESAPI design patterns (not language-specific): [http://www.owasp.org/images/8/82/Esapi-design-patterns.pdf (PDF], [http://www.owasp.org/index.php/File:Esapi-design-patterns.doc Word], [http://www.owasp.org/images/8/87/Esapi-design-patterns.ppt PPT)]
*The [[ESAPI Swingset|ESAPI Swingset]] sample application demonstrates how to leverage ESAPI to protect a web application.
*LAMP should be spelled LAMPE ([http://www.owasp.org/images/a/ac/LAMP_Should_be_Spelled_LAMPE.pdf PDF])
*ESAPI for Java interface documentation ([http://owasp-esapi-java.googlecode.com/svn/trunk_doc/index.html JavaDocs])
*ESAPI for PHP interface documentation ([http://owasp-esapi-php.googlecode.com/svn/trunk_doc/latest/index.html phpdoc])

|}

= 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]

*I used ESAPI for Java to build a low risk web application that was over 250,000+ lines of code in size. --[mailto:jim.manico@owasp.org 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. --[mailto:roman.hustad@yahoo.com Roman]

*I use ESAPI for Java to educate developers about application security principals at several of the world’s largest organizations. --[mailto:jim.manico@owasp.org Jim] 

= Glossary =

[[Image:Asvs-letters.jpg]]'''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 =

{{:GPC_Project_Details/OWASP_Enterprise_Security_API_Java_EE_Version | OWASP Project Identification Tab}}

= Dot NET =

{{:GPC_Project_Details/OWASP_Enterprise_Security_API_.NET_Version | OWASP Project Identification Tab}}

= Classic ASP =

{{:GPC_Project_Details/OWASP_Enterprise_Security_API_-_Classic_ASP_Version | OWASP Project Identification Tab}}

= PHP =

{{:GPC_Project_Details/OWASP_Enterprise_Security_API_-_PHP_Version | OWASP Project Identification Tab}}

= ColdFusion CFML =


{{:Projects/OWASP ESAPI for ColdFusion - CFML Project | Project About}}

= Python =

{{:GPC_Project_Details/OWASP_Enterprise_Security_API_-_Python_Version | OWASP Project Identification Tab}}

= JavaScript =

{{:GPC_Project_Details/OWASP_Enterprise_Security_API_JavaScript_Version | OWASP Project Identification Tab}}

= Objective C =

{{:Projects/OWASP ESAPI Objective - C Project | Project About}}

= Force com =

{{:GPC_Project_Details/OWASP_Enterprise_Security_API_-_Force.com_Version | OWASP Project Identification Tab}}

= Ruby =

{{:Projects/Owasp Esapi Ruby | Project About}}

= Swingset =

The ESAPI Swingset Project divides itself into sub-projects, i.e., [[Projects/OWASP ESAPI Swingset Interactive Project|Swingset Interactive]] and [[Projects/OWASP ESAPI Swingset Demo Project|Swingset Demo]].

= ESAPI C =

{{:Projects/OWASP ESAPI C Project | Project About}}

= ESAPI CPP =

{{:Projects/OWASP ESAPI C++ Project | Project About}}

= ESAPI Perl =

{{:Projects/OWASP ESAPI Perl Project | Project About}}

= Project Details =

{{:GPC_Project_Details/OWASP_Enterprise_Security_API | OWASP Project Identification Tab}}

__NOTOC__ <headertabs /> 

{{OWASP Builders}}

2011-12-12T17:19:08Z

Laurence Casey: Creating user page with biography of new user.

Information Security Professional with more than 4.5+ years of experience in Ethical Hacking, Vulnerability Assessment ,Penetration Testing and Application Security . Involved in training Application Security & Network Security since last 3 years. Currently working with IBM India as IT Security Specialist and managing Application Security Process.

2011-12-11T23:04:31Z

Laurence Casey:

<IfLanguage Is="en">
If you use OWASP materials, please consider becoming a member helping us continue our work -[http://www.owasp.org/index.php/Membership More Info]
* '''[[Member Offers]]''' - Discounts and other benefits available to OWASP members.

* '''Individual Members''' - [https://docs.google.com/spreadsheet/ccc?key=0ApZ9zE0hx0LNdGRwS1BTempMWXlZYjlNbHdITEoxUmc&hl=en_US#gid=9 Membership/members]

OWASP does not endorse commercial products or services
</IfLanguage>


<IfLanguage Is="es">
Si usa materiales de OWASP, por favor considere ayudarnos a continuar nuestro trabajo.

* '''[[Membership|Membrecía]]''' - Detalles para [https://www.owasp.org/index.php/Membership/members individuos] y miembros corporativos.
* '''[[Member Offers|Ofertas para miembros]]''' - Descuentos y otros beneficios disponibles para los miembros de OWASP.
* Lo invitamos a participar en las traducción de el sitio vea el proyecto de [[OWASP_Spanish|OWASP en Español]].


</IfLanguage>
{|style="width:100%;background-color:#fff;border:1px solid #ccc"
|style="text-align:center;color:#000"|

'''Organization and Barter In Trade Supporters'''

{{MemberLinks|link=http://www.acunetix.com|logo=Acunetix_logo_200.png}}
{{MemberLinks|link=http://www.accuvant.com|logo=Accuvant_Labs.jpg}}
{{MemberLinks|link=http://www.adobe.com|logo=Adobe_logo.png}}
{{MemberLinks|link=http://www.adp.com|logo=Adp.jpg}}
{{MemberLinks|link=http://www.aecert.ae|logo=Logo_aecert.jpg}}
{{MemberLinks|link=http://www.akamai.com|logo=Akamai_logo.gif}}
{{MemberLinks|link=http://www.amazon.com|logo=Amazon_Logo.jpg}}
{{MemberLinks|link=http://www.appliedtrust.com|logo=AT4owasp.jpg}}
{{MemberLinks|link=http://www.ascure.com|logo=Ascure_Logo.jpg}}
{{MemberLinks|link=http://www.aspectsecurity.com|logo=Aspect_logo_owasp.jpg}}
{{MemberLinks|link=http://www.astechconsulting.com|logo=Astech.jpg}}
{{MemberLinks|link=http://www.artofdefence.com|logo=AOD_Logo.gif}}
{{MemberLinks|link=http://www.bestbuy.com|logo=Best_Buy_logo.jpg}}
{{MemberLinks|link=http://www.blackhat.com|logo=Blackhat.png}}
{{MemberLinks|link=http://www.cargrill.com|logo=Cargrill.png}}
{{MemberLinks|link=http://www.cigital.com|logo=Cigital_OWASP.GIF}}
{{MemberLinks|link=http://www.coresecurity.com|logo=Core_Logo_June09.gif}}
{{MemberLinks|link=http://www.denimgroup.com|logo=Denim_Group_Logo.gif}}
{{MemberLinks|link=http://www.ddifrontline.com|logo=DDI_Logo_150x45.GIF}}
{{MemberLinks|link=http://www.dreamlab.net|logo=DreamLab.jpg‎}}
{{MemberLinks|link=http://www.eng.it|logo=Logo-Engineering_150x45.png}}
{{MemberLinks|link=http://www.fishnetsecurity.com|logo=Fishnet_Logo_AppSec.jpg}}
{{MemberLinks|link=http://fujitsu.com|logo=En_sm4cr.jpg}}
{{MemberLinks|link=http://www.gemalto.com|logo=Gemalto_brand.jpg}}
{{MemberLinks|link=http://www.gdssecurity.com|logo=GDS_LOGO_SMALL.jpg}}
{{MemberLinks|link=http://www.harrisconnect.com|logo=HarrisConnect_4clr.jpg}}
{{MemberLinks|link=http://www.htbridge.ch|logo=High-Tech_Bridge_SA.jpg}}
{{MemberLinks|link=http://www.huawei.com|logo=Huawei.jpg}}
{{MemberLinks|link=http://us.ibm.com|logo=IBM_150x45.jpg}}
{{MemberLinks|link=http://www.isc2.org|logo=ISC2_main_logo-small.jpg}}
{{MemberLinks|link=http://www.imperva.com|logo=Imperva_2color_RGB.jpg}}
{{MemberLinks|link=http://www.informationbuilders.com|logo=IBI_Logo.jpg}}
{{MemberLinks|link=http://www.intrepidusgroup.com|logo=150-22.png}}
{{MemberLinks|link=http://www.ioactive.com|logo=IOA_logo_300-Transparent.jpg}}
{{MemberLinks|link=http://www.mozilla.com|logo=Mozilla.png}}
{{MemberLinks|link=http://www.mnemonic.no|logo=Mnemonic_securing_150.png}}
{{MemberLinks|link=http://www.nixu.com|logo=NIXU_C12.jpg}}
{{MemberLinks|link=http://netiq.com|logo=Netiq_preflogo_rgb_medres.jpg}}
{{MemberLinks|link=http://www.nokia.com|logo=Nokia.jpg}}
{{MemberLinks|link=http://www.oracle.com|logo=Oracle_logo.gif}}
{{MemberLinks|link=http://www.pentasecurity.com|logo=Pentasecurity_ci.png}}
{{MemberLinks|link=http://www.praetorian.com|logo=Praetorian_Logo_150x45.png}}
{{MemberLinks|link=http://www.protiviti.com|logo=Protiviti.jpg}}
{{MemberLinks|link=http://www.qualys.com|logo=Qualys_Logo.gif}}
{{MemberLinks|link=http://www.quotium.com|logo=LogoQuotium.png}}
{{MemberLinks|link=http://www.rackspace.com|logo=Rackspace_logo.png}}
{{MemberLinks|link=http://www.redspin.com|logo=Redspin_Logo.gif}}
{{MemberLinks|link=http://www.salesforce.com|logo=Salesforce.jpg}}
{{MemberLinks|link=http://www.sdelements.com|logo=SD_Elements_logo_black.jpg}}
{{MemberLinks|link=http://www.securityinnovation.com|logo=Si-logo-100x40_(2).jpg‎}}
{{MemberLinks|link=http://www.securityps.com|logo=SPSLogo-whitebg-100x50.png}}
{{MemberLinks|link=http://www.seekersec.com|logo=55X80_seeker.PNG}}
{{MemberLinks|link=http://www.symantec.com|logo=Symantec.png}}
{{MemberLinks|link=http://www.tenablesecurity.com|logo=Tenable_T.png}}
{{MemberLinks|link=https://www.trustwave.com/application-security.php|logo=TrustwaveLogo.jpg}}
{{MemberLinks|link=https://www.ups.com/|logo=UPS.jpg}}
{{MemberLinks|link=https://www.whitehatsec.com/|logo=Whitehat.gif}}
 
<hr>
 

 
{|style="width:100%;background-color:#fff;border:1px solid #ccc"
|style="text-align:center;color:#000"|

'''Academic Supporters'''

{{MemberLinks|link=http://www.adelphi.edu|logo=AdelphiLogo-105x45.png}}
{{MemberLinks|link=http://anglia.ac.uk|logo=AngliaRuskinLogo.png}}
{{MemberLinks|link=http://www.aum.edu|logo=Auburn.jpg}}
{{MemberLinks|link=http://www.cit.ie|logo=Cit_logo.gif}}
{{MemberLinks|link=http://www.dartmouth.edu|logo=Dartmouth_BW.png}}
{{MemberLinks|link=http://www.dsu.edu|logo=Dsulogo.jpg}}
{{MemberLinks|link=http://www.dcu.ie|logo=Dculogo3.gif}}
{{MemberLinks|link=http://www.foi.hr|logo=FOI-vert-1.jpg}}
{{MemberLinks|link=http://www.kuleuven.be|logo=Kuleuven.jpg}}
{{MemberLinks|link=http://www.owasp.org|logo=GTISCLogo.gif}}
{{MemberLinks|link=http://www.hs-mannheim.de|logo=HSLogo.gif}}
{{MemberLinks|link=http://www.heig-vd.ch|logo=HEIG-VD_logo_couleur_small.jpg}}
{{MemberLinks|link=http://www.hs-furtwangen.de|logo=Logo_Hochschule_Furtwangen_University.jpg}}
{{MemberLinks|link=http://www.idc.ac.il|logo=IDC_Arazi_E_Black.jpg}}
{{MemberLinks|link=http://www.iscte.pt|logo=Iscte-iul-logo.png}}
{{MemberLinks|link=http://www.owasp.org|logo=TecnologicoMonterrey.png}}
{{MemberLinks|link=http://www.isep.fr|logo=Logo_ISEP_pour_le_Web.jpg}}
{{MemberLinks|link=http://www.itb.ie|logo=IT_Blanchardstown.jpg}}
{{MemberLinks|link=http://www.owasp.org|logo=NYP_Logo_vert_300.jpg}}
{{MemberLinks|link=http://www.ort.edu.uy|logo=LogoORT.png}}
{{MemberLinks|link=http://www.rutgers.edu|logo=Uw-university.gif}}
{{MemberLinks|link=http://www.scss.tcd.ie|logo=TCD_logo_stacked.jpg}}
{{MemberLinks|link=http://www.sgu.ac.id|logo=Logo_sgu-01_copy_copy.jpg}}
{{MemberLinks|link=http://www.cs.stevens.edu|logo=Stevens-Official-Logo-Preview.jpg}}
{{MemberLinks|link=http://www.it.teithe.gr|logo=Logotei_thessaloniki.jpg}}
{{MemberLinks|link=http://www.tp.edu.sg|logo=TPLOGO_master.jpg}}
{{MemberLinks|link=http://www.uci.edu|logo=Ucirvine_07_bluhex_sm3.jpg}}
{{MemberLinks|link=http://www.nku.edu|logo=Nku_main-logo.gif}}
{{MemberLinks|link=http://northumbria.ac.uk|logo=Northumbrialogo.jpg}}
{{MemberLinks|link=http://www.unt.edu|logo=UNT.gif}}
{{MemberLinks|link=http://www.gwu.edu|logo=Gw_stack_black.gif}}
{{MemberLinks|link=http://www.poly.edu|logo=Poly-nyu-logo.jpg‎}}
{{MemberLinks|link=http://www.teilar.gr/index_en.php|logo=TEIL.jpg}}
{{MemberLinks|link=http://www.fi.uba.ar|logo=Logo_fiuba_baja.gif}}
{{MemberLinks|link=http://www.ucla.edu|logo=Ucla_cw125.gif}}
{{MemberLinks|link=http://www.udemm.edu.ar|logo=Logo_udemm.jpg}}
{{MemberLinks|link=http://www.unkil.com|logo=Ukl.jpg}}
{{MemberLinks|link=http://www.utdallas.edu|logo=TEXWordmark.jpg}}

|}

2011-08-30T15:45:33Z

Laurence Casey: uploaded a new version of "File:Esapi-sponsors.PNG"

About The Open Web Application Security Project

2011-08-17T22:02:09Z

Laurence Casey: /* Volunteer Support */

==The OWASP Foundation==
The OWASP Foundation came online on [http://replay.waybackmachine.org/20011225110113/https://www.owasp.org/about_owasp/orgchart.shtml December 1st 2001] it was established as a not-for-profit charitable organization in the United States on April 21, 2004 to ensure the ongoing availability and support for our work at [[Main Page|OWASP]]. OWASP is an international organization and the OWASP Foundation supports OWASP efforts around the world. OWASP is an open community dedicated to enabling organizations to conceive, develop, acquire, operate, and maintain applications that can be trusted. All of the OWASP tools, documents, forums, and chapters are free and open to anyone interested in improving application security. We advocate approaching application security as a people, process, and technology problem because the most effective approaches to application security include improvements in all of these areas. We can be found at [[Main Page|www.owasp.org]].

OWASP is a new kind of organization. Our freedom from commercial pressures allows us to provide unbiased, practical, cost-effective information about application security. OWASP is not affiliated with any technology company, although we support the informed use of commercial security technology. Similar to many open-source software projects, OWASP produces many types of materials in a collaborative, open way. The [[OWASP Foundation]] is a not-for-profit entity that ensures the project's long-term success.

==OWASP Governance==
[https://www.owasp.org/images/d/d6/2011-06-OWASP-BYLAWS.pdf Foundation ByLaws last updated 06-2011]

==Citations==
OWASP and its materials are used, recommended and referenced by many government, standards and industry organisations. We maintain a list of some of the more important citations on the [[Industry:Citations]] page.

== Core Values ==
OPEN
Everything at OWASP is radically transparent from our finances to our code.

INNOVATION
OWASP encourages and supports innovation/experiments for solutions to software security challenges.

GLOBAL
Anyone around the world is encouraged to participate in the OWASP community.

INTEGRITY
OWASP is an honest and truthful, vendor agnostic, global community.

== Core Purpose ==
Be the thriving global community that drives visibility and evolution in the safety and security of the world’s software.

== Code of Ethics ==
Each of us is expected to behave according to the principles contained in the following Code of Ethics.
Breaches of the Code of Ethics may result in the foundation taking disciplinary action.

* Perform all professional activities and duties in accordance with all applicable laws and the highest ethical principles;
* Promote the implementation of and promote compliance with standards, procedures, controls for application security;
* Maintain appropriate confidentiality of proprietary or otherwise sensitive information encountered in the course of professional activities;
* Discharge professional responsibilities with diligence and honesty;
* To communicate openly and honestly;
* Refrain from any activities which might constitute a conflict of interest or otherwise damage the reputation of employers, the information security profession, or the Association;
* To maintain and affirm our objectivity and independence;
* To reject inappropriate pressure from industry or others;
* Not intentionally injure or impugn the professional reputation of practice of colleagues, clients, or employers;
* Treat everyone with respect and dignity; and
* To avoid relationships that impair — or may appear to impair — OWASP's objectivity and independence.

== Principles ==

* Free & Open
* Governed by rough consensus & running code
* Abide by a code of ethics (see ethics)
* Not-for-profit
* Not driven by commercial interests
* Risk based approach

==Tax Status: 501(c)(3) Not-For-Profit Organization==
The OWASP Foundation is a U.S. recognized [http://www.irs.gov/charities/charitable/article/0,,id=96114,00.html 501(c)(3)] not-for-profit charitable organization. The OWASP Foundation received its formal recognition by the U.S. government of its 501(c)(3) status on December 10, 2004. This not-for-profit status allows contributors to deduct any ''donations'' made to the OWASP Foundation.

==Tax Status: OWASP Europe==

==OWASP Mascot==
[https://www.owasp.org/index.php/About_OWASP/mascot Under Construction]

==Tax Deductability of Payments to OWASP==
OWASP membership fees, OWASP conferences fees, OWASP conference sponsorships, and OWASP banner ads are ''not'' considered tax-deductible donations due to the benefits the paying organization/individual receives.

Direct donations to OWASP are fully tax-deductible given OWASP's recognized U.S. not-for-profit status.

OWASP's U.S. Employer Identification Number (EIN) is: 20-0963503.

==Membership or Donations==
If you are interested in joining OWASP as a member, or donating funds for OWASP's efforts, please check out the [[Membership|OWASP Membership Page]].

==Contacting OWASP==
The easiest way to contact the [[OWASP Foundation]] is via e-mail. If you have a question concerning a particular project, we strongly recommend using the [https://lists.owasp.org/mailman/listinfo mailing list] for that project. Many questions can also be answered by [https://www.owasp.org/google/results.html searching] the [[Main Page|OWASP]] web site, so please check there first!

Our address for general correspondence and faxes can be sent to our physical office address, to the attention of [[User:Kate_Hartmann|Kate Hartmann]], at:

OWASP Foundation
9175 Guilford Road Suite #300
Columbia, MD 21046
301-604-8033 (fax)
[https://spreadsheets.google.com/a/owasp.org/viewform?hl=en&formkey=dFN1R2NIMTNROXN3dml4ZEcxXzJQYXc6MQ#gid=0 Submit a Inquiry]

[http://www.linkedin.com/companies/owasp https://www.owasp.org/images/9/98/Btn_cofollow_badge.png]

==Global Board Members==
Governed by 100% volunteer members with dedicated volunteerism to ensure the mission of OWASP "to make application security visible so that people and organizations can make informed decisions about application security risks". [https://www.owasp.org/index.php/Membership/2011Election 2011 Elections] are forthcoming.

[[User:Jeff_Williams|Jeff Williams]] - Board Member and Chair 2004 - Current
 jeff.williams(at)owasp.org

[[User:Wichers|Dave Wichers]] - Board Member 2004 - Current
 dave.wichers(at)owasp.org

[[User:Brennan|Tom Brennan]] - Board Member 2008 - Current
 tom.brennan(at)owasp.org

[[User:Sdeleersnyder|Sebastien Deleersnyder]] - Board Member 2007 - Current
 seba(at)owasp.org

[[User:EoinKeary|Eoin Keary]] - Board Member 2010 - Current
 eoin(at)owasp.org

[[User:mtesauro|Matt Tesauro]] - Board Member 2010 - Current
 matt.tesauro(at)owasp.org

==Board Meeting Minutes==
[[OWASP_Board_Meetings | Board meeting minutes for the record.]]

=== Global Committee Structure ===
OWASP recognized the extraordinary contribution of our most active leaders by engaging them to lead a set of six new committees. Each democratically established committee will focus on a key function or geographic region, such as OWASP projects, conferences, local chapters, membership and industry outreach.

{| style="width:80%" border="0" align="center"
| colspan="6" align="center" style="background:#4058A0; color:white" | OWASP GLOBAL COMMITTEES (OWASP GC)
|-
| style="width:17%; background:#f2984c" align="center" | [[Global Education Committee|Education]]
| style="width:17%; background:#f2984c" align="center" | [[Global Chapter Committee|Chapters]]
| style="width:17%; background:#f2984c" align="center" | [[Global Conferences Committee|Conferences]]
| style="width:17%; background:#f2984c" align="center" | [[Global Industry Committee|Industry]]
| style="width:16%; background:#f2984c" align="center" | [[Global Projects and Tools Committee|Projects & Tools]]
| style="width:16%; background:#f2984c" align="center" | [[Global Membership Committee|Membership]]
|}

==W2 Employees of the OWASP Foundation==

Kate Hartmann - [[User:Kate_Hartmann|Kate's Role w/OWASP]]
 OWASP Operations Director
 [mailto:kate.hartmann@owasp.org Kate Hartmann]

Alison Shrader - [[User:Alison_McNamee|Alison's Role w/OWASP]]
 OWASP Accounting
 [mailto:alison.shrader@owasp.org Alison Shrader]

==1099 Contractors==

Paulo Coimbra [[User:Paulo_Coimbra|Paulo's Role w/OWASP]]
 OWASP Project Manager
 [mailto:pcoimbra@owasp.org Paulo Combra]

Kelly Santalucia [[Kelly's Role w/OWASP]]
 OWASP Membership Committee

Sarah Baso [[User:Sarah_Baso|Sarah's Role w/OWASP]]
 OWASP Operational Support
 [mailto:sarah.baso@owasp.org Sarah Baso]

== Operational Procedures ==
[https://www.owasp.org/index.php/About_OWASP/Operational-Procedures Standard Operations Procedures (SOP)]

[[Staff Meetings]]

==Volunteer Support==

==Licensing==
All OWASP materials are available under an approved [[OWASP Licenses|FLOSS license]]. For more information, please see the '''[[OWASP Licenses]]''' page.

==Participation and Membership==
Everyone is welcome to participate in our [https://lists.owasp.org/mailman/listinfo forums], [[projects]], [[chapters]], and [[conferences]]. OWASP is a fantastic place to learn about application security, to network, and even to build your reputation as an expert.

If you find the OWASP materials valuable, please consider supporting our cause by becoming an OWASP member. All monies received by the OWASP Foundation go directly into supporting OWASP projects.

For more information, please see the '''[[Membership]]''' page.

==Projects==
OWASP's projects cover many aspects of application security. We build documents, tools, teaching environments, guidelines, checklists, and other materials to help organizations improve their capability to produce secure code.

For details on all the OWASP projects, please see the '''[[:Category:OWASP Project|OWASP Project]]''' page.

==Privacy Policy==
Given OWASP’s mission to help organizations with application security, you have the right to expect protection of any personal information that we might collect about our members.

In general, we do not require authentication or ask visitors to reveal personal information when visiting our website. We collect Internet addresses, not the e-mail addresses, of visitors solely for use in calculating various website statistics.

We may ask for certain personal information, including name and email address from persons downloading OWASP products. This information is not divulged to any third party and is used only for the purposes of:
* Communicating urgent fixes in the OWASP Materials
* Seeking advice and feedback about OWASP Materials
* Inviting participation in OWASP’s consensus process and AppSec conferences

OWASP publishes a list of member organizations and individual members. Listing is purely voluntary and "opt-in." Listed members can request not to be listed at any time.

All information about you or your organization that you send us by fax or mail is physically protected. If you have any questions or concerns about our privacy policy, please contact us at [mailto:owasp@owasp.org owasp@owasp.org].

==Tax Filings==
[http://204.203.220.33/EINS/200963503/200963503_2005_026A3A51.PDF Click here to get a copy of our 2005 Tax Return].

[https://www.owasp.org/images/e/ef/2006_Tax_Return.pdf Click here to get a copy of our 2006 Tax Return].

[https://www.owasp.org/images/5/57/2007_Form_990.pdf Click here to get a copy of our 2007 Tax Return] and [https://www.owasp.org/images/9/94/OWASP_Audit_Report_2007.pdf Audit Report].

[https://www.owasp.org/images/d/de/2008_Tax_Return.pdf Click here to get a copy of our 2008 Tax Return].

[https://www.owasp.org/images/d/d8/2009_Form_990.pdf Click here to get a copy of our 2009 Tax Return].

 

[[Category:OWASP Guide Project]]
[[Category:OWASP Testing Project]]
[[Category:OWASP Code Review Project]]

For more information, please see the pages listed below:

* [[Contributions]] for details about how to make contributions
* [[Advertising]] if you're interested in advertising on the OWASP site
* [[How OWASP Works]] for more information about projects and governance
* [[OWASP brand usage rules]] for information about using the OWASP brand

MediaWiki:Sidebar

2011-08-16T15:25:34Z

Laurence Casey: Undo revision 115723 by Laurence Casey (talk)