Render:

• Set a correct content type
• Set safe character set (UTF-8)
• Set correct locale

On Submit:

• Enforce input field type and lengths.
• Validate fields and provide feedback.
• Ensure option selects and radio contain only sent values.

Positive input validation using correct character set

(NR) Negative input validation. (LR) Sanitize input.

Tip: updating a negative list (such as looking for "script", "sCrIpT", "ßCrîpt", etc) will require expensive and constant deployments and will always fail as attackers work out your list of "bad" words. Positive validation is simpler, faster and usually more secure and needs updating far less than any other validation mechanism.

• Object relational model (Hibernate).
• Active Record design pattern.
• Stored procedures.

• Escape mechanisms such as ESAPI's Encoder:
  • EncodeForLDAP()
  • Encoder.EncodeforOS()

Tip: All SQL Injection is due to dynamic SQL queries. Strongly consider prohibiting dynamic SQL queries within your organization

• Testing for SQL Injection (OTG-INPVAL-005)
• Testing for LDAP Injection (OTG-INPVAL-006)
• Testing for ORM Injection (OTG-INPVAL-007)
• Testing for XML Injection (OTG-INPVAL-008)
• Testing for SSI Injection (OTG-INPVAL-009)
• Testing for XPath Injection (OTG-INPVAL-010)
• Testing for IMAP/SMTP Injection (OTG-INPVAL-011)
• Testing for Code Injection (OTG-INPVAL-012)
• Testing for Command Injection (OTG-INPVAL-013)
• Testing for Buffer Overflow (OTG-INPVAL-014)

• Validate user is authenticated.
• Validate role is sufficient for this view.
• Set "secure" and "HttpOnly" flags for session cookies.
• Send CSRF token with forms.

• Only use inbuilt session management.
• Store secondary SSO / framework / custom session identifiers in native session object – do not send as additional headers or cookies.

• Validate user is authenticated.
• Validate role is sufficient to perform this action.
• Validate CSRF token.

Tip: Consider the use of a "governor" to regulate the maximum number of requests per second / minute / hour that this user may perform. For example, a typical banking user should not perform more than ten transactions a minute, and one hundred per second is dangerous and should be blocked.

• Test Role Definitions (OTG-IDENT-001)
• Test User Registration Process (OTG-IDENT-002)
• Test Account Provisioning Process (OTG-IDENT-003)
• Testing for Account Enumeration and Guessable User Account (OTG-IDENT-004)
• Testing for Weak or unenforced username policy (OTG-IDENT-005)
• Testing for Credentials Transported over an Encrypted Channel (OTG-AUTHN-001)
• Testing for default credentials (OTG-AUTHN-002)
• Testing for Weak lock out mechanism (OTG-AUTHN-003)
• Testing for Bypassing Authentication Schema (OTG-AUTHN-004)
• Testing for Vulnerable Remember Password (OTG-AUTHN-005)
• Testing for Browser cache weakness (OTG-AUTHN-006)
• Testing for Weak password policy (OTG-AUTHN-007)
• Testing for Weak security question/answer (OTG-AUTHN-008)
• Testing for weak password change or reset functionalities (OTG-AUTHN-009)
• Testing for Weaker authentication in alternative channel (OTG-AUTHN-010)
• Testing for Bypassing Authorization Schema (OTG-AUTHZ-002)
• Testing for Privilege escalation (OTG-AUTHZ-003)
• Testing for Session Management Schema (OTG-SESS-001)
• Testing for cookies attributes (OTG-SESS-002)
• Testing for Session Fixation (OTG-SESS-003)
• Testing for Exposed Session Variables (OTG-SESS-004)
• Testing for CSRF (OTG-SESS-005)
• Testing for logout functionality (OTG-SESS-006)
• Test Session Timeout (OTG-SESS-007)
• Testing for Session puzzling (OTG-SESS-008)

Render:

• Set correct content type
• Set safe character set (UTF-8)
• Set correct locale
• Output encode all user data as per output context
• Set input constraints

On Submit:

• Enforce input field type and lengths.
• Validate fields and provide feedback.
• Ensure option selects and radio contain only sent values.

Positive input validation using correct character set

(NR) Negative input validation (LR) Sanitize input

Tip: Only process data that is 100% trustworthy. Everything else is hostile and should be rejected.

Tip: Use OWASP Scrubbr to clean tainted or hostile data from legacy data

• Testing for Reflected Cross site scripting (OTG-INPVAL-001)
• Testing for Stored Cross site scripting (OTG-INPVAL-002)
• Testing for DOM-based Cross site scripting (OTG-CLIENT-001)
• Testing for JavaScript Execution (OTG-CLIENT-002)
• Testing for HTML Injection (OTG-CLIENT-003)
• Testing for Cross site flashing (OTG-CLIENT-008)

Or

Render:

• Send indirect random access reference map value.

Or

Obtain direct value from random access reference access map.

