Patch Management Policy

MSP patch management policy

An MSP's policy has to answer who may approve patching on a system the MSP does not own. This variant ties every action to the client's written authority, runs the window clock from vendor release even when approval is late, and reports per client. EU Regulation 2024/2690 names managed service providers.

MSP variant: paste over the same-numbered sections of the general policy

1 Purpose and scope

1.1 This policy governs how [MSP name] patches systems that belong to its clients under written agreements. It covers each client's endpoints, servers, network devices and cloud tenants listed in that client's schedule.

1.2 No system is patched, rebooted or excluded without the authority recorded in the client's agreement or a written instruction from the client contact named in the schedule.

2 Roles and responsibilities

2.1 Service delivery lead ([role]): owns this policy.

2.2 Client technical contact ([named in schedule]): approves the client's maintenance window and exceptions.

2.3 Technicians: patch only inside the windows in the client schedule.

3 Asset inventory

3.1 The inventory is kept per client and records who administers each asset (MSP, client, third party) and any contractual or regulatory limit on patching.

4 Severity and patch windows

4.1 Default windows are those of the general policy, section 4.3. A client may require shorter windows. A client may not lengthen them beyond the default without a signed exception that names the systems and the end date.

4.2 The window clock runs from vendor release, whoever approves. Delay waiting for client approval is recorded and reported to the client contact.

6 Maintenance windows

6.1 Each client has its own windows and blackout dates, held in the schedule. Windows are not shared across clients unless agreed.

8 Reporting and metrics

8.1 One report per client per month: assets in scope, share patched inside the window by class, mean and median days, exceptions with age, and delays awaiting client approval.

8.2 Reports are delivered by [date each month] and kept for [period] after the agreement ends.

What differs when the estate belongs to someone else

Three facts from public text shape the variant. First, NIST SP 800-40 Rev. 4 lists, among inventory characteristics, the party who administrates the asset (IT department, third party, end user, vendor, shared responsibility) and any contractual restrictions on patching, for example a regulated asset that can only be patched by its manufacturer after testing. An MSP inventory must carry both for every client. Second, NIST adds that mission or business restrictions can limit risk responses, giving the example of an asset that can only be rebooted during a monthly maintenance outage; client windows and blackout dates are that rule in practice. Third, the MSP is itself a regulated entity in some places.

The EU Implementing Regulation 2024/2690 (adopted 17 October 2024, published in the Official Journal on 18 October 2024) covers, among other entity types, managed service providers and managed security service providers. Its point 6.6.1(a) requires security patches to be applied within a reasonable time after they become available, with testing before production, trusted sources, and added measures plus accepted residual risk where a patch is unavailable or not applied. Point 6.6.2 allows an entity to choose not to apply a patch where the disadvantages outweigh the benefits, provided it documents and substantiates the reasons. For an MSP that means a client's refusal must be recorded as the MSP's decision record, not left as a verbal note (source).

The clock problem

When approval comes from a client, windows slip for reasons outside the MSP's hands. The variant does not stop the clock; it records the delay and reports it (clause 4.2). That keeps the evidence honest for both sides: the monthly client report separates days the MSP held a patch from days it waited for the client's approval, so a late item is attributable.

Evidence map. NIST and Regulation 2024/2690 read 19 Nov 2026.
Evidence per clientWhere in the templateWhy it exists
Client schedule with windows and blackout dates1.1, 6.1NIST restriction on rebooting only in a maintenance outage
Written approval or standing authority1.2, 2.2No patch without recorded authority
Who administers each asset3.1NIST inventory characteristic: administering party
Signed exception with end date4.1NIS2 point 6.6.2: documented, substantiated reasons
Monthly report incl. approval delays8.1Shows where lateness came from

Where it connects

Use the general policy for sections not listed. Write the signed exceptions with the exceptions clause, and see roles and responsibilities for how to split duties when a client's staff share the work.

Sources

Last reviewed 19 Nov 2026