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

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Review Unified Security Exposure Management integrations

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

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 Review Unified Security Exposure Management integrations

The Review Unified Security Exposure Management integrations feature provides a centralized dashboard to monitor installed third-party security integrations and their run statuses.
It enables ServiceNow customers to track integration performance, identify issues, and manage data ingestion efficiently within the Security Exposure Management Workspace.
Show full answer Show less  

## Accessing the Integration Dashboard

Customers can access the dashboard by navigating to **Workspaces \> Security Exposure Management Workspace \> Administration** and selecting **Review** on any integration. The dashboard offers interactive charts and detailed reports for in-depth analysis.

## Key Features

* **Integration Runs Metrics:** Displays the number of integration runs completed, distinguishing between successful and failed runs over the past 7 and 30 days. Common failure causes include network interruptions and data corruption during transformation.
* **Ingestion Health Highlights:** Provides data on import queue processing/wait times and REST API response times, helping monitor ingestion efficiency.
* **Processing Health Metrics:** Tracks performance over the last 30 days for assignment rules, remediation task rules, CI lookup time, risk rules, and vulnerability item creation. Color coding helps quickly identify performance deviations.
* **Integration Details:** Shows integration name, activation status, run schedules (day/time), and last run status. Notes provide important information such as automatic token renewal for Tenable.sc integrations upon failure.

## Handling Integration Timeouts and Errors

Integration data arrives in pages processed within a one-hour limit per import queue entry. For large payloads, processing may exceed this limit, causing timeout errors. However, the integration continues processing despite such errors.

To avoid misinterpretation of stalled processing, the system sends periodic timestamp "heartbeats" to indicate active processing. The **Last Record Processed** field is updated accordingly. If this field is older than one hour, the entry is considered stuck and timed out to prevent delays.

## System Properties for Heartbeats

* **snseccmn.recordthresholdheartbeat:** Defines how many records are processed before sending a heartbeat timestamp.
* **snseccmn.maximumheartbeatdelay:** Sets the maximum allowable delay before an import queue entry times out.

## Practical Benefits for ServiceNow Customers

This integration management capability helps customers ensure their security exposure data is reliably ingested and processed, quickly identify and resolve integration failures, and maintain up-to-date vulnerability information. The dashboard's visualization and detailed metrics provide actionable insights to optimize integration health and performance.  
The integration dashboard provides an overview of the installed third-party applications and the status of the integration runs.  
In the chart, point to any part (bar, pie, data point, and so on) to view general data specific to that part. If you select any part of a report, a list opens to provide detailed information.

## Access the Integration Dashboard {#review-usem-integrations__section_hfc_mk1_kzb}

To open the dashboard, navigate to WorkspacesSecurity Exposure Management WorkspaceAdministration and select Review on any integration.

## Data visualization {#review-usem-integrations__section_nfc_mk1_kzb}

Note:  
To learn more about a widget, select the information icon ![Information icon]().  
{#review-usem-integrations__table_n43_yv4_mbc__entry__3}

| Metrics | 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. |
[Table 1. Overview]

{#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}  
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}

*[\>]: and then