Skip to content

Change Management

This document establishes the organization's policy for tracking, reviewing, approving, implementing, and validating changes to the system, and the procedures by which GRC-ITSM executes that policy. It covers the Change Request record and its structured field set, the FedRAMP significant-change taxonomy and the evaluation that assigns it, the change workflow with its Change Request Approvers CAB approval and its notice steps, the Security Impact Analysis, sending Significant Change Notifications and their artifacts, remediation traceability into vulnerability Issues, emergency changes, unauthorized changes and drift, and the machine validation evidence the workflow generates. It implements the FedRAMP Significant Change Notification (SCN) rule family from the FedRAMP Consolidated Rules for 2026 and the Change Management Key Security Indicators (KSI-CMT), with CMMC Level 2 and NIST 800-53 configuration change control lineage.

Quick Summary

No change reaches production outside a Change Request ticket. Every Change Request is classified against the FedRAMP significant-change taxonomy when it is raised, carries a Security Impact Analysis where FedRAMP requires one, and is approved by the Change Request Approvers CAB. The workflow then routes adaptive and transformative changes through a step for each Significant Change Notification they owe, and a Send SCN action on that step sends the notice and moves the change on. An emergency change skips the advance notices and sends a retroactive one. Notices are served through the Trust Center in both human-readable and JSON form. Operating the workflow generates dated KSI and notice validation evidence automatically, but enforcement of the analysis and test plan is human, at approval.

Related documentation

Download the KB article (Markdown)


Framework applicability

Framework What this document satisfies
FedRAMP 20x (all classes) SCN provider rules (SCN-CSO, SCN-RTR, SCN-ADP, SCN-TRF); KSI-CMT-LMC, KSI-CMT-RMV, KSI-CMT-RVP, KSI-CMT-VTD
FedRAMP Rev5 The same SCN provider rules; underlying NIST CM-2, CM-3, CM-4, CM-5, CM-6, CM-8, CM-9, SA-10, with CA-7 touchpoints. At Low, CM-3 is not in the baseline and the Change Request workflow applies as good practice
CMMC Level 2 CM.L2-3.4.3 (track, review, approve or disapprove, log changes), CM.L2-3.4.4 (security impact analysis), CM.L2-3.4.5 (access restrictions for change)

FedRAMP 20x classes differ in validation depth, not in the procedure itself: Class B should evidence each KSI with at least one automated method, Class C must use at least two, and Class D at least four. Class A follows its alternative-framework path and minimally carries KSI-CMT-LMC. The SCN provider rules apply to Classes B, C, and D.


Policy

  • P-1. Every change is a Change Request. No change reaches production outside a Change Request ticket in GRC-ITSM. The ticket is the system of record: change type, justification, impact, risk, plans, approvals, and timestamps live on it, and its audit trail is the change log (KSI-CMT-LMC).
  • P-2. Every potential significant change is evaluated and classified when it is raised. The evaluation determines the significant-change type and the SCN rules that follow from it (SCN-CSO-EVA, MUST). The evaluation is recorded on the Change Request as Change Type, Change Type Explanation, and Justification, and those records are auditable and available to FedRAMP on request (SCN-CSO-MAR, MUST). Change Type and Change Type Explanation are mandatory on Request Approval; a request missing either is refused.
  • P-3. A Security Impact Analysis is mandatory where FedRAMP requires one, and the CAB verifies it. SCN-triggering changes carry a Security Impact Analysis on the Change Request, because a copy of the business or security impact analysis is required information in every Significant Change Notification (SCN-CSO-INF, MUST), with Rev5 CM-4 and CM.L2-3.4.4 lineage on that track. The Change Request Approvers CAB verifies that the Security Impact Analysis and the test plan are present and adequate as part of approving the change. Verification is a human act at approval; no automated control blocks the workflow.
  • P-4. No change is implemented without recorded approval. Approval runs as the native approval process at the Change Approval step, decided by the Change Request Approvers CAB. Rejection returns the Change Request to Change Initiated with the reason recorded. Approval is event-driven per change so notification clocks and change windows are met, and does not wait for a scheduled meeting.
  • P-5. Notification is on the clock and reaches all necessary parties. Adaptive changes are notified within 10 business days after finishing (SCN-ADP-NTF, MUST). Transformative changes are notified on the 30 / 10 / 5 / 5 business-day ladder (SCN-TRF-NIP, SCN-TRF-NFP, SCN-TRF-NAF, SCN-TRF-NAV, each MUST), with service documentation updated within 30 business days after finishing (SCN-TRF-UPD, MUST). Routine recurring changes are exempt and no formal notification is sent for them (SCN-RTR-NNR, SHOULD NOT). All necessary parties always includes FedRAMP and every agency customer using the offering. Each notice is sent from the Change Request with a Send SCN action at the workflow step where it is due.
  • P-6. A certification class change cannot proceed under the SCN rules. A change likely to change the FedRAMP Certification class of the offering requires a new assessment and is out of scope for significant-change handling (SCN-CSO-EVA, MUST). Such changes are raised so the evaluation is on record, and are not implemented under this procedure.
  • P-7. Every notification and audit record exists in both human-readable and JSON form. All Significant Change Notifications and their related audit records are available in human-readable and JSON formats (SCN-CSO-HRM, MUST). The organization generates and keeps both formats for every Change Request, not only for SCN-triggering ones, so the machine-readable trail is complete rather than selective. That breadth is an internal commitment beyond the rule.
  • P-8. Change history stays available. Twelve months of historical Significant Change Notifications remain available with the organization's FedRAMP Certification Data (SCN-CSO-HIS, MUST). All Change Request tickets are retained indefinitely, which satisfies that availability requirement by a wide margin.
  • P-9. Emergencies may move first, and the paperwork follows. During an emergency or incident, a change including a transformative one may execute without following the SCN rules in advance; the organization then follows all relevant procedures, notifies all necessary parties, retroactively provides all SCN materials, and completes an appropriate assessment after the incident (SCN-CSO-EMG). The Emergency field routes an emergency Change Request past the advance-notice steps and to a retroactive notice step; expedited approval, assessment, and post-incident review remain human acts.
  • P-10. Changes land as redeploys, not edits. Changes to machine-based information resources are executed by redeploying version-controlled resources rather than by direct modification wherever reasonable (KSI-CMT-RMV): infrastructure as code, pipelines with enforced review, and immutable redeploys.
  • P-11. Testing and validation run throughout deployment and are automated. Every change carries a test plan and a backout plan, and validation runs through deployment rather than only at its end (KSI-CMT-VTD).
  • P-12. The procedure reviews itself persistently. The effectiveness of these documented change management procedures is reviewed persistently on the cadence in the ODV table, together with the change metrics (KSI-CMT-RVP).

Organization-defined values

Value Setting Default Force
Change Request Approvers CAB membership [CAB membership] Members hold the Approver - Change Requests role N/A
Security and privacy representative on the change control body [Name or role] ISSO (GRC-ITSM default; CM-3(4) leaves the representative organization-defined; 20x lineage via KSI-CMT-RVP) N/A
Approval model and CAB oversight cadence [event-driven approval plus oversight meeting frequency] Event-driven approval per Change Request; CAB meets monthly for oversight N/A
Change record retention [period] Indefinite (GRC-ITSM default) N/A
Historical Significant Change Notification availability 12 months with the FedRAMP Certification Data 12 months (SCN-CSO-HIS) MUST
Notification mechanism [mechanism] Trust Center serving surfaces, documented in the FedRAMP Certification Package (SCN-CSO-NOM) MAY
Adaptive change notification Within 10 business days after finishing 10 business days (SCN-ADP-NTF) MUST
Transformative change, initial plans At least 30 business days before starting 30 business days (SCN-TRF-NIP) MUST
Transformative change, final plans At least 10 business days before starting 10 business days (SCN-TRF-NFP) MUST
Transformative change, after finishing Within 5 business days after finishing 5 business days (SCN-TRF-NAF) MUST
Transformative change, after verification Within 5 business days after completing verification, assessment, or validation 5 business days (SCN-TRF-NAV) MUST
Transformative change, service documentation update Within 30 business days after finishing 30 business days (SCN-TRF-UPD) MUST
Third-party assessor review before transformative changes [when human validation of scope and impact is necessary] Engage an assessor where human validation is necessary, limited to security decisions requiring it (SCN-TRF-TPR) SHOULD
Routine recurring change notification None Exempt from notification (SCN-RTR-NNR) SHOULD NOT
Emergency change approver [ISSO or System Owner] ISSO or System Owner N/A
Retroactive Change Request after an emergency change [1 business day] 1 business day (internal commitment; the rules set no numeric clock) N/A
Post-incident review after an emergency change [48 hours] 48 hours (internal commitment; the rules set no numeric clock) N/A
Change windows [approved windows] Defined per system N/A
Configuration settings source [DoD STIGs, CIS Level 2, or documented custom baseline] STIGs, else CIS Level 2, else custom (CM-6) N/A
Change procedure effectiveness review [cadence] Persistently, reviewed at least quarterly with the change metrics (KSI-CMT-RVP) N/A
CMMC change management values [per contract] Per contract (CM.L2-3.4.3, CM.L2-3.4.4, CM.L2-3.4.5) N/A

