Resolve supports integration with several types of tools and products. While the overall setup is similar for each integration, the data flow depends on the type of integration.

Figure 1. Integration data flow
  • Ticketing —Finding information is shared between Resolve and the ticketing system. The data flow is bi-directional.
    Note: *Currently only uni-directional flow from Resolve to ServiceNow is supported.
  • Scanners — Resolve imports finding data from scanners.
  • CMDBs — Resolve imports asset data from a CMDB.
  • Notifications — Resolve exports finding data to a notification tool.

Setup overview

Each integration is set up and configured in the Resolve interface. For integrations that require data import, you must specify the business unit, site, zone, or project to import data to.

Once the configuration is saved and the connection is established, Resolve imports or exports data depending on the integration type. After the initial data sync, Resolve periodically syncs to the product or tool's API. The frequency of the sync is configured on a per-integration basis using a cron expression.

When importing data, Resolve keeps track of which files have been imported from the scanner or tool so that data is not imported twice. The original scan files are stored in the Resolve database for 30 days. However, vulnerability data in business units and projects are always retained.

Multiple instances of the same integration are supported. For example, you might have two separate ServiceNow servers in your organization. You can configure two ServiceNow integrations in Resolve, one for each server.