Patch Management Policy

Patch management roles and responsibilities

A roles clause names who owns the policy, runs the cycle, approves outage, installs, and decides an overdue window. NIST SP 800-40 Rev. 4 names seven audiences who need different patch metrics, from the board to system administrators, and DORA Article 10(4)(d) requires escalation when deadlines cannot be met.

The six roles most policies need

Duty table: the drafting is the site's own; the roles come from the general policy section 2.
DutyPolicy ownerPatch coordinatorSystem ownerPlatform adminExecutive sponsor
Approve the windowsDecidesAdvisesConsulted-Informed
Run the monthly cycleInformedDecidesConsultedDoes-
Approve outage time-InformedDecidesDoes-
Install and verify-ChecksInformedDoes-
Declare an emergencyDecidesDoesInformedDoesInformed
Decide an overdue windowAdvisesReportsAdvises-Decides
Sign exceptionsDecidesKeeps registerRequests-Decides on class 1 and 2

What public text says about roles

NIST SP 800-40 Rev. 4 section 3.6 notes that the audiences for patching metrics include the chief executive and board of directors, the chief information officer, the chief information security officer, mission or business unit leadership, application developers, security and system administrators, and other cybersecurity and IT personnel, and that each needs a somewhat different set of metrics suited to their role. Its inventory section also lists, as a characteristic to track, the party who administrates each asset: the IT department, a third party, an end user, the vendor or manufacturer, or a shared responsibility model. A roles clause that does not account for all five values leaves some assets with no one obliged to patch them.

DORA's RTS, Article 10(4)(d), asks financial entities for set deadlines for installing patches and updates and for escalation procedures in case those deadlines cannot be met. In the table, that is the 'decide an overdue window' row, which has to name a person, not a team.

Sample wording

2.1 The policy owner is [role]. The deputy is [role] and acts when the policy owner is absent for more than [2] working days.

2.2 The patch coordinator runs the monthly cycle and keeps the evidence.

2.3 System owners approve outage time within [2] working days of a request. Silence is not approval; if no answer comes, the patch coordinator escalates to the executive sponsor.

2.4 Where a third party administers a system, the contract names the patch windows, the report the third party sends and the person at [Company name] who receives it.

Common mistakes

  • Naming people instead of roles. Policies outlive staff; keep names in a register, roles in the policy.
  • No deputy. A single approver turns a 14 day window into a leave-calendar problem.
  • Approval with no deadline. NIST says that routine patching is often postponed and neglected, which gives attackers windows of opportunity; clause 2.3 above gives approval a clock.
  • Nobody for the third party. For an MSP, the question is reversed; see the MSP template.

For the clause that follows, see asset inventory; for the exception signers see the exceptions clause.

Sources

Last reviewed 19 Nov 2026