Radar Vulnerability scanning and management
Constant scanning that flags known weaknesses in your software and ranks them by the risk attackers actually pose.
A vulnerability scanner that returns four thousand findings has not helped you. Radar's job is to tell you which handful matter this week.
It takes the software inventory Quartermaster maintains and checks it against the public vulnerability record: the national database, the open-source advisory feeds, the vendor sources and the ecosystem-specific ones. Because it works from what you actually have installed, including versions, it can say whether a given weakness applies to you rather than whether it exists in the world.
Then it ranks. A weakness that is known to be exploited right now outranks a theoretical one with a higher score; a public probability of exploitation outranks a severity number on its own. What comes out is an ordered list with a fix for each item, which is a work queue rather than a report.
We have put real effort into the boring part of this: not crying wolf. Version comparison, vendor attribution and product naming are all places where scanners routinely produce findings about somebody else's software, and each of those has been closed deliberately, because a list you have learned to ignore protects nobody.
What Radar does
Version-aware
Findings are matched against the versions you actually run, not against product names.
Ranked by real risk
Known-exploited weaknesses and exploitation probability come first, not raw severity.
Comes with the fix
Each finding carries the version that resolves it, so the queue is actionable.
Tuned against false alarms
Cross-product and cross-version misattribution is filtered out rather than passed on.
- Continuous vulnerability detection across your estate, from your live inventory
- A prioritised queue driven by exploitation in the wild, not by score alone
- The fixing version for each finding, and the history of what you have closed
- A public lookup tool you can use on a single package for free, right now
Vulnerability handling and disclosure, prioritised by real-world exploitation.
And IMO maritime cyber resilience: IACS UR E26/E27
IACS UR E27 §5.2-5.4 / E26 §4.1.1.3: vulnerability handling and controlled patching of on-board software.
Works closely with
These are the capabilities Radar shares its facts with.
Want to see Radar on your own estate?
We will walk you through it against your actual sites, machines and obligations, and tell you where it would make no difference.