The FedRAMP Notices guide describes how the notice checks count these windows.


Roles and responsibilities

  • Anyone may raise a Change Request.
  • Assigned agent (Change Requests). Each Change Request is assigned a tracking owner automatically via the Agent Assignment - Change Requests role. Assignment confers tracking ownership, not approval authority.
  • Change Request Approvers CAB. The Approver - Change Requests role grants membership to the Change Request Approvers CAB, who approve Change Requests. Approval is always by the CAB, never by the assigned agent. The CAB verifies the Security Impact Analysis and the test plan as part of approving the change, and records its decision and rationale on the Change Request.
  • Implementers (system administrators, engineers). Raise Change Requests, implement approved changes inside approved windows, execute test and backout plans, record results, and update affected documentation.
  • Notice sender. Takes each Send SCN action at the step where the notice is due, attaches the business or security impact analysis, adds each approver's title, confirms the recipients and content in the email preview, and presses Send.
  • ISSO and System Owner. Accountability and escalation. Either may give expedited approval for an emergency change. The ISSO oversees the significance evaluation and reviews this document on the cadence in the ODV table; the System Owner gives final approval and authorizes exceptions.

The Change Request record

Every Change Request carries the following structured fields, which together supply the Significant Change Notification required-information set (SCN-CSO-INF):

Field group Fields
Classification Change Type, Change Type Explanation, Emergency (Yes/No), Justification
Assessment Impact, Customer Impact, Risk, Security Impact Analysis, New Risks
Plans Change Plan, Test Plan, Implementation Plan, Backout Plan, Communication Plan
Scheduling Downtime Required, Downtime Duration, change window
Scope Affected assets, the vulnerability Issues the change remediates, and Related Vulnerability (written automatically from the child Issues, by ID and CVE)
Approval and verification Approver (written automatically with the names of the Change Request Approvers CAB members), Verification Completed On
Exercise Is Exercise (ticked on exercise Change Requests)

The record also carries its approval decision and approver identity, the implementation and validation results, before and after states, and the full workflow timeline.


Change classification

Every Change Request carries a Change Type aligned to the FedRAMP significant-change taxonomy. Legacy Standard and Normal classifications map as shown. An emergency is not a change type: it is recorded in the separate Emergency field (see Emergency changes).

