Initiate rescans in the Qualys product from your Now Platform® instance. Note the following information about upgrades to v13.0 of Vulnerability Response and v12.0 of the Qualys Vulnerability Integration:

• A new integration, the Qualys Option Profile List Integration, retrieves scan profiles from the Qualys product. With Option Profiles, you can choose required scan settings when you initiate rescans in Qualys from your Now Platforminstance.
• Before you can initiate the enhanced rescans, you must complete the configuration steps listed in Advanced Qualys configurations and modifications.
• The auto scan for resolved vulnerable items is disabled by default. Enable the scan from your integration instance with the scan_on_resolved system property.

• New Host Import maps are added for Unclassed Hardware.
• Discovery source VR-Qualys is created and passed to IRE to create CIs.

New: The Rapid7 Site integration API integration ingests Sites data from Rapid7 Insight VM.

• Increased the password field length in the Rapid7 Configuration table to accommodate a KMF change.
• Updated permissions for one of the client scripts to ensure proper access.

Fixed: The KMF error by adding security modules.

• Vulnerability Solution Management
• Red Hat Solution Integration
• Microsoft Security Response Center Solution Integration

Fields as SDLC Status, Vulnerability Summary, Vulnerability Explanation, and Recommendation, imported and mapped to display on Application Vulnerable Item form.

To update your CIs with the network partition identifier, version 13.0 of Vulnerability Response includes the CMDB CI Class Models (v1.21.0) that include the Network Partition Identifier in the IRE identification rules. The system properties are: sn_vul_tenable.lookup_network_partition_io sn_vul_tenable.lookup_network_partition_sc. Pre-requisites are:

When you initiate a Tenable.sc rescan request via a MID Server, an error message is displayed if the API request takes longer than 30 seconds. See the Tenable.sc Rescan Error - No response after 30 seconds in ECC Queue [KB0862613] article in the HI Knowledge Base to reset the default timeout limit.

If you have been importing data with the Tenable-built integration, and you want to start using the ServiceNow® Vulnerability Response Integration with Tenable, see the Required data cleanup for migrating from the Tenable Vulnerability Response integration to the ServiceNow Vulnerability Response Integration with Tenable KB0863702 article for clearing existing vulnerability data in your instance.

Initial release.

Two integrations import CVE and CPE data from the NIST National Vulnerability Database:

• NIST National Vulnerability Database Integration - API (CVE only)
• NIST National Vulnerability Database Integration - API (CVE and CPE)

Fixed defects.

Fixed defects.

• Vulnerability Solution Management
• Red Hat Solution Integration
• Microsoft Security Response Center Solution Integration

When you initiate a Tenable.sc scan request via a MID Server, an error message is displayed if the API request takes longer than 30 seconds. See KB0862613 to reset the default time out limit.

• Shodan Exploit Integration for Security Operations
• Vulnerability Solution Management
• Red Hat Solution Integration
• Microsoft Security Response Center Solution Integration

When you initiate a Tenable.sc scan request via a MID Server, an error message is displayed if the API request takes longer than 30 seconds. See KB0862613 to reset the default time out limit.

• Qualys Vulnerability Integration for Security Operations
• Rapid7 Vulnerability Integration for Security Operations
• Performance Analytics for Vulnerability Response
• Vulnerability Response Mobile

• Shodan Exploit Integration for Security Operations
• Vulnerability Solution Management
• Red Hat Solution Integration
• Microsoft Security Response Center Solution Integration

• Qualys Vulnerability Integration for Security Operations
• Rapid7 Integration for Security Operations
• Performance Analytics for Vulnerability Response
• Shodan Exploit Integration for Security Operations
• Vulnerability Solution Management
• Red Hat Solution Integration
• Microsoft Security Response Center Solution Integration

• Qualys Vulnerability Integration for Security Operations
• Rapid7 Integration for Security Operations
• Performance Analytics for Vulnerability Response
• Shodan Exploit Integration for Security Operations
• Vulnerability Solution Management
• Microsoft Security Response Center Solution Integration

• Qualys Vulnerability Integration for Security Operations
• Rapid7 Integration for Security Operations
• Performance Analytics for Vulnerability Response
• Shodan Exploit Integration for Security Operations
• Microsoft Security Response Center Solution Integration
• Vulnerability Response Mobile

The Qualysseverity [qualys_severity] and Last updated by source [last_updated_by_source] fields listed in the Vulnerable item table [sn_vulnerable_item] are deprecated and no longer populated. Since the Business Rule (BR) Map Qualys Values uses Last updated by source, it is also deprecated.

Retry added for API failures such as timeouts.