Decision-makers rarely lack information about vulnerability management. They receive reports, vendor presentations, internal updates and audit findings. What they often lack is a clear way to test whether a proposal is sound. The difficulty is not that the subject is obscure. It is that the answers depend on details that proposals do not always state.
This guide takes a different approach from a standard explainer. Instead of describing the discipline from the top down, it sets out the questions that a senior leader can ask, explains why each one matters and describes what a satisfactory answer looks like. The questions apply whether the proposal comes from an internal team or an external provider.
Questions about scope
The first question is simple: what exactly will be covered? A proposal should name the assets in scope, including on-premises infrastructure, cloud accounts, applications, endpoints and third-party hosted services. Where something is excluded, the proposal should say why and who is responsible for it instead.
A second question follows from the first. How will the asset list be kept accurate? A programme that scans a list that was correct two years earlier will miss new systems and report on systems that no longer exist. A satisfactory answer describes how discovery works and who reviews its output.
A third question concerns the most important systems. Which services would cause the greatest harm if compromised, and are they covered at a level of detail that reflects that importance? A proposal that treats every asset identically is usually a proposal that has not thought hard about priorities.
Questions about ownership
Vulnerability management fails most often at the point where a finding must become a fix. The decision-maker should ask who owns each stage. Who receives findings? Who decides priority? Who approves exceptions? Who carries out the remediation? Who confirms that a fix has worked?
A proposal that answers these questions with a team name rather than a role is incomplete. Roles should map to people, and each system should have a named owner who is accountable for responding to its findings. Without that, reports accumulate and nothing changes.
Ask also how disputes are settled. Engineering teams sometimes contest a finding, and security teams sometimes contest a deferral. A process that resolves those disagreements quickly protects both the programme and the relationship between the teams.
Questions about priority and timing
Ask how the programme decides what to fix first. A satisfactory answer goes beyond the scanner's severity rating. It should consider whether the asset is exposed, how critical it is to the business, and whether there is credible information that the weakness is being exploited. It should also explain how these factors are combined and who has authority to change the outcome.
Timing questions matter as well. How quickly are critical findings expected to be addressed, and how is that expectation communicated? Are the timescales set by policy, by contract or by regulatory obligation? A decision-maker should be wary of timescales that appear in a proposal without any stated basis.
Questions about evidence
Ask what evidence the programme will produce. Frameworks such as ISO 27001, PCI DSS and SOC 2 each expect organisations to show that vulnerabilities are identified, assessed and addressed, and that fixes are verified. The exact expectations vary, so the decision-maker should confirm them with the relevant assessor before accepting a proposal that claims to satisfy them.
The evidence question also tests whether retesting is included. A finding closed without verification may simply have been hidden. A proposal that describes how fixes are checked gives more confidence than one that describes only how findings are closed.
Questions about cost and dependence
Ask what the proposal costs in full, including staff time, infrastructure, licences and any external support. A figure that covers only the tooling is not a complete cost. Ask also what the programme depends on. Does it rely on a single individual, a single provider or a single platform? If so, what happens when that dependency changes?
Exit arrangements deserve a question of their own. If the programme moves to a different provider or tool, can the asset history, findings and evidence be transferred? A satisfactory answer describes the data formats and the responsibilities for export.
Questions about the provider
When an external provider is involved, the decision-maker should ask how the provider's own staff are vetted and supervised, how scanning data is protected in transit and at rest, and where the data is stored. These questions are particularly important where the provider will see sensitive information about the estate. The answers should be specific enough to test, not reassurances.
Ask also what the provider will not do. A clear statement of exclusions prevents misunderstandings about what has been bought.
What a good answer sounds like
A satisfactory answer tends to be specific, consistent and open about limits. It names owners, describes process and acknowledges where the programme cannot see everything. A weak answer relies on general assurances, avoids naming responsibilities and treats the scanner as the solution.
Decision-makers should also notice when answers conflict. If the proposal promises rapid remediation but describes a backlog of unowned findings, the two statements cannot both be true.
Common mistakes
The most common mistake is accepting a proposal because it is supported by an impressive dashboard. A dashboard shows what has been measured, not whether the measurement is complete. Another mistake is delegating all the questions to a technical team without agreeing the answers in advance. A third is treating the decision as a one-off. Vulnerability management is continuous, and the questions should be revisited as the estate and obligations change.
Next steps
Take the questions in this guide and ask the internal or external team to answer them in writing before the next budget discussion. Compare the answers against the list of satisfactory characteristics. Where the answers are incomplete, treat that as information about the proposal rather than as a reason to proceed quickly.
Frequently asked questions
Who should own vulnerability management in the organisation?
Ownership should be clearly assigned at the level of each system, with an overall programme owner responsible for priority, governance and reporting. Unclear ownership is one of the most common reasons programmes stall.
Is a high-severity finding always the first thing to fix?
Not necessarily. Severity should be combined with exposure, asset criticality and any reliable information about active exploitation before priorities are set.
What is the most important question to ask a provider?
How they will protect the data they collect about the estate and what they will not do. Specific answers to those two questions reveal a great deal about the quality of the service.
Related reading
If you are working through this topic, these related articles cover neighbouring questions:
