What it looks like to run it.
Three views from the platform: the exposure dashboard, the scan queue, and the prioritized findings — the loop that takes a vulnerability from found to fixed to verified.
exposure dashboard
One score for the estate, and the four numbers that move it: open criticals, vulnerabilities already known to be exploited in the wild, findings on software the vendor no longer supports, and how long a fix is currently taking. The trend line is there so you can tell whether the number is falling.
scans
Scans run to a schedule and to a scope you authorize — discovery, vulnerability and web application passes, plus a PCI DSS-aligned profile for the checks that assessment asks about. The history shows what ran, what it found, and what failed rather than only what succeeded.
findings
Findings ordered by what to fix first, not by what was found first: severity next to a risk score, the EPSS probability that a vulnerability gets exploited, the CVE it maps to, and whether the clock on it has already run out. Every row names the asset it belongs to.
Interface mockups with sample data, not a client's environment: the findings, asset names and scores shown here are illustrative. What your own dashboard reports depends on the scope you authorize and what the scans actually find.
