Microsoft Exchange Online - SCuBA 1.6.0 Checklist Details (Checklist Revisions)
Supporting Resources:
-
Download Prose - BOD 25-01: Implementation Guidance for Implementing Secure Practices for Cloud Services
- Cybersecurity and Infrastructure Security Agency (CISA)
-
Download Prose - Microsoft Exchange Online
- Cybersecurity and Infrastructure Security Agency (CISA)
-
Download Machine-Readable Format - Microsoft Exchange Online - GitHub Markdown
- Cybersecurity and Infrastructure Security Agency (CISA)
Target:
Target | CPE Name |
---|---|
Microsoft Exchange Online | cpe:/a:microsoft:exchange_online:- (View CVEs) |
Checklist Highlights
- Checklist Name:
- Microsoft Exchange Online - SCuBA
- Checklist ID:
- 1088
- Version:
- 1.6.0
- Type:
- Compliance
- Review Status:
- Final
- Authority:
- Governmental Authority: Cybersecurity and Infrastructure Security Agency (CISA)
- Original Publication Date:
- 02/02/2024
Checklist Summary:
Microsoft 365 (M365) Exchange Online is a cloud-based messaging platform that gives users easy access to their email and supports organizational meetings, contacts, and calendars. This Secure Configuration Baseline (SCB) provides specific policies to strengthen Exchange Online security. Many admin controls for Exchange Online are found in the Exchange admin center. However, several of the security features for Exchange Online are shared between Microsoft products and are configured in either the Microsoft 365 Defender portal or Microsoft Purview compliance portal. Generally speaking, the use of Microsoft Defender is not strictly required for this baseline. When noted, alternative products may be used in lieu of Defender, on the condition that they fulfill these required baseline settings.
Checklist Role:
- Application Server
- Business Productivity Application
- Client / Server
- Enterprise Email Server
- Enterprise Mail Server
- Web Application Server
Known Issues:
Not Provided
Target Audience:
The CISA SCuBA SCBs for M365 help secure federal information assets stored within M365 cloud business application environments through consistent, effective, and manageable security configurations. CISA created baselines tailored to the federal government’s threats and risk tolerance with the knowledge that every organization has different threat models and risk tolerance. Non-governmental organizations may also find value in applying these baselines to reduce risks.
Target Operational Environment:
- Managed
- Standalone
Testing Information:
Not Provided
Regulatory Compliance:
A Binding Operational Directive is a compulsory direction to federal, executive branch, departments and agencies for purposes of safeguarding federal information and information systems. 44 U.S.C. § 3552(b)(1). Section 3553(b)(2) of title 44, U.S. Code, authorizes the Secretary of the Department of Homeland Security (DHS) to develop and oversee the implementation of binding operational directives. Federal agencies are required to comply with these directives. 44 U.S.C. § 3554(a)(1)(B)(ii). These directives do not apply to statutorily defined “national security systems” or to certain systems operated by the Department of Defense or the Intelligence Community. 44 U.S.C. §?3553(b), (d), (e)(2), (e)(3). This directive refers to the systems to which it applies as “Federal Civilian Executive Branch” systems, and to agencies operating those systems as “Federal Civilian Executive Branch” agencies. BOD 25-01: Implementing Secure Practices for Cloud Services
Comments/Warnings/Miscellaneous:
Not Provided
Disclaimer:
The information in this document is being provided “as is” for INFORMATIONAL PURPOSES ONLY. CISA does not endorse any commercial product or service, including any subjects of analysis. Any reference to specific commercial entities or commercial products, processes, or services by service mark, trademark, manufacturer, or otherwise, does not constitute or imply endorsement, recommendation, or favoritism by CISA. This document does not address, ensure compliance with, or supersede any law, regulation, or other authority. Entities are responsible for complying with any recordkeeping, privacy, and other laws that may apply to the use of technology. This document is not intended to, and does not, create any right or benefit for anyone against the United States, its departments, agencies, or entities, its officers, employees, or agents, or any other person.
Product Support:
[email protected] [email protected]
Point of Contact:
[email protected] [email protected]
Sponsor:
Not Provided
Licensing:
Portions of this document are adapted from documents in Microsoft’s M365 and Azure GitHub repositories. The respective documents are subject to copyright and are adapted under the terms of the Creative Commons Attribution 4.0 International license. Sources are linked throughout this document. The United States government has adapted selections of these documents to develop innovative and scalable configuration standards to strengthen the security of widely used cloud-based software services. Microsoft Purview Audit (Premium) logging capabilities, including creating a custom audit log retention policy, requires E5/G5 licenses or E3/G3 licenses with add-on compliance licenses. Additionally, maintaining logs in the M365 environment for longer than one year requires an add-on license. For more information, see Licensing requirements | Microsoft Docs. However, this requirement can also be met by exporting the logs from M365 and storing them with your solution of choice, in which case audit log retention policies are not necessary.
Change History:
checklist approved - 2/12/2024 updated to final - 3/11/2024 Changes Approved - 11/29/2024 Reviewed Updated Contents from Resources - 03/27/2025 Reviewed Updated Contents from Resources - 08/13/2025
Dependency/Requirements:
URL | Description |
---|
References:
Reference URL | Description |
---|---|
https://www.microsoft.com/en-us/security/blog/2023/07/19/expanding-cloud-logging-to-give-customers-deeper-security-visibility/ | Expanding cloud logging to give customers deeper security visibility |