Change Type (CR field) Definition Legacy mapping SCN obligation
Routine Recurring Regularly and routinely recurs as part of ongoing operations, vulnerability mitigation, or vulnerability remediation: routine patching, signature updates, capacity scaling, firewall rule updates, like-for-like remediation Standard None. No formal Significant Change Notification is sent (SCN-RTR-NNR, SHOULD NOT)
Adaptive Does not routinely recur and does not introduce substantive potential security risks needing in-depth assessment: OS or container upgrades with breaking changes, like-for-like component or crypto module swaps, multi-week feature deployments Normal Notify all necessary parties within 10 business days after finishing, including a summary of any new risks or vulnerabilities resulting from the change (SCN-ADP-NTF, MUST)
Transformative Introduces substantive potential security risks likely to affect existing risk determinations, which must be assessed in depth: IaaS or critical third-party swap, management-plane paradigm shift, cross-boundary data migration, new AI capability touching federal data differently Normal (major) Notify initial plans at least 30 business days before starting, final plans at least 10 business days before starting, within 5 business days after finishing, and within 5 business days after completing verification (SCN-TRF-NIP, NFP, NAF, NAV, each MUST); update service documentation within 30 business days after finishing (SCN-TRF-UPD, MUST); engage a third-party assessor before starting where human validation is necessary (SCN-TRF-TPR, SHOULD)
Certification Class Change Likely to change the FedRAMP Certification class of the entire offering, for example Class B to Class C n/a Cannot proceed under the SCN rules; requires a new assessment (SCN-CSO-EVA, MUST)
Impact Categorization Legacy. Retained so historical Change Requests keep their original classification. Not used for new changes; classify a class change as Certification Class Change n/a Not used for new changes: cannot proceed under the SCN rules (SCN-CSO-EVA, MUST)
Interim Requirement Executed to adopt a FedRAMP interim requirement on its adoption timeline n/a Per the interim requirement's own terms

Advance FedRAMP approval is not the default for any change type. It applies only where FedRAMP has imposed it as a condition of a formal Corrective Action Plan or other agreement (SCN-FRP-CAP, MAY).


Change Request workflow

The workflow routes each Change Request by its Change Type and its Emergency field, so every significant change passes through a step for each notice it owes. Each Send SCN action sends its notice and moves the Change Request to the next step.

Step Reached when Actions available
Change Initiated The Change Request is raised Request Approval (Change Type and Change Type Explanation mandatory); Cancel Change
Change Approval Approval is requested Approved (routes on Emergency and Change Type); Rejected (returns to Change Initiated)
Initial Plans Due Approved Transformative change, Emergency = No Send SCN: Initial Plans (to Final Plans Due); Proceed as Emergency; Cancel Change
Final Plans Due Initial plans sent Send SCN: Final Plans (to Awaiting Implementation); Proceed as Emergency; Cancel Change
Awaiting Implementation Approved change of any other type, an emergency change, or final plans sent Initiate Change (to Change Review); Reschedule Change; Cancel Change
Change Review Implementation started Complete Change (routes to the after-change notice step)
Completion Notice Due Transformative change finished, Emergency = No Send SCN: Complete (to Verification Notice Due); Proceed as Emergency
Verification Notice Due Transformative change: finishing notice sent (Send SCN: Complete, or Send SCN: Emergency) Send SCN: Verified (requires Verification Completed On; to Review)
Adaptive Notice Due Adaptive change finished, Emergency = No Send SCN: Adaptive (to Review); Proceed as Emergency
Emergency Notice Due Adaptive or Transformative change finished, Emergency = Yes Send SCN: Emergency (to Verification Notice Due for a Transformative change, otherwise to Review)
Review Notices sent, or a change type that owes none Complete Review (note mandatory; closes the Change Request); Close Child Tickets; Proceed as Emergency
Closed Review complete, or the change cancelled Terminal

Routine Recurring, Certification Class Change, Impact Categorization, and Interim Requirement changes go from Change Review to Review with no Send action.

