# Versioned baseline crosswalk, applicability rationale and policy-to-owner register

CISA SCuBA cloud security implementation | Worked example with fictional data

Step: Freeze the right baseline and requirement set
Owner: Cloud security architect + M365 or Google product owner + Licensing lead + Compliance counsel
When: After scope approval and before defining assessment success

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

## Example

### Fictional policy row
MS.EXO.4.1v2 | Exchange Online | SHALL under the current checked directive list: yes | automated check: yes | license dependency: confirm with tenant contract | owner: Messaging Engineering | actual: fail | intended: enable approved external forwarding block | evidence: change CHG-4821 | retest: pending

### Fictional not-applicable decision
The policy checks a product not licensed or provisioned in this tenant. The owner links the service inventory and license record, confirms no data or configuration exists, asks the compliance lead to approve the decision and schedules a recheck after procurement changes.

## 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.

Official reference: CISA BOD 25-01 required configurations
https://www.cisa.gov/resources-tools/services/bod-25-01-implementing-secure-practices-cloud-services-required-configurations

Use the current rules and any prescribed forms for your engagement.
