Skip to content
SOC 2 Compliance Software

Home / Glossary / Change management

Glossary, read 12 Nov 2026

Change management in a SOC 2 examination, defined with a sourced example

All termsRead the guides

The definition of Change management

For a software company the change population is mostly code deployments and infrastructure changes. The auditor pulls a sample from the full list of deployments in the observation window and checks each one for a ticket, a reviewer who was not the author, passing tests and an approval that came before release.

The frequent exceptions are self-approved pull requests, emergency fixes with no after-the-fact review, and infrastructure changes made in a console with no ticket at all. Setting branch protection so that a second person must approve a merge closes most of them and creates evidence automatically. Review each exception against the policy wording, because an emergency path that the policy permits is not an exception, while one it does not mention is.

NIST's guidance for CM-3 mentions Configuration Control Boards or Change Advisory Boards that review and approve proposed changes. A small team does not need a formal board, but it does need to say who approves, in the policy, and then show approvals in the tool. Unauthorized changes are part of CM-3 too, so detection matters as well as approval.

A sourced example

NIST SP 800-53 CM-3 guidance defines the scope as "the systematic proposal, justification, implementation, testing, review, and disposition of system changes, including system upgrades and modifications." Map that to a pull request: proposal is the ticket, justification is the description, testing is the CI run, review is the approver and disposition is the merge. NIST SP 800-53 Rev. 5 control catalog (OSCAL), read 12 Nov 2026.

Sources

  1. NIST SP 800-53 Rev. 5 control catalog (OSCAL), read 12 Nov 2026

Last reviewed 12 Nov 2026.