Incoming feed - Mandiant Threat Intelligence Feed v4 (Campaign Feed)#

Specifications

Transport type

Mandiant Threat Intelligence Feed v4 (Campaign Feed)

Content type

Mandiant Threat Intelligence Feed v4 (Campaign Feed)

Ingested data

Mandiant Threat Intelligence campaigns

Processed data

Retrieves and processes campaigns

Requirements#

  • Mandiant Threat Intelligence subscription. Check the Mandiant Documentation to see which subscription you have access to.

  • Mandiant API key ID.

  • Mandiant API secret.

Configure the incoming feed#

  1. Create or edit an incoming feed.

  2. Under Transport and content, fill out these fields:

    Note

    Required fields are marked with an asterisk (*).

    Field

    Description

    Transport type*

    Select Mandiant Threat Intelligence Feed v4 (Campaign Feed) from the drop-down menu.

    Content type*

    Select Mandiant Threat Intelligence Feed v4 (Campaign Feed) from the drop-down menu.

    API URL*

    Default: https://api.intelligence.mandiant.com

    Mandiant API key*

    Set this to your Mandiant API key ID.

    Mandiant API secret*

    Set this to your Mandiant API secret.

    Campaign Historic time*

    Enter the number of months to calculate the status of campaigns.

    If the last activity of a campaign happened before the selected number of months, the status of the campaign will be set to Historic.

    Otherwise it will be set to Ongoing.

    SSL verification

    Selected by default. Select this option to enable SSL for this feed.

    Path to SSL certificate file.

    Used when connecting to a feed source that uses a custom CA. Set this as the path to the SSL certificate to use when authenticating the feed source.

    See SSL Certificates.

    Start ingesting from*

    Ingest data from the feed source starting from this date and time. Use the drop-down calendar to select the date and time you want to start ingesting feed data from.

  3. Store your changes by selecting Save.

SSL Certificates#

To use an SSL certificate, it must be:

  • Accessible on the EclecticIQ Intelligence Center host.

  • Placed in a location that can be accessed by the eclecticiq user.

  • Owned by eclecticiq:eclecticiq.

To make sure that EclecticIQ Intelligence Center can access the SSL certificate:

  1. Upload the SSL certificate to a location on the EclecticIQ Intelligence Center host.

  2. On the EclecticIQ Intelligence Center host, open the terminal.

  3. Change ownership of the SSL certificate by running as root in the terminal:

    chown eclecticiq:eclecticiq /path/to/cert.pem

    Where /path/to/cert.pem is the location of the SSL certificate EclecticIQ Intelligence Center needs to access.