Requirement
Procedures for change management govern changes to information systems and networks.
What the engine looks for
For the control to count as covered, every group below must be satisfied by an affirmative statement, not a plan, a hedge or a denial. A term ending in … matches any word it begins. Supporting terms don't change the verdict. They raise confidence, and they separate a policy that names a mechanism from one that only gestures at a category.
Required element 1 — any one of
change managementchange controlchange requestchanges to productionproduction changeschange process
Required element 2 — any one of
approv…review…testeddocumentedprocedure
Supporting terms — specificity signals
314.4(c)(7)rollbackcab
Contradiction markers
Finding any of these outranks coverage: a policy that admits the gap is worse than silence.
no change management
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| ISO 27001 | A.8.32 | Change management | change-management |
| SOC 2 | CC3.4 | Assessment of significant change | change-management |
| SOC 2 | CC8.1 | Authorised change management | change-management |
| PCI DSS 4.0.1 | 6.5 | Change management and separation of environments | change-management |
| SOC 2 | CC5.2 | Technology general controls | change-management |