Release 4.1.82: Alibaba | Xenserver | KVM | Proxmox | GCP | Azure | AWS

September 25, 2025

The operating system for Virtual Scanner cannot be upgraded. You need to replace the scanner image or deploy a new scanner with the latest image, although this may not always be necessary. For details on when scanner replacement is necessary, refer to the Know when scanner replacement is needed section.

What's New?

This release brings new features and updates to data centers and desktop platforms.

Public Cloud: Alibaba, AWS, GCP, Azure
Data Center: XenServer, KVM, Proxmox

This version is not limited to just Alibaba, Xenserver, KVM, Proxmox, AWS, GCP, and Azure. It has already been released on VMware and HyperV. In upcoming releases, it will also be available for all other supported virtualization platforms.
The availability of scanners in cloud marketplaces depends on cloud vendors and usually takes a few weeks after general availability from Qualys.

New Features

With this release, we have introduced new features for:

Alibaba

qVSA 4.1 image version is based on Oracle Linux 8(x86_64) with UEK kernel-5.15.
The Scanner console displays the UI on tty1 and the system log on tty8.
Syslog forwarding is set up to forward all scanner logs, including both scanning-related logs, AUTOUPDATE logs, and all messages from /var/log/messages.
A Virtual Machine instance with a minimum of 2GB of RAM is required.
Support for TLSv1.3.

XenServer

qVSA 4.1 image version is based on Oracle Linux 8(x86_64) with UEK kernel-5.15.
The Scanner console displays the UI on tty1 and the system log on tty8.
Syslog forwarding is set up to forward all scanner logs, including both scanning-related logs, AUTOUPDATE logs, and all messages from /var/log/messages.
A Virtual Machine instance with a minimum of 2GB of RAM is required.
Support for TLSv1.3.

KVM

qVSA 4.1 image version is based on Oracle Linux 8(x86_64) with UEK kernel-5.15.
The Scanner console displays the UI on tty1 and the system log on tty8.
Syslog forwarding is set up to forward all scanner logs, including both scanning-related logs, AUTOUPDATE logs, and all messages from /var/log/messages.
A Virtual Machine instance with a minimum of 2GB of RAM is required.
Support for TLSv1.3.

Proxmox

qVSA 4.1 image version is based on Oracle Linux 8(x86_64) with UEK kernel-5.15.
The Scanner console displays the UI on tty1 and the system log on tty8.
Syslog forwarding is set up to forward all scanner logs, including both scanning-related logs, AUTOUPDATE logs, and all messages from /var/log/messages.
A Virtual Machine instance with a minimum of 2GB of RAM is required.
Support for TLSv1.3.

GCP

qVSA 4.1 image version is based on Oracle Linux 8(x86_64) with UEK kernel-5.15.
Syslog forwarding is set up to forward all scanner logs, including both scanning-related logs, AUTOUPDATE logs, and all messages from /var/log/messages.
A Virtual Machine instance with a minimum of 2GB of RAM is required.
Support for TLSv1.3.
Support of Shielded VM capabilities such as Secure Boot, vTPM (for Measured Boot), and Integrity Monitoring.

Enhancements

In this release, the following enhancements have been made for the platform on which qVSA 4.1 has already been released.

Azure

Support for instance sizes with Accelerated Networking, including D-Series v5, B4-series v2, and others.
qVSA 4.1.82+ virtual machines now report Agent Status and Agent Version to Azure.

AWS

The DNS server can be configured using user data for AWS scanners only.

Limitation

The following are the limitations of this release:

Currently, we are not supporting SCAP scanning.
UEFI(Secure Boot) is not supported on all platforms; it is currently supported only on GCE.
DNS server configuration using userdata is not supported on all platforms; it is currently supported only on AWS.