---
sourceDocument: Australia Security Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/security-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Manage Unified Security Exposure Management integrations

# Manage Unified Security Exposure Management integrations {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Manage Unified Security Exposure Management integrations

This guide explains how to manage, monitor, and review integrations within the Unified Security Exposure Management (USEM) framework in ServiceNow.
The integration dashboard centralizes visibility of installed third-party applications and the status of their integration runs, helping customers maintain a healthy and effective security exposure management process.
Show full answer Show less  

## Accessing and Configuring Integrations

* **Access:** Navigate to *Workspaces \> Security Exposure Management \> Administration \> Integrations* to access the integration dashboard and review integration details.
* **Configuration Options:** Integrations can be configured either via the unified exposure pipeline for scanners or through standard applications available on the ServiceNow Store.

## Monitoring and Reviewing Integrations

The integration dashboard provides multiple data visualization widgets to track integration health and performance:

* **Integration Runs (Vertical Bar):** Displays the count of successful and failed integration runs over the past 7 and 30 days. Common failure causes include network interruptions and data corruption during transformation. Re-running with full data import can resolve such issues.
* **Ingestion Health Highlights:** Shows import queue processing times, wait times, and REST API performance.
* **Processing Health (Multiple Lines):** Provides metrics on assignment rules, remediation tasks, CI lookups, risk rules, and vulnerability intelligence creation times over 30 days to identify performance deviations. This is not shown for scanner integrations using the unified exposure pipeline.
* **Integrations List and Integration Runs List:** Display detailed run information for standard and scanner integrations respectively.

## Integration Details and Run Tracking

Key integration attributes include name, active status, run schedule, last run status, and notes. Integration runs are tracked with details such as run ID, job type, timings, status, errors, fetched data counts, and normalization statistics for assets and vulnerabilities.

Note that for Tenable.sc integrations, authentication tokens expire on failures but are automatically regenerated for subsequent runs. Integration processes handle data in pages within import queue entries, observing strict processing time limits to avoid timeouts.

## Handling Integration Timeouts and Heartbeats

To manage large payload processing and avoid integration stalls, the system sends periodic heartbeat timestamps to confirm active processing. If an import queue entry exceeds a one-hour processing limit without progress, it is timed out. These behaviors are governed by system properties controlling heartbeat frequency and maximum allowed delay.

## Configuring Scanner Integrations Using the Unified Exposure Pipeline

For scanners, USEM normalizes assets, labels, and detections into a unified format before ingestion, ensuring consistent and reliable data integration across the security exposure management lifecycle.  
Manage, monitor, and review integrations.The integration dashboard provides an overview of the installed third-party applications and the status of the integration runs.  

## Accessing the Integration dashboard {#review-usem-integrations__section_hfc_mk1_kzb}

Navigate to WorkspacesSecurity Exposure ManagementAdministration and select Integrations.

## Configuring integrations {#review-usem-integrations__section_hfc_mk1_fgp}

You can configure integrations in any of the following ways:

