# Patch Testing and Staging Policy Clause

Canonical: https://patchmanagementpolicy.com/policy-sections/testing-and-staging/
Last reviewed: 19 Nov 2026

## Patch testing policy

A patch testing clause makes a small canary set install first, writes the rollback method down before deployment and keeps the evidence. NIST SP 800-40 Rev. 4 describes canary rounds lasting a few days, then a few weeks, and EU Regulation 2024/2690 point 6.6.1(b) requires testing before production.

### What the section must say

- Which assets form the canary set and who chooses them.
- How long the canary observes before the rollout widens, and what counts as an incident.
- That a rollback method exists before deployment, or that the fallback is named.
- What test evidence is kept, by whom.
- How the clause changes when a vulnerability is class 1.

NIST SP 800-40 Rev. 4 section 3.5.1 says a small subset of assets should get the patch first and act as canaries; if they show minimal impact the deployment widens, and if not a different response, such as a temporary mitigation, can be planned. For larger rollouts that affect users it describes multiple rounds: a first round with technically knowledgeable users for a few days, then a larger round of early adopters across the organization for a few weeks. It says that in effect this is how the patching gets tested.

### Where testing is required by text

| Source | Requirement | Read status |
|---|---|---|
| EU Implementing Regulation 2024/2690, point 6.6.1(b) | Patches tested before they are put into production | Read |
| DORA RTS 2024/1774, Article 10(4) | Procedures cover testing and deployment of patches, and emergency patching | Read |
| NIST SP 800-40 Rev. 4, 3.5.2 | In an emergency a canary period may last a few minutes to a few hours | Read |
| NIST SP 800-40 Rev. 4, procurement questionnaire | Ask vendors how they test patches before release and whether they provide rollback to uninstall them | Read |
| PCI DSS; SOC 2 CC8.1 | Not read | Text unreadable on 19 Nov 2026 |

Read 19 Nov 2026.

### Sample wording

```text
5.1 Each maintenance group has a canary set of [number or percent] assets chosen by the group owner to represent the group.
5.2 A patch installs on the canary set first. The rollout widens after [2] working days if there is no incident. An incident is [defined: failed boot, service outage, user-reported loss of function, security-tool alert].
5.3 For class 1 patches the canary period is [hours]; the rollout may widen sooner on the policy owner's decision, recorded with the reason.
5.4 A rollback method is written before deployment. Where none exists, the fallback is [restore from backup taken before the window].
5.5 For each patch the record holds: what was tested, by whom, result, date, and the decision to widen.
```

### Common mistakes

- **A lab that does not match production.** NIST's approach tests on real assets in the group; the canaries are real assets by design.
- **No incident definition.** 'No problems' cannot be audited; clause 5.2 lists what counts.
- **Skipping the canary in an emergency.** NIST still suggests a canary of a few minutes to a few hours even then, to confirm the patch is not corrupted and does not break the software.
- **Rollback assumed.** Some patches cannot be uninstalled; record the fallback.

Continue to [maintenance windows](https://patchmanagementpolicy.com/policy-sections/maintenance-windows/). The same work as a monthly step is described in [acquire and test](https://patchmanagementpolicy.com/process/acquire-and-test/), and the full procedure is the [patch management procedure template](https://patchmanagementpolicy.com/templates/patch-management-procedure/).

### Sources

- [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
- [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

Last reviewed 19 Nov 2026

### Related pages

- [Patch Management Policy Sections: The Nine to Include](https://patchmanagementpolicy.com/policy-sections/)
- [Patch Maintenance Window Policy Clause](https://patchmanagementpolicy.com/policy-sections/maintenance-windows/)
- [Step 4: Patch Testing Process with Canary Rings](https://patchmanagementpolicy.com/process/acquire-and-test/)
- [Patch Management Procedure Template, Nine Steps](https://patchmanagementpolicy.com/templates/patch-management-procedure/)
