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

Specifications

Transport type

Mandiant Threat Intelligence Feed v4 (Malware Feed)

Content type

Mandiant Threat Intelligence Feed v4 (Malware Feed)

Ingested data

Mandiant Threat Intelligence malwares

Processed data

See Data Mapping

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 (Malware Feed) from the drop-down menu.

    Content type*

    Select Mandiant Threat Intelligence Feed v4 (Malware 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.

    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.

  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.

Data Mapping#

Note

On EclecticIQ Intelligence Center 2.14, this extension produces TTP entities instead of Malware entities.

EIQ JSON field

Mandiant

Description

ID

malwares[malware].name

<UUID v5 based on malwares[malware].name>

Title

malwares[malware].name

Malware: <Value stored in malwares[malware].name>

Type

N/A

malware

Description

  • malwares[malware].description

  • malwares[malware].capabilites[capability].description

  • malwares[malware].detections[detection]

Value stored in malwares[malware].description

Estimated time: Observed

malwares[malware].last_updated

Timestamp in ISO8061 format

Observables

  • malwares[malware].aliases[alias].name

  • malwares[malware].actors[actor].name

  • malwares[malware].malware[malware].name

  • malwares[malware].cve[cve].cve_id

See Map to Observables for Malware

Tags

  • malwares[malware].operating_systems[os_system]

  • malwares[malware].detections[detection]

  • malwares[malware].roles[role]

  • malwares[malware].actors[actor].name

  • malwares[malware].capabilites[capability].name

  • malwares[malware].aliases[alias].name

  • actors[actor].audience.license

List of tags from the values found in the attributes listed in the previous column

TLP

actors[actor].audience.license

List of TLP colors found in all entries of actors[actor].audience[audience].license

Map to Observables for Malware#

EIQ Observable Types

Mandiant JSON field

actor-id

malwares[malware].aliases[alias].name

malware

  • malwares[malware].actors[actor].name

  • malwares[malware].malware[malware].name

cve

malwares[malware].cve[cve].cve_id