CISA SCuBA M365 Security Configuration Baselines
U.S. federal security baselines for Microsoft 365, developed by CISA as part of the Secure Cloud Business Applications (SCuBA) project.
Official documentation108
Controls
87
Auto-Remediable
6
Domains
Exchange(35)
CISA-MS.EXO.1.1Auto-forwarding to external domains disabled
CISA-MS.EXO.10.1Outbound spam notification configured
CISA-MS.EXO.10.2Emails identified as containing malware SHALL be quarantined or dropped.
CISA-MS.EXO.10.3Email scanning SHALL be capable of reviewing emails after delivery.
CISA-MS.EXO.11.1Connection filter IP allow list is empty
CISA-MS.EXO.11.2User warnings, comparable to the user safety tips included with EOP, SHOULD be displayed.
CISA-MS.EXO.11.3The phishing protection solution SHOULD include an AI-based phishing detection tool comparable to EOP Mailbox Intelligence.
CISA-MS.EXO.12.1Anti-phishing impersonation protection enabled
CISA-MS.EXO.12.2Safe lists SHOULD NOT be enabled.
CISA-MS.EXO.13.1Inbound anti-spam high confidence action set
CISA-MS.EXO.14.1A spam filter SHALL be enabled.
CISA-MS.EXO.14.2Spam and high confidence spam SHALL be moved to either the junk email folder or the quarantine folder.
CISA-MS.EXO.14.3Allowed domains SHALL NOT be added to inbound anti-spam protection policies.
CISA-MS.EXO.14.4If a third-party party filtering solution is used, the solution SHOULD offer services comparable to the native spam filtering offered by Microsoft.
CISA-MS.EXO.15.1URL comparison with a block-list SHOULD be enabled.
CISA-MS.EXO.15.2Direct download links SHOULD be scanned for malware.
CISA-MS.EXO.15.3User click tracking SHOULD be enabled.
CISA-MS.EXO.16.1Alerts SHALL be enabled.
CISA-MS.EXO.16.2Alerts SHOULD be sent to a monitored address or incorporated into a security information and event management (SIEM) system.
CISA-MS.EXO.2.1SPF record configured for all accepted domains
CISA-MS.EXO.2.2DKIM signing enabled for all accepted domains
CISA-MS.EXO.2.3DMARC policy set to reject or quarantine
CISA-MS.EXO.3.1SMTP AUTH disabled globally
CISA-MS.EXO.4.1Mailbox auditing enabled by default
CISA-MS.EXO.4.2The DMARC message rejection option SHALL be p=reject.
CISA-MS.EXO.4.3The DMARC point of contact for aggregate reports SHALL include reports@dmarc.cyber.dhs.gov.
CISA-MS.EXO.5.1Calendar sharing with external users restricted
CISA-MS.EXO.6.1Contact sharing with external users restricted
CISA-MS.EXO.6.2Calendar details SHALL NOT be shared with all domains.
CISA-MS.EXO.7.1External sender identification enabled in Outlook
CISA-MS.EXO.9.1Common attachment type filter enabled in malware policy
CISA-MS.EXO.9.2Malware filter internal sender notifications configured
CISA-MS.EXO.9.3Disallowed file types SHALL be determined and enforced.
CISA-MS.EXO.9.4Alternatively chosen filtering solutions SHOULD offer services comparable to Microsoft Defender's Common Attachment Filter.
CISA-MS.EXO.9.5At a minimum, click-to-run files SHOULD be blocked (e.g., .exe, .cmd, and .vbe).
Entra ID(31)
CISA-MS.AAD.1.1Block legacy authentication
CISA-MS.AAD.2.1Sign-in risk Conditional Access policy configured
CISA-MS.AAD.2.2User risk Conditional Access policy configured
CISA-MS.AAD.2.3Sign-ins detected as high risk SHALL be blocked.
CISA-MS.AAD.3.1Require MFA for admins
CISA-MS.AAD.3.2Require MFA for all users
CISA-MS.AAD.3.3Securing security info registration
CISA-MS.AAD.3.4Disable SMS sign-in as authentication method
CISA-MS.AAD.3.5Disable voice call as authentication method
CISA-MS.AAD.3.6Require MFA for admin portals
CISA-MS.AAD.3.7Require phishing-resistant MFA for admins
CISA-MS.AAD.3.8Authentication methods registration campaign enabled
CISA-MS.AAD.4.1Named/trusted location configured
CISA-MS.AAD.4.2Trusted IP-based named location defined
CISA-MS.AAD.5.1Disable user consent to third-party applications
CISA-MS.AAD.5.2Admin consent workflow enabled
CISA-MS.AAD.5.3An admin consent workflow SHALL be configured for applications.
CISA-MS.AAD.5.4Group owners SHALL NOT be allowed to consent to applications.
CISA-MS.AAD.6.1User passwords SHALL NOT expire.
CISA-MS.AAD.7.1Cross-tenant inbound MFA trust configured
CISA-MS.AAD.7.2Cross-tenant inbound compliant device trust configured
CISA-MS.AAD.7.3Restrict guest user access permissions
CISA-MS.AAD.7.4Cross-tenant inbound hybrid Azure AD join trust configured
CISA-MS.AAD.7.5Cross-tenant inbound compliant network trust configured
CISA-MS.AAD.7.6Activation of the Global Administrator role SHALL require approval.
CISA-MS.AAD.7.7Eligible and Active highly privileged role assignments SHALL trigger an alert.
CISA-MS.AAD.7.8User activation of the Global Administrator role SHALL trigger an alert.
CISA-MS.AAD.7.9User activation of other highly privileged roles SHOULD trigger an alert.
CISA-MS.AAD.8.1Block access from non-allowed countries/locations
CISA-MS.AAD.8.2Only users with the Guest Inviter role SHOULD be able to invite guest users.
CISA-MS.AAD.8.3Guest invites SHOULD only be allowed to specific external domains that have been authorized by the agency for legitimate business purposes.
Teams(18)
CISA-MS.TEAMS.1.1External participants cannot request control of shared screen
CISA-MS.TEAMS.1.2Anonymous users cannot start meetings
CISA-MS.TEAMS.1.3Anonymous and dial-in users must wait in lobby
CISA-MS.TEAMS.1.4Internal users auto-admitted to meetings
CISA-MS.TEAMS.1.5Dial-in users cannot bypass meeting lobby
CISA-MS.TEAMS.1.6Meeting recording disabled by default
CISA-MS.TEAMS.1.7Live event recording not set to always record
CISA-MS.TEAMS.2.1External access restricted to allowed domains only
CISA-MS.TEAMS.2.2Unmanaged Teams users cannot initiate contact
CISA-MS.TEAMS.2.3Internal users cannot contact unmanaged Teams users
CISA-MS.TEAMS.4.1Teams email integration disabled
CISA-MS.TEAMS.5.1Microsoft apps restricted to approved list
CISA-MS.TEAMS.5.2Third-party apps restricted to approved list
CISA-MS.TEAMS.5.3Custom apps restricted to approved list
CISA-MS.TEAMS.7.1Safe Attachments enabled for Teams
CISA-MS.TEAMS.7.2Users prevented from opening malicious files in Teams
CISA-MS.TEAMS.8.1Safe Links URL scanning enabled for Teams
CISA-MS.TEAMS.8.2User click tracking enabled for Safe Links in Teams
Defender(11)
CISA-MS.DEFENDER.1.1Standard and strict preset security policies enabled
CISA-MS.DEFENDER.1.2All users added to EOP in standard or strict preset security policy
CISA-MS.DEFENDER.1.3All users added to Defender for Office 365 in standard or strict preset security policy
CISA-MS.DEFENDER.1.4Sensitive accounts added to Exchange Online Protection in strict preset security policy
CISA-MS.DEFENDER.1.5Sensitive accounts added to Defender for Office 365 in strict preset security policy
CISA-MS.DEFENDER.2.1User impersonation protection enabled for sensitive accounts
CISA-MS.DEFENDER.2.2Domain impersonation protection enabled for organization domains
CISA-MS.DEFENDER.2.3Domain impersonation protection enabled for key partners and suppliers
CISA-MS.DEFENDER.3.1Safe Attachments enabled for SharePoint, OneDrive, and Microsoft Teams
CISA-MS.DEFENDER.5.1Required CISA security alerts enabled
CISA-MS.DEFENDER.5.2Security alerts sent to monitored address or SIEM
Purview(10)
CISA-MS.DEFENDER.6.3Audit logs maintained for minimum duration per OMB M-21-31
CISA-MS.EXO.17.1Microsoft Purview Audit (Standard) logging SHALL be enabled.
CISA-MS.EXO.17.2Microsoft Purview Audit (Premium) logging SHALL be enabled.
CISA-MS.EXO.17.3Audit logs SHALL be maintained for at least the minimum duration dictated by OMB M-21-31 (Appendix C).
CISA-MS.EXO.8.1Unified audit logging enabled
CISA-MS.EXO.8.2The DLP solution SHALL protect personally identifiable information (PII) and sensitive information, as defined by the agency.
CISA-MS.EXO.8.3The selected DLP solution SHOULD offer services comparable to the native DLP solution offered by Microsoft.
CISA-MS.EXO.8.4At a minimum, the DLP solution SHALL restrict sharing credit card numbers, U.S. Individual Taxpayer Identification Numbers (ITIN), and U.S. Social Security numbers (SSN) via email.
CISA-MS.TEAMS.6.1DLP solution enabled for Teams
CISA-MS.TEAMS.6.2DLP protects PII and sensitive information in Teams
SharePoint(3)
CISA-MS.SHAREPOINT.1.1SharePoint external sharing restricted appropriately
CISA-MS.SHAREPOINT.1.2Legacy authentication protocols disabled for SharePoint
CISA-MS.SHAREPOINT.1.3External sharing SHALL be restricted to approved external domains and/or users in approved security groups per interagency collaboration needs.
