PerimeterX Python Middleware

Latest stable version: v3.3.0

Latest GAE stable version: v3.3.0

Table of Contents

• Installation
• Upgrading
• Required Configuration
• Advanced Blocking Response
• Optional Configuration
  • Module Enabled
  • Module Mode
  • Blocking Score
  • Send Page Activities
  • Debug Mode
  • Sensitive Routes
  • Whitelist Routes
  • Sensitive Headers
  • IP Headers
  • First-Party Enabled
  • Custom Request Handler
  • Additional Activity Handler
  • Px Disable Request
  • Test Block Flow on Monitoring Mode
  • Enforce Specific Routes

Installation

Standalone

• To install the PerimeterX Python middleware in standalone mode, use PIP as follows:

pip install perimeterx-python-wsgi

Google App Engine

The following procedure is based on Google's Third-Party Libraries Guideline

1. Create a folder to store the PerimeterX Python middleware:

mkdir lib

2. Using PIP, intall the PerimeterX Python middleware with the -t flag to have it installed to the folder previouesly created:

pip install -t lib/ perimeterx-python-wsgi-gae

3. Create a file named appengine_config.py in the same folder as your app.yaml file with the following content:

from google.appengine.ext import vendor

vendor.add('lib')

4. In your app.yaml file, request the following libraries:

libraries:
- name: flask
  version: "0.12"
- name: pycrypto
  version: "2.6.1"
- name: werkzeug
  version: "0.11.10"
- name: ssl
  version: "2.7.11"

5. Deploy the app

Upgrading

To upgrade to the latest PerimeterX Enforcer version, run:

• Standalone: pip install -U perimeterx-python-wsgi
• Google App Engine: pip install -t lib/ -U perimeterx-python-wsgi-gae

For more information, contact PerimeterX Support.

Required Configurations

To use PerimeterX middleware on a specific route follow this example:

from perimeterx.middleware import PerimeterX

px_config = {
    'app_id': 'APP_ID',
    'cookie_key': 'COOKIE_KEY',
    'auth_token': 'AUTH_TOKEN',
}
application = get_wsgi_application()
application = PerimeterX(application, px_config)

• The PerimeterX Application ID / AppId and PerimeterX Token / Auth Token can be found in the Portal, in Applications.
• PerimeterX Risk Cookie / Cookie Key can be found in the portal, in Policies. The Policy from where the Risk Cookie / Cookie Key is taken must correspond with the Application from where the Application ID / AppId and PerimeterX Token / Auth Token. For details on how to create a custom Captcha page, refer to the documentation

Optional Configuration

In addition to the basic installation configuration above, the following configurations options are available:

Module Enabled

A boolean flag to enable/disable the PerimeterX Enforcer. Default: true

config = {
  ...
  module_enabled: False
  ...
}

Module Mode

Sets the working mode of the Enforcer. Possible values:

• active_blocking - Blocking Mode
• monitor - Monitoring Mode Default: monitor - Monitor Mode

config = {
  ...
  module_mode: 'active_blocking'
  ...
}

Blocking Score

Sets the minimum blocking score of a request. Possible values:

• Any integer between 0 and 100. Default: 100

config = {
  ...
  blocking_score: 100
  ...
}

Send Page Activities

Enable/disable sending activities and metrics to PerimeterX with each request.
Enabling this feature allows data to populate the PerimeterX Portal with valuable information, such as the number of requests blocked and additional API usage statistics. Default: true

config = {
  ...
  send_page_activities: True
  ...
}

Debug Mode

Enable/disable the debug log messages. Default: False

config = {
  ...
  debug_mode: True
  ...
}

Sensitive Routes

An array of route prefixes that trigger a server call to PerimeterX servers every time the page is viewed, regardless of viewing history. Default: Empty

config = {
  ...
  sensitive_routes: ['/login', '/user/checkout']
  ...
}

Whitelist Routes

An array of route prefixes which will bypass enforcement (will never get scored). Default: Empty

config = {
  ...
  whitelist_routes: ['/about-us', '/careers']
  ...
}

Sensitive Headers

An array of headers that are not sent to PerimeterX servers on API calls. Default: ['cookie', 'cookies']

config = {
  ...
  sensitive_headers: ['cookie', 'cookies', 'x-sensitive-header']
  ...
}

IP Headers

An array of trusted headers that specify an IP to be extracted. Default: Empty

config = {
  ...
  ip_headers: ['x-user-real-ip']
  ...
}

First-Party Enabled

Enable/disable First-Party mode. Default: True

config = {
  ...
  first_party: False
  ...
}

Custom Request Handler

A Python function that adds a custom response handler to the request.
You must declare the function before using it in the config.
The Custom Request Handler is triggered after PerimeterX's verification. The custom function should handle the response (most likely it will create a new response) Default: Empty

config = {
  ...
  custom_request_handler: custom_request_handler_function,
  ...
}

Additional Activity Handler

A Python function that allows interaction with the request data collected by PerimeterX before the data is returned to the PerimeterX servers. Does not alter the response. Default: Empty

config = {
  ...
  additional_activity_handler: additional_activity_handler_function,
  ...
}

PerimeterX Data Enrichment

This is a cookie we make available for our costumers, that can provide extra data about the request

context.pxde
context.pxde_verified

Px Disable Request

This is a property that allows the developer to disable the module for a single request. Its value should be True for disabling, and False for enabling

...
environ['px_disable_request'] = False #The request shall be passed to the enforcer.
or
environ['px_disable_request'] = True #The enforcer shall be disabled for that request.

Test Block Flow on Monitoring Mode

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.

The Header Name is configurable using the bypass_monitor_header property.

Default: Empty

config = {
  ...
  bypass_monitor_header: 'x-px-block',
  ...
}

Enforced Specific Routes

An array of route prefixes that are always validated by the PerimeterX Worker (as opposed to whitelisted routes). When this property is set, any route which is not added - will be whitelisted.

Default: Empty

config = {
 ...
 enforced_specific_routes: ['/profile']
 ...
};