How to Configure PII Enterprise Security

Step 1: Log in to DoubleTick

Log in to your DoubleTick account using the Primary Owner's credentials, as only the owner has permission to configure Enterprise Security.


Step 2: Open Settings

From the dashboard, navigate to Settings.


Step 3: Find Enterprise Security

In Settings, search for Enterprise Security and open it.

You will see two configuration options:

  • Block Sensitive Information

  • IP Address Restriction

To learn more about IP Address Restriction, refer to the dedicated documentationarrow-up-right.


Step 4: Open Block Sensitive Information

Click Block Sensitive Information to configure how sensitive text and media should be handled.

You will see two sections:

  • Media Blocking

  • Text Blocking


Step 5: Configure Media Blocking

Enable the toggle for Media Blocking.

You can choose one of the following options:

Reject Media containing sensitive data will be blocked.

Blur Sensitive information in media will be blurred before storing or sharing.


Step 6: Configure Text Blocking

Enable the toggle for Text Blocking.

You can choose how text messages containing sensitive information should be handled:

Reject Messages containing sensitive data will not be sent.

Mask Sensitive information inside the message will be hidden.


Step 7: Add Your Security API Endpoint

Provide your Security API Endpoint URL.

This API analyzes the message or media and returns the response indicating whether sensitive data exists and how it should be handled.

Your organization’s technical team typically provides this API.


Step 8: Save and Connect

After adding the API endpoint and selecting your preferred settings: Save the configuration & Connect the API

Once configured, all messages and media will follow the security rules defined by your API.


Enterprise Security enables organizations to enforce their own data protection policies while communicating with customers. By integrating existing security systems with DoubleTick, enterprises can ensure that sensitive information is consistently protected across conversations.

Last updated