Injection Protection Policy

Policy Name

Injection Protection

Summary

Scans incoming requests to protect against SQL, XSS, and custom injection attacks

Category

Security

First Omni Gateway version available

v1.12.0

Release Notes

Injection Protection Policy

Returned Status Codes

400 - Bad Request

Summary

The Injection Protection policy scans incoming request headers, path, query string, and body for SQL injection, XSS (Cross-Site Scripting), and custom injection attacks. The policy provides built-in protections againt SQL and XSS attacks. Configure custom protections by defining regex patterns that the policy should scan for.

The policy checks the request against the enabled built-in and custom rules. Depending on wether Reject Requests is enabled, the policy either:

Rejects the request and returns 400 (Bad Request) with the added response header x-injection-protection: blocked.
Allows the request to reach the backend service and logs a policy violation.

Configuring Policy Parameters

Omni Gateway Local Mode

When you apply the policy via declarative configuration files, Refer to the following policy definition and table of parameters:

- policyRef:
    name: injection-protection-flex
  config:
    builtInProtections: ["sql", "xss"]  // REQUIRED: include "sql", "xss", or both
    customProtections: []               // OPTIONAL: list of { name: <string>, regex: <string> }
    protectPathAndQuery: <bool>         // REQUIRED
    protectHeaders: <bool>              // REQUIRED
    protectBody: <bool>                 // REQUIRED
    headersToProtect: <string>          // OPTIONAL, default: "" (empty = all headers)
    rejectRequests: <bool>              // REQUIRED: true = reject with 400, false = allow and log

Parameter Required Default Value Description

Parameter	Required	Default Value	Description
`builtInProtections`	Yes (at least one protection required)	—	The built-in protection types to enable. Valid values are `"sql"`, `"xss"`, or both. SQL protection detects patterns such as tautologies (for example, `OR 1=1`), comment-based injection (`--`, `#`), union/select statements, and keywords such as `DROP` and `DELETE`. XSS protection detects patterns such as script and iframe tags, event handlers, and common script schemes.
`customProtections`	No		Custom protection rules for application-specific injection types. Each rule requires a `name` and a `regex` pattern. Values must be valid and not empty.
`protectPathAndQuery`	Yes	—	If `true`, the policy checks the request path and query string. The policy applies URL decoding to the path and query before matching.
`protectHeaders`	Yes	—	If `true`, the policy checks request headers. `headersToProtect` specifies which headers the policy checks.
`headersToProtect`	No	"" (empty)	A case-insensitive, comma-separated list of header names to check. If the value is empty, the policy checks all headers. This parameter is ignored if `protectHeaders` is `false`.
`protectBody`	Yes	—	If `true`, the policy checks the request body for injection patterns.
`rejectRequests`	Yes	—	If `true`, the gateway rejects matching requests with a `400` response code and a JSON error message. If `false`, the gateway allows matching requests and logs a warning.

builtInProtections

Yes (at least one protection required)

—

The built-in protection types to enable. Valid values are "sql", "xss", or both. SQL protection detects patterns such as tautologies (for example, OR 1=1), comment-based injection (--, #), union/select statements, and keywords such as DROP and DELETE. XSS protection detects patterns such as script and iframe tags, event handlers, and common script schemes.

customProtections

Custom protection rules for application-specific injection types. Each rule requires a name and a regex pattern. Values must be valid and not empty.

protectPathAndQuery

Yes

—

If true, the policy checks the request path and query string. The policy applies URL decoding to the path and query before matching.

protectHeaders

Yes

—

If true, the policy checks request headers. headersToProtect specifies which headers the policy checks.

headersToProtect

"" (empty)

A case-insensitive, comma-separated list of header names to check. If the value is empty, the policy checks all headers. This parameter is ignored if protectHeaders is false.

protectBody

Yes

—

If true, the policy checks the request body for injection patterns.

rejectRequests

Yes

—

If true, the gateway rejects matching requests with a 400 response code and a JSON error message. If false, the gateway allows matching requests and logs a warning.

Resource Configuration Example

- policyRef:
    name: injection-protection-flex
  config:
    builtInProtections: ["sql", "xss"]
    customProtections: []
    protectPathAndQuery: true
    protectHeaders: true
    headersToProtect: "referer,user-agent"
    protectBody: true
    rejectRequests: true

Managed Omni Gateway and Omni Gateway Connected Mode

When you apply the policy from the UI, the following parameters are displayed:

Field Description

Field	Description
Built-in Protections	The built-in SQL and XSS injection protection settings.
Custom Protections	The rules defined with a name and regex pattern for custom injection types.
Protect Path and Query	If enabled, the gateway checks the request path and query string.
Protect Headers	If enadbled, the gateway checks the request headers.
Headers to Protect	List of header names to check. Leave empty to check all headers.
Protect Body	If enabled, the gateway checks the request body.
Reject Requests	If enabled, the gateway rejects matching requests with a `400` response code. Otherwise, the gateway allows them to reach the upstream service and logs a policy violation.

Built-in Protections

The built-in SQL and XSS injection protection settings.

Custom Protections

The rules defined with a name and regex pattern for custom injection types.

Protect Path and Query

If enabled, the gateway checks the request path and query string.

Protect Headers

If enadbled, the gateway checks the request headers.

Headers to Protect

List of header names to check. Leave empty to check all headers.

Protect Body

If enabled, the gateway checks the request body.

Reject Requests

If enabled, the gateway rejects matching requests with a 400 response code. Otherwise, the gateway allows them to reach the upstream service and logs a policy violation.