What is our primary use case?
I am using Qualys Patch Management for two years, and everything is satisfactory from my side.
Before purchasing Qualys Patch Management, we were already using Qualys VMDR and the cloud agent model. At that time, we were generating reports and facing issues with patching vulnerabilities. Large vulnerabilities, such as Google Chrome and browser-related issues, were appearing every two weeks, making it difficult to patch. Similarly, we were getting browser vulnerabilities and software-related vulnerabilities. It became very easy to automate this process and showcase the management of vulnerability remediation cost.
Initially, we were doing it manually, so we implemented Qualys Patch Management as a solution. The management was ready to take the initiative. We purchased around 2000 licenses and started patching approximately 1600 servers. We initially only patched the server and focused on some vulnerabilities as zero-day vulnerabilities for preventive methods. The preventive method gave us the capability to run scripts and make registry changes through Qualys Patch Management. We patched more than 1000 assets in one go, which was a significant initiative for us.
What is most valuable?
The main feature that is helpful for us in Qualys Patch Management is that we can make registry changes and run scripts through this particular module. We can either run specific scripts, update software, or remove specific software versions. For example, in the case of 7-Zip, when we update it, it installs the latest version but does not remove the older version.
Therefore, we use scripts, PowerShell scripts, and we bypass PowerShell execution policies through this module, allowing us to achieve the removal of that folder version of 7-Zip. This feature is very helpful, and it allows us to take preventive measures for zero-day vulnerabilities.
Additionally, the risk-based approach for creating automation to address risks is used mainly through dashboards. The dashboards give us a TruRisk dashboard. They show us what assets we can prioritize for patching and what critical patches we are pending for those machines. Accordingly, we create patch jobs and execute them, and initiate the reboot on priority. Additionally, we initiate some of the machines to reboot for creating another job as we have implemented these actions.
What needs improvement?
Regarding improvements in Qualys Patch Management, I did not quite understand the downsides they were expecting.
Initially, I was confused about where to find and how to use the available features. It was challenging to identify the options we could employ and why we were using them. However, once I gained hands-on experience, I was able to identify the tool's particular features, making it easier for us to use it. The initial phase had some difficulty with the user interface.
I would them to improve user training. They have used many colors, which can be confusing, so they should use specific colors for specific options. For critical options, they could make them red, green for medium, and blue for less significant options. This would make it easier for a beginner to recognize which buttons are dangerous to click. Such adjustments can help new users learn the solution faster.
What do I think about the stability of the solution?
Regarding stability, I rate it a perfect ten out of ten for uptime, as I never experience lag, latency, or loading time. They also inform us beforehand if there will be ongoing maintenance that might affect speed.
How are customer service and support?
I have contacted their technical support when implementing QGS. After the initial phase, the management identified a gap in downloading patches from the Internet directly, which became a security issue. We implemented a QGS server in a fixed location, configured it, and began patching using QGS. During this time, the support team helped us configure every server for initial patching, and they were very helpful.
If I were to rate the support, I would give it a nine out of ten.
Which solution did I use previously and why did I switch?
We added the Qualys Patch Management solution on top of the existing vulnerability management solution. We purchased the particular license and extended it.
How was the initial setup?
The initial deployment of Qualys Patch Management was easy for me. The support team was very helpful, providing scripts that made it straightforward to deploy in the cloud agents on both servers and endpoints through Intune.
Setting up on 2000 servers takes around two weeks for completion.
What about the implementation team?
Within the IT team, there were more than 10 people involved; however, in the initial phase, we faced some issues with certain Linux operating systems such as Red Hat and others. This caused some delays. Otherwise, it would have been completed within one week as we were deploying more than 10 or 15 machines concurrently.
What was our ROI?
After starting to use Qualys Patch Management, I have seen an improvement in our patch rates. We can say that the number has increased by about 30-40% over the past month. Subsequently, we are ready to bring up the process and have automated some common patches as we are managing this effectively with only two resources. Therefore, it is very cost-effective for us to handle with just those two resources.
What's my experience with pricing, setup cost, and licensing?
From a pricing perspective, I find Qualys to be a bit higher, but it is worth it. Compared to other tools, it is on the costly side, but I believe it is worth the investment.
Which other solutions did I evaluate?
I have used alternatives to Qualys Patch Management, specifically Rapid7. I found that Rapid7 does not have as many features available. For example, the cloud agent has many features, while Rapid7's patch management tool does not have an updated patch inventory. With Qualys, we can see patches immediately whenever new vulnerabilities are released and be ready to push them. However, in Rapid7, we experienced delays in getting updates for two or three days.
What other advice do I have?
Regarding whether Qualys Patch Management gives a single source of truth for assets and vulnerabilities that need to be assessed, prioritized, and remediated, I cannot say we solely rely on it. We are also using VMDR, as we do not depend only on the patch management module for patch priorities. Our patch priorities are established using the VMDR for vulnerability prioritization, and the patch criticality comes after that.
I saw the benefits of Qualys Patch Management after we started using it. Before purchasing Qualys Patch Management, we remedied around 100 or 150 vulnerabilities from more than 90,000 vulnerabilities. We still remedy 150 or 160 vulnerabilities, but the management was aware of that because we were doing it manually. When we started the Patch Management module during the testing phase, we remedied 400 vulnerabilities in a month. That was very impressive from the management perspective. They agreed to move out of the testing phase, so we could bring up the process for some common vulnerabilities such as Google Chrome, Microsoft Teams, or any other related software we are using.
The TruRisk automation helps us remediate vulnerabilities without needing to involve the security team. Although we did not actually rely on the true list dashboard because we are using the QIDs released. By using the QID, we are able to update the formulas automatically. We do it manually in some cases due to applications that have dependencies on servers we need to exclude.
I have not used the risk reduction recommendation report. We are using the normal vulnerability scan report generated from VMDR. From the Patch Management perspective, we only generate the report once the patch is completed, where we assess which patches have failed and why.
We do not use integrations with CMDB or ITSM tools for ticket management yet, as the management is not approving that particular request. However, integrating that would make automation and report generation much easier, allowing us to segregate the tasks among different teams, applications, or servers.
The integration in VMDR is very important for us, as we are getting many dashboards by different criteria, such as SLA. We differentiate on SLA based on critical, high, or medium criteria, so we are using trending formulas also. It is very helpful for us to prioritize the vulnerabilities by considering the exploitability rate and if it is publicly available.
Overall, I would rate Qualys Patch Management a ten out of ten for everything.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other