Skip to main content
Feedback

Regex Threat Protection Policy Configuration Values

The following configuration values can be defined while configuring the Regex Threat Protection policy on the Call Transformation page:

note
  • Only pre-processing is applicable for this policy. Post-processing is not applicable.
  • This policy supports only one entry for any given PreInput value. If you enter the same PreInput value more than once, only one value will be used.
Field nameTypeField ValueRequired/OptionalDescription
Processing AdapterStringcom.mashery.proxy.protection.regex-threat-protectionRequiredAdapter that evaluates request content against a configured regular expression and rejects matching requests with HTTP 400.
Perform Pre-processingBooleanEnabled / DisabledRequiredWhen enabled, the policy inspects the request before forwarding it to the backend. Note: This policy only supports pre-processing. The post-processing toggle has no effect.
Data to make available for pre-processing (PreInput Values)Map
StringregexOptionalA regular expression used to detect malicious content. The policy uses full-string matching, so that the entire evaluated string must match the pattern. Wrap the pattern with .* on both sides to detect substrings within larger strings. For example: .*(?i)(SELECT|DROP|UNION).* rather than (?i)(SELECT|DROP|UNION)
BooleancaseSensitiveOptionalWhen true, matching is case-sensitive. Note: Enabling case-sensitive matching may miss mixed-case attack variants such as DrOp TaBlE. Only enable case-sensitive matching when your use case specifically requires exact-case evaluation. Default: false.
BooleancheckHeadersOptionalWhen true, evaluates the regex against request header names and values. Default: false.
BooleancheckPathOptionalWhen true, evaluates the regex against the URL path and query parameter values (both URL-decoded). Query parameter keys are not decoded. Default: false.
BooleancheckBodyOptionalWhen true, evaluates the regex against the entire request body content. Default: false.

Configuration steps

Refer to the Configuring Call Transformation for an Endpoint for more information on the configuration steps.

On this Page