* Using the unified exposure pipeline, you can configure scanners. See [Configure a scanner integration using the unified exposure pipeline](https://www.servicenow.com/docs/vKJzIsI3oF8dSDJq3Gbnbw "For a scanner, normalize assets, labels, and detections into one consistent format before this data reaches Unified Security Exposure Management.").
* From ServiceNow Store, you can configure all standard integration applications (scanners and other integrations).

## Reviewing integrations {#review-usem-integrations__section_nfc_mk1_kzb}

Navigate to WorkspacesSecurity Exposure ManagementAdministrationIntegrations and select Review for the required integration.  
{#review-usem-integrations__table_n43_yv4_mbc__entry__3}

| Data | Type | Description |
|-|-|-|
| Integration runs | Vertical Bar | The number of integration runs completed for each integration. Shows both successful and failed runs in the past 7 and 30 days. The most common causes for a failed run include: * Network interruption * Bit decay in the data transfer resulting in corrupted data during the transform {#review-usem-integrations__check-imports-shodan_ul_ecy_cnn_xcb}If you encounter any of these conditions, select the Full data import check box, click Execute Now, and rerun the integration. |
| Ingestion health | Highlights | Provides information on the following: * Import queue processing time. * Import queue wait time. * REST API time. {#review-usem-integrations__ul_rgk_rgn_ggc} |
| Processing health | Multiple lines | Provides performance metrics for assignment rules, remediation task rules, CI lookup time, risk rules, and VI creation time for the last 30 days, to identify the cause for any deviations in performance. The performance is calculated based on the time taken for each activity. These parameters are calculated and associated at the integration run level. Each parameter is color coded for easy identification. Note: It is not displayed for scanner integrations configured using the unified exposure pipeline. |
| Integrations | List | Provides information about the integration run. Note: It is displayed only for standard integrations. |
| Integration runs | List | Provides information about the fetch and normalization runs of the integration. Note: It is displayed only for scanner integrations configured using the unified exposure pipeline. |
[Table 1. Data visualization widgets]

{#review-usem-integrations__table_n43_yv4_mbc}  
Note:  
Multiple factors can impact the performance of the integration run, like the amount of data and time taken to process this data.
{#review-usem-integrations__table_bd1_cw4_mbc__entry__2}

| Name | Description |
|-|-|
| Name | Name of the integration. |
| Active | Status of the integration whether active or not. |
| Run | Run schedule of the integration |
| Day | Day on which the integration runs. |
| Time | Time at which the integration runs. |
| Last run status | Status of the last integration run whether failed or successful. |
| Notes | Notes |
[Table 2. Integrations]

{#review-usem-integrations__table_bd1_cw4_mbc} {#review-usem-integrations__table-advanced-integration-runs__entry__2}

| Column | Description |
|-|-|
| Run ID | Identifier of the fetch run. |
| Type | Job type of the run. |
| Run time | Time of the run. |
| Status | Status of the run. |
| Error | Errors that occurred during the run, such as authentication, permission, or configuration errors. |
| Notes | Notes about the run. |
| Fetched data | Counts of the records fetched from the scanner in the run. |
| Fetch time | Time that the fetch took. |
| Normalized assets | Counts of the assets that the run normalized, such as new, modified, unchanged, skipped, and failed assets. |
| Normalized vulnerabilities | Counts of the vulnerabilities that the run normalized, such as new, modified, unchanged, skipped, and failed vulnerabilities. |
| Normalization time | Time that normalization took. |
[Table 3. Integration runs]

{#review-usem-integrations__table-advanced-integration-runs}  
Note:  
If a Tenable.sc integration run fails for any reason, the authentication token for Tenable.sc automatically expires and a message is displayed on the Vulnerability Integration Process record. A new token is automatically generated for the next integration process. All the integration processes, failed and successful, are displayed on the Vulnerability Integration Process tab on the Vulnerability Integration Process record.  
During integration execution, multiple processes are generated, and data is received in the form of pages. Each process can contain one or more import queue entries with attached data in pages. These entries must process the data within the one-hour time limit. However, if the payload size is large, the processing time may exceed one hour or get stuck, resulting in an integration timeout error. The integration continues to process the data despite the timeout error. To avoid this miscommunication, timestamps (heartbeats) are sent periodically to indicate if the queue is active and processing data. The Last Record Processed field in the Import Queue Entry page is updated based on the count of records the import queue creates or updates. In case an import queue entry exceeds the one-hour time limit, the system checks the Last Record Processed field to see if it is also older than one hour. If it is, this indicates that the import queue entry is stuck, and it is timed out to prevent any further delays in processing. The Last Record Processed field is updated based on what is defined in the following system properties:

* sn_sec_cmn.record_threshold_heartbeat: Defines the number of processed records, after which the heartbeat (timestamp) is sent to the import queue entry.
* sn_sec_cmn.maximum_heartbeat_delay: Defines the time after which the import queue entry must be timed out.
{#review-usem-integrations__fortify-check-imports_ul_g23_sgw_dyb}
* **[Configure a scanner integration using the unified exposure pipeline](https://www.servicenow.com/docs/vKJzIsI3oF8dSDJq3Gbnbw)**   
  For a scanner, normalize assets, labels, and detections into one consistent format before this data reaches Unified Security Exposure Management.

*[\>]: and then


