Skip to main content
Checks that Qualys vulnerability alerts are resolved within the defined SLA.

​
About

When you connect Qualys to DSALTA, the platform retrieves the current security findings using read-only API access. DSALTA tracks their status and activates this check when action is required.

​
Why This Matters

Known vulnerabilities in your code and dependencies are publicly catalogued and actively exploited, often within hours of disclosure. Detecting and remediating them within a defined SLA is required by SOC 2 and ISO 27001.

​
How to Fix

Before you begin
  • Ensure the Qualys integration is connected so DSALTA sees the current findings.
Resolve vulnerability alerts within SLA
  1. Open the vulnerability findings in Qualys, sorted by severity.
  2. Remediate each finding (patch, update, or reconfigure) and mark it resolved in the source.
  3. Define and follow an SLA — Critical within 24-48 hours, High within 7 days, Medium within 30 days.
Once the alerts are resolved within SLA, DSALTA retrieves the change on the next sync and sets the check status to Passing.

​
Frequently Asked Questions

This check runs automatically every 24 hours while the Qualys integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
A failing check appears in your Data Library → Tests dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Qualys.