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.
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.
The checklist
Tick the steps as you go. The ticks are kept in this browser only; nothing is sent to us.
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].
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].
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.
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].
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].
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].
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].
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].
Spotted an error? Tell us and we will check it and correct the checklist where needed.