What CISA SCuBA Microsoft 365 baselines is
The Secure Cloud Business Applications (SCuBA) baselines from the US Cybersecurity and Infrastructure Security Agency, as checked by CISA’s ScubaGear tool (version 2.0): the “SHALL” and “SHOULD” policies for Entra ID, Defender, Exchange Online, SharePoint and Teams, mapped by policy id.
Who asks for it: US federal agencies and anyone using CISA’s secure configuration baselines.
What Microsoft 365 can show
Of the 104 policies in CISA SCuBA Microsoft 365 baselines (ScubaGear 2.0), ConfigCheckup checks 59 in full (57%), 14 in part, and 31 not at all. A check covers a policy in full when it reads the setting the policy names and applies its test, so it never passes a tenant the policy would fail. In part means it reads a different signal, applies a weaker threshold or tests one step of several.
| Section | Policies | In full | In part | Not checked |
|---|---|---|---|---|
| MS.AAD Microsoft Entra ID | 34 | 29 | 2 | 3 |
| MS.DEFENDER Microsoft Defender | 19 | 10 | 6 | 3 |
| MS.EXO Exchange Online | 12 | 10 | 1 | 1 |
| MS.POWERBI Power BI | 8 | 0 | 0 | 8 |
| MS.POWERPLATFORM Power Platform | 9 | 0 | 0 | 9 |
| MS.SHAREPOINT SharePoint and OneDrive | 8 | 1 | 1 | 6 |
| MS.TEAMS Microsoft Teams | 14 | 9 | 4 | 1 |
The 31 policies no check covers
Each one stays on this list until a check covers it, in full or in part, and is counted above as not checked.
- MS.AAD.2.2v1 Administrators notified when high-risk users are detected
- MS.AAD.4.1v1 Security logs sent to the security operations centre
- MS.AAD.9.1v1 Risky AI agents blocked
- MS.DEFENDER.4.5v1 Apps restricted from files protected by DLP are listed
- MS.DEFENDER.4.6v1 The DLP policy blocks restricted apps and unwanted Bluetooth apps
- MS.DEFENDER.5.2v1 Alerts go to a monitored address or a SIEM
- MS.EXO.4.3v1 DMARC aggregate reports go to CISA (US federal agencies)
- MS.POWERBI.1.1v1 Publish to web disabled
- MS.POWERBI.2.1v1 Guest access to the Power BI tenant disabled
- MS.POWERBI.3.1v1 Inviting external users disabled
- MS.POWERBI.4.1v1 Service principals with API access limited to security groups
- MS.POWERBI.4.2v1 Service principals creating profiles limited to security groups
- MS.POWERBI.5.1v1 ResourceKey-based authentication blocked
- MS.POWERBI.6.1v1 Python and R interactions disabled
- MS.POWERBI.7.1v1 Sensitivity labels enabled for Power BI
- MS.POWERPLATFORM.1.1v1 Production and sandbox environment creation limited to admins
- MS.POWERPLATFORM.1.2v1 Trial environment creation limited to admins
- MS.POWERPLATFORM.2.1v1 A DLP policy restricts connectors in the default environment
- MS.POWERPLATFORM.2.2v1 Every other environment has a DLP policy
- MS.POWERPLATFORM.3.1v1 Tenant isolation enabled
- MS.POWERPLATFORM.3.2v1 Inbound and outbound connection allow list configured
- MS.POWERPLATFORM.4.1v1 Content Security Policy enforced for Power Apps
- MS.POWERPLATFORM.5.1v1 Power Pages site creation limited to admins
- MS.POWERPLATFORM.6.1v1 Share with Everyone disabled
- MS.SHAREPOINT.1.2v1 OneDrive external sharing limited to existing guests or the organisation
- MS.SHAREPOINT.2.1v1 Default sharing scope is specific people
- MS.SHAREPOINT.2.2v1 Default sharing permission is view only
- MS.SHAREPOINT.3.1v1 Anyone links expire within 30 days
- MS.SHAREPOINT.3.2v1 Link permissions limited to view only
- MS.SHAREPOINT.3.3v2 Verification-code reauthentication within 30 days
- MS.TEAMS.5.1v2 Only approved Microsoft apps can be installed
The 14 policies checked in part
- MS.AAD.7.2v1 Finer-grained roles used instead of Global Administrator
- MS.AAD.7.5v1 Highly privileged roles provisioned only through a PAM system
- MS.DEFENDER.1.4v1 Sensitive accounts in the Exchange Online Protection strict preset
- MS.DEFENDER.1.5v1 Sensitive accounts in the Defender for Office 365 strict preset
- MS.DEFENDER.2.1v1 User impersonation protection for sensitive accounts in both presets
- MS.DEFENDER.2.3v1 Domain impersonation protection for key partners in both presets
- MS.DEFENDER.4.1v2 A custom DLP policy protects sensitive information
- MS.DEFENDER.6.3v1 Audit logs kept for the required period
- MS.EXO.2.2v3 SPF fails every sender not approved, for each domain
- MS.SHAREPOINT.1.1v1 SharePoint external sharing limited to existing guests or the organisation
- MS.TEAMS.1.3v1 Anonymous users and dial-in callers not admitted automatically
- MS.TEAMS.1.4v1 Internal users admitted automatically
- MS.TEAMS.5.2v2 Only approved third-party apps can be installed
- MS.TEAMS.5.3v2 Only approved custom apps can be installed
Outside Microsoft 365
Policies for Power Platform and Power BI, the SharePoint settings Microsoft Graph does not expose (default links, link expiry, OneDrive’s own sharing level), sending logs to a US federal SOC, and the DMARC reporting address for federal agencies are not assessed. Teams policies are read once the client gives ConfigCheckup the Teams Reader role, and DLP and alert policies once Purview is set up for the tenant. The Frameworks page lists each policy no check covers fully.
Readiness is not certification or an audit opinion: it covers only what Microsoft 365 can evidence, and the report says so.
Every policy and the checks behind it
The mappings were last checked against the published standards in October 2026. Each check links to what it looks at and how to fix it.
MS.AAD Microsoft Entra ID
| Number | Policy | Coverage | Checks |
|---|---|---|---|
| MS.AAD.1.1v1 | Legacy authentication blocked | Checked in full | |
| MS.AAD.2.1v1 | Users detected as high risk blocked | Checked in full | |
| MS.AAD.2.2v1 | Administrators notified when high-risk users are detected | Not checked | |
| MS.AAD.2.3v1 | Sign-ins detected as high risk blocked | Checked in full | |
| MS.AAD.3.1v1 | Phishing-resistant MFA enforced for all users | Checked in full | |
| MS.AAD.3.2v2 | MFA enforced for all users | Checked in full | |
| MS.AAD.3.3v2 | Microsoft Authenticator shows login context | Checked in full | |
| MS.AAD.3.4v1 | Authentication methods migration set to complete | Checked in full | |
| MS.AAD.3.5v2 | SMS, voice call and email one-time passcode disabled | Checked in full | |
| MS.AAD.3.6v1 | Phishing-resistant MFA required for highly privileged roles | Checked in full | |
| MS.AAD.3.7v1 | Managed devices required for authentication | Checked in full | In part: |
| MS.AAD.3.8v1 | Managed devices required to register MFA | Checked in full | In part: |
| MS.AAD.3.9v1 | Device code authentication blocked | Checked in full | |
| MS.AAD.4.1v1 | Security logs sent to the security operations centre | Not checked | |
| MS.AAD.5.1v1 | Only administrators can register applications | Checked in full | |
| MS.AAD.5.2v1 | User consent to applications restricted | Checked in full | |
| MS.AAD.5.3v1 | Admin consent workflow configured | Checked in full | |
| MS.AAD.5.5v1 | Adding passwords (client secrets) to applications blocked | Checked in full | |
| MS.AAD.5.6v1 | Application password lifetime of 180 days or less | Checked in full | |
| MS.AAD.5.7v1 | Application certificate lifetime of 365 days or less | Checked in full | |
| MS.AAD.6.1v1 | User passwords do not expire | Checked in full | |
| MS.AAD.7.1v1 | Between two and eight Global Administrators | Checked in full | |
| MS.AAD.7.2v1 | Finer-grained roles used instead of Global Administrator | Checked in part | In part: |
| MS.AAD.7.3v1 | Privileged users have cloud-only accounts | Checked in full | |
| MS.AAD.7.4v1 | No permanent active assignments to highly privileged roles | Checked in full | |
| MS.AAD.7.5v1 | Highly privileged roles provisioned only through a PAM system | Checked in part | In part: |
| MS.AAD.7.6v1 | Global Administrator activation requires approval | Checked in full | |
| MS.AAD.7.7v1 | Highly privileged role assignments trigger an alert | Checked in full | |
| MS.AAD.7.8v1 | Global Administrator activation triggers an alert | Checked in full | |
| MS.AAD.7.9v1 | Activation of other highly privileged roles triggers an alert | Checked in full | |
| MS.AAD.8.1v1 | Guests have limited or restricted directory access | Checked in full | |
| MS.AAD.8.2v1 | Only the Guest Inviter role can invite guests | Checked in full | |
| MS.AAD.8.3v1 | Guest invitations only to authorised domains | Checked in full | |
| MS.AAD.9.1v1 | Risky AI agents blocked | Not checked |
MS.DEFENDER Microsoft Defender
| Number | Policy | Coverage | Checks |
|---|---|---|---|
| MS.DEFENDER.1.1v1 | Standard and strict preset security policies enabled | Checked in full | |
| MS.DEFENDER.1.2v1 | All users in Exchange Online Protection standard or strict preset | Checked in full | |
| MS.DEFENDER.1.3v1 | All users in Defender for Office 365 standard or strict preset | Checked in full | |
| MS.DEFENDER.1.4v1 | Sensitive accounts in the Exchange Online Protection strict preset | Checked in part | In part: |
| MS.DEFENDER.1.5v1 | Sensitive accounts in the Defender for Office 365 strict preset | Checked in part | In part: |
| MS.DEFENDER.2.1v1 | User impersonation protection for sensitive accounts in both presets | Checked in part | In part: |
| MS.DEFENDER.2.2v1 | Domain impersonation protection for the organisation’s domains in both presets | Checked in full | |
| MS.DEFENDER.2.3v1 | Domain impersonation protection for key partners in both presets | Checked in part | In part: |
| MS.DEFENDER.3.1v1 | Safe Attachments for SharePoint, OneDrive and Teams | Checked in full | |
| MS.DEFENDER.4.1v2 | A custom DLP policy protects sensitive information | Checked in part | In part: |
| MS.DEFENDER.4.2v1 | The DLP policy covers Exchange, OneDrive, SharePoint, Teams chat and devices | Checked in full | |
| MS.DEFENDER.4.3v1 | The DLP policy blocks sharing sensitive information with everyone | Checked in full | |
| MS.DEFENDER.4.4v1 | The DLP policy notifies users | Checked in full | |
| MS.DEFENDER.4.5v1 | Apps restricted from files protected by DLP are listed | Not checked | |
| MS.DEFENDER.4.6v1 | The DLP policy blocks restricted apps and unwanted Bluetooth apps | Not checked | |
| MS.DEFENDER.5.1v1 | The alerts the baselines require are enabled | Checked in full | |
| MS.DEFENDER.5.2v1 | Alerts go to a monitored address or a SIEM | Not checked | |
| MS.DEFENDER.6.1v1 | Unified audit logging enabled | Checked in full | |
| MS.DEFENDER.6.3v1 | Audit logs kept for the required period | Checked in part | In part: |
MS.EXO Exchange Online
| Number | Policy | Coverage | Checks |
|---|---|---|---|
| MS.EXO.1.1v2 | Automatic forwarding to external domains disabled | Checked in full | In part: |
| MS.EXO.2.2v3 | SPF fails every sender not approved, for each domain | Checked in part | In part: |
| MS.EXO.3.1v1 | DKIM enabled for every domain | Checked in full | In part: |
| MS.EXO.4.1v1 | DMARC published for every second-level domain | Checked in full | |
| MS.EXO.4.2v1 | DMARC policy set to reject | Checked in full | In part: |
| MS.EXO.4.3v1 | DMARC aggregate reports go to CISA (US federal agencies) | Not checked | |
| MS.EXO.4.4v1 | An organisational contact receives DMARC aggregate and failure reports | Checked in full | |
| MS.EXO.5.1v1 | SMTP AUTH disabled | Checked in full | |
| MS.EXO.6.1v1 | Contact folders not shared with all domains | Checked in full | |
| MS.EXO.6.2v1 | Calendar details not shared with all domains | Checked in full | |
| MS.EXO.7.1v1 | External sender warnings implemented | Checked in full | |
| MS.EXO.13.1v1 | Mailbox auditing enabled | Checked in full |
MS.POWERBI Power BI
| Number | Policy | Coverage | Checks |
|---|---|---|---|
| MS.POWERBI.1.1v1 | Publish to web disabled | Not checked | |
| MS.POWERBI.2.1v1 | Guest access to the Power BI tenant disabled | Not checked | |
| MS.POWERBI.3.1v1 | Inviting external users disabled | Not checked | |
| MS.POWERBI.4.1v1 | Service principals with API access limited to security groups | Not checked | |
| MS.POWERBI.4.2v1 | Service principals creating profiles limited to security groups | Not checked | |
| MS.POWERBI.5.1v1 | ResourceKey-based authentication blocked | Not checked | |
| MS.POWERBI.6.1v1 | Python and R interactions disabled | Not checked | |
| MS.POWERBI.7.1v1 | Sensitivity labels enabled for Power BI | Not checked |
MS.POWERPLATFORM Power Platform
| Number | Policy | Coverage | Checks |
|---|---|---|---|
| MS.POWERPLATFORM.1.1v1 | Production and sandbox environment creation limited to admins | Not checked | |
| MS.POWERPLATFORM.1.2v1 | Trial environment creation limited to admins | Not checked | |
| MS.POWERPLATFORM.2.1v1 | A DLP policy restricts connectors in the default environment | Not checked | |
| MS.POWERPLATFORM.2.2v1 | Every other environment has a DLP policy | Not checked | |
| MS.POWERPLATFORM.3.1v1 | Tenant isolation enabled | Not checked | |
| MS.POWERPLATFORM.3.2v1 | Inbound and outbound connection allow list configured | Not checked | |
| MS.POWERPLATFORM.4.1v1 | Content Security Policy enforced for Power Apps | Not checked | |
| MS.POWERPLATFORM.5.1v1 | Power Pages site creation limited to admins | Not checked | |
| MS.POWERPLATFORM.6.1v1 | Share with Everyone disabled | Not checked |
MS.SHAREPOINT SharePoint and OneDrive
| Number | Policy | Coverage | Checks |
|---|---|---|---|
| MS.SHAREPOINT.1.1v1 | SharePoint external sharing limited to existing guests or the organisation | Checked in part | In part: |
| MS.SHAREPOINT.1.2v1 | OneDrive external sharing limited to existing guests or the organisation | Not checked | |
| MS.SHAREPOINT.1.3v1 | External sharing limited to approved domains or security groups | Checked in full | |
| MS.SHAREPOINT.2.1v1 | Default sharing scope is specific people | Not checked | |
| MS.SHAREPOINT.2.2v1 | Default sharing permission is view only | Not checked | |
| MS.SHAREPOINT.3.1v1 | Anyone links expire within 30 days | Not checked | |
| MS.SHAREPOINT.3.2v1 | Link permissions limited to view only | Not checked | |
| MS.SHAREPOINT.3.3v2 | Verification-code reauthentication within 30 days | Not checked |
MS.TEAMS Microsoft Teams
| Number | Policy | Coverage | Checks |
|---|---|---|---|
| MS.TEAMS.1.1v1 | External participants cannot request control of shared screens | Checked in full | |
| MS.TEAMS.1.2v2 | Anonymous users cannot start meetings | Checked in full | |
| MS.TEAMS.1.3v1 | Anonymous users and dial-in callers not admitted automatically | Checked in part | In part: |
| MS.TEAMS.1.4v1 | Internal users admitted automatically | Checked in part | In part: |
| MS.TEAMS.1.5v1 | Dial-in users cannot bypass the lobby | Checked in full | |
| MS.TEAMS.1.6v1 | Meeting recording disabled | Checked in full | |
| MS.TEAMS.1.7v2 | Events not set to always record | Checked in full | |
| MS.TEAMS.2.1v2 | External access only on a per-domain basis | Checked in full | |
| MS.TEAMS.2.2v2 | Unmanaged users cannot initiate contact | Checked in full | |
| MS.TEAMS.2.3v2 | Internal users cannot initiate contact with unmanaged users | Checked in full | |
| MS.TEAMS.4.1v1 | Teams email integration disabled | Checked in full | |
| MS.TEAMS.5.1v2 | Only approved Microsoft apps can be installed | Not checked | |
| MS.TEAMS.5.2v2 | Only approved third-party apps can be installed | Checked in part | In part: |
| MS.TEAMS.5.3v2 | Only approved custom apps can be installed | Checked in part | In part: |
Related frameworks
- CIS Microsoft 365 Foundations v6.0.0: The Center for Internet Security’s hardening benchmark for Microsoft 365.
- SOC 2: The AICPA Trust Services Criteria, asked of SaaS and service providers.
- NIST SP 800-171: Protecting controlled unclassified information in the US defence supply chain.
- CMMC Level 2: The NIST SP 800-171 practices, as US defence contractors are assessed on them.