What's unpatched, what's actively exploited, who owns it
Vulnerability Management
Open CVEs across connected scanners, ranked by severity and flagged when they're on the CISA Known Exploited catalog. Answers the leader's question, how many unpatched vulns do we have, by severity, on which hosts, in one screen.
Why it matters
Built for outcomes, not checkboxes
CISA KEV Flagging, Daily
The platform pulls the CISA Known Exploited Vulnerabilities catalog every day and flags matching CVEs. No NVD dependency.
Top-Exposed Hosts
Which 10 servers own most of your critical exposure? Answers per-asset, sorted by open criticals descending.
Team Ownership
OS vulns route to Platform, library CVEs to AppSec, endpoint patches to IT Ops. Ownership inherits from the asset.
SLA Aging Buckets
How many vulns have been sitting past 90 days? The leader question, answered with a 3-bucket strip.
How it works
Everything in one place, nothing to bolt on
Exec Strip That Answers the CEO Question
Total open, open critical, Known Exploited (KEV) count, past-SLA count. Four numbers pulled from a single-row denormalized stats table, sub-ms regardless of tenant size.
- Total open CVEs, by severity
- KEV count flagged daily from CISA catalog
- Past-SLA count with critical call-out
- Average age of open vulnerabilities
Scanner Coverage
Connected scanners with sync freshness, so a stale source never silently drops out of the numbers. Tenable, CrowdStrike, SentinelOne, AWS Security Hub, and more feed through a shared writer.
- Per-scanner last-sync-at status
- Stale-source call-out (>48h)
- Direct link to manage integrations
- Shared writer architecture prevents data drift
Per-Asset and Per-Team Breakdown
Beyond totals: which hosts have the most open criticals, and which team owns them. Team assignment inherits from cmdb_assets and propagates to each CVE automatically.
- Top 15 most-exposed assets ordered by criticals
- Per-team rollup: open by severity, KEV count, past-SLA count
- Per-vuln-type segmentation (OS, application, library, network, cloud config, web/API, container)
- Team and scanner filters on the asset list
Aging That Drives Action
The leader question isn't 'how many', it's 'what's stuck?' Aging buckets surface vulns past 90 days so conversations happen before audits and insurers.
- 90-day / 30-90-day / under 30-day buckets
- Critical-past-90-days call-out in red
- Fixed-in-last-30-days for resolution trend
- MTTR computed over a 90-day window
Get started today
Run your security program, not just your tools
Whether you're the security lead holding it together in-house without a CISO, or a vCISO, consultant, or MSSP running client programs, Radius360 turns your stack into decisions your board and auditors trust.
We use cookies
We use strictly necessary cookies to make Radius360 work. With your consent, we'd also like to use analytics cookies to understand how visitors use our site so we can improve it. You can change your choice anytime. See our Privacy Policy.