# Step 4: Patch Testing Process with Canary Rings

Canonical: https://patchmanagementpolicy.com/process/acquire-and-test/
Last reviewed: 19 Nov 2026

## Patch testing process

Test a patch by validating it, then patching a small canary group first. NIST SP 800-40 Rev. 4 suggests a first round of administrators lasting a few days, then early adopters for a few weeks; in an emergency the canary period can shrink to minutes or hours. Read 19 Nov 2026.

### Validate before you test

Authenticity and integrity come first. NIST says a patch “should be confirmed, preferably by automated means, before the patch is tested or installed,” because it could have come from a rogue source or been tampered with in transit ([NIST SP 800-40 Rev. 4, section 2.3.1](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf)). Record the hash or signature check and its result with the patch identifier.

Where this fits: it follows [assess and prioritize](https://patchmanagementpolicy.com/process/assess-and-prioritize/) and precedes [approval](https://patchmanagementpolicy.com/process/approve-and-schedule/); the policy section is [testing and staging](https://patchmanagementpolicy.com/policy-sections/testing-and-staging/).

### Canary rings

NIST's routine plan uses phased deployment in which a small subset “act as canaries.” For larger rollouts it describes two rounds: a small first round of technically knowledgeable users lasting a few days, then a larger round of willing early adopters for a few weeks, ideally representative of everyone who will later get the patch. For emergencies NIST keeps the canary step but compresses it: “a few minutes to a few hours” (section 3.5.2). A policy states the ring sizes and minimum durations per maintenance group so the test is not decided under pressure.

| Control | What the vendor documents | Use in testing |
|---|---|---|
| Windows update rings in Intune | Rings set deferral periods, restart settings and deadlines; a ring can be paused for up to 35 days, then the pause expires | Stage test, pilot and production rings; the 35-day cap bounds how long a ring can hold back |
| Microsoft optional preview update | Released in the fourth week of the month, “typically used for early validation of the monthly security update” | Install the preview on test rings about two weeks before the second-Tuesday release |
| AWS Patch Manager default baselines | Windows Server and several Linux baselines auto-approve 7 days after release; the 7-day wait is not applied to Debian or Ubuntu, where release dates are unreliable | The delay is a built-in test window; a custom baseline is needed to shorten it |

Sources: Microsoft Learn and AWS documentation, read 19 Nov 2026.

### Limits of testing

Testing cannot cover everything. NIST SP 800-82 Rev. 3 warns for operational technology that “a patch may remove a vulnerability, but it can also introduce a greater risk from a production or safety perspective,” and advises regression testing and, where possible, offline system testing. See [OT and medical devices](https://patchmanagementpolicy.com/patching/ot-and-medical-devices/) for those windows. Hotpatch updates for Windows Server do not support automatic rollback: a problem means uninstalling the update and installing the last working baseline, which needs a restart ([Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/get-started/hotpatch)).

### The record to keep

- The validation result for each patch (what was checked, by whom or by which tool).
- Ring membership: which assets were canaries, and the dates each ring started and ended.
- The decision to widen, hold, or switch to a mitigation, with the evidence that drove it.
- Defects found, with the vendor ticket, so [approval](https://patchmanagementpolicy.com/process/approve-and-schedule/) can cite them.

### 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
- [NIST SP 800-82 Rev. 3, section 6.2.11](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-82r3.pdf), read 19 Nov 2026
- [Microsoft Learn, Intune Windows update rings](https://learn.microsoft.com/en-us/mem/intune/protect/windows-10-update-rings), read 19 Nov 2026
- [Microsoft Learn, Update release cycle](https://learn.microsoft.com/en-us/windows/deployment/update/release-cycle), read 19 Nov 2026
- [AWS Systems Manager, predefined and custom patch baselines](https://docs.aws.amazon.com/systems-manager/latest/userguide/patch-manager-predefined-and-custom-patch-baselines.html), read 19 Nov 2026
- [Microsoft Learn, Hotpatch for Windows Server](https://learn.microsoft.com/en-us/windows-server/get-started/hotpatch), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [Patch Management Process in 9 Steps (NIST SP 800-40r4)](https://patchmanagementpolicy.com/process/)
- [Step 5: Patch Approval Process and Scheduling](https://patchmanagementpolicy.com/process/approve-and-schedule/)
- [Step 3: How to Prioritize Patches by Risk Response](https://patchmanagementpolicy.com/process/assess-and-prioritize/)
- [Patch Testing and Staging Policy Clause](https://patchmanagementpolicy.com/policy-sections/testing-and-staging/)
- [OT Patch Management Policy and Medical Devices](https://patchmanagementpolicy.com/patching/ot-and-medical-devices/)
