# Patch Management Policy Exceptions Clause Template

Canonical: https://patchmanagementpolicy.com/templates/patch-exceptions-clause/
Last reviewed: 19 Nov 2026

## Patch management policy exceptions clause

An exceptions clause names the grounds, the fields a request must hold, who signs, how long it lasts and when it is re-checked. This template sets a 90 day maximum and a 30 day re-check as site defaults; the grounds follow the HIPAA proposal of 6 January 2025 and EU Regulation 2024/2690 point 6.6.2.

### Where each part of the clause comes from

This page gives policy wording only. How an organization decides whether to accept a risk is a different subject and is not covered here. What a clause must contain is partly set by public text.

| Part of the clause | Source read | Text or requirement | Status |
|---|---|---|---|
| Grounds (a) and (b) | HIPAA Security Rule proposal, 90 FR 898, proposed 164.308(a)(4)(ii)(D) | No patch available; or the only available patch would adversely affect the confidentiality, integrity, or availability of ePHI | Proposal, not in force on 19 Nov 2026 |
| Ground (d) and written reasons | EU Implementing Regulation 2024/2690, point 6.6.2 | May choose not to apply patches when the disadvantages outweigh the cybersecurity benefits; must duly document and substantiate the reasons | In force; applies to the entity types in the regulation |
| Measures applied meanwhile (field 4) | HIPAA proposal (E) and (F); NIST SP 800-40 Rev. 4 section 3.5.4 | Documented compensating controls; approved long-term mitigation methods for unpatchable assets | Proposal; NIST is guidance |
| Escalation (A.10) | DORA RTS 2024/1774 Article 10(4)(d) | Set deadlines and escalation procedures in case those deadlines cannot be met | In force for financial entities |
| Re-check (A.7) | NIST SP 800-40 Rev. 4 section 3.5.5 | All exceptions to maintenance plans should be reviewed regularly to determine if the maintenance plan can be implemented now | Guidance |
| Maximum duration (A.6) | None found on 19 Nov 2026 in the sources read | No source read sets a maximum | Site default: 90 days |

Sources read 19 Nov 2026. The 90 and 30 day figures are the site's suggested defaults.

### Why requests need an end date

NIST says organizations should closely track and monitor all exceptions to maintenance plans, that having some is inevitable, and that assets with similar long-term exceptions might need a separate maintenance group with its own plan. An exception without an end date does neither: it is invisible and permanent. Field 5 of the clause forces a date and A.8 turns the expiry into a reported miss.

The five grounds are deliberately narrow. 'We were busy' and 'the owner is on leave' are not grounds; they are reasons to escalate under A.10 or to delegate approval, as in the [enterprise variant](https://patchmanagementpolicy.com/templates/enterprise/).

### The template

```text
## Annex A. Patch exceptions

A.1 Definition. An exception is an approved departure from a window in section 4 of this policy for named assets, for a stated period.

A.2 Who may request. A system owner, group owner or the patch coordinator.

A.3 Grounds. A request is accepted for consideration only on one of these grounds: (a) no patch is available; (b) the only available patch would adversely affect the confidentiality, integrity or availability of the system or its data; (c) the vendor no longer supports the software; (d) the disadvantages of applying the patch outweigh the security benefit and the reasons can be substantiated in writing; (e) a legal or contractual restriction prevents patching in the window.

A.4 The request records:
1. The assets (inventory IDs), their owner and maintenance group.
2. The vulnerability or patch (identifier, vendor advisory, class, original deadline).
3. The ground under A.3 and the evidence for it.
4. The measures applied meanwhile, who operates them and how their working is checked.
5. The requested end date.
6. The plan to remove the exception, with a named owner.
7. The requester and the date.

A.5 Signers. The group owner and the policy owner sign every exception. An exception on a class 1 or class 2 vulnerability also requires [executive sponsor].

A.6 Maximum duration. [90] calendar days. A longer period needs the executive sponsor's signature and a fresh request, not an extension.

A.7 Re-check. The patch coordinator reviews every open exception at least every [30] days to determine whether the window can be met now, and records the result.

A.8 Expiry. An exception ends on its end date. The asset then falls under the standard window; an expired exception is reported as a missed window in the next monthly report.

A.9 Register. The patch coordinator keeps a register of open and closed exceptions with every field in A.4; the register is part of the monthly report.

A.10 Escalation. A window that is going to be missed without an approved exception is escalated to the executive sponsor before it expires.

```

### Using it

Paste it as Annex A of the [general policy](https://patchmanagementpolicy.com/templates/patch-management-policy-template/), or of any variant. A healthcare provider adds the HIPAA lines in the [HIPAA variant](https://patchmanagementpolicy.com/templates/healthcare-hipaa/).

### Sources

- [Federal Register, HIPAA Security Rule to Strengthen the Cybersecurity of ePHI, 90 FR 898 (6 January 2025), proposed 164.308(a)(4)](https://www.federalregister.gov/documents/2025/01/06/2024-30983/hipaa-security-rule-to-strengthen-the-cybersecurity-of-electronic-protected-health-information), read 19 Nov 2026
- [EU Implementing Regulation 2024/2690, Annex, point 6.6](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402690), read 19 Nov 2026
- [EU Delegated Regulation 2024/1774 (DORA RTS), Article 10(4)](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32024R1774), read 19 Nov 2026
- [NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning (April 2022)](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [General Patch Management Policy Template, Full Text](https://patchmanagementpolicy.com/templates/patch-management-policy-template/)
- [HIPAA Patch Management Policy Template](https://patchmanagementpolicy.com/templates/healthcare-hipaa/)
- [Patch Management Policy Template Set, 10 Documents](https://patchmanagementpolicy.com/templates/)
