View the (National Vulnerability Database) NVD integration import run status

Rversion finale: Australia

Mis à jour 12 mars 2026

2 minutes de lecture

Use the Vulnerability Integration Runs related list to verify the success of your integration runs, locate any issues, and inform your remediation decisions.

Avant de commencer

To view the NVD integration import run status:

Vulnerability Response and the Vulnerability Response integration with NVD integration application must be installed and configured.
The NVD integration imports must be running. The NIST National Vulnerability Database Integration-API (CVE only) integration runs by default.
Remarque :
The NIST National Vulnerability Database Integration-API (CPE only) and the NIST National Vulnerability Database Integration-API (Unmapped CPE) integrations are inactive by default. See Activate the NIST National Vulnerability Database–API (CPE only) and Activate the NIST National Vulnerability Database–API (Unmapped CPE) for more information.

Role required: sn_vul.vulnerability_admin or App-Sec Manager

Pourquoi et quand exécuter cette tâche

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, starting from version 18.2.4 of Vulnerability Response, 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’s also older than one hour. The last record processed being older than an hour indicates that the import queue entry is stuck, and it’s timed out to prevent any further delays in processing.

Remarque :

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.

Procédure

If you aren’t using the NVD integration run status chart, Navigate to All > Vulnerability Response or Application Vulnerability Response > Administration > Integrations.
Select a link for an integration.
Select the Vulnerability Integration Runs related list.
Verify that all imports have succeeded.
The most common causes for a failed run include:
- Network interruption.
- An issue in the data transfer resulting in corrupted data during the transform.
If you encounter any of these conditions, select Execute Now, and rerun the integration.