Qualys TruRisk Eliminate 2.0 Puts Patch Reliability to Work
12m
Remediation Beyond Patching
Lavish Jhamb recently moved from compliance to the remediation side of Qualys. He now leads product management for TruRisk Eliminate. At Qualys ROCon 2026, he joins Alan Shimel to discuss TruRisk Eliminate 2.0 and its new confidence layer.
Patching takes time to test and roll out. It can also disrupt critical systems. Shimel recalls large banks needing 90 days to deploy Patch Tuesday updates. The real issue, he argues, has always been trust.
Jhamb says teams need more options than patching alone. They can mitigate an exposure, isolate an asset, or use controls they already own, such as Zscaler. The goal is to fix the most critical 1% first and plan the rest.
Scoring Patch Reliability
Qualys scores every patch that enters its catalog. It weighs social signals alongside its own telemetry. When a vulnerability reopens across its customer base, that often means a patch was rolled back. Combining both sources produces a patch reliability score.
That score helps teams decide what to automate. A high-reliability browser or standalone app patch on a non-critical asset can deploy without approval. Jhamb estimates automation can handle about 60% of the remaining backlog. Chrome, Firefox, and Adobe updates are prime candidates.
Some flaws, such as SMBv1 issues, have no vendor patch at all. They can linger for seven to 10 months. Qualys offers mitigations for those cases and for Patch Tuesday releases. When patch reliability is low, teams can mitigate first.
Confidence During Rollout
A successful install does not always mean a safe one. TruRisk Eliminate 2.0 works with Dynatrace to watch test systems for CPU spikes and service disruptions. If problems appear, the rollout stops before reaching production. That replaces the 24- to 48-hour cooling period many teams wait out today.
VMDR customers can request a personalized report. It identifies their top 1% and maps the rest into remediation waves.