Template library
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

Template fields

Fill in each section with details from your work.

Fictional change
[Add details here]
Fictional closure
[Add details here]

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

  1. 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.
  2. 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.
  3. 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)

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes