Security Controls

Security Controls prevent false positives reporting in vulnerability detection using escaping and sanitization functions. Security functions refine how data is processed, ensuring that legitimate transformations do not trigger unnecessary security alerts.

Input validators vs. sanitizers

Security Controls differentiate between Input Validators and Sanitizers, depending on how a function is used in security validation:

  • Input Validators: Used when the function validates the parameters passed to it. Validators ensure that user inputs comply with expected formats before they are processed.
  • Sanitizers: Used when the function validates or modifies the return value before it is used further in the application. Sanitizers help clean data to ensure it does not contain potentially harmful content.

Configuring security controls

The Security Controls definition must be placed in the configuration variable DD_IAST_SECURITY_CONTROLS_CONFIGURATION. To configure a list of security controls, follow the format and field specifications below. This format uses specific separators to structure each security control entry.

Format

<TYPE>:<SECURE_MARKS>:<CLASS/FILE>:<METHOD>:<PARAMETERS (Optional)>:<PARAMETERS TO VALIDATE (Optional)>

Field specifications

FieldDescription
TypeDefines the type of control. Accepted values: INPUT_VALIDATOR or SANITIZER.
Secure MarksList of vulnerability types to apply. Possible values are defined in Secure marks. Optionally, use * to indicate applicability to all types.
Class/FileFully qualified class or file implementing the security control.
MethodName of the method implementing the security control.
Parameters (Optional)Fully qualified class parameters. Used to distinguish between overloaded methods. If omitted and overloading exists, the security control applies to all overloaded methods.
Parameters to Validate (Optional)Zero-based list of parameter positions to validate. The first parameter is position 0. This field applies only to INPUT_VALIDATOR types. Used when not all parameters require validation.

Separators

  • ; (semicolon): Separates each security control.
  • : (colon): Separates each field within a security control.
  • , (comma): Separates items within a field that accepts a list.

Secure marks

The available secure marks correspond to the codes associated with each injection-related vulnerability. These codes and their availability for each language can be found in supported vulnerabilities.

The injection-related vulnerabilities are:

  • Code Injection
  • Command Injection
  • Email HTML Injection
  • Header Injection
  • LDAP Injection
  • NoSQL Injection
  • Path Traversal
  • Reflection Injection
  • Server-Side Request Forgery (SSRF)
  • SQL Injection
  • Trust Boundary Violation
  • Untrusted Deserialization
  • Unvalidated Redirect
  • XPath Injection
  • Cross-Site Scripting (XSS)

Examples

Input validator

Method that validates all input parameters to avoid command injection vulnerabilities

Method

bar.foo.CustomInputValidator#validate(String input1, String input2)

Config

INPUT_VALIDATOR:COMMAND_INJECTION:bar.foo.CustomInputValidator:validate

Method that validates one input parameter to avoid command injection vulnerabilities

Method

bar.foo.CustomInputValidator#validate(String input1, String inputToValidate)

Config

INPUT_VALIDATOR:COMMAND_INJECTION:bar.foo.CustomInputValidator:validate:1

Method that validates two input parameters to avoid command injection vulnerabilities

Method

bar.foo.CustomInputValidator#validate(String input1, String firstInputToValidate, String secondInputToValidate, Object anotherInput)

Config

INPUT_VALIDATOR:COMMAND_INJECTION:bar.foo.CustomInputValidator:validate:1,2

Method that validates the input parameter to avoid command injection and code injection vulnerabilities

Method

bar.foo.CustomInputValidator#validate(String input)

Config

INPUT_VALIDATOR:COMMAND_INJECTION,CODE_INJECTION:bar.foo.CustomInputValidator:validate

Method that validates the input parameter to avoid any vulnerabilities

Method

bar.foo.CustomInputValidator#validate(String input)

Config

INPUT_VALIDATOR:*:bar.foo.CustomInputValidator:validate

Overloaded method that validates the input parameter to avoid command injection vulnerabilities

Methods

bar.foo.CustomInputValidator#validate(String input)

bar.foo.CustomInputValidator#validate(String input, String input2)

Config

INPUT_VALIDATOR:COMMAND_INJECTION:bar.foo.CustomInputValidator:validate:java.lang.String

Note

Applies for the first method.

Overloaded methods that validate the input parameter to avoid command injection vulnerabilities

Methods

bar.foo.CustomInputValidator#validate(String input)

bar.foo.CustomInputValidator#validate(String input, String input2)

Config

INPUT_VALIDATOR:COMMAND_INJECTION:bar.foo.CustomInputValidator:validate

Note

Applies for both methods.

Sanitizer

Sanitizer to avoid command injection vulnerabilities

Method

bar.foo.CustomSanitizer#sanitize(String input)

Config

SANITIZER:COMMAND_INJECTION:bar.foo.CustomSanitizer:sanitize

Sanitizer to avoid command injection and code injection vulnerabilities

Method

bar.foo.CustomSanitizer#sanitize(String input)

Config

SANITIZER:COMMAND_INJECTION,CODE_INJECTION:bar.foo.CustomSanitizer:sanitize

Sanitizer to avoid any vulnerabilities

Method

bar.foo.CustomSanitizer#sanitize(String input)

Config

SANITIZER:*:bar.foo.CustomSanitizer:sanitize

Overloaded sanitizer to avoid command injection vulnerabilities

Methods

bar.foo.CustomSanitizer#sanitize(String input)

bar.foo.CustomSanitizer#sanitize(String input, String input2)

Config

SANITIZER:COMMAND_INJECTION:bar.foo.CustomSanitizer:sanitize:java.lang.String

Note

applies for the first method

Overloaded sanitizers to avoid command injection vulnerabilities

Methods

bar.foo.CustomSanitizer#sanitize(String input)

bar.foo.CustomSanitizer#sanitize(String input, String input2)

Config

SANITIZER:COMMAND_INJECTION:bar.foo.CustomSanitizer:sanitize

Note

applies for both methods