In 2023 Windows updates enforced Microsoft's DCOM hardening, and OPC Classic links to SCADA failed on sites that had not prepared.
The process had not changed, only the operating system. So a patch on a validated server is a change under Annex 11 clause 10, which asks for changes to a computerized system, configuration included, to follow a defined procedure.
The record we expect for an operating system or application patch:
- Release notes and the SCADA vendor's compatibility statement for that exact patch.
- A risk assessment of the GxP functions it could touch: audit trail, e-signatures, alarms, historian writes.
- A run on a test system that mirrors the validated one.
- A full backup, and a restore that has been tested, taken just before installation.
- Regression checks sized to the risk, from logins and audit trail up to a partial OQ re-run.
The breakages are usually small: a historian service that does not restart after the reboot, or a time-sync setting reset so audit trail entries land out of order. A test server shows them in an afternoon.
Microsoft ships security updates monthly. A site that batches them into a quarterly validated cycle runs up to three months behind by choice, and that choice belongs in the risk assessment.
When we design SCADA to 21 CFR Part 11 and Annex 11, the test server is part of the architecture from the start.
How long is the patch cycle on your validated servers today?
Industries



