> This page is for Applications Protection.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.humansecurity.com/llms.txt.

# Credentials Intelligence: Enforcer Integration Guidelines

This section details all the required features that should be configured in the Enforcer (server-side integration) for Credential Intelligence to work.

[Supported Enforcer Types](/applications/enforcer-integration-generic-guidelines#supported-enforcer-types)\
[Required Configurations](/applications/enforcer-integration-generic-guidelines#required-configurations)

## Supported Enforcer Types

[Akamai EdgeWorker Enforcer](/applications/akamai-edgeworker-enforcer)\
[Apache - C Module](/applications/apache-c-module-configuration)\
[AWS Lambda Edge](/applications/aws-lambdaedge/v4/installation)\
[AWS API Gateway Lambda Authorizer](/applications/aws-lambda-authorizer/installation)\
[Cloudflare Worker](/applications/install-the-cloudflare-enforcer)\
[Fastly](/applications/configuration-fastly-vcl-11#credential-intelligence-configurations)\
[GO](/applications/go)\
[Salesforce Commerce Cloud Cartridge](/applications/salesforce-commerce-cloud-cartridge)\
[Java](/applications/java-intro)\
[NGINX - C Module](/applications/nginx-config)\
[NGINX - LUA Module](/applications/nginx-lua-module)\
[Node.JS Express](/applications/nodejs-express/changelog)\
[PHP](/applications/php)

## Required Configurations

### Step 1: Enable the Credential Extraction Flag

This is a boolean flag on the enforcer configuration to enable the product.

> Click [](/applications/)[here](/applications/cloudflare-config#login-credentials-extraction) to review an example of Cloudflare configuration.

### Step 2: Configure the Credential Extraction Paths

This is an array of extraction configurations that detail which requests have credentials on them and how to extract the credentials from these requests. Please note, that it is important to configure all authentication paths, including account login, new account creation, and password reset/change (for more information on the authentication path guidelines, click [here](/applications/credential-intelligence-top-ten-questions-during-onboarding) to view top questions during onboarding). Click [here](/applications/cloudflare-config#login-credentials-extraction) to review an example of Cloudflare configuration.

> **Note**
>
> It may be necessary to **configure sensitive routes** to include all login paths for older enforcer versions.
> Click [here](/applications/cloudflare-config#sensitive-routes) to review an example for Cloudflare configuration.

### Step 3: Configure the Method to Retrieve the Response Status (Fail/Pass)

This is a series of configurations that determine how to report whether the login request was successful or not on the `additional_s2s` activity. Please note, that configuring the  `additional_s2s` activity allows us to quantify the number of compromised accounts that were observed active on the app.

> Click [here](/applications/cloudflare-config#additional-s2s-activity) to review an example of Cloudflare configuration.

### Step 4: Configure Multi-Step Logins if Applicable

This step is required only for multi-step authentication methods. Only in cases where usernames and passwords are sent in separate HTTP requests, the `px_credentials_intelligence_version` configuration value should be set to `multistep_sso`.

> **Note**
>
> Multiple authentication methods and paths are supported, even if some are multi-step and some are not.
> Click [here](/applications/cloudflare-config#multistep-login) to review an example of Cloudflare configuration.