Get Started with Scanner Deployment in OpenStack Cloud Platform

Welcome to Qualys Enterprise TruRisk™ Platform, which brings you solutions for securing your cloud IT infrastructure and your traditional IT infrastructure.

This document briefly describes how to deploy the Qualys Virtual Scanner Appliance on the OpenStack cloud platform. Once deployed, the scanner functions as a standard virtual scanner.

Manage Scanner Instances

While managing the instance, you are not allowed to do the following actions:

Instance Snapshots or Cloning is Not Allowed

Using a snapshot or clone of a virtual scanner instance to create a new instance is strictly prohibited. The new instance created using the existing virtual scanner instance will not function as a scanner. All configuration settings and platform registration information will be lost, which may also lead to scan failures and errors for the original scanner.

Moving or Exporting Instance Not Allowed

Moving or exporting a registered scanner instance from a virtualization platform in any file format to the OpenStack cloud platform is strictly prohibited. Doing so will break scanner functionality and cause it to permanently lose all of its settings.

Prerequisites

To deploy a virtual scanner appliance on the OpenStack platform, the following prerequisites must be met:

An active Qualys subscription is required. If your subscription is inactive, contact Qualys Support or register on the Qualys website.
A 14-digit Scanner Personalization Code, available from your Qualys account, is needed to proceed.
Ensure that the Qualys Virtual Scanner Appliance VM can connect to the Qualys Enterprise TruRisk™ Platform over HTTPS (port 443).

Virtual Machine Size to Host Scanner

The recommended minimum instance configuration for the Scanner VM is 4 CPU cores and 8 GB of RAM. In the event of scan delays, failure, or performance issues, it is advisable to increase the instance size. Ensure that the CPU: RAM ratio is maintained at 1:2 or 1:3 for optimal performance.

The instance size should be scaled up based on he frequency of scanning and the number of virtual machines being scanned.