Qualys Extends Cyber Risk Management to the Surfaces It Couldn’t Measure
Five partners bring mobile, industrial and identity telemetry into one score. The scoring problem is the hard part, and the release treats it as solved.
Qualys has expanded its global mROC alliance with five technology partners covering mobile, operational technology and identity, bringing telemetry from those surfaces into its Enterprise TruRisk Management platform so that risk from systems which cannot run an agent appears alongside risk from servers and laptops. The partners are Lookout and NowSecure for mobile, Claroty and Nozomi Networks for operational technology and IoT, and Okta for identity. Qualys also added two partner certification tracks, one for advisory work and one for delivery and implementation, alongside its existing managed-service track.
The least-measured surfaces problem
The argument underneath the announcement is sound and worth stating plainly. Enterprise security grew up around what can be instrumented. A server runs an agent, a laptop runs an agent, a cloud workload reports through an API. Each produces telemetry, and vulnerability management grew up around it.
The fastest-growing parts of the estate do not work that way. A medical device in a hospital cannot run an agent, because the manufacturer does not permit it and the regulatory approval does not cover it. An industrial controller in a plant cannot tolerate an active scan, because a scan can stop a production line. A mobile phone belongs to an employee and runs whatever they installed. And an identity is not a machine at all, so its risk lies in what it can reach rather than in what it runs.
Qualys’s claim is that these surfaces end up in a separate tool with its own scoring, or in no tool at all, so a CISO cannot compare a vulnerable infusion pump against a vulnerable server on the same scale. That is a real problem and it is the reason this entire category of product exists at all in the first place.
What each partner contributes
The three groups address different technical problems.
Lookout and NowSecure cover mobile, and the mechanism described is continuous visibility into device posture, operating-system vulnerabilities and application-level risk identified through binary analysis, including vulnerabilities inside embedded third-party software development kits. That last detail is the substantive one. Mobile risk frequently arrives not from the application a company built but from a library it did not write, and finding those requires looking inside the binary rather than at a manifest.
Claroty and Nozomi Networks cover operational technology and IoT, and the mechanism is passive discovery rather than scanning. A passive sensor watches network traffic and infers what devices exist and what they are, which is the only approach that works on a plant floor where active probing is unacceptable. The release notes that exposures which resist scanning or patching become visible and rise up the list, with compensating mitigations tracked in the same workflow. That is the right concession: for a device nobody can patch, the mitigation is a network control rather than a software update.
Okta covers identity, and the framing is that the platform weighs an at-risk account alongside the systems it can reach. That is a meaningful change from scoring identity risk in isolation, because an over-privileged service account with no reach is a different problem from one with domain administrator rights.
What a risk operations centre is for
A risk operations centre is worth defining, because the term carries weight the release does not unpack. It is not a security operations centre, which watches for incidents and responds to them. A ROC is the layer deciding which exposures matter, in what order, and who fixes them, and it exists because most organisations now have more findings than capacity to act on them.
That makes cyber risk management a triage discipline rather than a detection one, and it explains why scoring is the product rather than a feature. Detection tools are numerous and each works. The problem is that their outputs do not add up to a decision, and a ROC is the mechanism that turns them into one coherent decision.
The scoring problem the release treats as solved
The crux of any aggregation play is comparability, and the release treats it as settled. Every security tool produces a severity score, and those scores are not commensurable: a critical rating from a mobile binary analyser, a CVSS score from a vulnerability scanner and a risk rating from an industrial sensor measure different things on different scales.
Collapsing them into one number requires either a common ontology or a weighting model. TruRisk is Qualys’s answer, described as proprietary and not described further. That is fair commercially and it means a reader cannot judge whether the unified score carries more meaning than the five it replaces, or merely less detail.
The operational technology problem deserves one more sentence because it is the hardest of the three. Passive discovery tells you what is on the network, and it cannot tell you what runs on a device, which version, or whether that version carries a known flaw. Inferring firmware from network fingerprints is possible and imperfect. An OT risk score built on passive data therefore carries more uncertainty than one built on an agent, and the release does not discuss how that uncertainty propagates into a unified number.
The certification tracks and why they matter
The two new partner tracks are less interesting technically and more consequential commercially. Authorized mROC Advisor covers assessing a customer’s risk programme, defining priorities on the TruRisk basis and designing the operating model. Authorized mROC Delivery and Implementation Partner covers deploying the platform, integrating it with the existing stack including third-party findings and alliance telemetry, and standing up the workflows. The existing mROC Partner track covers running the centre as a managed service.
Three tracks at three stages describe a partner programme that has moved past reselling into a services structure. That matters because a risk operations centre is not a product a customer installs. It is an operating model, and most organisations buying one need someone to design it and someone to run it. Qualys is building the channel to supply both, which is a distribution decision rather than a technology one.

The AI framing, examined
The release opens by arguing that frontier AI models find vulnerabilities faster than any security team can triage, and that adversaries hold the same capability, so finding more vulnerabilities only deepens the backlog. The quoted executive calls a specific vulnerability event a wake-up call and says AI changed the economics of discovery and exploitation.
That framing is correct in direction and worth examining in one respect. If AI genuinely accelerates discovery, a platform whose value lies in scoring and prioritising findings becomes more valuable rather than less, because triage is the bottleneck. The vendor’s interest and the customer’s interest align here, which is worth noting precisely because it is not always true in security marketing.
What the release does not do is quantify any of it, at all. No figure appears for how many findings a customer sees, no measure of how much a unified score reduces triage time, and no customer describes a before and after. The argument is logical, internally coherent and entirely unevidenced.
The market logic
Qualys says more than 10,000 organisations trust it, including most of the Fortune 100, which is an installed base that makes a cyber risk management alliance programme attractive to partners. Claroty, Nozomi, Lookout, NowSecure and Okta each gain distribution into accounts they may not already hold, and Qualys gains telemetry that makes its score more complete.
Both sides benefit, which is why these alliances form and why they are worth reading as distribution arrangements rather than as engineering milestones. The technical work is real; the commercial purpose is coverage.
The competing approaches
Competing approaches to the same problem exist and the release does not mention them. One is to standardise on a single vendor’s platform and accept its scoring. Another is to keep the tools and aggregate their outputs in a data lake, building the scoring logic in-house. A third is to buy a risk quantification product that converts technical findings into financial exposure.
Qualys is selling the first, packaged as an alliance. That is a reasonable position and it competes against the other two on one axis: whether the customer trusts a vendor’s weighting model more than its own.
What is missing
The release names no customer. No pricing appears for the alliance programme, the certification tracks or the integrations. The release gives no timeline for partner availability, and does not say whether the five integrations are live today or planned. No technical detail appears on how the platform normalises telemetry across five vendors with five different data models, which is the engineering problem at the centre of any aggregation play of this kind. And it offers no figure for how many organisations have adopted mROC since the programme launched.
What to watch
Whether the five integrations are generally available or announced ahead of delivery. Whether Qualys publishes how TruRisk normalises telemetry across partners, because that determines whether the unified score is genuinely comparable or merely aggregated. And, whether a customer describes the before and after in triage volume, which is the only evidence that would substantiate the opening argument about cyber risk management under AI-accelerated discovery. And whether the certification tracks produce a partner base large enough to deliver, because a services structure with three tiers needs partners in all three to function.

