A strategy describes how vulnerability management will be carried out. Governance determines who sets its direction, who holds the authority to accept risk and how the organisation knows whether its choices are sound. The two are closely linked, yet they are often treated separately. Technical teams draft the strategy, and leaders are asked to approve it without a clear view of the governance it depends on. This article takes the leadership perspective and sets out the governance questions that should be settled before the strategy is finalised.
Start with the policy and its authority
The policy sets the principles and obligations: that the organisation identifies and addresses weaknesses, that the process applies to defined assets and that exceptions follow a controlled route. The strategy then describes how those principles will be met. Confusion arises when the two documents disagree, or when the policy is written so loosely that it cannot be enforced.
Leaders should confirm who has authority to approve the policy, who can amend it and how often it is reviewed. A policy that nobody with authority has endorsed will not carry weight in a dispute between teams.
Define the risk appetite in operational terms
Risk appetite statements are often expressed in broad language that does not guide decisions. For vulnerability management, the appetite needs to be translated into operational terms. Which categories of system may carry unresolved high-priority weaknesses, and for how long? Which categories must never carry them? What evidence is needed before a higher level of risk can be accepted?
These answers shape the exception process and the priority bands. Without them, each exception becomes a negotiation, and inconsistent decisions follow.
Assign accountability clearly
Accountability should be written in a form that people can apply. A responsibility matrix that sets out who is responsible for doing the work, who is accountable for the outcome, who must be consulted and who must be informed helps prevent gaps. In vulnerability management the common points of confusion are the ownership of shared platforms, the authority to accept risk and the responsibility for verifying that fixes have worked.
Accountability should rest with people who have both the authority and the resources to act. Naming an owner who cannot allocate work to fix a weakness is a formality rather than governance.
Control exceptions with discipline
Exceptions are where governance is tested. A disciplined exception process requires a written request that states the weakness, the business reason for the delay, the compensating measures, the proposed review date and the approver. The approval level should rise with the severity and the business significance of the item. Each approved exception should be recorded in a register that is reviewed regularly, and expired exceptions should escalate automatically.
Leaders should look for patterns in the register. A large number of exceptions for one platform, or a steady increase in exceptions for one business unit, may indicate a structural problem that needs funding rather than repeated approval.
Consider compliance obligations at a general level
Many organisations operate under contractual, sector or framework-based expectations about how they manage security weaknesses. These expectations may cover the scope of assessment, the frequency of review, the handling of third-party components and the evidence retained. The precise requirements vary considerably, and leaders should not rely on general descriptions when deciding what the governance must achieve.
The practical step is to obtain the relevant obligations from the people who manage those relationships, confirm them with qualified advisers where necessary and map each obligation to a governance control. A map of that kind shows where the programme already meets an obligation and where additional work is needed.
Build oversight without micromanagement
Leaders need enough information to hold the programme to account without taking over technical decisions. A standing governance forum, with representation from security, technology and the business, can review exceptions, trends and resourcing. The forum should have terms of reference that define its decisions, its quorum and its escalation route to the executive team.
Oversight is most effective when it focuses on decisions. Leaders should ask whether the right decisions are being made, by the right people, on the basis of reliable information. They do not need to validate individual findings.
Plan the reporting line
Governance also requires a clear reporting line. Decide who receives regular reports, how often they receive them and what action is expected in response. Reports that arrive without a decision attached tend to be filed rather than acted upon.
Keeping a record of decisions
Governance depends on memory as much as on structure. Decisions about risk acceptance, scope exclusions and priority changes shape the programme for months or years, and the people who made them may move on. A decision log that records the decision, the date, the people involved, the options considered and the reasoning provides continuity and lets later reviewers understand why the programme looks the way it does.
The log should be proportionate. Not every operational choice needs a formal entry, but changes to policy, risk appetite, exception thresholds and scope should always be recorded. Entries should be short and written in plain language, with links to supporting evidence rather than copies of it. Where a decision has been reversed, the log should record that too, so the history is complete rather than selective.
Independent review adds value. An internal audit function, or a peer reviewer from outside the programme, can periodically sample decisions and test whether they followed the agreed rules. Findings should go to the governance forum with agreed actions and owners. Reviews that stay within the programme team tend to confirm its own view, whereas an independent sample is more likely to surface weaknesses that insiders have stopped noticing.
Common mistakes
- Approving a strategy without confirming the policy, risk appetite and accountability it depends on.
- Writing risk appetite in language that cannot guide a decision.
- Allowing exceptions to be approved informally or without expiry dates.
- Relying on general descriptions of compliance obligations rather than confirming them.
- Setting up a forum without decision rights or an escalation route.
Next steps
Ask the executive team to confirm three things before approving the strategy: the owner of the policy, the operational statement of risk appetite and the approval levels for exceptions. Once those are agreed, map the strategy's controls to the obligations that apply to the business, and review the gaps with the responsible owners.
Frequently asked questions
Who should own the vulnerability management policy?
Usually a senior executive with responsibility for security or risk, supported by the security function. The owner should have the authority to enforce it across technology teams.
What is the difference between risk appetite and risk tolerance?
Risk appetite describes the level of risk the organisation is willing to accept in pursuit of its objectives. Risk tolerance describes the acceptable variation around specific measures. Both should be stated in terms that help decisions about exceptions.
Does governance need to be different for outsourced programmes?
The principles are the same, but the contract must give the organisation the visibility, reporting and decision rights it needs. Confirm those terms before the service starts.
Related reading
If you are working through this topic, these related articles cover neighbouring questions:
