From scanner finding to deployed fix, with the Change in between.
TENSOR does not scan hosts. It takes what your scanners and advisory feeds report, connects it to the CIs and services in your CMDB, and routes the fix through the same governed Change process as everything else, so the data that drives the daily work is also the evidence your auditor asks for.
Deciding what to fix first, getting the fix approved, and proving it afterwards.
One finding per weakness, not per import
A finding is one weakness on one source asset, and one port and protocol where relevant, with its source identity and first-seen date. Repeated imports update the same finding instead of creating duplicates. Pen-test results and vendor notices go in as manual findings, and recording the same one twice returns the existing finding.
Scanner integration
Scheduled pulls from Tenable.io, Qualys VMDR and Rapid7 InsightVM record open findings as CVEs on the matching CI, duplicate-safe and above your minimum CVSS score.
CVEs in CMDB context
Each CI's CVE panel lists open CVEs with CVSS score and status, alongside suggested patches from the catalogue that close them. Impact and topology views show open-CVE counts and highlight CIs that support a critical function. Accepting a CVE exposure on a CI needs a second person to co-sign.
A patch catalogue that doesn't round unknowns to zero
Every patch with vendor, product, severity, adoption, missing CIs, CVE IDs and KB article, searched and sorted across the whole catalogue. When no CI has been assessed, adoption reads Not assessed instead of a misleading 0 %. A per-service rollup and a 90-day compliance trend sit alongside. Patches ingest daily from the Microsoft Update Catalog.
Patching as a governed Change
Deploy patch creates a Normal Change linked to every CI where the patch is missing, with a description from the patch metadata and a rollback plan, so CAB approval, freeze windows and segregation of duties apply as they do to any Change. The implementer records each CI as Installed, Failed with a reason, or Deferred.
Known-issue advisories that revoke pre-approval
When a vendor reports that a patch itself causes problems, an exact KB or CVE match marks it Known issue. A pre-approved Standard Change deploying that patch loses its pre-authorisation and goes back for a decision as a Normal Change. Withdrawing the advisory re-approves nothing.
Evidence as sealed reports
The Critical CVE evidence report snapshots which CIs carry critical CVEs. The DORA RTS Art. 10 remediation report traces each CVE to its patch, the Change that deployed it, the approval, the per-CI outcome and the resulting status. Every report is stored immutably, content-hashed, and bound to the head of the audit chain.
Prioritisation you can trace back
Source severity and CVSS, whether the CI supports a critical function, the services affected, due date and age. Scoring inputs are frozen when they are used, so a later change in an external feed never moves a deadline silently.
How this connects to regulation
Where this connects
What vulnerability coordinators ask.
See TENSOR running on your own estate.
30 minutes, screen-shared, no slides. Bring the process you are least sure we handle and we will start there.