Jump to content

OWASP: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Initial check-in. I'm going to be creating a bunch of webappsec pages over the next few days
 
No edit summary
Line 27: Line 27:
==External links==
==External links==
* [http://www.owasp.org/ OWASP Project]
* [http://www.owasp.org/ OWASP Project]
* [http://www.webappsec.org/ The Web Application Security Consortium (WASC)]
* [http://www.threatsandcountermeasures.com/ Threats and Countermeasures]
* [http://www.threatsandcountermeasures.com/ Threats and Countermeasures]
* [http://www.microsoft.com/mspress/books/5957.asp Writing Secure Code (MS Press)]
* [http://www.microsoft.com/mspress/books/5957.asp Writing Secure Code (MS Press)]

Revision as of 00:54, 22 August 2005

The Open Web Application Security Project is an open-standards community which creates free (as in freedom and beer) standards for web_application_security. The Project's most successful outputs include the OWASP_Guide and the OWASP_Top_10.

The project has participation from a wide range of web application consultants and like-minded companies, which is reflected in its output. Rarely do physical widgets or products feature in OWASP materials.

History

The OWASP Project was started in 2001 by Mark Curphey, who wrote the original OWASP Guide in a few months. His original Guide influenced the creation of another web application security book by Howard and LeBlanc at Microsoft, and he later participated in the creation of Microsoft's Threats and Countermeasures web application security book. Mark Curphey left OWASP in 2004 and has since started another site, Threats and Countermeasures.

The primary users of the OWASP output are financial institutions and government bodies, although they rarely contribute to the project through volunteer time.

Principles

The principles within the OWASP's projects are directly related to existing security principles, such as:

  • risk - a risk is a possible event which could cause a loss
  • threat - a threat is a method of triggering a risk event
  • countermeasure - a countermeasure is a way to stop a threat from triggering a risk event
  • defense in depth - never rely on one single security measure alone
  • assurance - assurance is the level of guarantee that a security system will behave as expected

See Also

Category:Security