CISA Binding Operational Directive 25-01 on secure cloud configurations, explained
BOD 25-01 requires federal civilian agencies to inventory in-scope cloud tenants, run CISA’s SCuBA assessment tools, report the results and implement every mandatory SCuBA policy, first for Microsoft 365 and now for Google Workspace.
What a binding operational directive is
A binding operational directive is a compulsory direction to federal executive branch departments and agencies to safeguard federal information and information systems. Section 3553(b)(2) of title 44 authorizes the Secretary of Homeland Security to develop and oversee them, and agencies are required to comply. They do not apply to statutorily defined national security systems or to certain systems operated by the Department of Defense or the intelligence community [1].
CISA issued BOD 25-01 on December 17, 2024, citing incidents in which improperly configured cloud security controls led to actual compromises. It builds on CISA’s Secure Cloud Business Applications (SCuBA) project, which produced Secure Configuration Baselines and automated tools to assess tenants against them. The directive says it complements FedRAMP, NIST guidance and the TIC 3.0 Cloud Use Case [1].
Which tenants are in scope
The directive applies to all production or operational cloud tenants, operating in or as federal information systems, that have a finalized SCuBA baseline published by CISA. When new baselines are issued, those products come into scope; a baseline not updated within one year falls out of scope [1]. CISA’s implementation guidance clarifies each part [2]:
- a production or operational tenant is one used to conduct official government business, whether run by the government or a contractor; a tenant used mainly to test configuration changes or software before deployment elsewhere is not;
- a tenant must be part of an information system, as defined in 44 U.S.C. 3502(8), owned or operated by or for an agency;
- only Software as a Service is in scope, so Platform and Infrastructure as a Service are out, including Azure subscriptions that do not use Microsoft 365 services; and
- Microsoft 365 was in scope at issuance, and Google Workspace entered scope in the third quarter of fiscal year 2026. CISA says these are the only finalized baselines so far.
Only policies marked as SHALL actions in the baselines are mandatory. SHOULD policies are left to agency discretion, although CISA strongly advises implementing them where possible [1] [2].
The four requirements
For all in-scope tenants, agencies must [1]:
- Identify tenants. Report each tenant’s name and owning agency or component by Friday, February 21, 2025, and update the inventory in the first quarter annually. The guidance says by the end of the first quarter of each fiscal year [2].
- Deploy the assessment tools. Deploy all SCuBA assessment tools by Friday, April 25, 2025, and begin continuous reporting, either by feeding results into CISA’s continuous monitoring solution or by reporting results manually each quarter in a CISA-approved, machine-readable format.
- Implement mandatory policies. Implement all mandatory policies in effect at issuance by Friday, June 20, 2025, and implement later updates on the timelines set on CISA’s Required Configurations page.
- Cover new tenants. Implement all mandatory baselines and begin continuous monitoring for a new tenant before granting it an Authorization to Operate.
An agency’s Authorizing Official may accept risk for deviations from mandatory policies to account for operational needs. The agency must identify and explain each deviation in the assessment tool output it reports to CISA [1].
The guidance offers three reporting routes: manual submission in CyberScope, automated reporting through CISA’s hosted ScubaConnect tool, or an agency-hosted, semi-automated model that integrates with Continuous Diagnostics and Mitigation [2]. The assessment tool for Microsoft 365 is ScubaGear, and for Google Workspace it is ScubaGoggles [2].
Google Workspace dates, and one to confirm
The implementation guidance, updated July 27, 2026, sets Google Workspace dates for the same requirements: the tenant inventory by Monday, November 2, 2026; deployment of the tools, or onboarding to ScubaConnect, by Tuesday, December 1, 2026; and implementation of the mandatory policies by Thursday, December 31, 2026 [2].
The Required Configurations page lists a due date of 12/01/2026 against each Google Workspace policy [3]. As checked on November 14, 2026, the two CISA pages therefore show different dates for implementing Google Workspace policies. The directive names CyberDirectives@mail.cisa.dhs.gov as the contact for assistance [1].
The required configurations keep changing
The directive makes CISA responsible for maintaining the list of in-scope policies, emailing agencies about changes, and supporting agencies with tools and reporting. Within one year of issuance, CISA was to report on agency progress to the Secretary of Homeland Security, the Director of OMB and the National Cyber Director [1].
The Required Configurations page lists each mandatory policy with its identifier, the required action, the month it was added or modified, and a due date. Dates below are from that column. For Microsoft 365 policies, the due date shown is the end of each fiscal quarter [3]. Policies on the page as checked include [3]:
- legacy authentication blocked, and phishing-resistant MFA enforced for all users and required for highly privileged roles;
- SMS, voice call and email one-time passcode methods disabled (dated February 2026);
- a DMARC policy of p=reject published for every second-level domain, and automatic forwarding to external domains disabled;
- risky AI agents blocked (dated March 2026), and external sharing restricted to approved external domains or users in approved security groups (dated September 2026); and
- for Google Workspace, phishing-resistant MFA for all users, no SMS or voice as an MFA method, and passwords of at least 12 characters.
In our view, the rolling dates are the operational point. A configuration that passed the last scan can fall out of compliance when a policy is added or revised, so an agency needs someone who reads CISA’s update notices and a change process that can apply new policies before the next quarterly due date.
Outside the federal civilian government
The directive binds only Federal Civilian Executive Branch agencies. CISA says on the Required Configurations page that it strongly recommends all stakeholders implement the policies and use the SCuBA assessment tool [3]. For organizations outside the Federal Civilian Executive Branch, such as state and local governments, the directive makes it a recommendation, not a requirement. A tenant a contractor runs for an agency can still be in scope [2].
This explainer describes the directive; it is not legal advice, and agencies should confirm requirements and dates with CISA.
Moraph’s teams help organizations with work like this. See our solutions.
Spotted an error? Tell us and we will check it and correct the explainer where needed.