COPRSETR WORKSHEET
Approved change tickets, user-impact and rollback plan, exception approvals and before/after retest evidence
CISA SCuBA cloud security implementation · Step 5 · Implement changes through a tested change and exception process- Who prepares it
- Product owner + Change advisory board + Identity or messaging admins + Privacy + User support + Risk owner
- When to prepare it
- Use approved maintenance windows; start with a pilot; track every deviation until retest
Worked example
This example uses fictional details. Use the same fields with evidence from your work.
- Fictional change
- CHG-4821 | block auto-forwarding to external addresses | owner Messaging Engineering | pilot: 12 users across 3 business units | support check: CRM notification workflow remains functional | rollback: restore approved connector if named business critical flow breaks | approvals: CAB and data owner
- Fictional closure
- The follow-up report shows the policy now passes, but the reviewer also checks the Exchange setting, samples the pilot users, verifies the change audit event and tests a safe alert. The evidence set records the policy version and an independent approver.
Gather first
- Prior assessment
- Target policy
- Product configuration guide
- License and user-impact analysis
- Change calendar
- Test account
- Support and rollback procedures
How to prepare it
- For each change state the current value and tenant scope, target value, reason, dependent services, user groups, license requirement, expected security result, outage risk, owner, approver and support message. Link the exact baseline policy and check the current vendor configuration instructions.
- Test the setting on a restricted pilot group or non-production tenant where available. Preserve pre-change and post-change exports, representative user journeys, alert tests, admin audit events and rollback trigger. Expand deployment in controlled waves with a service-health watch.
- Retest with the same versioned assessment method and independently inspect the setting in the administrator interface or API. A policy exception needs the permitted approving authority, business reason, scope, risk, compensating control, expiry or review date and monitoring owner. Record unresolved results and reopen a change if the retest fails.
Review
Closure is based on an effective setting, a controlled rollout and a successful retest, not an administrator assertion or a closed ticket.
Handoff
Notify the SOC of meaningful changes and test that the expected audit and alert events remain available after the change.
Use the issuer’s current instructions and any required forms when you submit.
CISA secure configuration baseline and BOD requirements (opens in a new tab)