Release 10.32.1
February 02, 2025
What’s New?
Qualys Vulnerability Management (VM)
Enhancement to EC2/Cloud Instances Purge Event
A Cloud Resource ID is a unique identifier assigned to each individual resource within a cloud computing environment. It is primarily used to precisely identify and manage specific resources across different cloud services. The cloud providers include AWS (EC2), Azure, and GCP. For example, an EC2 asset includes an EC2 instance and instance IP address, which are tracked by the EC2 instance.
Earlier, when the auto-purge was triggered, the system was not only purging the scan data for the specific instance but was also deleting the IPs from all the networks, which interrupted the IP tracked host scheduled scans.
With this release, when the auto-purge event is triggered, the system purges only the scan data for the specific instances where the purge event is configured. This ensures that the IP tracked host scheduled scans and asset groups for other networks remain unaffected.
Qualys Policy Compliance (PC)
Supported Technologies for Network User user-defined control
In the 10.32 release, we introduced: New UDC (User Defined Control) Type- Network UDC. With this release, the following technologies are supported for Network UDC. You can create a custom check control to assess the following technologies on the network devices:
- Cisco IOS 12.x - 15.x
- Cisco IOS XR 6.x - 7.x
- Cisco IOS XE
- Cisco ASA 8.x - 9.x
- ArubaOS 6.x & 8.x
- Juniper JUNOS 10.x - 22.x
- IBM Datapower Gateway 10.x
- Arista EOS 4.x
- ApconTap Switch
Issues Addressed
The following reported and notable customer issues have been fixed in this release:
| Component/Category | Application |
Description |
| VM - Authentication Records | Vulnerability Management | When the user was viewing the list of IPs on the vCenter ESXi Mapping Data page, it was observed that a user with Unit Manager role could view and manage assets similar to a Manager user. However, this IPs list, created via map scans or manual CSV uploads, is accessible to all users irrespective of their roles, as user-level scoping applies only to hosts, not IP addresses. This information is now documented in the Online Help in How to Scan ESXi hosts on vCenter. |
| VM - UI General | Vulnerability Management | When the users were viewing assets in the Tracking Consistency Check window, they observed that the image icon for all agent tracked assets were displayed broken. Relevant code changes have been made to fix the issue. Now, the image icon for all agent tracked assets is displayed correctly for the corresponding IPs. |
| VM - Asset Groups | Vulnerability Management | When the users tried to download the asset group list in CSV format, the count was showing 0 (zero) for the Asset groups to which the scanner appliances were assigned. Relevant code changes have been made to fix the issue. |
| VM - Reports General | Vulnerability Management | When the users executed and downloaded an authentication report, information in the All Asset Tags and Host ID columns was missing for both Cloud agents and IP hosts with authentication Not Attempted Status. Relevant code changes have been made to fix the issue. |
| VM - Scans | Vulnerability Management | When the users executed a scheduled scan API 2.0, api/2.0/fo/schedule/scan/, scans could not be completed, and were not able to get the latest vulnerability on critical assets. Relevant code changes have been made to fix the issue. |
| VM - User Management | Vulnerability Management | When the users were deleted from the subscription, the PCI account was not unlinked for that specific user. Relevant code changes have been made to fix the issue. |
| PC - Reports | Policy Compliance | When the users were running a new compliance scorecard report and attempting to add policies, they observed that in the Policies dropdown no policies were listed and an error message No data to display is displayed. This prevented them from adding policies as expected. Relevant code changes have been made to fix the issue. |
| PC - New UI | Policy Compliance | When the users checked the cloud agent assets in the PC application, stale asset entries were observed in the list. Relevant code changes were made to fix the issue. |
| PC | Policy Compliance | When the users tried to fetch the PC data for certain controls, the PC data was not visible on the User Interface for Windows technology. Relevant code changes have been made to fix the issue. |
| PC - Schedule Report | Policy Compliance | When the users were recreating a new scheduled policy report, the report did not launch at the scheduled time. Relevant code changes have been made to fix the issue. |