# A platform ranks the findings you give it, so the inventory, the owners and the rules have to exist first

PROGRAM GUIDE, read 10 Nov 2026

**The short answer.** A platform unifies findings and ranks them, but it cannot invent an asset inventory, name an owner or settle a policy. Programs that buy first spend the first quarter discovering those gaps. Five things should exist on paper before a proof of concept: scope, inventory, owners, rules and a baseline.

## The platform decides order, not the program's policy

A platform for unifying findings takes what your scanners, application security tools and cloud tools report, matches it to assets, and sorts it. That sorting is the product. The inputs to the sort are yours: which assets matter, who owns them, how fast each class of finding must close, and who may approve an exception. NIST frames patching the same way. [NIST SP 800-40 Rev. 4](https://csrc.nist.gov/pubs/sp/800/40/r4/final) defines enterprise patch management as identifying, prioritizing, acquiring, installing and verifying updates, and notes a divide between business or mission owners and security or technology management about the value of patching.

A team that signs a contract before these inputs exist usually discovers them during implementation, with the vendor's clock running. The five items below take a few weeks to produce. None needs a purchase.

## 1. A written scope

Write down what is in the program: environments (production, staging, corporate endpoints), asset classes (servers, containers, cloud accounts, applications, network devices) and finding types (software vulnerabilities, misconfigurations, code and dependency findings). Write down what is out. A platform will happily ingest everything it has a connector for, and a queue that mixes endpoint patches with code findings before anyone has agreed on a policy for each will not be worked.

Name the compliance drivers in the same document. A program under FedRAMP, CISA directives or PCI has due dates that are set outside the team; a program without them sets its own. The remediation SLA guide in this publication covers how to write those dates down.

## 2. An inventory you would stake an audit on

Every ranking depends on matching a finding to an asset. If the scanner sees 14,000 hosts and the configuration management database lists 11,000, the 3,000 difference is where findings go unowned. Before a proof of concept, export the list of assets from each source and measure the overlap on one key (hostname, IP and MAC, cloud instance ID). The overlap number is the first fact the platform will expose, so know it before the vendor does.

This publication does not rank asset inventory products; that is a separate category. The point here is narrower: decide which source is the system of record for asset identity, and write down the tie-break when two sources disagree.

## 3. Owners at the level a ticket can reach

A finding without an owner is a statistic. Owners need to exist as names or team queues in the ticketing system the work will be done in, not as a column in a spreadsheet. The owner assignment guide covers the rules. The prerequisite is simpler: for each asset class, you can say today which team gets the ticket. ServiceNow's documentation for its Vulnerability Response product describes assignment rules that run in ascending order with the first match applying ([ServiceNow docs](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/CYDyzm_AEkiaQuEnwDs3Ng/content)), which is a fair description of what any tool will ask of you: an ordered list of rules, each of which names a group.

If the answer for a class of assets is "it depends", the platform will not fix that. It will route to a default queue, and the default queue will age.

## 4. Rules for what counts as urgent

Decide the inputs and the ladder before any vendor shows you theirs. The common inputs are CISA's Known Exploited Vulnerabilities catalog, the [EPSS](https://www.first.org/epss/) probability that a CVE will be exploited in the next 30 days, [CVSS](https://www.first.org/cvss/) severity, and your own asset criticality. The guide on risk scoring rules gives a worked ladder using the numbers from the KEV Lag Ledger: 318 additions between 2025-11-10 and 2026-11-09, of which 10.4 percent carried a CVSS score below 7.

A written ladder is also your best defense in an audit. It lets you show that the order of work came from a rule, applied the same way every time, rather than from whoever shouted.

## 5. A baseline you can measure against

Pick the four numbers you will report before and after: mean time to remediate by priority, SLA attainment, scan coverage of the inventory, and the count of open findings past due by age. If you cannot produce even rough values from the current tools, say so and plan to produce them during the proof of concept. A vendor's claim of faster remediation can only be tested against a baseline you recorded. The measuring guide defines each formula.

With the baseline in hand, the choice between a scanner's built-in prioritization and a unifying platform becomes an empirical question, and the guide on scanner versus platform describes where the line usually sits.

## What to do when two or three of the five are missing

Some of the items can be produced inside the proof of concept, if the contract allows it. Scope, rules and baseline can be drafted in days. Inventory and owners are the slow ones, because they depend on other teams. If both are missing, a platform will still work, but expect its early reports to show a high share of findings with no matching asset and no owner. Treat that share as the first deliverable of the program, and check it again at 30 and 90 days.

A useful test before signing: pick one scanner's last export and trace 25 findings by hand to an asset, an owner and a due date. If you cannot do it by hand, the platform will not do it for you.

## Sources

- NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning: https://csrc.nist.gov/pubs/sp/800/40/r4/final (read 10 Nov 2026)
- FIRST, Exploit Prediction Scoring System: https://www.first.org/epss/ (read 10 Nov 2026)
- FIRST, Common Vulnerability Scoring System: https://www.first.org/cvss/ (read 10 Nov 2026)
- ServiceNow documentation, Vulnerability Response assignment rules: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/CYDyzm_AEkiaQuEnwDs3Ng/content (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/guides/what-a-program-needs-before-a-platform/
