This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit

Difference between revisions of "Executable space protection"

Jump to: navigation, search
Line 1: Line 1:
| type=inactiveDraft
| lastRevision=2016-07-27
| comment=Content is incomplete
Every '''[[Control]]''' should follow this template.
Every '''[[Control]]''' should follow this template.

Latest revision as of 02:04, 28 July 2016

This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.

This page contains draft content that has never been finished. Please help OWASP update this content! See FixME.
Last revision (yyyy-mm-dd): 2016-07-27
Comment: Content is incomplete

Every Control should follow this template.

This is a control. To view all control, please see the Control Category page.

Last revision (mm/dd/yy): 07/28/2016


A control (countermeasure or security control) is a protection mechanism that prevents, deters, or detects attacks, or prevents or reduces vulnerabilities.

  1. Start with a one-sentence description of the control
  2. How does the countermeasure work?
  3. What are some examples of implementations of the control (steer clear of specific products)

Risk Factors

  • Talk about the factors that this control affects
  • What effect does this countermeasure have on the attack or vulnerability?
  • Does this control reduce the technical or business impact?

Difficulty to Implement

  • Discuss the typical difficulty of implementing this control, emphasizing the factors that make it easier or harder
  • Steer clear of language/platform specific information here


Short example name

A short example description, small picture, or sample code with links

Short example name

A short example description, small picture, or sample code with links

Related Attacks

Related Vulnerabilities

Related Controls