The procedure runs across those steps as follows.

  1. Raise (Change Initiated). The requester opens a Change Request with the field set above, classifies the change per the taxonomy, records the Change Type Explanation and Justification as the significance evaluation (SCN-CSO-EVA, SCN-CSO-MAR), and attaches the Security Impact Analysis where the change is SCN-triggering. Patch-window Change Requests parent the vulnerability Issues they remediate.
  2. Approve (Change Approval). Request Approval routes the change to the Change Request Approvers CAB; it is refused if Change Type or Change Type Explanation is blank. The CAB reviews the classification, the Security Impact Analysis, and the test plan, and approves or rejects. Rejection returns the Change Request to Change Initiated with the reason recorded, and the change does not proceed. Transformative changes are the ones most likely to need a third-party assessor review of scope and impact before starting (SCN-TRF-TPR).
  3. Notify plans (Transformative only). At Initial Plans Due the sender sends the initial plans notice with Send SCN: Initial Plans (SCN-TRF-NIP), and at Final Plans Due the final plans notice with Send SCN: Final Plans (SCN-TRF-NFP).
  4. Schedule (Awaiting Implementation). Approved changes wait here until their window. Initiate Change starts implementation; Reschedule Change moves the window; Cancel Change stops the change with the record intact.
  5. Implement (Change Review). Implementation runs inside the approved window, as a redeploy of version-controlled resources wherever reasonable (KSI-CMT-RMV). Before and after states are captured on the Change Request. A failed change executes its backout plan. Complete Change records the finish, which starts the after-finishing clocks.
  6. Notify completion. A Transformative change goes to Completion Notice Due, where Send SCN: Complete sends the after-finishing notice (SCN-TRF-NAF), then to Verification Notice Due. Once verification, assessment, or validation is complete, the sender fills Verification Completed On, which starts the after-verification clock, and sends Send SCN: Verified (SCN-TRF-NAV). An Adaptive change goes to Adaptive Notice Due, where Send SCN: Adaptive sends its notice (SCN-ADP-NTF).
  7. Review and close (Review). Test and validation results are recorded against the test plan (KSI-CMT-VTD): pipeline gates, post-deploy checks, and re-scan or targeted verification that the change met its objective and that security controls still operate as intended. Close Child Tickets may close the Change Request's children alongside it. Complete Review, with its mandatory note, closes the Change Request.

To stop a change, use Cancel Change, offered on Change Initiated, Initial Plans Due, Final Plans Due, and Awaiting Implementation, before the change is initiated. A cancelled change owes no notices. Do not close a Change Request by changing its status: an Adaptive or Transformative change closed that way without Complete Change records a Fail for each after-change notice it owed.


Significant Change Notification

When a change is Adaptive or Transformative, the organization notifies all necessary parties, which always includes FedRAMP and every agency customer using the offering, on the clocks in the classification table.

Each notification includes at minimum (SCN-CSO-INF): the FedRAMP ID of the service offering, the assessor name if applicable, the related vulnerability if applicable, the significant-change type with an explanation of the categorization, a short description of the change, the reason for the change, a summary of customer impact including changes to services and customer configuration responsibilities, the plan and timeline for the change including verification, assessment, or validation of impacted KSIs or Rev5 controls, a copy of the business or security impact analysis, and the name and title of the approver. Adaptive notifications additionally include a summary of any new risks or vulnerabilities resulting from the change where applicable (SCN-ADP-NTF). Transformative notifications carry embedded content requirements at every step: initial plans include a summary of any likely security impacts or changes in risk (SCN-TRF-NIP); final plans and after-finishing notifications include updates to all previously sent information (SCN-TRF-NFP, SCN-TRF-NAF); and notifications after verification additionally include updates to all previously sent information, that same new-risk summary, and a copy of the security assessment report where applicable (SCN-TRF-NAV). Additional relevant information may be included at the organization's discretion (SCN-CSO-ARI, MAY).

Sending. Each Significant Change Notification is sent from the Change Request with the Send SCN action at the step where it is due. The action opens the matching FedRAMP SCN template in an email preview, filled from the Change Request: Transformative Initial Plans, Transformative Final Plans, Transformative Change Complete, Transformative Verification Complete, Adaptive Change Complete, or Emergency Change (Retroactive). Nothing goes out until the sender presses Send in the preview, and that send moves the Change Request to its next step. No AI or API tool sends a notice. Before pressing Send, the sender:

  • attaches the business or security impact analysis; the template states that it is attached (SCN-CSO-INF);
  • checks the "Approved by" row before sending: it prints each approver as Name, Title from the agent's Job Title, or the name alone where Job Title is blank, and adds any missing title, because the required information includes the name and title of the approver (SCN-CSO-INF);
  • confirms the recipients in the preview.

