Incoming feed - Flashpoint Indicator Intelligence feed

This article describes how to configure incoming feeds for a particular feed source. To see how to configure incoming feeds in general, see Configure incoming feeds general options.

Specifications

Transport types

Flashpoint Indicator Intelligence feed

Content type

Flashpoint v4 JSON

Ingested data

Ingests events and their attributes.

Endpoint(s)

https://fp.tools/api/v4/indicators/attribute

Processed data

Produces indicators.

Requirements

  • Flashpoint API key

Execution schedule recommendation

The Execution schedule field allows you to set the feed to run automatically at specified intervals. Running the feed too frequently can strain resources and exhaust API rate limits. The Execution schedule field is set to None by default.

Reduce the frequency with which the feed runs if you run into the following issues:

  • Feed has stopped downloading new packages from Flashpoint for a number of days.

  • Feed encounters a rate limit error from Flashpoint, causing it to fail.

To fix these issues, you can:

  • Manually run the incoming feed. Set the Execution schedule to None.

  • Or automatically run the incoming feed a maximum of once every 2 hours:

    1. Set the Execution schedule to: Every [n] hours

    2. Then, select 2 from the drop-down menu that appears below so that the line reads:

      “Every 2 hours”

Configure the incoming feed

  1. Create or edit an incoming feed.

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

    Required fields are marked with an asterisk (*).

    Field

    Description

    Transport type*

    Select Flashpoint Indicator Intelligence feed from the drop-down menu.

    Content type*

    Select Flashpoint v4 JSON from the drop-down menu.

    API URL*

    By default, this is set to https://fp.tools/api/v4/indicators/attribute.

    API key*

    Set this to your Flashpoint API key.

    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.

    For more information, 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 with the platform, it must be:

  • Accessible on the EclecticIQ Platform host.

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

  • Owned by eclecticiq:eclecticiq.

To make sure that the platform can access the SSL certificate:

  1. Upload the SSL certificate to a location on the platform host.

  2. On the platform 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 the platform needs to access.