---
title: "Mandiant Advantage collector"
canonical: "https://docs.devo.com/space/latest/386859012/Mandiant%20Advantage%20collector"
format: markdown
---
> Macro (toc)
## Overview
Mandiant takes an intelligence-led, multi-vendor approach to XDR, enhancing existing security controls and enabling the SOC to improve efficiency and efficacy in finding malicious security incidents quickly and at scale.
The Mandiant Advantage collector allows users to ingest alerts and create lookups based on Mandiant threat intelligence.
## Devo collector features
| **Feature** | **Details** |
| --- | --- |
| Allow parallel downloading (`multipod`) | `not allowed` |
| Running environments | - `collector server`
- `on-premise` |
| Populated Devo events | - `table`
- `lookups` |
| Flattening preprocessing | `no` |
| Allowed source events obfuscation | `yes` |
## Data sources
| **Data source** | **Description** | **API endpoint** | **Collector service name** | **Devo table** | **Available from release** |
| --- | --- | --- | --- | --- | --- |
| Mandiant Advantage Digital Threat Monitoring | DTM Alerts | `/v4/dtm/alerts` | `dtm_alert` | `xdr.mandiant.threatintel.dtm_alert` | v0.0 |
| Mandiant Threat Intelligence | Indicators | `/v4/indicator` | `indicator` | N/A | v0.0 |
For more information on how the events are parsed, [visit our page](https://devodocs.atlassian.net/wiki/spaces/latest/pages/387219457).
## Minimum configuration required for basic pulling
Although this collector supports advanced configuration, the fields required to retrieve data with basic configuration are defined below.
> ℹ️ This minimum configuration refers exclusively to those specific parameters of this integration. There are more required parameters related to the generic behavior of the collector. Check setting sections for details.
| **Setting** | **Details** |
| --- | --- |
| `api_key_public` | The Mandiant public API key |
| `api_key_secret` | The Mandiant secret API key |
> ℹ️ See the **Accepted authentication methods** section to verify what settings are required based on the desired authentication method.
## Accepted authentication methods
| | |
| --- | --- |
| **Authentication method** | **API key public / secret** |
| API key | Required |
## Run the collector
Once the data source is configured, you can either send us the required information if you want us to host and manage the collector for you (Cloud collector), or deploy and host the collector in your own machine using a Docker image (On-premise collector).
> Macro (rw-ui-tabs-macro)
>
> > Macro (rw-tab)
>
> We use a piece of software called Collector Server to host and manage all our available collectors. If you want us to host this collector for you, [get in touch with us](https://devo.my.site.com/support/login?ec=302&startURL=%2Fsupport%2Fs%2F) and we will guide you through the configuration.
>
> > Macro (rw-tab)
>
> This data collector can be run in any machine that has the Docker service available because it should be executed as a docker container. The following sections explain how to prepare all the required setup for having the data collector running.
>
> ### Structure
>
> The following directory structure should be created for being used when running the collector:
>
> ```
>
> └── devo-collectors/
> └── /
> ├── certs/
> │ ├── chain.crt
> │ ├── .key
> │ └── .crt
> ├── state/
> └── config/
> └── config.yaml
> ```
>
> > ⚠️ Replace `` with the proper value.
>
> ### Devo credentials
>
> In Devo, go to **Administration → Credentials → X.509 Certificates**, download the **Certificate**, **Private key** and **Chain CA** and save them in `/certs/`. Learn more about security credentials in Devo [here](#).
>
> 
>
> > ⚠️ Replace `` with the proper value.
>
> ### Editing the config.yaml file
>
> ```
> globals:
> debug:
> id: not_used
> name: mandiant_advantage
> persistence:
> type: filesystem
> config:
> directory_name: state
> outputs:
> devo_us_1:
> type: devo_platform
> config:
> address:
> port: 443
> type: SSL
> chain:
> cert:
> key:
> inputs:
> mandiant_advantage:
> id:
> enabled: true
> environment:
> credentials:
> api_key_public:
> api_key_secret:
> services:
> dtm_alert:
> override_tag:
> start_time_in_utc:
> obfuscation_data: []
> indicator:
> override_base_lookup_name:
> override_m_score_threshold:
> override_lookback_days:
> ```
>
> > ℹ️ All defined service entities will be executed by the collector. If you do not want to run any of them, just remove the entity from the `services` object.
>
> Replace the placeholders with your required values following the description table below:
>
> | | | | | |
> | --- | --- | --- | --- | --- |
> | **Parameter** | **Data type** | **Type** | **Value Range / Format** | **Details** |
> | `debug_status` | `bool` | mandatory | true / false | If the value is `true`, the debug logging traces will be enabled when running the collector. If the value is `false`, only the info, warning, and error logging levels will be printed. |
> | `devo_address` | `str` | mandatory | - collector-us.devo.io
> - collector-eu.devo.io | Use this parameter to identify the Devo Cloud where the events will be sent. |
> | `chain_filename` | `str` | mandatory | minimum length: 4 maximum length: 20 | Use this parameter to identify the chain.cert file downloaded from your Devo domain. Usually this file's name is: `chain.crt`. |
> | `cert_filename` | `str` | mandatory | minimum length: 4 maximum length: 20 | Use this parameter to identify the file.cert downloaded from your Devo domain. |
> | `key_filename` | `str` | mandatory | minimum length: 4 maximum length: 20 | Use this parameter to identify the file.key downloaded from your Devo domain. |
> | `input_id_value` | `str` | mandatory | minimum length: 1 maximum length: 5 | Use this parameter to give a unique ID to this input service. > ⚠️ This parameter is used to build the persistence address; do not use the same value for multiple collectors. It could cause a collision. |
> | `environment_value` | `str` | optional | minimum length: 1 | This is an optional control parameter that is injected into the events and allows you to differentiate the environment. For example: dev and prod. > ℹ️ This parameter should be removed if it is not used. |
> | `api_key_public_value` | `str` | mandatory | minimum length: 1 | The Mandiant Advantage public API key |
> | `api_key_secret_value` | `str` | mandatory | minimum length: 1 | The Mandiant Advantage secret API key |
> | `override_tag_value` | `str` | optional | Devo tag-friendly string (no special characters, spaces, etc.) For more information see [Devo Tags](https://docs.devo.com/space/latest/95126204/About%20Devo%20tags). | An optional tag that allows users to override the service default tags. > ℹ️ This parameter can be removed or commented. |
> | `start_time_in_utc_value` | `str` | optional | UTC datetime string having datetime string format `%-Y-%m-%d %H-%M-%S` (e.g., “`2000-01-01 00:00:01`”) | This configuration allows you to set a custom date as the beginning of the period to download. This allows downloading historical data (one month back for example) before downloading new events. > ℹ️ This parameter should be removed if it is not used. |
> | `obfuscation_data_values` | `array