Notice emails print planned start and planned completion in UTC and label them "(UTC)". On an exercise Change Request (Is Exercise ticked) the email shows an Exercise Status row; the FedRAMP Notices guide covers how exercise notices are addressed and scored.

Artifacts. Human-readable and machine-readable (JSON) artifacts are generated and kept for every Change Request, not only for SCN-triggering ones (SCN-CSO-HRM, exceeded by internal commitment). They are served through the Trust Center on two surfaces:

  • the Significant Changes (Agency) report, one row per notifiable Change Request in the SCN-CSO-INF shape with an Emergency column, in the agency report catalog; exercise Change Requests are excluded; and
  • the Certification Documents section, which serves the FedRAMP-schema JSON artifacts. The Security Decision Record, Certification Overview, and Vulnerability Detail JSONs are published there today, and the Significant Change JSON is planned to be published alongside them.

Internally, the Transformative Change Notice Windows report lists Transformative Change Requests waiting at Initial Plans Due or Final Plans Due whose planned start is close enough that the plans notice is due, and leaves out exercise Change Requests.

The notification mechanism is documented in the FedRAMP Certification Package as part of adopting this policy, and is easily accessible (SCN-CSO-NOM). After a significant change completes, the SSP (Rev5) or the Security Decision Record (20x) is regenerated so published certification data reflects the implemented state.


Remediation traceability

Patch-window Change Requests parent the vulnerability Issues they remediate, so the remediation trail runs from finding to change without a manual join. The Review step's Close Child Tickets action can close those children alongside the Change Request.

A Change Request may close without remediating everything it was raised to address. Unremediated child Issues stay open on their own lifecycle and close on scan evidence that the finding is gone, not on change completion. Vulnerability handling itself follows the Vulnerability Detection, Evaluation, and Response Policy and Procedures.


Emergency changes

Emergency changes, including transformative ones, may execute ahead of a window and without advance notification during an active incident, outage, or exploited vulnerability (SCN-CSO-EMG).

An emergency change is marked with Emergency = Yes on its Change Request. Its Change Type still records the real type of the change (Routine Recurring, Adaptive, Transformative, and so on), so the emergency never hides how significant the change is. An emergency change whose type is Adaptive or Transformative owes the retroactive Significant Change Notification materials (SCN-CSO-EMG). A Routine Recurring emergency change owes no notification (SCN-RTR-NNR). Certification Class Change and Interim Requirement changes keep the obligations in the classification table above. Emergency is set when the Change Request is raised; once the change has started, it can be set only through the Proceed as Emergency action, offered on Initial Plans Due, Final Plans Due, Completion Notice Due, Adaptive Notice Due, and Review. Older Change Requests may still show the retired Emergency change type.

The workflow handles an emergency change this way:

  • Emergency = Yes skips the advance-notice steps. The change goes from approval to Awaiting Implementation without Initial Plans Due or Final Plans Due.
  • A significant emergency change owes a retroactive notice. After Complete Change, an Adaptive or Transformative emergency change goes to Emergency Notice Due, where Send SCN: Emergency sends the notice retroactively. Any other type goes to Review with no Send action.
  • A Transformative emergency change still owes the verification notice. After the emergency notice it goes to Verification Notice Due (SCN-TRF-NAV).
  • The finishing and adaptive notices bind emergency changes. A Send SCN: Emergency taken within the after-finishing or adaptive window satisfies those notices (SCN-TRF-NAF, SCN-ADP-NTF).
  • The assessment is the Review note. On an emergency change, the Complete Review note opens with Post-emergency assessment (SCN-CSO-EMG):.

  • The implementer obtains expedited approval from the ISSO or the System Owner.

  • The implementer files a retroactive Change Request within [1 business day] carrying the full field set, including the Security Impact Analysis performed as rapidly as the incident allowed.
  • For an Adaptive or Transformative emergency change, the organization provides all retroactive Significant Change Notification materials to all necessary parties with Send SCN: Emergency. Every emergency change gets an appropriate assessment, recorded as the Complete Review note on the Change Request.
  • A post-incident review completes within [48 hours], recording lessons learned and any permanent-fix plan on the Change Request.

