Articles

Change management and change approval: who signs, and what the record shows

An approval nobody can point at never happened: what a change record has to prove.

Reading: 5 minCybersecurity Governance

Article cover: Change management and change approval: who signs, and what the record shows

The governance act in change management is not the deployment; it is the approval. Someone with named authority reviews a proposed change against an analysis of its security impact, decides, and leaves a record showing what was approved, by whom, and with which baseline before and after. An approval nobody can point at is a decision that never happened.

Not every change is a change

The scope question comes first: it is a written decision, not a judgement taken per ticket. SP 800-128 defines configuration change control as the “process for managing updates to the baseline configurations for the configuration items” (line 884), and adds the four verbs that make it governance rather than maintenance: changes are “formally requested, evaluated for their security impact, tested for effectiveness, and approved before the changes are implemented” (lines 2640–2644). CM-3 opens by requiring the organisation to “determine and document the types of changes to the system that are configuration-controlled” (lines 7239–7240). An exempted or pre-approved change still leaves a trace — “however, system documentation may still require updating” (lines 2660–2663). An exemption that skips the record is not an exemption but an untracked change.

Who approves, and on what evidence

SP 800-128 defines the approving body: the Configuration Control Board (CCB) is “a group typically consisting of two or more individuals that have the collective responsibility and authority to review and approve changes to an information system” (lines 1164–1166), and it is “a check and balance on configuration change activity” (lines 1167 and 1176–1179).

The evidence is itself a control. CM-3 makes the approval conditional — approve or disapprove “with explicit consideration for security and privacy impact analyses” (lines 7242–7244) — and CM-4 IMPACT ANALYSES requires the organisation to “analyze changes to the system to determine potential security and privacy impacts prior to change implementation” (lines 7403–7404). SP 800-128 puts the analysis, not the meeting, at the centre: it happens “preferably before they are approved and implemented, but also in the case of emergency/unscheduled changes” (lines 1304–1306). Approval without a preceding impact analysis is a signature on a description.

What the record has to show

CM-3 reads as a specification for that record: document the decisions (c), implement the approved changes (d), “retain records of configuration-controlled changes to the system” for an assigned period (e), monitor and review the activity (f), and give oversight to a named element that convenes at an assigned frequency or under assigned conditions (g). SP 800-128’s sample change request shows the fields behind those duties: who initiated the change, its justification, its urgency as scheduled, urgent or unscheduled, the components to be changed, the expected impact, the back-out plan, and the line “Authorized Signature(s)” (lines 4270–4292).

request   ->  impact analysis  ->  approval   ->  implement   ->  verify
   |              |                   |              |              |
recorded       before the         decision       baseline       changed
on the         approval           documented     updated        behaviour
change                            and retained   (CM-2)         confirmed
                                                              (CM-4(2))

The baseline is the object the record moves. CM-2 requires the current baseline to be reviewed and updated “When system components are installed or upgraded” (line 7143), and SP 800-128 narrates the swap: “As changes are made to baseline configurations, the new baseline becomes the current version”, with the previous one no longer valid but retained for historical purposes (lines 2881–2882).

When the change reaches the authoriser

Board approval is not the last signature. SP 800-37r2 sets the second threshold: “A significant change is defined as a change that is likely to substantively affect the security or privacy posture of a system” (lines 9482–9483). Its examples run from a new or upgraded operating system to modifications to cryptographic modules or services. What elevates a change is its effect, not its size: the organisation sets its own criteria (lines 9519–9524) and may use risk assessment or impact analysis results to decide whether a change triggers an authorization action (lines 9525–9528). SP 800-128 reaches the same point from the change side: where there is high risk or a significant change, “a system reauthorization may be required” (lines 2877–2879).

Emergency changes are legalised afterwards, not exempt

The unscheduled change is where approval usually fails, and the source anticipates it instead of forbidding it. When “time does not allow for following the established configuration change control process, unscheduled changes are still managed and controlled”; the procedures carry instructions for handling them “as well as instructions for handling unauthorized changes that are subsequently discovered”, and both are “reviewed/resolved by the CCB as soon as is practical” (lines 2723–2729). The review comes after the change; the record does not disappear.

