Configure EDM CLI App Connectivity to Enterprise DLP

1. Create a Service Account for EDM Dataset Uploads.
2. Set Up the EDM CLI App.

   Download EDM CLI app version 3.0 or later version to upload an EDM dataset to a TSG-supported tenant.

   Download EDM CLI app version 3.5 or later to create an encrypted EDM dataset in an air-gapped environment.
3. On the local device where you downloaded the EDM CLI app, navigate to and open the upload configuration file.

   The EDM CLI app bundles the upload configuration file with the package-edm-secure-cli-<version>-<platform>.zip file contents you extracted when you set up the EDM CLI app.

   The name of the upload configuration file for Linux and Windows versions of the EDM CLI display as:

   • Linux—upload_config.properties
   • Windows—upload_config

4. Configure the upload configuration file to enable connectivity to Enterprise DLP.

   • EDM CLI App Version 4.0 and 5.0
     1. Add the client_id and client_secret.
        EDM CLI app version 4.0 and later support connections to Enterprise DLP using the Client ID and Client Secret only. EDM CLI app version 4.0 and later doesn't support connections to Enterprise DLP using Access and Refresh API tokens.
     2. (Proxy server only) Configure the proxy server settings.
        Skip this step if you don't require a proxy server for the local device to connect to the internet.
        • Specify whether the local device uploading the EDM dataset to Enterprise DLP requires a proxy server to the connect to the internet.
          If you don't require a proxy server, enter no (default).
          If you require a proxy server, enter yes.
        • Enter the proxy_host_name and proxy_port_number.
        • Enter the proxy_user_name and proxy_password.
     3. Enter the dataset_name for the EDM dataset you want to upload. Enterprise DLP uses the dataset name entered here in Strata Cloud Manager for the uploaded EDM dataset.
     4. (FedRAMP only) Configure the FedRAMP settings.
        Skip this step if not uploading to a FedRAMP Enterprise DLP environment.
        • In the fed_ramp field, enter yes if uploading an EDM dataset to a FedRAMP Enterprise DLP environment.
        • In the fed_ramp_level field, enter the FedRAMP impact level (moderate or high)
     5. Enter the region_name to specify a specific region where you want your hashed and encrypted EDM datasets uploaded if your organization must adhere to data residency requirements.
        Review the list of FQDNs for EDM for a full list of supported regions. Enter the Country name in the region_name field. The default region_name is United States.
     6. Save the changes to the upload configuration file.

   • EDM CLI App Version 6.0 and Later
     1. Add the client_id and client_secret.
        (EDM CLI App 6.0 and Later) Add the client_id and client_secret if encrypted when creating your service account.
     2. (Proxy server only) Configure the proxy server settings.
        Skip this step if you don't require a proxy server for the local device to connect to the internet.
        • Specify whether the local device uploading the EDM dataset to Enterprise DLP requires a proxy server to the connect to the internet.
          If you don't require a proxy server, enter no (default).
          If you require a proxy server, enter yes.
        • Enter the proxy_host_name and proxy_port_number.
        • Enter the proxy_user_name and proxy_password.
     3. Enter the dataset_name for the EDM dataset you want to upload. Enterprise DLP uses the dataset name entered here in Strata Cloud Manager for the uploaded EDM dataset.
     4. (FedRAMP only) Configure the FedRAMP settings.
        Skip this step if not uploading to a FedRAMP Enterprise DLP environment.
        • In the fed_ramp field, enter yes if uploading an EDM dataset to a FedRAMP Enterprise DLP environment.
        • In the fed_ramp_level field, enter the FedRAMP impact level (moderate or high)
     5. Enter the region_name to specify a specific region where you want your hashed and encrypted EDM datasets uploaded if your organization must adhere to data residency requirements.
        Review the list of FQDNs for EDM for a full list of supported regions. Enter the Country name in the region_name field. The default region_name is United States.
     6. Save the changes to the upload configuration file.

5. (Air-gapped Environments only) Create the environment.properties file to instruct the EDM CLI app to skip checking for a connection to Enterprise DLP.

   By default, the EDM CLI app connects to Enterprise DLP each time you create an encrypted EDM dataset to verify the CLI app version. Encrypted EDM dataset creation fails when running an unsupported EDM CLI app version or if the EDM CLI app can't connect to Enterprise DLP.

   The EDM CLI app version 3.5 and later check for the existence of environment.properties file every time you create an encrypted EDM dataset. The environment.properties file instructs the EDM CLI app to skip connecting to Enterprise DLP to allow you to create the encrypted EDM dataset.

   1. Open a new text editor and enter the following:

      skip_dlp_api_call_for_create_cmd=true

   2. Save the ext file your EDM CLI app configuration folder using the exact name below:

      environment.properties

   3. Save the changes to the environment.properties file.
6. Create and upload your EDM datasets to Enterprise DLP.

   • Upload an Encrypted EDM Data Set to Enterprise DLP Using a Configuration File
   • Create and Upload an Encrypted EDM Data to Enterprise DLP in Interactive Mode