Skip to content

Rapid7 InsightVM Data Warehouse

Connect Furl directly to the Rapid7 InsightVM Data Warehouse via Postgres for advanced vulnerability and asset reporting.

The InsightVM Data Warehouse is a Postgres-compatible export of your Rapid7 InsightVM data, intended for analytics and reporting. Connecting Furl to the warehouse lets it pull asset and vulnerability data at a level of detail that the Insight Platform API cannot easily expose, particularly for very large environments.

If you primarily want findings from the Insight cloud platform, use the standard Rapid7 InsightVM integration instead. Use this Data Warehouse integration when you need direct database access for high-volume reporting scenarios.

  1. Enable the InsightVM Data Warehouse export in your Rapid7 console. See Rapid7’s documentation on configuring data warehousing settings for the full setup.
  2. Create a database user with read-only access to the warehouse schema. Don’t reuse a personal account.
  3. Note the connection details: host, port, database name, username, password.
  4. Allow network access from Furl to the warehouse host. If the warehouse is on-premises, this typically means opening firewall rules or running a connector that exposes Postgres.

Provide the following in Furl:

  • Database Host — The hostname or IP of the InsightVM Data Warehouse.
  • Database Port — The Postgres port (typically 5432).
  • Database Name — The name of the warehouse database.
  • Database Username — The read-only user for the integration.
  • Database Password — The password for that user.
  • Assets → Retrieve assets directly from the InsightVM Data Warehouse.
  • Vulnerability Findings → Retrieve vulnerability findings directly from the InsightVM Data Warehouse.

Currently no actions are supported for this integration.

  • If Furl can’t connect, verify that the warehouse host is reachable from Furl’s network and that the port is open.
  • Confirm the credentials work by connecting from a separate Postgres client (psql, etc.) before configuring the integration.
  • The Data Warehouse schema can lag the Insight cloud platform by a refresh cycle. If a vulnerability appears in the cloud console but not via this integration, give the warehouse export a chance to refresh before assuming there’s a problem.