|
| 1 | +--- |
| 2 | +id: digital-guardian-source |
| 3 | +title: Digital Guardian Source |
| 4 | +sidebar_label: Digital Guardian |
| 5 | +tags: |
| 6 | + - cloud-to-cloud |
| 7 | + - digital-guardian |
| 8 | +description: Learn how to collect export data from the Digital Guardian and send it to Sumo Logic. |
| 9 | +--- |
| 10 | +import CodeBlock from '@theme/CodeBlock'; |
| 11 | +import ExampleJSON from '/files/c2c/digital-guardian/example.json'; |
| 12 | +import MyComponentSource from '!!raw-loader!/files/c2c/digital-guardian/example.json'; |
| 13 | +import TerraformExample from '!!raw-loader!/files/c2c/digital-guardian/example.tf'; |
| 14 | +import ForwardToSiem from '/docs/reuse/forward-to-siem.md'; |
| 15 | +import useBaseUrl from '@docusaurus/useBaseUrl'; |
| 16 | + |
| 17 | +<img src={useBaseUrl('img/send-data/digital-guardian-logo.svg')} alt="icon" width="50"/> |
| 18 | + |
| 19 | +Digital Guardian is a data protection platform that discovers, classifies, and controls data movement across endpoints, networks, and the cloud. Digital Guardian Analytics and Reporting Cloud (DG ARC) is an advanced analytics, workflow, and reporting cloud service that delivers no-compromise data protection. |
| 20 | + |
| 21 | +The Digital Guardian integration ingests the export data using the Export API and uses Acknowledge API to advance the bookmark value to obtain the next chunk of data from export endpoint. |
| 22 | + |
| 23 | +## Data collected |
| 24 | + |
| 25 | +| Polling Interval | Data | |
| 26 | +| :--- | :--- | |
| 27 | +| 5 min | Export data | |
| 28 | + |
| 29 | +## Setup |
| 30 | + |
| 31 | +### Vendor configuration |
| 32 | + |
| 33 | +The Digital Guardian source requires you to provide the Digital Guardian Base URL (API Gateway URL), Authentication Server URL, Client ID, Client Secret, and Profile to export to configure the source. Follow the below steps to generate the required values: |
| 34 | + |
| 35 | +1. From the ARC Tenant Settings, copy and save the **Tenant ID (API Client ID)** and **Authentication Token (API Secret)**. |
| 36 | +1. From the Digital Guardian Management Console (DGMC), copy the **Access Gateway Base URL (API Gateway URL)** and **Authorization server URL**. |
| 37 | +1. To copy ARC **Export Profile ID**: |
| 38 | + 1. Navigate to **Admin** > **reports** > **export profiles**. |
| 39 | + 1. Copy only the GUID part from the export profile. |
| 40 | + |
| 41 | +### Source configuration |
| 42 | + |
| 43 | +When you create a Digital Guardian Source, you add it to a Hosted Collector. Before creating the Source, identify the Hosted Collector you want to use or create a new Hosted Collector. For instructions, see [Configure a Hosted Collector and Source](/docs/send-data/hosted-collectors/configure-hosted-collector). |
| 44 | + |
| 45 | +To configure Digital Guardian Source: |
| 46 | +1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the Sumo Logic top menu select **Configuration**, and then under **Data Collection** select **Collection**. You can also click the **Go To...** menu at the top of the screen and select **Collection**. |
| 47 | +1. On the Collectors page, click **Add Source** next to a Hosted Collector. |
| 48 | +1. Search for and select the **Digital Guardian** icon. |
| 49 | +1. Enter a **Name** to display for the Source in Sumo Logic. The description is optional. |
| 50 | +1. (Optional) For **Source Category**, enter any string to tag the output collected from the Source. Category metadata is stored in a searchable field called `_sourceCategory`. |
| 51 | +1. (Optional) **Fields**. Click the **+Add Field** link to define the fields you want to associate. Each field needs a name (key) and value. |
| 52 | + *  A green circle with a check mark is shown when the field exists in the Fields table schema. |
| 53 | + *  An orange triangle with an exclamation point is shown when the field doesn't exist in the Fields table schema. In this case, an option to automatically add the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo Logic that does not exist in the Fields schema it is ignored, known as dropped. |
| 54 | +1. In **API Gateway URL**, enter the API Gateway URL of your account. |
| 55 | +1. In **Authorization Server URL**, enter the Authorization Server URL of your account. |
| 56 | +1. In **API Client ID**, enter the API Client ID you generated from the Digital Guardian platform. |
| 57 | +1. In **API Secret**, enter the API Secret you generated from the Digital Guardian platform. |
| 58 | +1. In **Export Profile**, enter the name of the profile that needs to be exported. |
| 59 | +1. The **Polling Interval** is set for 5 minutes hours by default. You can adjust it based on your needs. |
| 60 | +1. When you are finished configuring the Source, click **Save**. |
| 61 | + |
| 62 | +## JSON schema |
| 63 | + |
| 64 | +Sources can be configured using UTF-8 encoded JSON files with the Collector Management API. See [Use JSON to Configure Sources](/docs/send-data/use-json-configure-sources) for details. |
| 65 | + |
| 66 | +| Parameter | Type | Value | Required | Description | |
| 67 | +|:--|:--|:--|:--|:--| |
| 68 | +| schemaRef | JSON Object | `{"type":"Digital Guardian"}` | Yes | Define the specific schema type. | |
| 69 | +| sourceType | String | `"Universal"` | Yes | Type of source. | |
| 70 | +| config | JSON Object | [Configuration object](#configuration-object) | Yes | Source type specific values. | |
| 71 | + |
| 72 | +### Configuration Object |
| 73 | + |
| 74 | +| Parameter | Type | Required | Default | Description | Example | |
| 75 | +|:--|:--|:--|:--|:--|:--| |
| 76 | +| name | String | Yes | `null` | Type a desired name of the source. The name must be unique per Collector. This value is assigned to the [metadata](/docs/search/get-started-with-search/search-basics/built-in-metadata) field `_source`. | `"mySource"` | |
| 77 | +| description | String | No | `null` | Type a description of the source. | `"Testing source"` |
| 78 | +| category | String | No | `null` | Type a category of the source. This value is assigned to the [metadata](/docs/search/get-started-with-search/search-basics/built-in-metadata) field `_sourceCategory`. See [best practices](/docs/send-data/best-practices) for details. | `"mySource/test"` |
| 79 | +| fields | JSON Object | No | `null` | JSON map of key-value fields (metadata) to apply to the Collector or Source. Use the boolean field `_siemForward` to enable forwarding to SIEM.|`{"_siemForward": false, "fieldA": "valueA"}` | |
| 80 | +| APIGatewayURL | String | Yes | `null` | API Gateway URL of your account. | | |
| 81 | +| authServerURL | String | Yes | `null` | Authorization Server URL of your account. | | |
| 82 | +| clientID | String | Yes | `null` | API Access ID of your account. | | |
| 83 | +| clientSecret | String | Yes | `null` | API Secret of your account. | | |
| 84 | +| exportProfile | String | Yes | `null` | Profile to be exported. | | |
| 85 | +| pollingIntervalMin | Integer | Yes | 5 mins | Set to true to duplicate logs for each element in the users array. | | |
| 86 | + |
| 87 | +### JSON example |
| 88 | + |
| 89 | +<CodeBlock language="json">{MyComponentSource}</CodeBlock> |
| 90 | + |
| 91 | +<a href="/files/c2c/digital-guardian/example.json" target="_blank">Download example</a> |
| 92 | + |
| 93 | +### Terraform example |
| 94 | + |
| 95 | +<CodeBlock language="json">{TerraformExample}</CodeBlock> |
| 96 | + |
| 97 | +<a href="/files/c2c/digital-guardian/example.tf" target="_blank">Download example</a> |
| 98 | + |
| 99 | +## FAQ |
| 100 | + |
| 101 | +:::info |
| 102 | +Click [here](/docs/c2c/info) for more information about Cloud-to-Cloud sources. |
| 103 | +::: |
0 commit comments