# Checklist: meeting CISA BOD 25-01 for Microsoft 365 and Google Workspace tenants

Thirteen steps for federal civilian agencies under Binding Operational Directive 25-01: scoping tenants, reporting the inventory, running ScubaGear or ScubaGoggles, applying the mandatory SCuBA policies by the stated dates, recording deviations, and checking new tenants before authorization.

Checklist · Government · Platforms & Architecture. Published November 14, 2026. Last reviewed November 14, 2026.

## The directive and its dates

CISA issued Binding Operational Directive 25-01, Implementing Secure Practices for Cloud Services, on December 17, 2024 [1]. It requires Federal Civilian Executive Branch agencies to implement the mandatory policies in CISA’s Secure Cloud Business Applications (SCuBA) Secure Configuration Baselines, run CISA’s assessment tools, report results and fix deviations. It does not apply to national security systems or certain Defense Department and Intelligence Community systems [1]. The directive started with Microsoft 365; CISA’s implementation guidance, updated July 27, 2026, says Microsoft 365 and Google Workspace are the only finalized baselines and sets separate Google Workspace dates [2].

One date differs between CISA’s pages as checked on November 14, 2026: the guidance gives December 31, 2026 for implementing the mandatory Google Workspace policies, while the Required Configurations page lists 12/01/2026 as the due date for each Google Workspace policy [2] [3]. The steps show both.

## Reading the steps

The owner under each step is a typical role; the directive assigns actions to agencies, not to named roles, except where a step says it names one. Where a step is our suggestion rather than a requirement, it says so.

Moraph’s teams help organizations with work like this. [See our solutions](https://www.moraph.com/solutions).

## The checklist

1. **Decide which tenants are in scope: production or operational Microsoft 365 and Google Workspace tenants that operate in or as federal information systems.** (Agency CISO with system owners) The directive applies to production or operational cloud tenants with a finalized SCuBA baseline [1]. The guidance adds that test and development tenants are out of scope, that tenants operated by contractors for official business count, that only SaaS is covered, and that Azure subscriptions not using Microsoft 365 services are out of scope [2].
2. **Agree the reporting route with the department-level point of contact and get CyberScope access in place.** (Component CISO) The guidance says sub-components should coordinate with their top-level department before reporting, that manual CyberScope reporting is usually submitted by department-level contacts, and that CyberScope accounts need their approval [2].
3. **Report the tenant inventory: tenant name and system-owning agency or component for each tenant.** (Cloud platform owner) The directive set February 21, 2025 for the first inventory [1]. The guidance asks for the Microsoft 365 tenant ID and fully qualified domain name, and sets November 2, 2026 for the Google Workspace inventory, with the customer ID and fully qualified domain name [2]. As of November 14, 2026, that Google Workspace date has passed.
4. **Update the inventory every year by the end of the first quarter of the fiscal year, and when tenants change.** (Cloud platform owner) The directive requires an annual update in the first quarter [1]; the guidance says by the end of the first quarter of each fiscal year and encourages immediate updates when tenants change [2].
5. **Choose one of the three reporting methods: manual quarterly upload to CyberScope, CISA-hosted ScubaConnect, or an agency-hosted ScubaConnect integrated with CDM.** (Agency CISO) The directive allows automated integration with CISA’s continuous monitoring or quarterly manual reporting in a machine-readable format [1]; the guidance describes the three options [2].
6. **Deploy the assessment tool for every in-scope tenant and start continuous reporting: ScubaGear for Microsoft 365, ScubaGoggles for Google Workspace.** (Cloud security engineer) The directive set April 25, 2025 for Microsoft 365 [1]. The guidance sets December 1, 2026 for Google Workspace and says to set the agency and sub-component names in the tool’s configuration file [2].
7. **Implement every mandatory (“shall”) policy on the Required Configurations page.** (Cloud platform owner) The directive set June 20, 2025 for the Microsoft 365 policies [1]. For Google Workspace, the guidance gives December 31, 2026 [2], while the Required Configurations page lists 12/01/2026 for each Google Workspace policy and “End of each fiscal quarter” for each Microsoft 365 policy [3]. Planning to the earlier Google Workspace date and confirming with CISA is our suggestion. For contacting CISA, the directive gives CyberDirectives@mail.cisa.dhs.gov [1]; CISA’s implementation guidance gives CyberDirectives@cisa.dhs.gov [2].
8. **Treat the Required Configurations page as the list of record, and check its date-added column for changed policies.** (Cloud security engineer) The guidance says the page is the authoritative list of finalized baselines and mandatory policies [2]. As checked, it lists, for example, blocking legacy authentication, phishing-resistant MFA for all users, and disabling SMS, voice call and email one-time passcodes, the last shown as added or modified in February 2026 [3].
9. **Apply future changes to mandatory policies on the timelines CISA sets, and subscribe to CISA’s BOD 25-01 updates.** (Cloud security engineer) The directive requires agencies to implement future updates on the timelines on the Required Configurations page, and commits CISA to email agencies about changes [1]. The guidance explains how to subscribe to the BOD 25-01 topic on GovDelivery [2].
10. **Record any deviation the authorizing official accepts, with its rationale, in the tool’s configuration file so it shows as omitted in the reported results.** (Authorizing official, named in the directive, with the ISSO) The directive lets agency authorizing officials accept risk for deviations and requires agencies to identify and explain them in the tool output reported to CISA [1]. The guidance says omissions must be approved within the organization’s risk management process and can be time-bound [2].
11. **Track each failed policy in the action plan file the tool produces, fix it, rerun the tool and resubmit.** (Cloud security engineer) The guidance describes the CSV action plan template for non-compliant policies, akin to a plan of action and milestones, and the rerun and resubmission steps [2].
12. **For any new tenant, apply the baselines and start continuous monitoring before granting an Authorization to Operate.** (Authorizing official with the system owner) The directive requires this [1]. The guidance says to list the tenant with the ATO field set to No, then change it to Yes once the ATO is granted [2].
13. **Decide which recommended (“should”) policies to adopt, and, for state, local and other non-federal tenants, which baselines to use voluntarily.** (CISO) The “should” policies are left to agency discretion [1], and the guidance says CISA strongly advises implementing them to the greatest extent possible [2]. The Required Configurations page says CISA strongly recommends all stakeholders implement the policies and use the assessment tools, although the directive binds only Federal Civilian Executive Branch agencies [3].

## Sources

1. Cybersecurity and Infrastructure Security Agency. BOD 25-01: Implementing Secure Practices for Cloud Services (December 17, 2024; checked November 14, 2026). <https://www.cisa.gov/news-events/directives/bod-25-01-implementing-secure-practices-cloud-services> Checked November 14, 2026.
2. Cybersecurity and Infrastructure Security Agency. BOD 25-01: Implementation Guidance for Implementing Secure Practices for Cloud Services (updated July 27, 2026; checked November 14, 2026). <https://www.cisa.gov/news-events/directives/bod-25-01-implementation-guidance-implementing-secure-practices-cloud-services> Checked November 14, 2026.
3. Cybersecurity and Infrastructure Security Agency. BOD 25-01: Implementing Secure Practices for Cloud Services Required Configurations (checked November 14, 2026). <https://www.cisa.gov/resources-tools/services/bod-25-01-implementing-secure-practices-cloud-services-required-configurations> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-cisa-bod-25-01-scuba-saas-secure-configuration>
Publisher: Moraph Insights
