Qualys

Import Qualys VMDR vulnerabilities as risks, linked to their CVEs.

Qualys VMDR (Vulnerability Management, Detection and Response) scans your hosts and records the weaknesses it finds. This connector reads those detections through the Qualys API and turns each one into a risk in the Aegis risk register, so a vulnerability can be assessed, owned and treated like any other risk. A CVE (Common Vulnerabilities and Exposures, the public catalogue number of a known weakness) is the intended link between the scan result and the risk. Aegis only reads from Qualys; it never changes anything in your Qualys subscription.

At a glance

Direction Into Aegis.
What it brings in Detected vulnerabilities with the status New, Active or Re-Opened, from a minimum severity (3, serious, by default), with the QID details (the Qualys description of each vulnerability).
Where it lands Risks. The connector page has no category choice; a risk category can only be set when the sync is started through the API.
Credentials and permissions A Qualys API user (username and password) with read access to vulnerability data, and the Qualys platform of your subscription (for example EU_1).
Owner of imported records The person who ran the sync.
When it runs On demand from the connector page or the API.
Set it up /connectors/qualys, by people allowed to configure connectors, where the Qualys connector module is switched on for your organisation.
Known limitation: the import does not complete in this release

In the current build the sync checks for an earlier import by a reference that the risk register does not store. That check fails for every detection, so a sync reports each vulnerability as failed and creates no risks. The connection test is not affected. The CVE number and the Qualys solution text are also not kept on the risk today. Until this is fixed, read the steps below as the intended flow, and record Qualys findings in Risks by hand or by import.

Who uses it

The page is for Manager and Admin. Both can save the configuration, test the connection, run a sync and disconnect the connector. A Contributor or Viewer who opens /connectors/qualys is redirected to the access-denied page, /unauthorized. When the Qualys connector module is not switched on for your organisation, the page still opens but saving, testing and syncing are refused.

What's on this screen

No screenshot of this page was captured for this edition, so this section describes the page as the product builds it. From top to bottom:

Prepare the Qualys API user

Do this in Qualys before you open Aegis. It matches the Setup Instructions panel on the page.

  1. Sign in to your Qualys subscription as an administrator and create a dedicated API user with the Reader role for Vulnerability Management. A separate user keeps the connector's access narrow and easy to withdraw.
  2. Enable API access for that user and assign it to the asset groups whose scans Aegis should see. Detections on hosts outside those groups are not returned.
  3. Note your platform from the address you use for Qualys, for example qualysapi.qualys.eu is EU_1.

Save the configuration

  1. Open Connectors and select the Qualys tile, or go to /connectors/qualys. The page opens with the configuration form at the top and Not Tested under Connection Status, with the line “Configure your Qualys API credentials above to enable connection.”
  2. Enter the API Username. Save Configuration stays disabled until this field has a value.
  3. Enter the API Password. Once a password is stored the field shows dots; leaving it blank on a later save keeps the stored password.
  4. Choose the Qualys Platform. The list offers US platforms 1 to 4, EU platforms 1 and 2, and the India, Canada, Australia and UAE platforms, each with its API address. US Platform 1 is the default.
  5. Select Save Configuration. The button reads Saving..., then the Test Connection button appears under Connection Status. Saving never marks the connector Connected: a new or changed configuration stays disconnected until a test or sync succeeds.

Test the connection

  1. Select Test Connection. The badge reads Testing... while Aegis asks Qualys for a small sample of detections at any severity.
  2. On success the badge turns Connected and a box headed Connected to Qualys VM API shows how many recent detections came back, how many unique hosts were scanned, how many carry a CVE identifier, and a count per severity. The Vulnerability Sync panel appears below.
  3. On failure the badge reads Connection Failed with the reason. Check the username, password and platform, save again and retest.

Run a sync

  1. In Vulnerability Sync, read the purple note: vulnerabilities are imported as risks with CVE linking. See the warning at the top of this chapter for what the current build does.
  2. Set Minimum severity to sync as risks: with the slider, from Minimal (1) to Urgent (5). It starts at Serious; the label reads, for example, Serious+ selected, and a line below confirms “Vulnerabilities with severity 3 or higher will be imported as risks.”
  3. Select Sync Now. The button reads Syncing... and a blue bar shows “Syncing vulnerabilities from Qualys...”. With QID details fetched, a large subscription can take several minutes.
  4. When it finishes, an entry appears under Sync History marked Sync Complete or Sync Failed, with the time and a line such as “risks created, skipped, failed (from vulnerabilities)”. Before the first run the list reads No sync history yet.; after it, the panel shows Last successful sync: with the date and time of the last completed sync.

How severities become risk scores

Each risk is meant to take its impact from the Qualys severity, as the Severity Mapping panel on the page shows, and a likelihood of 4, because a detected vulnerability has a known way to be exploited. The scores are then placed on your organisation's risk methodology like any other imported risk.

Qualys severity Risk impact
Urgent (5) Critical
Critical (4) High
Serious (3) Medium
Medium (2) Low
Minimal (1) Minimal

The import builds each risk's title from the QID title followed by the host address, for example a vulnerability name “on” the host IP. Its description carries the Qualys diagnosis, the consequence, up to 500 characters of the detection result, the affected host and its operating system. A detection already imported is meant to be skipped rather than duplicated; in this release that same check is what fails (see the warning above).

Disconnect the connector

  1. Scroll to Disconnect connector. It explains that disconnecting deletes the stored Qualys configuration and credentials, and the sync schedules and mappings that use it, while records already imported stay in Aegis.
  2. Select Disconnect. A dialog asks “Disconnect Qualys?” and repeats that you can configure the connector again later.
  3. Confirm. You return to the Connectors catalogue, with Qualys back to unconfigured.

Tips and limits

Where this connects

Imported risks are worked in Risks. The catalogue, sync schedules and the shared disconnect behaviour are covered in Connectors. Other security connectors that pull findings are CrowdStrike Falcon, AWS and Palo Alto Networks.