Account security

Learn how to enforce Dashboard & API security access.

📘

Enforce account security

When dealing with user access to the Dashboard and API, you may consider adding an extra layer of security. Here you will find a way to restrict access to both Dashboard & API only to the IP addresses you specify.

You will also learn how to activate your email notifications to receive information about events occurring in your configuration, in few seconds. Email notifications is a very useful feature when you're away from the Dashboard while important events have occurred.

This page focuses on how to setup the following:

Dashboard access IP restriction

🚧

Caution

When this feature is enabled, the Dashboard access will be restricted to the list of allowed IP addresses

Here you can input the IP address to be allowed.
Simply click on the "Add" button to input an IP address:

After you click "Confirm", you will be able to see the IP address in the following list:

From here, you simply need to activate the list by clicking on the toggle button.

API access IP restriction

❗️

Caution

This restriction will be applied to both APIs: the Protection API and the Management API
As a result you would need to allow your infrastructure IP where DataDome module is integrated .

🚧

Caution

When this feature is enabled, the API calls will be restricted to the list of allowed IP addresses

The same principle applies here. You can add the IP address to be allowed:

When your IP address is added and confirmed, you can then activate the list by clicking on the toggle button:

Email notifications

All the events listed below will trigger an email notification to all the users with admin rights:

  • Global protection Status Toggle: if the status of global protection has changed
  • Endpoint protection Status Toggle: if the protection status of one of your endpoints has changed
  • User invitation: each time a new user is provided access to your DataDome Dashboard
  • User role edition: each time a user role is changed
  • User deletion: each time a user account gets deleted
  • Failed login attempt: each time a known user of your DataDome Dashboard failed to connect
  • Deactivation of email notifications: whenever the email notifications are turned off

To activate the email notifications, click on the toggle button as shown below:

Enforcing Two-Factor Authentication for all users

🚧

Caution

You must activate Two-Factor Authentication on your personal profile before you can enforce it for all users.

Switch the toggle button to the "ON" position. On their next login attempt, all users will be directed to a mandatory screen with a prompt to enable Two-Factor Authentication (2FA) on their profile. They will not be able to access the Dashboard until they have enabled 2FA.

888

Enabling Single Sign-On (SSO)

🚧

Plan restriction

This feature is only available to Enterprise plans.

📘

Multiple workspace owner

The SSO configuration can only be manage through your parent workspace.

Single Sign-On (SSO) allows your team to log in to the DataDome Dashboard using your corporate Identity Provider (IdP). This enhances security by centralizing user authentication and management.

DataDome supports 3 types of SSO:

  • SAML 2.0
  • Microsoft Entra ID
  • Open ID Connect

We support any Identity Provider compliant with SAML 2.0, such as Okta, Bitium, OneLogin, Centrify, etc.


Configuration Overview

Configuring SSO is a four-step process:

  1. Choose Your IdP: Select your Identity Provider from the tabs below.
  2. Configure in IdP: Create a new application within your IdP for DataDome by following the steps provided.
  3. Configure in DataDome: Copy the required details from your IdP into the DataDome Console's SSO settings.
  4. Test & Enforce: Test the connection with a pilot user before enforcing SSO for all users in your organization.

Identity Provider Configuration

Select your provider below for detailed, step-by-step instructions.

We recommend using OIDC for its modern security and ease of setup.

OIDC (Recommended)

Step 1: Create an OIDC App Integration in Okta

  1. In the Okta Admin Console, navigate to Applications > Applications.
  2. Click Create App Integration.
  3. Select OIDC - OpenID Connect as the sign-in method and Web Application as the application type.
  4. On the settings page:
    • App integration name: Enter DataDome.
    • Sign-in redirect URIs: Enter the callback URL from your DataDome SSO settings. It will be https://app.datadome.co/auth/callback.
  5. Under Assignments, choose who can access the application.
  6. Click Save.

Step 2: Retrieve OIDC Credentials After saving, copy the following values from the application's configuration page:

  • Client ID
  • Client secret
  • Okta domain (e.g., your-company.okta.com)

Step 3: Configure DataDome

  1. In the DataDome Console, navigate to Management > Account Security.
  2. Click on Add SSO, select OIDC and create a name for this connexion
  3. Fill in the fields with the information from Okta:
    • Client ID: Paste the Client ID.
    • Client Secret: Paste the Client Secret.
    • Issuer URL: Enter your Okta domain with a https:// prefix (e.g., https://your-company.okta.com).
  4. Save the configuration and test.

SAML

