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.
|
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:
-
Header. A breadcrumb
Connectors / Qualys VM, the titleQualys Vulnerability Management Connectorand one line on what it does. -
Configuration. A blue
API User Requirementsbox (aReaderrole for Vulnerability Management, API access enabled, access to the asset groups you need), thenAPI Username,API Password,Qualys Platformand theSave Configurationbutton. -
Connection Status. A status badge —
Not Tested,Testing...,ConnectedorConnection Failed— and theTest Connectionbutton once credentials are saved. -
Vulnerability Sync. Shown only while the connection reads
Connected: aSync Nowbutton, a severity slider and aSync Historylist. -
Disconnect connector. Shown once a configuration exists, with a red
Disconnectbutton. -
Help panels.
Setup Instructions(seven steps on the Qualys side),CVE LinkingandSeverity Mapping.
Prepare the Qualys API user
Do this in Qualys before you open Aegis. It matches the
Setup Instructions panel on the page.
-
Sign in to your Qualys subscription as an administrator and create a
dedicated API user with the
Readerrole for Vulnerability Management. A separate user keeps the connector's access narrow and easy to withdraw. - 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.
-
Note your platform from the address you use for Qualys, for example
qualysapi.qualys.euisEU_1.
Save the configuration
-
Open
Connectorsand select the Qualys tile, or go to/connectors/qualys. The page opens with the configuration form at the top andNot TestedunderConnection Status, with the line “Configure your Qualys API credentials above to enable connection.” -
Enter the
API Username.Save Configurationstays disabled until this field has a value. -
Enter the
API Password. Once a password is stored the field shows dots; leaving it blank on a later save keeps the stored password. -
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 1is the default. -
Select
Save Configuration. The button readsSaving..., then theTest Connectionbutton appears underConnection Status. Saving never marks the connectorConnected: a new or changed configuration stays disconnected until a test or sync succeeds.
Test the connection
-
Select
Test Connection. The badge readsTesting...while Aegis asks Qualys for a small sample of detections at any severity. -
On success the badge turns
Connectedand a box headedConnected to Qualys VM APIshows how many recent detections came back, how many unique hosts were scanned, how many carry a CVE identifier, and a count per severity. TheVulnerability Syncpanel appears below. -
On failure the badge reads
Connection Failedwith the reason. Check the username, password and platform, save again and retest.
Run a sync
-
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. -
Set
Minimum severity to sync as risks:with the slider, fromMinimal(1) toUrgent(5). It starts atSerious; the label reads, for example,Serious+ selected, and a line below confirms “Vulnerabilities with severity 3 or higher will be imported as risks.” -
Select
Sync Now. The button readsSyncing...and a blue bar shows “Syncing vulnerabilities from Qualys...”. With QID details fetched, a large subscription can take several minutes. -
When it finishes, an entry appears under
Sync HistorymarkedSync CompleteorSync Failed, with the time and a line such as “risks created, skipped, failed (from vulnerabilities)”. Before the first run the list readsNo sync history yet.; after it, the panel showsLast 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
-
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. -
Select
Disconnect. A dialog asks “Disconnect Qualys?” and repeats that you can configure the connector again later. -
Confirm. You return to the
Connectorscatalogue, with Qualys back to unconfigured.
Tips and limits
- Fetching QID details gives richer risks but makes the sync slower. The page always fetches them; only an API call can turn them off. If the details cannot be fetched, the sync carries on without them.
- Each sync reads up to 500 hosts with results, and the connection test up to 20. A very large estate may need several runs, or a narrower asset group for the API user.
-
The runs listed under
Sync Historylive on the page only: it keeps the last five runs of your visit and drops them after a reload, leaving only theLast successful sync:line. Each run is also written to the audit log. - An authentication error during a sync sets the connector to an error state and shows “Authentication failed. Please check your credentials.”
-
There is no scheduled Qualys sync. The background scheduler has no Qualys
handler, so a schedule set up for Qualys under
Sync Settingsdoes not import anything; its run reports that no sync handler is configured. -
The
CVE Linkingpanel lists intended uses, such as cross-referencing with vulnerability databases and remediation tracking. Treat it as a description of purpose, not of what the current import stores.
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.