|
| 1 | +--- |
| 2 | +id: mandiant-threat-intel-source |
| 3 | +title: Mandiant Threat Intel Source |
| 4 | +sidebar_label: Mandiant Threat Intel |
| 5 | +tags: |
| 6 | + - cloud-to-cloud |
| 7 | + - mandiant-threat-intel |
| 8 | +description: Learn how to collect indicators list from Mandiant Threat Intel platform. |
| 9 | +--- |
| 10 | +import CodeBlock from '@theme/CodeBlock'; |
| 11 | +import ExampleJSON from '/files/c2c/mandiant-threat-intel/example.json'; |
| 12 | +import MyComponentSource from '!!raw-loader!/files/c2c/mandiant-threat-intel/example.json'; |
| 13 | +import TerraformExample from '!!raw-loader!/files/c2c/mandiant-threat-intel/example.tf'; |
| 14 | +import useBaseUrl from '@docusaurus/useBaseUrl'; |
| 15 | + |
| 16 | +<img src={useBaseUrl('img/send-data/mandiant-threat-intel-logo.png')} alt="icon" width="60" /> |
| 17 | + |
| 18 | +Mandiant is a recognized leader in dynamic cyber defense, threat intelligence, and incident response services. By scaling decades of frontline experience, Mandiant helps organizations to be confident in their readiness to defend against and respond to cyber threats. Mandiant is part of Google Cloud. The Mandiant Threat Intel integration ingests the indicators data from Mandiant API and send it to Sumo as normalized threat indicators. |
| 19 | + |
| 20 | +## Data collected |
| 21 | + |
| 22 | +| Polling Interval | Data | |
| 23 | +| :--- | :--- | |
| 24 | +| 5 min | Indicators | |
| 25 | + |
| 26 | +## Setup |
| 27 | + |
| 28 | +### Vendor configuration |
| 29 | + |
| 30 | +:::note |
| 31 | +The Mandiant API documentation is not public and can only be accessed by partners or customers. |
| 32 | +::: |
| 33 | + |
| 34 | +The Mandiant Threat Intel source requires you to provide API Key ID and API Secret. |
| 35 | + |
| 36 | +### Source configuration |
| 37 | + |
| 38 | +When you create a Mandiant Threat Intel 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). |
| 39 | + |
| 40 | +To configure a Mandiant Threat Intel source: |
| 41 | +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**. |
| 42 | +1. On the Collection page, click **Add Source** next to a Hosted Collector. |
| 43 | +1. Search for and select **Mandiant Threat Intel**. |
| 44 | +1. Enter a **Name** for the Source. The description is optional. |
| 45 | +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`. |
| 46 | +1. (Optional) **Fields**. Click the **+Add** button to define the fields you want to associate. Each field needs a name (key) and value. |
| 47 | + *  A green circle with a check mark is shown when the field exists in the Fields table schema. |
| 48 | + *  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. |
| 49 | +1. **API Key ID**. Enter the API key ID collected from the Mandiant Threat Intel platform. |
| 50 | +1. **API Secret**. Enter the API secret collected from the from the Mandiant Threat Intel platform. |
| 51 | +1. **Sumo Logic Threat Intel Source ID**. Enter your Sumo Logic namespace ID in which the indicators will be stored. |
| 52 | +1. **Polling Interval**. The polling interval is set for 5 minutes by default. You can adjust it based on your needs. This sets how often the source checks for new data. |
| 53 | +1. **Processing Rules for Logs**. Configure any desired filters, such as allowlist, denylist, hash, or mask, as described in [Create a Processing Rule](/docs/send-data/collection/processing-rules/create-processing-rule). |
| 54 | +1. When you are finished configuring the source, click **Save**. |
| 55 | + |
| 56 | +## JSON schema |
| 57 | + |
| 58 | +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. |
| 59 | + |
| 60 | +| Parameter | Type | Value | Required | Description | |
| 61 | +|:--|:--|:--|:--|:--| |
| 62 | +| schemaRef | JSON Object | `{"type":"Mandiant Threat Intel"}` | Yes | Define the specific schema type. | |
| 63 | +| sourceType | String | `"Universal"` | Yes | Type of source. | |
| 64 | +| config | JSON Object | [Configuration object](#configuration-object) | Yes | Source type specific values. | |
| 65 | + |
| 66 | +### Configuration Object |
| 67 | + |
| 68 | +| Parameter | Type | Required | Default | Description | Example | |
| 69 | +|:--|:--|:--|:--|:--|:--| |
| 70 | +| 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"` | |
| 71 | +| description | String | No | `null` | Type a description of the source. | `"Testing source"` |
| 72 | +| 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"` |
| 73 | +| 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"}` | |
| 74 | +| apiKeyId | String | Yes | `null` | API Key ID of the user. | | |
| 75 | +| apiSecret | String | Yes | `null` | API Secret of the account. | | |
| 76 | +| userSourceId | String | Yes | `null` | The Sumo Logic namespace in which the indicators will be stored. | | |
| 77 | +| pollingInterval | integer | Yes | `5 minutes` | Time interval (in minutes) after which the source will check for new data. | | |
| 78 | + |
| 79 | +### JSON example |
| 80 | + |
| 81 | +<CodeBlock language="json">{MyComponentSource}</CodeBlock> |
| 82 | + |
| 83 | +<a href="/files/c2c/mandiant-threat-intel/example.json" target="_blank">Download example</a> |
| 84 | + |
| 85 | +### Terraform example |
| 86 | + |
| 87 | +<CodeBlock language="json">{TerraformExample}</CodeBlock> |
| 88 | + |
| 89 | +<a href="/files/c2c/mandiant-threat-intel/example.tf" target="_blank">Download example</a> |
| 90 | + |
| 91 | +## FAQ |
| 92 | + |
| 93 | +:::info |
| 94 | +Click [here](/docs/c2c/info) for more information about Cloud-to-Cloud sources. |
| 95 | +::: |
0 commit comments