The 1-business-day and 48-hour values are organization-defined internal commitments. The SCN rules set no numeric clock for either.


Unauthorized changes and drift

The approved infrastructure-as-code baseline is the reference state. Drift from it is treated as an unauthorized change: detected by automated configuration evaluation, investigated, and either reverted or regularized through a retroactive Change Request. Logical access to make production changes is restricted and enforced with automated audit records; physical access restrictions are inherited from the infrastructure provider (CM-5, CM.L2-3.4.5).


Documentation and certification data changes

Documentation (policies, procedures, plans, diagrams, this article) is version controlled with review and approval before merge, and the change history is the audit trail. Documentation changes that affect the FedRAMP Certification Package or SSP content run through the same significance evaluation as technical changes. After transformative changes, service documentation such as user guides and marketplace listing information is updated within 30 business days after finishing (SCN-TRF-UPD). Every new Change Request carries a Publish updated service documentation to-do, which records that update. Technical Change Requests identify the documentation they affect, and the documentation change references the Change Request.


Recurring reviews

Review Cadence Source
Privileges to change production At least quarterly CM-5(5)
Component inventory At least monthly, and on change CM-8
Baseline configuration At least annually and on significant change CM-2
Configuration compliance scans At least monthly CA-7 / CM-6
Effectiveness of these change procedures Persistently, reviewed at least quarterly with the change metrics KSI-CMT-RVP
Change management audit (sampled Change Requests, Security Impact Analysis completion, decision records, implementation-matches-approval) Annually CM-3; CA-7

Each of these runs as a recurring compliance task on the cadence parent for its interval, under the task program described in the Continuous Monitoring and Reporting Policy and Procedures. The tasks and where they sit:

Task Cadence parent Discharges
CAB oversight meeting Monthly The oversight half of the approval model; event-driven approval per Change Request is separate and does not wait for it
Configuration compliance scan review Monthly Configuration compliance scans (CA-7, CM-6)
Change procedure effectiveness review Quarterly Effectiveness of these change procedures, reviewed with the change metrics (KSI-CMT-RVP)
Change management audit Annual The sampled audit above (CM-3, CA-7)

Three reviews in the table are executed by the continuous monitoring task program rather than by this procedure, and appear here for traceability only: privileges to change production is the quarterly developer and integrator privilege review, component inventory is the monthly inventory and scan data review, and baseline configuration is the annual baseline configuration review. The change metrics that the quarterly effectiveness review reads are the ones listed under Records, retention, and metrics below.


Automated validation evidence

Operating this process produces machine validation evidence automatically. A deployed event runbook fires when a Change Request is logged and on every subsequent ticket update. For each Change Management KSI carried on the Change Request it ensures a per-KSI Validation record exists under that KSI's validation parent, writes one dated validation run, and sets the record's status to Satisfied or Not Satisfied.

Each validation run records the validation method as Automated, the validation identifier CR-WORKFLOW, the evidence type as an audit record, the timestamp, and a note naming the source Change Request number, its category, its current status, and whether the Security Impact Analysis and Test Plan fields carry content.

The pass and fail conditions as deployed:

KSI Fails when Notes
KSI-CMT-LMC (Logging Changes) Never The Change Request record is itself the log, so any Change Request satisfies it
KSI-CMT-VTD (Validating Throughout Deployment) The Change Request has reached an implemented-terminal status and either the Test Plan or the Security Impact Analysis field is blank
KSI-CMT-RVP (Reviewing Change Procedures) The Change Request has reached an implemented-terminal status and the Security Impact Analysis field is blank
KSI-SVC-EIS, KSI-SVC-ACM, KSI-CNA-DFP Same condition as KSI-CMT-RVP Written only when the Change Request carries these KSIs

Every other state passes, including rejection: a rejected Change Request evidences that the review procedure worked.

