COPRSETR WORKSHEET
Versioned baseline crosswalk, applicability rationale and policy-to-owner register
CISA SCuBA cloud security implementation · Step 2 · Freeze the right baseline and requirement set- Who prepares it
- Cloud security architect + M365 or Google product owner + Licensing lead + Compliance counsel
- When to prepare it
- After scope approval and before defining assessment success
Template fields
Fill in each section with details from your work.
- Fictional policy row
- [Add details here]
- Fictional not-applicable decision
- [Add details here]
Gather first
- Current CISA baseline files
- BOD required configurations
- Tenant edition and license matrix
- Service configuration export
- Prior exceptions
- Product-owner list
How to prepare it
- Freeze the CISA retrieval date, baseline release, BOD list version and tool release. Save the original files in the controlled evidence repository and give each import a stable hash or repository revision.
- Create one row per policy ID. Capture exact version, product, policy text, SHALL or SHOULD indicator, automated or manual method, required configuration, applicable tenant environments, license dependency, current setting, intended setting and test source.
- Record applicability with a reason and approver. Map each SHALL policy to an accountable owner, change dependency, proof of implementation, compensating control if allowed, and a retest. Reconcile mandatory-policy totals with the live CISA required-configurations source before reporting.
Review
The file distinguishes mandatory from recommended policies, errors and not-applicable rows. Baseline and tool versions remain visible when results are compared across runs.
Handoff
Send the approved crosswalk to tenant administrators, privacy, procurement and the assessment owner; review it whenever CISA changes a baseline or a service is added.
Use the issuer’s current instructions and any required forms when you submit.
CISA BOD 25-01 required configurations (opens in a new tab)