Where an approved deviation goes

One hook connects the change record to the exception path. CM-8(6) requires the system component inventory to “include assessed component configurations and any approved deviations to current deployed configurations” (lines 7932–7935), and CM-6 requires deviations from established configuration settings to be identified, documented and approved (lines 7534–7537). An approved deviation is therefore a second record, not a silent edit. The deviation path belongs to the L3 sheet on exceptions, approvals and compensating controls, and the configuration process as a whole to the L3 sheet on configuration management as a control process; this sheet owns the approval act and the record it leaves.

Level and prerequisites

L3 — process coordination: read a change record and decide whether the approval it claims is defensible, and place a change against two thresholds, configuration-controlled and significant. It assumes the L2 sheet on technical standards and operating procedures, and the vocabulary of the baseline and the configuration item.

Where to go next

References

  • NIST — Guide for Security-Focused Configuration Management of Information Systems (SP 800-128) — https://doi.org/10.6028/NIST.SP.800-128 — configuration change control as a process (line 884) and as a sequence of steps (§3.3.2, lines 2638–2700); the baseline configuration definition (lines 867–870); the Configuration Control Board (lines 1163–1179); security impact analysis (§2.3.9, lines 1295–1313); unscheduled and unauthorized changes (lines 2713–2729); record and archive (§3.3.4, lines 2872–2886); the sample change request including its authorised signature line (Appendix E, lines 4264–4295).
  • NIST — Security and Privacy Controls for Information Systems and Organizations (SP 800-53 Rev. 5) — https://doi.org/10.6028/NIST.SP.800-53r5 — CM-3 CONFIGURATION CHANGE CONTROL (heading line 7235, statement lines 7239–7263, discussion lines 7265–7276), CM-4 IMPACT ANALYSES (lines 7401–7404 and enhancement (2) at lines 7442–7445), CM-5 ACCESS RESTRICTIONS FOR CHANGE (lines 7451–7454), CM-2 BASELINE CONFIGURATION (lines 7130–7143), CM-6 CONFIGURATION SETTINGS (lines 7524–7539), CM-8(6) ASSESSED CONFIGURATIONS AND APPROVED DEVIATIONS (lines 7932–7935).
  • NIST — Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy (SP 800-37 Rev. 2) — https://doi.org/10.6028/NIST.SP.800-37r2 — event-driven triggers and significant changes (Appendix F, lines 9455–9533): the definition of a significant change, its examples, the criteria the organisation sets, the use of impact analysis to determine significance, and the statement that most changes are handled through continuous monitoring and ongoing authorization.
  • NIST — The NIST Cybersecurity Framework (CSF) 2.0 (NIST CSWP 29) — https://doi.org/10.6028/NIST.CSWP.29 — ID.RA-07 (lines 905–906): changes and exceptions are managed, assessed for risk impact, recorded and tracked; the ID.IM improvement category (lines 916–927).
Nodrius Field Kit — cover

Get the Nodrius Field Kit

Enter your email and we'll send you the complete Field Kit: eight technical resources in one download.

Your email address is sent to Nodrius and used to deliver the Field Kit to you by email. Marketing messages are separate and optional: the checkbox does not affect your download, and you are only added to our updates list if you tick it. Privacy Policy.

Privacy & cookies

This site does not use cookies, analytics or tracking, and it does not profile you. There is nothing technical to switch off, so Accept and Reject change nothing about how the site works: either choice lets you browse everything normally.

The only difference is what your browser remembers: two entries in local storage — your choice here, so this notice is not shown again, and a marker that the Field Kit offer has already been made — so the offer is presented once and not on every page. They contain no identifier, they are not shared with anyone, and the site sets no cookie for either.

What we do with your data
How your email address is used when you ask for a Resource, how long it is kept and which rights you have — in the Privacy Policy.
What the site stores in your browser
Two entries in local storage — your choice on this notice and whether the Field Kit offer has been shown — and no cookies, no session storage, no third-party content: in the Cookie Policy.