Skip to main content
Investigation Insights (formerly Polarity) is a Dataminr product that overlays threat intelligence on the tools analysts already use, so an indicator gets context wherever it appears on screen, from a ticket to a terminal window. The Pulsedive integration adds Pulsedive as one of those sources, so an IP or domain anywhere on your screen gets an overlay with its Pulsedive risk data, without a manual lookup.

Prerequisites

Before you connect Investigation Insights to Pulsedive, make sure you have:
  • A Pulsedive account and API key. Find your API key on your Pulsedive account page. A free key works, though it is rate-limited to 30 requests per minute.
  • Access to your Polarity= Server’s integrations directory, with permission to install and configure integrations.

Connecting Investigation Insights to Pulsedive

Follow these steps to install and configure the Pulsedive integration on your Polarity Server:
  1. Go to Polarity’s Pulsedive integration’s releases page on GitHub and download the .tgz file for your Polarity Server version.
  2. Upload the file to your Polarity Server’s integrations directory (/app/integrations).
  3. In the Investigation Insights admin console, open the Pulsedive integration’s settings and enter your Pulsedive API key.
  4. Choose which risk levels to display and whether to show indicators with unknown risk, so the overlay only surfaces what is relevant to your team.
  5. Save the configuration.
To learn more, visit Polarity’s Pulsedive integration on GitHub.

Verifying the Connection

Confirm that Investigation Insights is returning Pulsedive data before you rely on it during an investigation.
  1. Open a page or document containing an IP or domain you know Pulsedive has data on.
  2. Confirm that an Investigation Insights overlay with Pulsedive risk data appears.

Using Pulsedive Data in Investigation Insights

Once configured, Investigation Insights surfaces Pulsedive data automatically on any IP or domain on your screen. Use the Ignored Entities and Ignored Domain Regex settings to keep the overlay focused, so internal or noisy domains don’t clutter your results.