Connect Qualys VMDR, schedule a recurring import, watch scans sync live, and feed findings into correlation.
This guide shows how to bring Qualys VMDR data into PMAP and keep it current. You connect an integration whose credentials stay encrypted at rest, set a severity filter so only findings at or above your threshold are persisted, and learn how Qualys data reaches PMAP through orphan adoption and the blocklist guard that keeps deleted scans gone.
It is written for vulnerability managers who run a continuous Qualys feed. By the end you can schedule a recurring import driven by a cron value, confirm the live status sync ticker keeps every scan current without manual refresh, use the importable-scan picker to read each vendor scan’s PMAP adoption status, and see how imported findings flow through correlation while cascade delete reaches back to the vendor.
Inside this guide
- Understand how Qualys data reaches PMAP and stays in sync.
- Test Qualys credentials, then create the VMDR connector with encryption at rest.
- Set the severity threshold so low-signal results never persist.
- Schedule the recurring import and confirm live status sync is updating scans.
- Review the importable-scan picker and import findings into a project.
- Verify imported findings reached the correlation engine.
- Let orphan adoption mirror new scans and confirm the blocklist on delete.
Before you start
- A PMAP account with permission to create and edit integrations and to create scans (scan:create).
- Qualys VMDR API credentials and the base URL for your Qualys platform, ready to paste into the connection wizard.
- At least one completed Qualys scan on the vendor side, so there is real data to import and adopt.
- A target PMAP company and project to route the imported findings into.
- Familiarity with cron expression syntax, since the recurring schedule is driven by a cron value.
