Most organisations already run vulnerability scans. Fewer can explain what happens to the results, who is expected to act on them and how the organisation would know whether its exposure was going down. A strategy answers those questions. It is a short, owned and measurable plan that sets out what is in scope, who does what, how quickly different kinds of weakness must be addressed and how progress will be reported. Planning for 2027 is a good moment to write one down, while budgets and audit cycles are still being set.
Start with a defined scope
The strategy should state what it covers in terms the business recognises. An IP address range is a technical boundary, but it says little about what is at stake. A better starting point is a list of business services and the components that support them: on-premises servers, cloud accounts, containers, endpoints, network devices, customer-facing applications and any third-party hosted systems that handle the organisation's data.
Equally important is the statement of what is excluded and why. An exclusion is sometimes justified, for example where a system is being retired or is managed under a separate contract. An undocumented exclusion is a blind spot.
Assign ownership before selecting tools
Tooling decisions tend to dominate early planning, but a tool cannot assign a fix to a team. The strategy should name owners by role for each class of asset. A common pattern separates three responsibilities. The security function sets requirements, maintains the risk view and verifies closure. Platform and infrastructure teams own remediation for the systems they operate. Application teams own the libraries and components they build and deploy.
Consider an illustrative organisation in which findings in a shared internal library were reported repeatedly but never closed, because two product teams each assumed the other owned it. A one-page ownership table would have resolved that within a single planning meeting.
Build risk-based priorities
The strategy should define how findings are ranked. Useful factors include exposure to untrusted networks, sensitivity of the data processed, business criticality of the service, evidence of active exploitation and the strength of existing compensating controls. Those factors can be grouped into a small number of priority bands.
Each band should map to a response timeframe that has been agreed with the teams who must meet it. Avoid copying timeframes from another organisation without reviewing whether they are realistic for your change processes. A timeframe that nobody can meet is worse than no timeframe, because it trains people to ignore the policy.
Define exceptions and risk acceptance
No programme closes every finding on time. Some fixes depend on vendor releases, some systems cannot be patched without disrupting a critical process and some risks are accepted deliberately. The strategy should describe an exception process that is time-limited, documented, reviewed and approved at a level appropriate to the risk. An exception without an expiry date becomes a permanent exposure that is no longer visible to anyone.
Choose an operating rhythm
A strategy needs a cadence. Scanning and asset discovery are usually continuous or frequent. Triage of new findings is typically a weekly activity. A monthly review with system owners can address ageing items and recurring issues. A quarterly steering discussion with senior leaders should focus on exposure trends, exceptions and resource needs rather than individual vulnerabilities. Writing the rhythm down makes it easier to defend when urgent work competes for the same people.
Plan the roadmap in phases
Few organisations can mature every capability at once. A sensible roadmap usually begins by stabilising the asset inventory and ownership model, then extends coverage to the remaining estate. Prioritisation can be refined once the data is reliable, and workflow automation makes sense only after the process is understood by the people running it. Integration with change management comes last, once the basic loop of finding, fixing and verifying is working consistently.
Measure what changes behaviour
Measurement should show whether exposure is falling and whether the process is working. Useful measures include the proportion of the estate covered by scanning, the age profile of open high-priority items, the number and age of active exceptions, and the rate at which closed findings reappear. Activity counts, such as the number of scans run, measure effort rather than outcomes and should be treated as supporting information only.
Aligning the strategy with budgets and audit cycles
A strategy that ignores the calendar is unlikely to be funded. Most organisations plan budgets, recruitment and technology purchases on an annual cycle, and they schedule external assessments on a separate timetable. The strategy should show when decisions are needed so that resourcing requests reach the right forum in time. A proposal to change the scanning approach may need approval before the next budget round, and a service change may need lead time to be procured and tested.
Audit cycles deserve similar attention. Where an external assessor will review the programme, the strategy should identify the evidence that will be requested, the records that must exist before the review starts and the gaps that management already knows about. Presenting known gaps with a plan is usually more credible than having them discovered during the assessment. Milestones of this kind can be set out in a simple table showing the owner, date and status of each item.
The strategy should also allow for change that arrives without warning. New systems may be commissioned, a supplier may be replaced or a regulator may revise its expectations. A short section describing how the plan will be updated in those circumstances, and who can re-prioritise funds, prevents the strategy from drifting away from reality.
A practical test is whether each objective can be linked to a budget line, an owner and a date. Objectives without all three tend to remain aspirations. Where an objective cannot be funded in the coming cycle, the strategy should say so and record the consequence of deferral, so that the trade-off is visible to leaders rather than hidden in the plan.
Common mistakes
- Writing a strategy that describes tools but not ownership or decisions.
- Setting timeframes that look impressive on paper and cannot be met.
- Allowing exceptions to run without expiry dates or review.
- Presenting activity metrics to leaders instead of exposure trends.
- Treating the strategy as finished once approved, rather than reviewing it after major changes to the estate.
Next steps
Draft a two-page strategy statement covering scope, ownership, priority bands, exception rules, operating rhythm and measures. Test it with three system owners before seeking formal approval, and record the review date in the document itself. The aim is a plan that people will actually follow.
Frequently asked questions
Should the vulnerability management strategy be separate from the policy?
Often yes. A policy states principles and obligations, while the strategy explains how those obligations will be met, who is responsible and what the timeline and measures are.
How often should the strategy be reviewed?
At least annually, and after any significant change to the estate, the operating model or the regulatory obligations that apply. The next review date should be recorded in the document.
Does the board need to approve the strategy?
That depends on the governance arrangements. Boards generally need visibility of material risk and exceptions rather than the detail of individual findings.
Related reading
If you are working through this topic, these related articles cover neighbouring questions:
