Protection & Endpoints

What is an endpoint?

An endpoint has 3 main properties:

• traffic source: it indicates the origin of the traffic directed to the endpoint
• traffic usage: it indicates the functional context of the resources included in the endpoint, to separate different parts of your website and/or mobile app
• name: a name of your choice, to identify the traffic directed to the endpoint in the dashboard

📘

Fine-grained protection

DataDome uses the traffic source and traffic usage parameters to apply the right algorithms and detect specific threats.

Traffic sources

We define the following values for the sources:

Traffic usages

We currently propose the following usages:

How to manage endpoints?

🚧

Deleted endpoint visualization

If you just deleted an endpoint, you will still be able to see it in the analytics screens of the dashboard if it matched traffic over the past 30 days. After the 30 days period, the corresponding deleted endpoint won't appear anymore on the analytics screens.

📘

Default endpoint

By default, one endpoint is pre-set in your account: “Web (default)”.
The endpoint “Web (default)” cannot be reordered or deleted.

Go to Management > Protection & Endpoints

A list of endpoints connected to your account is displayed.
The endpoints are matched following the top-down order: for a given request, the first matched endpoint is chosen. Changing the order in the list implies a change in the matching priorities.

Admin view

Roles & actions

Endpoint set-up

To set-up an endpoint, several pieces of information are requested.

General information

Traffic identification

Two methods can be used to identify the endpoint traffic. The two methods described below are mutually exclusive: they cannot be used both at the same time for a given endpoint.

1. Traffic query

Traffic matching an endpoint can be defined using a single traffic query. The list of available fields and the syntax guidelines are described in the traffic queries syntax user guide.

📘

Case sensitivity

Traffic queries for endpoints definition are matched case-insensitively. You can still use case-sensitive queries in interface for a more accurate preview of the matched traffic.

2. Regex on URL and UA

Traffic matching an endpoint can also be identified defining regex conditions (following the PCRE regular expression syntax) for at least one of the following elements:

• Domain inclusion
• URL path inclusion
• URL path exclusion
• User Agent inclusion

For example, here you can find a pattern of any relevant path for payment:

^(https?:\/\/)?([\w.-]+)\.(\w+)(\/[\w.-]*)*\/(pay|payment|checkout|purchase|order)(\/|$|\?)

Security policy

It is possible to control the security policy applied to the traffic reaching the endpoint.

Detection

DataDome detection can be enabled or disabled

Protection

If detection is enabled, DataDome protection can be

• disabled, i.e. threat traffic is allowed
• enabled, i.e. threat traffic is blocked or challenged
• sampled, i.e. protection is only applied on a ratio of incoming traffic, according to a chosen sampling rate

📘

Sampled protection

When protection is sampled with a given traffic ratio, the sampling ratio is applied on session IDs. This ensures protection policy remains consistent along sessions, but the actual ratio of protected requests might vary, as the distribution of traffic across sessions is not uniform. For example, setting a sampling ratio to 10% will ensure 10% of the sessions will be protected, but the ultimate protected traffic could be slightly different (likely between 8% and 12%), as some sessions send much more requests than others.

Protected vs unprotected traffic can be filtered in the explore section using the field protection(adding a filtering conditionprotection:enabled or protection:disabled) and tracked via the specific enriched header X-DataDome-protection.

📘

Global protection coverage

It is possible to apply a protection rate to all protected endpoints at once, selecting the option Edit ratio of protected traffic from the Managed Endpoints menu.

Responses

CAPTCHA and Device Check responses can be enabled or disabled. By default, they are enabled with protection. If a request matches a model set with a disabled response, DataDome choses the first less impactful response available. If none, the request is allowed.

🚧

Impact on protection

We suggest to keep all responses enabled, as disabling a response implies a degradation of protection. CAPTCHA and Device Check should be disabled only in specific and circumscribed contexts.

How to analyze traffic?

The percentage of traffic is indicated for each endpoint. It includes normal users & bots and is calculated for the last 20 minutes.

You can analyze the endpoint’s traffic by clicking on Actions > View Traffic Details to display the following information:

• An overview of the last 24 hours with the number of requests, URLs and IPs, the top 2 IP owners, and the top 3 UA.
• The last 100 requests.

You can also analyze through the "Explore" view (Read more about the Explore view.