What Is Vulnerability Management? How to Measure Success: Planning for Growth

Vulnerability management produces a great deal of data. Scanners report findings, ticketing systems record activity and dashboards display totals. Yet a programme can generate impressive numbers while exposure remains high. The purpose of measurement is to show whether the organisation is becoming less exposed over time, and whether the process that produces that outcome is working. This article begins with a brief definition for readers new to the discipline, then focuses on the measures that matter and how to plan for them as the estate grows.

A brief definition for context

Vulnerability management is the continuous process of finding, assessing, prioritising, fixing and verifying weaknesses across an organisation's systems. Measurement sits within that loop. It tells leaders and practitioners whether the loop is closing, how quickly it does so and where it stalls. Without measures, the programme relies on assurances that are difficult to test.

Measures that reveal activity, and why they mislead

Activity measures are easy to collect. The number of scans run, the number of findings detected and the number of tickets opened all describe work done. They can be useful for capacity planning, but they say little about exposure. A rise in detected findings may mean that coverage has improved, which is good, or that a new build process is introducing weaknesses, which is not. Activity measures should support the outcome measures, not replace them.

Measures that reveal exposure

Several outcome measures give a more reliable picture. Coverage shows the proportion of the estate that is being assessed, ideally with the scope broken down by asset type and business service. Validated exposure shows how many confirmed weaknesses exist in each priority band, and how that number is changing. Backlog ageing shows how long open items have been waiting, grouped by priority, so that overdue high-priority items stand out.

Time to remediate, measured from validation to verified closure, shows how quickly the organisation responds to weaknesses. The median and the spread both matter. A good median that hides a long tail of old items is not reassuring. Reopened findings, which return after closure, indicate whether fixes are durable or whether root causes are being missed. Exception counts and their ages show how much residual risk is being carried deliberately.

Choosing the right measures

A small set of measures is usually better than a large dashboard. Choose measures that connect to decisions. Coverage matters if leaders need to know whether they can rely on the programme. Backlog ageing matters if owners need to know where to focus. Reopened findings matter if the question is whether the process is producing durable results.

Each measure should have a definition, a data source, an owner and an agreed interpretation. A measure without a definition will be interpreted differently by each reader.

Avoid targets that encourage the wrong behaviour

Targets can distort behaviour. If teams are measured only on the number of items closed, they may close easy items first and leave difficult ones. If they are measured only on time to close, they may downgrade priorities to meet deadlines. Targets should be designed to reward the outcome that matters, and should be reviewed to check for unintended effects.

Where a target is set, record the basis for it. Targets based on arbitrary numbers are difficult to defend when the organisation's circumstances change.

Planning measurement for growth

Measurement needs to grow with the estate. A set of measures built for a small estate may become unreliable when new asset types arrive, when acquisitions bring in unfamiliar systems or when teams are reorganised. Plan for growth by documenting how measures will be applied to new asset types, by reviewing the scope of coverage at regular intervals and by checking that data sources remain complete.

Growth also changes the audience. A measure that is meaningful to a platform team may be too granular for an executive committee. Plan separate views for operational owners, programme managers and senior leaders, drawing on the same underlying data.

Reading trends without over-reading them

Trend lines are powerful, but they are easy to misread. A short-term rise in open findings may reflect a new scan that covers more assets, not a deterioration in security. A sudden fall may reflect a scope change that removed hard-to-assess systems from the count. Before drawing conclusions, check whether the scope, the scanning method and the classification rules have stayed the same across the period being compared.

Small numbers also mislead. A team that handles only a few items a quarter can show large percentage swings from one period to the next, and those swings may reflect chance more than performance. Where volumes are small, use longer periods or show the underlying counts alongside the percentages. Annotate reports with significant events, such as a platform migration or a change in the priority model, so that readers can interpret the lines correctly.

Be cautious about comparing teams directly. Teams differ in their estates, risk profiles and types of work. A team running legacy platforms may carry older findings and longer ageing than one running modern services, and that difference is not necessarily a failure. Comparisons are more useful when they focus on how each team responds to its own findings, such as how quickly it acts on new high-priority items and how often it reopens closed work.

A useful habit is to write one sentence explaining each trend in every report. If the sentence cannot be written with confidence, the trend should be described as unclear, and further investigation should be scheduled before any decision depends on it. Leaders should also ask what the trend would look like if the scope were held constant. Restating the historical series on a comparable basis is more work than it appears, but it is the only reliable way to tell whether the programme is improving or merely changing shape.

Common mistakes

  • Presenting the number of scans or findings as evidence of improvement.
  • Reporting averages without showing the spread or the oldest items.
  • Setting targets without recording their basis or checking for unintended effects.
  • Changing the scope of coverage without restating previous results on a comparable basis.
  • Building a large dashboard that nobody uses to make decisions.

Next steps

Select five measures across coverage, exposure, ageing, remediation and reopened findings. For each one, write the definition, the data source, the owner and the decision it informs. Review the set after two reporting cycles and remove any measure that has not changed a decision.

Frequently asked questions

What is the most important vulnerability management metric?

There is no single answer. Coverage and backlog ageing are usually the most revealing starting points, because they show whether the programme sees the estate and whether it is keeping pace.

Should we publish our remediation times externally?

Only if the figures are accurate, defined consistently and placed in context. Public statements about performance carry commercial and legal implications, so they should be reviewed before release.

How often should measures be reviewed?

Review the definitions and their usefulness at least annually, and whenever the estate or the reporting audience changes materially.

Related reading

If you are working through this topic, these related articles cover neighbouring questions:

Leave a Comment