Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
In Microsoft Entra, we group our security recommendations into several main areas. This structure allows organizations to logically break up projects into related consumable chunks.
Tip
Some organizations might take these recommendations exactly as written, while others might choose to make modifications based on their own business needs. In our initial release of this guidance, we focus on traditional workforce tenants. These workforce tenants are for your employees, internal business apps, and other organizational resources.
We recommend that all of the following controls be implemented where licenses are available. These patterns and practices help to provide a foundation for other resources built on top of this solution. More controls will be added to this document over time.
Protect identities and secrets
Reduce credential-related risk by implementing modern identity standards.
Protect tenants and isolation production systems
Check | Minimum required license |
---|---|
Permissions to create new tenants are limited to the Tenant Creator role | Microsoft Entra ID Free |
Guest access is limited to approved tenants | Microsoft Entra ID Free |
Guests are not assigned high privileged directory roles | Microsoft Entra ID Free Microsoft Entra ID P2 or Microsoft ID Governance for PIM |
Guests can't invite other guests | Microsoft Entra ID Free |
Guests have restricted access to directory objects | Microsoft Entra ID Free |
App instance property lock is configured for all multitenant applications | Microsoft Entra ID Free |
Guests don't have long lived sign-in sessions | Microsoft Entra ID P1 |
Guest access is protected by strong authentication methods | Microsoft Entra ID Free Microsoft Entra ID P1 recommended for Conditional Access |
Guest self-service sign-up via user flow is disabled | Microsoft Entra ID Free |
Outbound cross-tenant access settings are configured | Microsoft Entra ID Free Microsoft Entra ID P1 recommended for Conditional Access |
Guests don't own apps in the tenant | Microsoft Entra ID Free |
All guests have a sponsor | Microsoft Entra ID Free Microsoft Entra ID P2 or Microsoft ID Governance for entitlement managed and access reviews |
Inactive guest identities are disabled or removed from the tenant | Microsoft Entra ID Free Microsoft Entra ID P2 or Microsoft ID Governance for entitlement managed and access reviews |
Protect networks
Protect your network perimeter.
Check | Minimum required license |
---|---|
Named locations are configured | Microsoft Entra ID P1 |
Tenant restrictions v2 policy is configured | Microsoft Entra ID P1 |
Protect engineering systems
Protect software assets and improve code security.
Monitor and detect cyberthreats
Collect and analyze security logs and triage alerts.
Check | Minimum required license |
---|---|
Diagnostic settings are configured for all Microsoft Entra logs | Microsoft Entra ID P1 |
Privileged role activations have monitoring and alerting configured | Microsoft Entra ID P2 |
Privileged users sign in with phishing-resistant methods | Microsoft Entra ID P1 |
All high-risk users are triaged | Microsoft Entra ID P2 |
All high-risk sign-ins are triaged | Microsoft Entra ID P2 |
All user sign-in activity uses strong authentication methods | Microsoft Entra ID P1 |
High priority Microsoft Entra recommendations are addressed | Microsoft Entra ID P1 |
ID Protection notifications enabled | Microsoft Entra ID P2 |
No legacy authentication sign-in activity | Microsoft Entra ID P1 |
All Microsoft Entra recommendations are addressed | Microsoft Entra ID P1 |
Accelerate response and remediation
Improve security incident response and incident communications.
Check | Minimum required license |
---|---|
Workload identities based on risk policies are configured | Microsoft Entra Workload ID |
Restrict high risk sign-ins | Microsoft Entra ID P2 |
Restrict access to high risk users | Microsoft Entra ID P2 |