This runbook generates evidence. It does not enforce anything. The workflow itself refuses Request Approval without Change Type and Change Type Explanation, Complete Review without a note, and Send SCN: Verified without Verification Completed On. No automated control blocks approval, implementation, or closure of a Change Request whose Security Impact Analysis or test plan is missing. Enforcement is human: the Change Request Approvers CAB verifies both as a condition of approval (P-3). A missing artifact therefore surfaces as failed validation evidence after the fact, not as a blocked workflow.

Separate notice checks score the Significant Change Notifications themselves, on Classes B, C, and D, when a Send SCN action is taken and when the Change Request closes: the evaluation (SCN-CSO-EVA), the required information (SCN-CSO-INF), each transformative notice (SCN-TRF-NIP, SCN-TRF-NFP, SCN-TRF-NAF, SCN-TRF-NAV), the adaptive notice (SCN-ADP-NTF), the documentation update (SCN-TRF-UPD), the emergency notice and assessment (SCN-CSO-EMG), and the FedRAMP ID on each notice (CDS-CSO-FID). A daily sweep writes a Fail for an after-finishing, after-verification, adaptive, or documentation-update obligation still owed past its window. An Adaptive or Transformative change closed by status without Complete Change records a Fail for each after-change notice it owed; a cancelled change owes nothing. The FedRAMP Notices guide covers the windows, the checks, and the sweep.

KSI-CMT-RMV is evidenced separately, by the pipeline and drift-detection records showing changes landing as version-controlled redeploys. Validation results accumulate as append-only pass and fail history and roll up to the KSI reporting used for continuous monitoring and certification data sharing.


Records, retention, and metrics

The Change Request audit trail retains, per change: identifier, requester and timestamps, description and justification, change type and significance evaluation, affected assets, Security Impact Analysis, approval decision and rationale, implementation and validation results, before and after states, and any backout. All Change Request tickets are retained indefinitely. Significant Change Notification records additionally follow the 12-month availability rule alongside the FedRAMP Certification Data (SCN-CSO-HIS).

Monthly metrics: changes by type, success rate versus backouts, approval latency, emergency-change count and justification, Significant Change Notifications sent by type with clock adherence, validation pass rate, and unauthorized-change (drift) findings.


Authority, review, and revision

Issued under the authority of the System Owner and binding on all personnel with access to the system. Exceptions require written System Owner approval and are documented.

The ISSO reviews this document for effectiveness persistently on the cadence in the ODV table, and when frameworks, the system, or lessons learned warrant; the System Owner gives final approval. This review, together with the change metrics, evidences persistent review of documented change management procedure effectiveness (KSI-CMT-RVP). Because that cadence is quarterly rather than annual, it is tracked by the quarterly change procedure effectiveness review task rather than by the annual plan and policy review task that carries the other procedure documents.


FedRAMP coverage

SCN provider rules: Evaluate Changes (MUST), Maintain Audit Records (MUST), Required Information (MUST), Historical Notifications (MUST), Human and Machine-Readable Notifications (MUST), Notification Mechanisms (MAY), Additional Relevant Information (MAY), Emergency Changes (MAY, with embedded MUSTs) (SCN-CSO); No Notification Requirements for routine recurring changes (SCN-RTR-NNR, SHOULD NOT); Notification Requirements for adaptive changes (SCN-ADP-NTF, MUST); Notification of Initial Plans, Notification of Final Plans, Notification After Finishing, Notification After Verification, Update Documentation (each MUST) and Third-Party Review (SHOULD) for transformative changes (SCN-TRF). The FedRAMP-side rule that can impose advance approval is SCN-FRP-CAP (MAY). KSI-CMT: Logging Changes, Redeploying vs Modifying, Reviewing Change Procedures, Validating Throughout Deployment. Adjacent KSIs the Change Request workflow also evidences when carried on the record: KSI-SVC-EIS, KSI-SVC-ACM, KSI-CNA-DFP. Underlying NIST: CM-2, CM-3, CM-4, CM-5, CM-6, CM-8, CM-9, SA-10, CA-7. CMMC: CM.L2-3.4.3, CM.L2-3.4.4, CM.L2-3.4.5.