What is our primary use case?
The major use cases from my side for Qualys Enterprise TruRisk Platform integrate with our VMDR, Qualys VMDR. Basically, what TruRisk does is it helps with risk prioritization. We do all the integrations with existing products, which again is Qualys VMDR for us. We also integrate with a couple of other products, next-gen antivirus and others. Then it helps us normalize the overall risk that we have, not just looking at vulnerabilities. Based on that, we just prioritize whether this patching process or putting in any security controls is worth an effort or not. If it is worth the effort, then how do we prioritize? Which ones should go at the top? Which one needs to be dealt with first, and then gradually, the non-critical ones can stay down the chain.
The threat prioritization feature of Qualys Enterprise TruRisk Platform helps for resource allocation, especially for the crown jewel applications that we have. Of course, we feed that via CMDB into the tool. So we kind of prioritize what risks need to be taken care of, and then depending upon who owns it or we have a detailed RACI matrix which shows that hey, this particular thing or gap needs to be fixed by the network team, for example, or infrastructure team, server team, then we allocate those resources based upon priority. If it is a very high risk to the business, then we allocate resources based on that kind of risk prioritization, which is what the tool is meant to do. It is done on an ad-hoc basis, so on the process side, it needs to be taken care of from the process and cannot be automated, the resource allocation. But once we know that it is a high priority, then we allocate the resources within the span of time and that needs to be dealt with.
The benefits of visibility from Qualys Enterprise TruRisk Platform is that it is the central tool. The first thing that we integrate with is our asset inventory or CMDB, and we do it via ServiceNow. So we have all the assets, and then a lot of it depends on or it is a prerequisite to have very clean and hygienic CMDB. So there we have got all the assets, we have got all the applications, the business owners, stakeholders, and all of those. Then there is asset criticality, which is the most important thing that gets fed into TruRisk, and that is something which creates a positive or a negative bias on the risk that comes in because it is us, the business owners who understand the criticality of it, and that is more a subjective thing. So that is fed and then that is the most central integration. Then we do integrate with Qualys VMDR and all the other platforms which spit out their own various versions of vulnerabilities and risk and all of that. The tool then quantifies it and then prioritizes which ones need to be handled at the top.
What is most valuable?
Positive aspects of Qualys Enterprise TruRisk Platform are that it is mandatory for every organization. Every day we have so many security products, and then all of them spit out their own version of risk. Unless we consolidate them and quantify them, there is no way we can actually prioritize. Palo Alto may be giving some particular vulnerability a CVSS score or some high risk. Then some other product may be giving something else, and then our team does not understand which one to prioritize. That is where we absolutely need this tool so that it integrates with everyone. We have also integrated that with our ServiceNow CMDB and we have mentioned the asset criticality. Based upon that, it gets fed into Qualys Enterprise TruRisk Platform, and then we get the final quantified risk. Then it gives us these are the things that we need to handle, these are the top ones in the business technology risk, and then we need to take care of those first. Of course, there are some positives or false positives, but something which the tool says is something, but then for us, it may not be that big of a deal because we may have some compensatory control. This tool is mandatory if we are looking for a holistic, enterprise-wide solid risk governance and anything that has a GRC. They would absolutely need the content that this tool spits out. Else, it is a nightmare to deal with everything.
It is all continuous. The continuous monitoring feature of Qualys Enterprise TruRisk Platform is a continuous threat and exposure management kind of essential CTEM that is built in it. It is not the tool that does it. It is the feeds that it gets from other tools that enriches it, and then we get various metrics. We have foundational metrics, CVSS scores, severity and all of those. Then it takes care of all of those, consolidates them, checks all the vulnerability signatures. Again, not every vulnerability leads to a risk. A couple of them have not been exploited. That is how it works.
What needs improvement?
I think the CTEM part of Qualys Enterprise TruRisk Platform can get better, not that anyone else is doing, but continuous threat and exposure management. We are now going beyond the risk, especially in areas where AI is involved. For example, we have all these AI models, and then there are new products coming in, for example, AI runtime security and others. I think it is high time that we start feeding those things from those platforms into something like TruRisk. That gives us again, it is very difficult I understand, to attach a particular value or a score to that particular risk because with AI, we have all these new things for which there is no signature or there is no vulnerability known, and that thing is very dynamic, but it has to be done. So that is one of those things. Integration with AI runtime security tools, I guess that is crucial. Feeding Qualys may develop or have its own database of vulnerabilities which are AI specific or not, I do not know, but it should have the capability to get the feeds from all the other sources. So I think that is crucial.
That one about AI runtime security, I think it is high time that everyone starts thinking about that and bringing integrating all the risks that come along with AI runtime. For example, we use ChatGPT, and then there are all the tech teams which have API integrations with OpenAI, Claude, Anthropic and others. Then there are all these prompts or prompt injection attacks or model poisoning and others. If there is something and then we do use a Palo Alto, for example, for AI runtime security. Now, if something happens, someone is trying to poison the model, or if the runtime system itself has some vulnerabilities, it is crucial that every single risk prioritization tool also has the ability to integrate with that tool and then ingest and then figure out what is the risk level of that particular event or that particular system. Everyone needs to inherit that. It is not a Qualys thing. Of course, it is very difficult to do it without the risk of bringing in a lot of false positives. But that must be done.
For how long have I used the solution?
I have been dealing with Qualys Enterprise TruRisk Platform for about two, two and a half, three years, I guess. I do not think it is a very old product either. It has been around quite recently, and that is how I have been working with it.
What do I think about the stability of the solution?
If it is not stable, then it does not make any difference to us, to be frank, because this is more a scoresheet. We have so many things coming in, and then we have a final scorecard, which is this particular platform. We do not use it on a day-to-day basis, to be really frank. This is a periodic drill. So it matches with our vulnerability scans and all of that. For high-critical assets, yes, and there is a dedicated team, especially the senior architect, someone the me, we usually look at very closely. But it is not a 24/7 thing. It is not critical in the way that we have for Cortex XDR where if it fails, then the organization basically ceases to function.
What do I think about the scalability of the solution?
All we do is purchase the license and it just scales out. Qualys is fairly elastic. When purchasing a tenant, if we have a fair understanding of our landscape, we can just tell the SE, the account executive, and then they can provision a tenant based upon that. I have never faced any challenges. Qualys is very elastic in their cloud. So that does not create any challenges.
How are customer service and support?
The technical support from Qualys is the same as VMDR, the one that we checked earlier. The only technical challenges that we had so far were with integrations, and then they just fixed it. Maybe we were doing certain areas not correctly. There was one instance where there was not enough documentation, or it was there, but it was not that detailed. So that was one instance, but apart from that, we never faced any challenges.
Which solution did I use previously and why did I switch?
I would rate that a nine. They are always available, so I would say nine. Nine is great. The tool that I was thinking about earlier was RiskSense. That is the competitor we had in mind when we brought in TruRisk. Then I think we also ran a couple of evaluations, but because of our VMDR, we preferred the risk prioritization tool as TruRisk as well.
How was the initial setup?
It is a cloud tenant. We do not have to do anything for the deployment procedure. We just have a cloud tenant and we just have integration. So we just put in our API keys and do the same on the other side. It takes about less than a minute sometimes. Maybe three minutes for integration.
What's my experience with pricing, setup cost, and licensing?
The experience with pricing, setup cost, and licensing for Qualys Enterprise TruRisk Platform is expensive. It is definitely expensive. If I were to compare that with the one that we had, I do not recall the name exactly. It is taken over by Cisco now. I do not remember. I will update the notes once we publish it or send it out for review. So I think that was not on par with what TruRisk does. Qualys Enterprise TruRisk Platform is way better than the other one. It is taken over by Cisco now. RiskLens or something. That is the one.
Which other solutions did I evaluate?
If we compare Qualys to its competitors, it really helps if we are using the VMDR solution which is a risk prioritization tool that TruRisk of the same vendor which we deployed for VMDR. Because a lot of those things, most of those things, in fact, they come from VMDR. So I think that makes if we give Nessus or Tenable as one, and then we use TruRisk, then we may not get the same kind of output. So preferably, our VMDR solution and the risk prioritization tool, I would prefer them to be the same.
What other advice do I have?
The metrics for real-time threat intelligence updates are fed in real time. We have configured it real time, and the effectiveness of those largely depends. So the existing ones, all the vulnerabilities that have been there, we that is usually understood by the individual vendors. Where it becomes most effective is where Qualys is capable of building a QID or a signature and all of that before others do. That is where it becomes super effective. Else it is again, all the vendors, they typically are on top of these things, so I do not think there is a significant lag, but of course, Qualys does do much better.
Qualys Enterprise TruRisk Platform is a fantastic tool. It is kind of expensive, but it is indispensable. It is not something that we can do away with. TruRisk, every single enterprise which is trying to reach a maturity level, especially with risk governance and all of those, this is crucial. It is kind of not thought of often, but it really makes life simple once we have got it. I would rate this review a nine overall.
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