Qualys incident

All Shared Platforms: WAS Authentication is failed with parameterized credentials

Started: Apr 17, 2026, 12:32 PM UTC
Resolved: Apr 20, 2026, 06:29 AM UTC
Duration: 2d 17h
Detected by Pingoru: Apr 17, 2026, 12:32 PM UTC

Affected components

Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)

Update timeline

investigating Apr 17, 2026, 12:32 PM UTC

Qualys Cloud Operations has detected an issue impacting WAS/TAS authentication scans when parameterized credentials are used in the latest WAS 10.16 release. Further updates will be shared as they become available. Workaround: As a temporary workaround, users are advised to disable the “Add credentials to Selenium Script” option and instead manually hardcode the required credential values directly into the Selenium script. This approach has been verified to restore successful authentication. The ticket reference for this incident is IM-12596.
identified Apr 17, 2026, 01:29 PM UTC

The issue has been identified and currently working on the fix.
resolved Apr 20, 2026, 06:29 AM UTC

This incident has been resolved.

Looking to track Qualys downtime and outages?

Pingoru polls Qualys's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

Real-time alerts when Qualys reports an incident
Email, Slack, Discord, Microsoft Teams, and webhook notifications
Track Qualys alongside 5,000+ providers in one dashboard
Component-level filtering
Notification groups + maintenance calendar

Start monitoring Qualys for free

5 free monitors · No credit card required