Personally Identifiable Information (PII) is information that can be used on its own or with other information to identify a single person, or to identify an individual in context.
It is important for us to keep personal private information out of our servers. Therefore, by default, we do not send the request body and cookies to PerimeterX backend servers, the entire communication is based on headers data.
PII is not a recommended setting. If PII is essential for your organization, contact Support.
When PII is enabled, PerimeterX does not store a client’s full IP information (Client IP, HTTP Headers). In IPv4 this is done by zeroing 4th IP octet (for example, the IP 1.2.3.4 will be stored as 1.2.3.0). In IPv6 this is done by zeroing the last four (4) octets (for example, the IP 1:2:3:4:1:2:3:4 will be stored as 1:2:3:4:1:2:3:0). Removing the IP’s last octet can result small reduction of detection capability, usually for the models and signatures that are based on IPs.
A boolean flag to enable/disable the HUMAN Enforcer.
Default: false
By default, the PerimeterX plugin is set to Monitor Only mode. To active blocking mode, set the px_block_enabled property to true.
Default: false
Sets the minimum blocking score of a request. Do not change this value without consulting with a HUMAN support engineer.
Possible values:
Default: 100
A boolean flag to enable/disable the debug log messages.
Default: false
An array of route prefixes/suffixes that trigger a server call to PerimeterX servers every time the route is called, regardless of viewing history.
Default: Empty array
Allowing (bypassing enforcement) can be configured on different aspects of the request, ranging from URI to IP addresses and user agents. The rules are OR based.
Default: Empty array
Allows you to define a set of routes on which the plugin will be active. An empty list sets all routes in the application as active.
Default: empty array (all routes are active)
An array of headers that are not sent to HUMAN servers on server-to-server API calls.
Default: [“cookie”, “cookies”]
An array of trusted headers that specify an IP to be extracted.
Default: Empty array
An array of up to 10 header keys that allows you to send up to 10 custom parameters back to HUMAN servers. The parameters should be passed according to the correct order (1-10). Skipping is possible using an empty string (i.e [“header1”, “header2”, "", “header4”]).
Default: Empty array
A set of properties configuring sending the PerimeterX score on upstream and/or downstream headers.
Default: false / empty string
Controls the timeout property for HUMAN requests. Times are in MS.
Default: 1000
An array of cookie names that are allowed to be sent to HUMAN servers on server-to-server calls.
Default: Empty array
Enables/disables the Advanced Blocking Response functionality.
Default: false
Modifies a custom CSS by adding the px_css_ref property and providing a valid URL to the CSS.
Default: Empty
Adds a custom JS file by adding the px_js_ref property and providing the JS file that is loaded with the block page.
Default: Empty
The logo is displayed at the top of the the block page.
Max-height = 150px, Width = auto.
Default: Empty
Allows you to test an enforcer’s blocking flow while you are still in Monitor Mode.
When the header name is set (eg. x-px-block) and the value is set to 1, when there is a block response (for example from using a User-Agent header with the value of PhantomJS/1.0) the Monitor Mode is bypassed and full block mode is applied. If one of the conditions is missing you will stay in Monitor Mode. This is done per request.
To stay in Monitor Mode, set the header value to 0.
Default: Empty
Allows you to pass a specific header (e.g. x-px-active) when px_enabled is off. When the header has a value of 1, the module is enabled for the specific request. When the header has a value of 0, the module is not enabled.
This feature can be used for a/b testing.
Default: Empty
The name of the cookie that contains the JWT token from which user identifiers should be extracted.
Default: ""
The field name in the JWT object, extracted from the JWT cookie, that contains the user ID to be extracted and reported.
Default: ""
The field names in the JWT object, extracted from the JWT cookie, that should be extracted and reported in addition to the user ID.
Default: []
The name of the header that contains the JWT token from which user identifiers should be extracted.
Default: ""
The field name in the JWT object, extracted from the JWT header, that contains the user ID to be extracted and reported.
Default: ""
The field names in the JWT object, extracted from the JWT header, that should be extracted and reported in addition to the user ID.
Default: []