• Testing Directory traversal/file include (OTG-AUTHZ-001)
• Testing for Insecure Direct Object References (OTG-AUTHZ-004)
• Testing for Local File Inclusion
• Testing for Remote File Inclusion

PHP: Ensure allow_url_fopen and allow_url_include are both disabled in php.ini. Consider the use of Suhosin extension

XML: Ensure common web attacks (remote XSLT transforms, hostile XPath queries, recursive DTDs, and so on) are protected by your XML stack. Do not hand craft XML documents or queries – use the XML layer.

Fingerprint Web Server (OTG-INFO-002) Fingerprint Web Application Framework (OTG-INFO-008) Fingerprint Web Application (OTG-INFO-009) Test Network/Infrastructure Configuration (OTG-CONFIG-001) Test Application Platform Configuration (OTG-CONFIG-002) Test File Extensions Handling for Sensitive Information (OTG-CONFIG-003) Review Old, Backup and Unreferenced Files for Sensitive Information (OTG-CONFIG-004) Enumerate Infrastructure and Application Admin Interfaces (OTG-CONFIG-005) Test HTTP Methods (OTG-CONFIG-006) Test RIA cross domain policy (OTG-CONFIG-008) Analysis of Error Codes (OTG-ERR-001) Analysis of Stack Traces (OTG-ERR-002)

• Use strong ciphers (AES 128 or better) with secure mode of operations (do not use ECB).
• Use strong hashes (SHA 256 or better) with salts for passwords.
• Protect keys more than any other asset.
• Use TLS 1.2 or later for all web communications.
• Buy extended validation (EV) certificates for public web servers.

Tip: Use TLS 1.2 always – even internally. Most snooping is done within corporate networks – and it is as easy and unethical as fishing with dynamite.

Render:

• Do not send keys or hashes to the browser.

• Use strong ciphers (AES 128 or better) with secure mode of operations (do not use ECB).
• Use strong hashes (SHA 256 or better) with salts for passwords.
• Protect keys more than any other asset.
• Mandate strong encrypted communications between web and database servers and any other servers or administrative users.

Tip: Only certain personally identifiable information and sensitive values MUST be encrypted. Encrypt data that would be embarrassing or costly if it was leaked or stolen.

Tip: It is best to encrypt data on the application server, rather than the database server.

• Mandate strong encrypted communications with application servers and any other servers or administrative users.

Tip: Do not use RDBMS database, row or table level encryption. The data can be retrieved in the clear by anyone with direct access to the server, or over the network using the application credentials. It might even traverse the network in the clear despite being "encrypted" on disk.

• Testing for Weak SSL/TLS Ciphers, Insufficient Transport Layer Protection (OTG-CRYPST-001)
• Testing for Padding Oracle (OTG-CRYPST-002)
• Testing for Sensitive information sent via unencrypted channels (OTG-CRYPST-003)
• Test HTTP Strict Transport Security (OTG-CONFIG-007)
• Testing for Credentials Transported over an Encrypted Channel (OTG-AUTHN-001)

• Ensure all non-web data is outside the web root (logs, configuration, etc).
• Use octet byte streaming instead of providing access to real files such as PDFs or CSVs or similar.
• Ensure every page requires a role, even if it is "guest".

Pre-render:

• Validate user is authenticated.
• Validate role is sufficient to view secured URL.

Render:

• Send CSRF token.

• Validate user is authenticated.
• Validate role is sufficient to perform secured action.
• Validate CSRF token.

Tip: It's impossible to control access to secured resources that the web application server does not directly serve. Therefore, PDF reports or similar should be served by the web application server using binary octet streaming.

Tip: Assume attackers will learn where "hidden" directories and "random" filenames are, so do not store these files in the web root, even if they are not directly linked.

Testing Directory traversal/file include (OTG-AUTHZ-001) Testing for bypassing authorization schema (OTG-AUTHZ-002) Testing for bypassing authentication schema (OTG-AUTHN-004)

• Validate user is authenticated
• Validate role is sufficient for this view

Render:

• Send CSRF token.
• Set "secure" and "HttpOnly" flags for session cookies.

• Validate CSRF token.
• Validate role is sufficient to perform this action.
• Validate role is sufficient.

Tip: CSRF is always possible if there is XSS, so make sure XSS is eliminated within your application.

• Testing for CSRF (OTG-SESS-005)

• Enumerate Applications on Webserver (OTG-INFO-004)

• Design the app without URL redirection parameters.

or

Render:

• Use random indirect object references for redirection parameters.

• Design the app without URL redirection parameters.

or

• Obtain direct redirection parameter from random indirect reference access map.
• (LR) Positive validation of redirection parameter.
• (NR) Java – Do not forward() requests as this prevents SSO access control mechanisms.

• Validate role is sufficient to create, read, update, or delete data.

• Testing for Client Side URL Redirect (OTG-CLIENT-004)