GUIDES, read 10 Nov 2026
Guides for the people who run the program
- What a program needs before a platformA platform unifies findings and ranks them, but it cannot invent an asset inventory, name an owner or settle a policy.
- Scanner versus platform: where each one stopsA scanner finds weaknesses on the assets it can reach and scores them its own way.
- How to write a risk scoring rule with KEV, EPSS and criticalityWrite the rule as an ordered ladder.
- The remediation SLA that survives an auditCISA's BOD 22-01 set two weeks for newer CVEs in the KEV catalog and six months for older ones.
- FedRAMP in plain words: Moderate, High and who is authorizedFedRAMP authorizes a named cloud service offering at Low, Moderate or High impact, not a company.
- Measuring the program: MTTR, SLA attainment, coverage, backlog ageReport four measures, each with a written formula: mean and median time to remediate by tier, the share of items closed within SLA, the share of the inventory scanned recently, and open items past due by age band.
- Correlating and de-duplicating findings across scannersTwo scanners reporting one missing patch produce two findings.
- Planning connectors: count your sources, not the vendor's numberVendors publish connector counts from 100 (Qualys, Vulcan Cyber) to 500 (Rapid7), and each counts differently.
- Running a platform proof of concept with your own dataRun the proof of concept on your own exports for four weeks, with pass criteria written first: connectors working, a known-overlap merge, your scoring rule reproduced, tickets routed to real owners, and a report an auditor would accept.
- Owner assignment rules that route findings to a personOwnership data decides whether a ranked list becomes fixed systems.
Last reviewed 10 Nov 2026.