Security Fundamentals
In brief
The page was retitled and rewritten to clarify security controls for external tenants, including authentication approach supportability, access control, Conditional Access, fraud, bot, DDoS, and monitoring protections. Links and descriptions were also updated.
What Entra admins need to know
Administrators can use the revised guidance to assess security controls for customer-facing identity flows.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
Security fundamentals for Microsoft Entra External ID external tenants
[!INCLUDE applies-to-external-only]
External-facing identity systems support a wide range of customer experiences. That wide range also makes them attractive targets for common customerCustomer identity and access management (CIAM) attack patternssystems face threats such as credential stuffing, automated bot sign-ups, account takeover attempts, and high-volume traffic spikes. Understanding these threats helps explain why a clear, layered security approach is essential. Microsoft Entra External ID provides foundationalsecurity capabilities you can build on. Thison to address these threats. Use this guide helps you understand how to strengthen that foundation with recommendedprioritize controls and integrations based on common CIAM threat patterns.that help protect your customer-facing applications.
[!INCLUDE authentication-approaches]
This article outlines:
- The attack vectors that commonly target CIAM systems.
- The security controls that can help you address them.
- A prioritized roadmap to guide implementation.
- Available
third‑third-party integrations for fraud, bot, andDDoSdistributed denial-of-service (DDoS) protection. - Known limitations specific to external tenants.
Our goal is to offer a practical, actionable roadmap that helps you make informed decisions about how to secure your customer-facing experiences.
Security model for external tenants
A defense‑in‑depth strategy requires combining multiple control layers:
Front‑Front-door protection(WAF,through a web application firewall (WAF), bot mitigation, and IPcontrols)controls.- Identity security
(MFA,through multifactor authentication (MFA), Conditional Access, and accesscontrol)control. - Fraud prevention
(sign‑through third-party sign-up andsign‑sign-in detectionthrough 3P providers)providers. Application‑Application-levelauthorizationauthorization.- Monitoring and
alertingalerting.
Each layer addresses a different class of attacks, reducing the likelihood of compromise and limiting the blast radius.
Priority 1: Immediate implementation
TheseStart with these protections are foundational. They're quick to enable and essential for establishingestablish a securesecurity baseline for your external identity flows. Additional protections introduced in Priority 2 addressadds protections against fraud, bots, DDoS, and more advanced attack patterns.
| Security feature | Description | Threats addressed | User impact | Implementation effort |
|---|---|---|---|---|
| Brute force protection | Mitigates brute force attacks by limiting the number of sign-in attempts to prevent unauthorized access through repeated password guessing. Note: Smart lockout focuses on password misuse; broader bot and fraud activity is addressed through additional controls later in this article. |
Prevents brute force, account takeover. | None — No end-user impact | None – Enabled by default |
| Common networking HTTP protection | These built‑in protections help filter malformed traffic, limit abusive request patterns, and mitigate common protocol‑level attacks. Note: These safeguards support application stability, but high‑volume DDoS and sophisticated bots require WAF or bot‑mitigation integrations described later. |
Protects against common network attacks. | Low – Sensitive actions only | None – Enabled by default |
| Access Control | Note: Access |
Enforces authorization in applications. | Medium– User adoption | Medium – Setup required |
| Enable multifactor authentication (MFA) for all users | MFA adds a second verification step beyond passwords, significantly reducing the risk of account takeover. Note: MFA limits stolen‑credential attacks but must be paired with fraud detection and monitoring to prevent automated or malicious sign‑up attempts. |
Adds second factor authentication. | High – User adoption | Medium – Setup required |
| Passkeys (FIDO2) | Phishing-resistant, passwordless authentication that uses face, fingerprint, PIN, or a security key. A passkey satisfies MFA in a single gesture and can also serve as a primary, passwordless sign-in method. | Prevents phishing, password theft, and credential replay. | Low – Familiar gestures | Medium – Setup and credential management UX required |
| Activity logging & User insights | Activity logs and insights provide visibility into sign-ups, sign-ins, error patterns, and anomalies. They help you identify unusual trends and investigate issues quickly, supporting early detection, and informed decision making. | Enables threat detection. | None — No end-user impact | Medium – Setup required |
| Security feature | Description | Threats addressed | User impact | Implementation effort |
|---|---|---|---|---|
| Conditional Access | Provides |
Medium – User adoption | Medium – Setup required | |
| Credential and secret management | Prefer certificates over client secrets for app authentication to External ID because certificates are more secure and harder to compromise. | Secures app credentials. | None — No end-user impact | Medium – Setup required |
| Token lifetime management | Configure the token lifetime to reduce your app’s exposure to compromised tokens. | Limits exposure. | High – Requires frequent refreshes | Medium – Setup required |
| Custom Domain with Web Application Firewall (WAF) | Use Cloudflare, Akamai or Azure WAF for tenant security against DDoS attacks. | Provides DDoS and bot protection. | Medium – User adoption | High – WAF integration |
@@ -1,51 +1,51 @@ ----title: Security Features in External Tenants+title: Security Fundamentals description: Learn about security features and fundamentals for Microsoft Entra External ID customer identity and access management (CIAM) in external tenant configurations. ms.topic: concept-article-ms.date: 01/28/2026-ms.custom: it-pro+ms.date: 11/11/2026+ms.custom: it-pro, msecd-doc-authoring-1030+ai-usage: ai-assisted+#customer intent: As a security administrator, I want to understand security controls for external tenants so that I can protect customer-facing identity systems. --- -# Security fundamentals for external tenants+# Security fundamentals for Microsoft Entra External ID external tenants -[!INCLUDE [applies-to-external-only](../includes/applies-to-external-only.md)]+Customer identity and access management (CIAM) systems face threats such as credential stuffing, automated bot sign-ups, account takeover attempts, and high-volume traffic spikes. Microsoft Entra External ID provides security capabilities you can build on to address these threats. Use this guide to prioritize controls and integrations that help protect your customer-facing applications. -External-facing identity systems support a wide range of customer experiences. That wide range also makes them attractive targets for common customer identity and access management (CIAM) attack patterns such as credential stuffing, automated bot sign-ups, account takeover attempts, and high-volume traffic spikes. Understanding these threats helps explain why a clear, layered security approach is essential. Microsoft Entra External ID provides foundational capabilities you can build on. This guide helps you understand how to strengthen that foundation with recommended controls and integrations based on common CIAM threat patterns.+[!INCLUDE [authentication-approaches](../includes/applies-to-authentication-approaches.md)] This article outlines: - The attack vectors that commonly target CIAM systems. - The security controls that can help you address them. - A prioritized roadmap to guide implementation.-- Available third‑party integrations for fraud, bot, and DDoS protection.+- Available third-party integrations for fraud, bot, and distributed denial-of-service (DDoS) protection. - Known limitations specific to external tenants. -Our goal is to offer a practical, actionable roadmap that helps you make informed decisions about how to secure your customer-facing experiences.- ## Security model for external tenants A defense‑in‑depth strategy requires combining multiple control layers: -- Front‑door protection (WAF, bot mitigation, IP controls)-- Identity security (MFA, Conditional Access, access control) -- Fraud prevention (sign‑up and sign‑in detection through 3P providers) -- Application‑level authorization-- Monitoring and alerting +- Front-door protection through a web application firewall (WAF), bot mitigation, and IP controls.+- Identity security through multifactor authentication (MFA), Conditional Access, and access control.+- Fraud prevention through third-party sign-up and sign-in detection providers.+- Application-level authorization.+- Monitoring and alerting. Each layer addresses a different class of attacks, reducing the likelihood of compromise and limiting the blast radius. > [!IMPORTANT]-> Your choice of authentication approach affects your security model. With **browser-delegated authentication**, Microsoft manages the sign-in surface, which reduces your app's exposure to phishing and credential-harvesting attacks. With **native authentication**, your development team shares security responsibility with Microsoft Entra because your app handles credentials directly. Before choosing native authentication, review the [security considerations in Choose an authentication approach](concept-choose-authentication-approach.md#security-considerations).+> Confirm control and method availability for your integration in the [authentication approach comparison](concept-supported-features-customers.md#authentication-approach-supportability). Review the [security considerations in Choose an authentication approach](concept-choose-authentication-approach.md#security-considerations) before implementing your integration. ### Priority 1: Immediate implementation -These protections are foundational. They're quick to enable and essential for establishing a secure baseline for your external identity flows. Additional protections introduced in Priority 2 address fraud, bots, DDoS, and more advanced attack patterns.+Start with these protections to establish a security baseline for your external identity flows. Priority 2 adds protections against fraud, bots, DDoS, and more advanced attack patterns. | **Security feature** |**Description** |**Threats addressed** | **User impact** | **Implementation effort** | |----|----|----|----|----| | **[Brute force protection](/entra/identity/authentication/howto-password-smart-lockout)** |Mitigates brute force attacks by limiting the number of sign-in attempts to prevent unauthorized access through repeated password guessing. <br> **Note:** Smart lockout focuses on password misuse; broader bot and fraud activity is addressed through additional controls later in this article. |Prevents brute force, account takeover. | None — No end-user impact |None – Enabled by default | | **[Common networking HTTP protection](/entra/external-id/customers/reference-service-limits)** |These built‑in protections help filter malformed traffic, limit abusive request patterns, and mitigate common protocol‑level attacks.<br> **Note:** These safeguards support application stability, but high‑volume DDoS and sophisticated bots require WAF or bot‑mitigation integrations described later. |Protects against common network attacks. |Low – Sensitive actions only |None – Enabled by default |-| **[Access Control](/entra/external-id/customers/how-to-use-app-roles-customers)** | Ensures users only access what they should by applying app roles and authorization rules.<br> **Note:** Access Control enforces authorization, not user verification -so combining it with MFA and adaptive controls enhances overall security. |Enforces authorization in applications. |Medium– User adoption |Medium – Setup required | +| **[Access Control](/entra/external-id/customers/how-to-use-app-roles-customers)** | Limits user access by applying app roles and authorization rules.<br> **Note:** Access control enforces authorization, not user verification. Combine it with MFA and adaptive controls to strengthen security. |Enforces authorization in applications. |Medium– User adoption |Medium – Setup required | | **[Enable multifactor authentication (MFA) for all users](concept-multifactor-authentication-customers.md)** |MFA adds a second verification step beyond passwords, significantly reducing the risk of account takeover.<br> **Note:** MFA limits stolen‑credential attacks but must be paired with fraud detection and monitoring to prevent automated or malicious sign‑up attempts. |Adds second factor authentication. |High – User adoption |Medium – Setup required | | **[Passkeys (FIDO2)](how-to-sign-in-with-passkey.md)** | Phishing-resistant, passwordless authentication that uses face, fingerprint, PIN, or a security key. A passkey satisfies MFA in a single gesture and can also serve as a primary, passwordless sign-in method. | Prevents phishing, password theft, and credential replay. | Low – Familiar gestures | Medium – Setup and credential management UX required | | **[Activity logging](/entra/identity/monitoring-health/concept-sign-ups) & [User insights](/entra/external-id/customers/how-to-user-insights)** |Activity logs and insights provide visibility into sign-ups, sign-ins, error patterns, and anomalies. They help you identify unusual trends and investigate issues quickly, supporting early detection, and informed decision making. |Enables threat detection. | None — No end-user impact |Medium – Setup required |@@ -57,7 +57,7 @@ Once baseline controls are in place, implement protections that materially impro | **Security feature** |**Description** |**Threats addressed** | **User impact** | **Implementation effort** | |----|----|----|----|----|-| **[Conditional Access](/entra/external-id/customers/concept-supported-features-customers#conditional-access)** | Customizable policies that trigger MFA to defend against threats like phishing and account takeovers. See [What is Conditional Access?](~/identity/conditional-access/overview.md) and [Developer guide to Conditional Access authentication context](~/identity-platform/developer-guide-conditional-access-authentication-context.md) for more information. |Provides risk-based access control. |Medium – User adoption |Medium – Setup required | +| **[Conditional Access](/entra/external-id/customers/concept-supported-features-customers#conditional-access)** | Configure policies to require MFA and manage sessions. Check control availability for your authentication integration, including [sign-in frequency (SIF)](../../identity/conditional-access/concept-session-lifetime.md#user-sign-in-frequency). See [What is Conditional Access?](~/identity/conditional-access/overview.md) and [Developer guide to Conditional Access authentication context](~/identity-platform/developer-guide-conditional-access-authentication-context.md) for more information. |Provides access control. |Medium – User adoption |Medium – Setup required | | **[Credential and secret management](/entra/architecture/deployment-external-operations#application-security-credential-and-secret-management)** |Prefer certificates over client secrets for app authentication to External ID because certificates are more secure and harder to compromise. |Secures app credentials. |None — No end-user impact |Medium – Setup required | | **[Token lifetime management](/entra/architecture/deployment-external-operations#risk-reduction-with-token-lifetime-management)** |Configure the token lifetime to reduce your app’s exposure to compromised tokens. |Limits exposure. |High – Requires frequent refreshes |Medium – Setup required | | **Custom Domain with Web Application Firewall (WAF)** |Use [Cloudflare](/entra/external-id/customers/how-to-configure-waf-integration), [Akamai](/entra/external-id/customers/how-to-configure-akamai-integration) or [Azure WAF](/entra/external-id/customers/tutorial-configure-external-id-web-app-firewall) for tenant security against DDoS attacks. |Provides DDoS and bot protection. | Medium – User adoption |High – WAF integration | 