Skip to main content

Fortra DLP

Visualize Fortra Digital Guardian DLP watchlists, user groups, host groups, incidents, and monitor data loss prevention events through queries and alerts.

Installation​

Prerequisites in Fortra Digital Guardian​

info

You will need the following parameters from your Digital Guardian Analytics & Reporting Cloud (ARC) account:

  • Access Gateway URL: The base URL for API requests
    • Example: https://accessgw-usw.msp.digitalguardian.com
  • Authorization Server URL: The OAuth2 token endpoint URL
    • Example: https://authsrv.msp.digitalguardian.com
  • Client ID: Your API Client ID (Tenant ID)
  • Client Secret: Your API Secret (Authentication Token)

Obtaining API Credentials​

  1. Log in to the Digital Guardian Management Console (DGMC).

  2. Navigate to ARC Tenant Settings.

  3. Copy and save the following values:

    • Tenant ID — This is your Client ID
    • Authentication Token — This is your Client Secret

  4. From the DGMC, also copy:

    • Access Gateway Base URL
    • Authorization Server URL

Export Profiles (Optional)​

To ingest DLP incidents or agent version data, configure Export Profiles in Digital Guardian before setting up the JupiterOne integration:

  1. In DGMC, navigate to Admin > Reports > Export Profiles.

  2. Create or identify the export profile(s) you want to use.

  3. Copy the Export Profile ID (UUID) for each profile.

For more information, see the Fortra Digital Guardian product page.

Configuration in JupiterOne​

To install the Fortra DLP integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Fortra DLP. Click New Instance to begin configuring your integration.

Creating an instance requires the following:

  • The Account Name used to identify the Fortra DLP account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.

  • Description to assist in identifying the integration instance, if desired.

  • Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.

  • Your Digital Guardian Access Gateway URL — The base URL for API requests.

  • Your Digital Guardian Authorization Server URL — The OAuth2 token endpoint.

  • Your Digital Guardian Client ID and Client Secret for OAuth2 authentication.

Click Create once all values are provided to finalize the integration.

Data Volume Configuration​

Data Filtering Options​

The following optional fields control which data the integration ingests. Leave both blank to skip incident and agent-version enrichment ingestion.

FieldDescriptionDefault
Export Profile IDsComma-separated UUIDs of Export Profiles to fetch DLP incidents from. Each profile must be pre-configured in DGMC. Leave blank to skip incident ingestion.(none)
Agent Version Export Profile IDsComma-separated UUIDs of Export Profiles used to enrich host agents with their Digital Guardian agent version. The profiles must include the dg_machine_name, dg_agent_version, and dg_guid fields and must be pre-configured in DGMC. Leave blank to skip agent-version enrichment.(none)

Next steps​

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.