Skip to main content
Version: 2.1.1-preview

CISA Tests

These tests verify Microsoft 365 tenant configuration against CISA Secure Cloud Business Applications baseline guidance.

Tests

Test IDTitleSeverityCategory
CISA.MS.AAD.1.1Legacy authentication SHALL be blocked.HighEntra ID P1
CISA.MS.AAD.2.1Users detected as high risk SHALL be blocked.HighEntra ID P2
CISA.MS.AAD.2.2A notification SHOULD be sent to the administrator when high-risk users are detected.HighEntra ID P2
CISA.MS.AAD.2.3Sign-ins detected as high risk SHALL be blocked.HighEntra ID P2
CISA.MS.AAD.3.1Phishing-resistant MFA SHALL be enforced for all users.HighEntra ID P1
CISA.MS.AAD.3.2If phishing-resistant MFA has not been enforced, an alternative MFA method SHALL be enforced for all users.HighEntra ID P1
CISA.MS.AAD.3.3If Microsoft Authenticator is enabled, it SHALL be configured to show login context information.MediumEntra ID P1
CISA.MS.AAD.3.4The Authentication Methods Manage Migration feature SHALL be set to Migration Complete.HighEntra ID P1
CISA.MS.AAD.3.5The authentication methods SMS, Voice Call, and Email One-Time Passcode (OTP) SHALL be disabled.HighEntra ID P1
CISA.MS.AAD.3.6Phishing-resistant MFA SHALL be required for highly privileged roles.HighEntra ID P1
CISA.MS.AAD.3.7Managed devices SHOULD be required for authentication.HighEntra ID P1
CISA.MS.AAD.3.8Managed Devices SHOULD be required to register MFA.HighEntra ID P1
CISA.MS.AAD.4.1Security logs SHALL be sent to the agency's security operations center for monitoring.HighEntra ID P1
CISA.MS.AAD.5.1Only administrators SHALL be allowed to register applications.HighEntra ID Free
CISA.MS.AAD.5.2Only administrators SHALL be allowed to consent to applications.HighEntra ID Free
CISA.MS.AAD.5.3An admin consent workflow SHALL be configured for applications.HighEntra ID Free
CISA.MS.AAD.5.4Group owners SHALL NOT be allowed to consent to applications.HighEntra ID Free
CISA.MS.AAD.6.1User passwords SHALL NOT expire.HighEntra ID Free
CISA.MS.AAD.7.1A minimum of two users and a maximum of eight users SHALL be provisioned with the Global Administrator role.HighEntra ID Free
CISA.MS.AAD.7.2Privileged users SHALL be provisioned with finer-grained roles instead of Global Administrator.HighEntra ID Free
CISA.MS.AAD.7.3Privileged users SHALL be provisioned cloud-only accounts separate from an on-premises directory or other federated identity providers.HighEntra ID Free
CISA.MS.AAD.7.4Permanent active role assignments SHALL NOT be allowed for highly privileged roles.HighEntra ID P2
CISA.MS.AAD.7.5Provisioning users to highly privileged roles SHALL NOT occur outside of a PAM system.HighEntra ID P2
CISA.MS.AAD.7.6Activation of the Global Administrator role SHALL require approval.HighEntra ID P2
CISA.MS.AAD.7.7Eligible and Active highly privileged role assignments SHALL trigger an alert.HighEntra ID P2
CISA.MS.AAD.7.8User activation of the Global Administrator role SHALL trigger an alert.HighEntra ID P2
CISA.MS.AAD.7.9User activation of other highly privileged roles SHOULD trigger an alert.HighEntra ID P2
CISA.MS.AAD.8.1Guest users SHOULD have limited or restricted access to Azure AD directory objects.MediumEntra ID Free
CISA.MS.AAD.8.2Only users with the Guest Inviter role SHOULD be able to invite guest users.HighEntra ID Free
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.MediumEntra ID Free
CISA.MS.EXO.1.1Automatic forwarding to external domains SHALL be disabled.Highexchange
CISA.MS.EXO.2.1A list of approved IP addresses for sending mail SHALL be maintained.MediumDeprecated
CISA.MS.EXO.2.2An SPF policy SHALL be published for each domain, designating only these addresses as approved senders.Mediumexchange
CISA.MS.EXO.3.1DKIM SHOULD be enabled for all domains.Mediumexchange
CISA.MS.EXO.4.1A DMARC policy SHALL be published for every second-level domain.Mediumexchange
CISA.MS.EXO.4.2The DMARC message rejection option SHALL be p=reject.Highexchange
CISA.MS.EXO.4.3The DMARC point of contact for aggregate reports SHALL include reports@dmarc.cyber.dhs.gov.Mediumexchange
CISA.MS.EXO.5.1SMTP AUTH SHALL be disabled.Highexchange
CISA.MS.EXO.6.1Contact folders SHALL NOT be shared with all domains.Mediumexchange
CISA.MS.EXO.6.2Calendar details SHALL NOT be shared with all domains.Mediumexchange
CISA.MS.EXO.7.1External sender warnings SHALL be implemented.Mediumexchange
CISA.MS.EXO.8.1A DLP solution SHALL be used.Highexchange
CISA.MS.EXO.8.2The DLP solution SHALL protect personally identifiable information (PII) and sensitive information, as defined by the agency.Mediumexchange
CISA.MS.EXO.8.3The selected DLP solution SHOULD offer services comparable to the native DLP solution offered by Microsoft.Mediumexchange
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.Highexchange
CISA.MS.EXO.9.1Emails SHALL be filtered by attachment file types.Mediumexchange
CISA.MS.EXO.9.2The attachment filter SHOULD attempt to determine the true file type and assess the file extension.Mediumexchange
CISA.MS.EXO.9.3Disallowed file types SHALL be determined and enforced.Highexchange
CISA.MS.EXO.9.4Alternatively chosen filtering solutions SHOULD offer services comparable to Microsoft Defender's Common Attachment Filter.Mediumexchange
CISA.MS.EXO.9.5At a minimum, click-to-run files SHOULD be blocked (e.g., .exe, .cmd, and .vbe).Highexchange
CISA.MS.EXO.10.1Emails SHALL be scanned for malware.Highexchange
CISA.MS.EXO.10.2Emails identified as containing malware SHALL be quarantined or dropped.Highexchange
CISA.MS.EXO.10.3Email scanning SHALL be capable of reviewing emails after delivery.Highexchange
CISA.MS.EXO.11.1Impersonation protection checks SHOULD be used.Highexchange
CISA.MS.EXO.11.2User warnings, comparable to the user safety tips included with EOP, SHOULD be displayed.Mediumexchange
CISA.MS.EXO.11.3The phishing protection solution SHOULD include an AI-based phishing detection tool comparable to EOP Mailbox Intelligence.Mediumexchange
CISA.MS.EXO.12.1IP allow lists SHOULD NOT be created.Mediumexchange
CISA.MS.EXO.12.2Safe lists SHOULD NOT be enabled.Mediumexchange
CISA.MS.EXO.13.1Mailbox auditing SHALL be enabled.Highexchange
CISA.MS.EXO.14.1A spam filter SHALL be enabled.Highexchange
CISA.MS.EXO.14.2Spam and high confidence spam SHALL be moved to either the junk email folder or the quarantine folder.Mediumexchange
CISA.MS.EXO.14.3Allowed domains SHALL NOT be added to inbound anti-spam protection policies.Mediumexchange
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.Mediumexchange
CISA.MS.EXO.15.1URL comparison with a block-list SHOULD be enabled.Mediumexchange
CISA.MS.EXO.15.2Direct download links SHOULD be scanned for malware.Highexchange
CISA.MS.EXO.15.3User click tracking SHOULD be enabled.Mediumexchange
CISA.MS.EXO.16.1Alerts SHALL be enabled.Highexchange
CISA.MS.EXO.16.2Alerts SHOULD be sent to a monitored address or incorporated into a security information and event management (SIEM) system.Mediumexchange
CISA.MS.EXO.17.1Microsoft Purview Audit (Standard) logging SHALL be enabled.Highexchange
CISA.MS.EXO.17.2Microsoft Purview Audit (Premium) logging SHALL be enabled.MediumDeprecated
CISA.MS.EXO.17.3Audit logs SHALL be maintained for at least the minimum duration dictated by OMB M-21-31 (Appendix C).Mediumexchange
CISA.MS.SHAREPOINT.1.1External sharing for SharePoint SHALL be limited to Existing guests or Only People in your organization.Mediumspo
CISA.MS.SHAREPOINT.1.3External sharing SHALL be restricted to approved external domains and/or users in approved security groups per interagency collaboration needs.Highspo