Difference between revisions of "Output Validation"

From OWASP
Jump to: navigation, search
Line 1: Line 1:
 
{{Template:Countermeasure}}
 
{{Template:Countermeasure}}
 +
 +
==Description==
  
 
Output validation refers to the process of validating the output of a process before it is sent to some recepient. For example, if you search your output for credit card numbers and replace them with asterisks (*), you have validated the output before sending it.  You might also validate the output for common attacks, such as [[XSS]] and [[SQL Injection]] before sending it.
 
Output validation refers to the process of validating the output of a process before it is sent to some recepient. For example, if you search your output for credit card numbers and replace them with asterisks (*), you have validated the output before sending it.  You might also validate the output for common attacks, such as [[XSS]] and [[SQL Injection]] before sending it.
Line 5: Line 7:
 
NOTE: See [[HTML Entity Encoding]] which is a sort of output validation.
 
NOTE: See [[HTML Entity Encoding]] which is a sort of output validation.
  
{{Template:Stub}}
+
==Examples ==
 +
 
 +
==Related Threats==
 +
 
 +
==Related Attacks==
 +
 
 +
==Related Vulnerabilities==
 +
 
 +
==Related Countermeasures==

Revision as of 13:45, 12 August 2006

This is a countermeasure. To view all countermeasures, please see the Countermeasure Category page.

Description

Output validation refers to the process of validating the output of a process before it is sent to some recepient. For example, if you search your output for credit card numbers and replace them with asterisks (*), you have validated the output before sending it. You might also validate the output for common attacks, such as XSS and SQL Injection before sending it.

NOTE: See HTML Entity Encoding which is a sort of output validation.

Examples

Related Threats

Related Attacks

Related Vulnerabilities

Related Countermeasures