Step 1: Create a SAML App Integration in Okta

  1. In the Okta Admin Console, go to Applications > Applications and click Create App Integration.
  2. Select SAML 2.0 as the sign-in method.
  3. On the Configure SAML tab, enter the following:
    • Single sign on URL (ACS): Enter the ACS URL from your DataDome SSO settings (https://app.datadome.co/saml/acs).
    • Audience URI (SP Entity ID): Enter the Entity ID from your DataDome SSO settings (urn:datadome:sso).
    • Name ID format: Select EmailAddress.
    • Application username: Select Email.
  4. Click Next, then Finish.

Step 2: Retrieve SAML Metadata

  1. On the application's Sign On tab, find the SAML Signing Certificates section.
  2. Click Actions > View IdP metadata.
  3. A new tab will open with the XML metadata. Save this URL or download the XML file.

Step 3: Configure DataDome

  1. In the DataDome Console, navigate to Management > Account Security. 2. Click on Add SSO, select SAML and create a name for this connexion
  2. Provide the metadata from Okta by either uploading the XML file or pasting the Metadata URL.
  3. Save the configuration and test.

Automatic login from your Identity provider

To allow users to log in directly from your Identity Provider on the DataDome Dashboard, you can:

  • if you use SAML 2.0 enable the IdP-Initiated Login option:

  • for Entra ID and Open ID Connect, just use the URL at step 2 called "Initiate login URL" and past it into your IdP configuration

Configuring domain

🚧

Domain for multiple workspace

The verified domain will be active for all your current workspace.

It means that an user will be able to access any of your DataDome workspaces on which he has been added.

Follow step 3 to add any domain you need, associated with your SSO configuration.


FAQ when configuring SSO

  1. Which name do I need to choose for my configuration?
    You can choose any name
  2. Where am I supposed to add the CallBack URL?
    Depending on what IdP you are using, sometimes it's called "Initiate Login URI" on OKTA with OpenID Connect, "PostBack URL", "Sign On URL" on Microsoft Entra ID, or "Login URL" on JumpCloud.
  3. Can I add multiple configurations?
    Yes, you can add several SSO configurations, useful if you need to switch from one configuration to another. Please remember that you can have only 1 enabled simultaneously.
  4. Can I add several domains to my configuration?
    Yes, you can add several domains per SSO configuration. Please note that all these domains will be enabled for all your DataDome workspaces.
  5. What are Client ID and Secret used for?

    [!INFO] The Client ID and Client Secret are credentials used only for OIDC-based SSO.

    • The Client ID is a public identifier for the DataDome application in your IdP.
    • The Client Secret is a confidential password that proves the authentication request is coming from the legitimate DataDome application.

    These are not used for SAML configurations, which use a certificate-based verification method instead. Always keep your Client Secret secure.*

  6. What is the Redirect URI / ACS URL I should use? The values you need to provide to your IdP are available in the DataDome Console's SSO settings. They are typically:
  • OIDC Redirect URI: https://app.datadome.co/auth/callback
  • SAML ACS URL: https://app.datadome.co/saml/acs

[!WARNING]

Always copy the exact URL from your DataDome SSO configuration page to ensure it is correct for your account and region.

Automatic Account Creation

🚧

Plan restriction

This feature is only available to Enterprise plans.

📘

For SSO only users

You must have a SSO configuration already configured.

You will find the Automatic Account Creation (a.k.a User Provisioning) on the Account Security tab of the Management panel of the DataDome Dashboard.

Make sure your SSO configuration is already activated

Configure your Automatic Account Creation

🚧

Be sure to configure your Automatic Account Creation through your main Workspace.

  1. Click "Add AAC" and choose the domain you want the account to be created automatically.
  1. If you have multiple workspaces, choose at least one where you want this configuration to be applied
  1. From there, you can keep the default configuration, meaning that every newly created user will have the default DataDome role 'Viewer' and then you're done
  1. Choose the 'Customized roles' option to customize the role of every new user to map it to your Identity Provider roles
🚧

If you selected multiple workspaces, please note than this roles will be applied across all the selected workspaces

  1. Go back to your Identity Provider (Okta for example here) and add an Attribute to your Profile Editor
📘

Please note that every Identity Provider is different and you may need to adapt this configuration

  1. Click on 'Define enumerated list of values' and add the attribute members to map your roles into DataDome roles: Admin, Editor, Viewer
📘

Attribute mapping guidelines

To configure the first name and last name of your users, you must send one of the following attributes:

  • name: expected values is with first and last names separated by a space, ex: “John Doe”
  • or
  • first_name: expected values is "John" and last_name: expected values is "Doe"
  • or
  • firstName and lastName, same expected values as above
  • or
  • given_name and family_name, same expected values as above

For the role you can have:

  • either datadome_role or role with the following values: viewer, editor, admin (case insensitive)
  1. Choose 'Yes' for 'Attribute Required'
  1. Save your attribute configuration and you should see your Profile editor as shown below

  2. Then go back to DataDome Dashboard and 'Add AAC'

FAQ when configuring Automatic Account Creation

  1. What is Automatic Account Creation (user provisioning)?
    Automatic Account Creation (a.k.a User provisioning) is a process that creates user accounts and their profiles across IT infrastructure and business applications.
  2. How does user provisioning work in our DataDome Dashboard?
    DataDome utilizes SAML 2.0 to automate the process of creating, updating, and managing user accounts. It assigns roles to users, a default one (viewer), or any other role coming from your Identity Provider if you wish.
  3. How can I activate it?
    Just follow all the steps above from your main workspace if you have more than one.
  4. What are the prerequisites?
    You must have an SSO configuration up and running.
  5. What will happen if I activate it on my existing account with current users?
    If you activate it with the default role mapping, your current users won't be affected by these changes. On the contrary, if you choose the customized role mapping, please note that the roles of your current users will be impacted. If you map DataDome role 'viewer' to one of your roles on your Identity Provider, all your current users with this role will become 'viewer' on the DataDome Dashboard.
  6. Is my Identity Provider compatible?
    If your Identity Provider supports SAML 2.0 then it's compatible.
  7. How can I map the role from my Identity Provider?
    See the Step. 6 above.
  8. Can I delete users thanks to this feature? (de-provisioning)
    No, this feature is not available.
  9. Can I activate it on all my Workspace?
    Yes, please follow the step 2 above.
  10. I already have an SSO configured on one of my workspaces, can I use this feature to add my current on other workspaces?
    Yes, you can use this feature to add automatically your current users in another workspace if that's not the case. Follow the steps above from your main workspace to activate it.