Change Request¶
Quick Summary
Formalizes any proposed change to systems within the authorization boundary, from routine patching to emergency security fixes. Change requests capture the implementation plan, risk assessment, and rollback strategy, and require approval by the Change Request Approvers CAB before execution.
The Change Request ticket type is the formal mechanism for documenting and approving modifications to systems, configurations, and infrastructure within the authorization boundary. Every change, whether it's a routine patch cycle, a configuration update, or an emergency response to a zero-day, flows through this ticket type to maintain the audit trail required by FedRAMP CM-3 and CMMC CM.L2-3.4.3.
Change Types¶
Each change request is classified by type, which determines the review rigor, approval routing, and which notices the change owes. Change Type and Change Type Explanation are mandatory at Request Approval, and a request missing either is refused.
| Change Type | Description | Compliance Context |
|---|---|---|
| Routine Recurring | Pre-approved, regularly scheduled changes such as patching cycles or certificate renewals | Supports FedRAMP CM-3 and CMMC CM.L2-3.4.3 by establishing predictable, documented change patterns |
| Adaptive | Changes in response to environmental shifts: vendor updates, dependency upgrades, or infrastructure adjustments | Aligns with FedRAMP CM-4 (impact analysis), requiring assessment of how external changes affect security posture |
| Transformative | Significant architectural or functional changes such as new service deployments, major upgrades, or boundary modifications | May constitute a FedRAMP Significant Change requiring notification and potentially reassessment |
| Certification Class Change | Changes likely to change the FedRAMP Certification class of the offering (for example Class B to Class C) | Cannot proceed under the significant-change notification rules; requires a new assessment |
| Impact Categorization | Legacy. Retained so historical change requests keep their original classification; not used for new changes | Classify a class change as a Certification Class Change instead |
| Interim Requirement | Changes driven by interim compliance directives, binding operational directives (BODs), or emergency security guidance | Supports timely response to CISA BODs and FedRAMP PMO directives that require action within defined timeframes |
Emergency is a field, not a type
Emergency is a Yes/No field on the change request. Any change type can be an emergency. Account actions such as user access are not change requests; they use the User Access Request ticket type.
Workflow¶
The steps a change passes through depend on its type.
| Change type | Steps after approval |
|---|---|
| Transformative | Initial Plans Due, Final Plans Due, Awaiting Implementation, implementation, Completion Notice Due, Verification Notice Due, Review |
| Adaptive | Awaiting Implementation, implementation, Adaptive Notice Due, Review |
| All other types | Awaiting Implementation, implementation, Review, with no notice to send |
Every change starts at Change Initiated and passes through Request Approval, Change Approval, and Approved. At each notice step, a Send SCN action opens a templated email in preview. Sending moves the ticket to the next step. Verification Notice Due requires Verification Completed On before you can send. The last step is Review, where you click Complete Review and add a mandatory note.
- Cancel Change is offered only before the change is initiated. Reschedule Change is offered on Awaiting Implementation.
- Closing a Transformative or Adaptive change by status, without Complete Change, Fails the notices it owed. Use Cancel Change instead. A cancelled change owes nothing.
- Every new change request carries a Publish updated service documentation to-do.
- Link vulnerability Issues to the change as child tickets so they appear on the notices.
Emergency changes¶
Set Emergency to Yes to skip the advance-notice steps. After the change completes, a significant emergency (Adaptive or Transformative) goes to Emergency Notice Due, where Send SCN: Emergency sends the notice retroactively. A Transformative emergency still owes the verification notice. If the emergency becomes clear after planning starts, click Proceed as Emergency to set the field late. The Complete Review note for an emergency must open with "Post-emergency assessment (SCN-CSO-EMG):".
Sending a notice¶
Before pressing Send, attach the business or security impact analysis to the email, because the template states that it is attached. Check the "Approved by" row: it prints each approver as Name, Title from the agent's Job Title, or the name alone where Job Title is blank. Add any missing title before you press Send, and keep Job Title filled on approver agents. Notice emails print planned dates in UTC and label them "(UTC)". See FedRAMP Notices for the windows, checks, and daily sweep that score each notice.
Approval Workflow¶
Change requests are approved by the Change Request Approvers CAB -- the named approval board for changes, with role-based membership. When users in your organization hold the Change Approver role, an optional second, organizational stage applies: after the CAB approves, the request is forwarded to that approver for final sign-off. Emergency changes skip the advance-notice steps but still require full documentation after the fact.
Approval processes are highly customizable to suit your organization's needs. See the Approval Processes admin guide for configuration details.
Scope of Documentation¶
The change request form captures the full lifecycle of the proposed change:
- Justification - why the change is necessary, tied to compliance requirements, security findings, or operational needs
- Risk assessment - impact analysis aligned with FedRAMP CM-4
- Implementation plan - step-by-step execution including sequencing and dependencies
- Test plan - how the change will be validated after implementation
- Backout / rollback plan - steps to reverse the change if issues arise
- Communication plan - stakeholder notification before, during, and after
- Affected assets - systems and components impacted, selected from the asset inventory
- Verification Completed On - the date verification finished, required to send the verification notice
- Emergency - Yes or No
- Is Exercise - marks a practice change that stays out of the Trust Center (Agency) reports
- Approver - written automatically from the holders of the agent role Approver - Change Requests (the Change Request Approvers CAB), each as Name, Title
- Related Vulnerability - filled from linked child vulnerability Issues
- New Risks - risks the change introduces
See the Change Requests end-user guide for details on submitting change requests.
Related documentation¶
- Change Execution playbook -- how to drive a change through the workflow
- Change Management policy -- the policy and procedure for changes
- Change Management area -- the change management working area