You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/threat-management.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,10 +14,12 @@ ms.author: kengaderdus
14
14
ms.subservice: B2C
15
15
---
16
16
17
-
# Mitigate credential attacks in Azure AD B2C
17
+
# Mitigate credential attacks in Azure AD B2C with smart lockout
18
18
19
19
Credential attacks lead to unauthorized access to resources. Passwords that are set by users are required to be reasonably complex. Azure AD B2C has mitigation techniques in place for credential attacks. Mitigation includes detection of brute-force credential attacks and dictionary credential attacks. By using various signals, Azure Active Directory B2C (Azure AD B2C) analyzes the integrity of requests. Azure AD B2C is designed to intelligently differentiate intended users from hackers and botnets.
20
20
21
+
## How smart lockout works
22
+
21
23
Azure AD B2C uses a sophisticated strategy to lock accounts. The accounts are locked based on the IP of the request and the passwords entered. The duration of the lockout also increases based on the likelihood that it's an attack. After a password is tried 10 times unsuccessfully (the default attempt threshold), a one-minute lockout occurs. The next time a login is unsuccessful after the account is unlocked (that is, after the account has been automatically unlocked by the service once the lockout period expires), another one-minute lockout occurs and continues for each unsuccessful login. Entering the same, or similar password repeatedly doesn't count as multiple unsuccessful logins.
22
24
23
25
> [!NOTE]
@@ -27,16 +29,16 @@ Azure AD B2C uses a sophisticated strategy to lock accounts. The accounts are lo
27
29
28
30
The first 10 lockout periods are one minute long. The next 10 lockout periods are slightly longer and increase in duration after every 10 lockout periods. The lockout counter resets to zero after a successful login when the account isn’t locked. Lockout periods can last up to five hours. Users must wait for the lockout duration to expire. However, the user can unlock by using self-service [password user flow](add-password-reset-policy.md).
29
31
30
-
## Manage password protection settings
32
+
## Manage smart lockout settings
31
33
32
-
To manage password protection settings, including the lockout threshold:
34
+
To manage smart lockout settings, including the lockout threshold:
33
35
34
36
1. Sign in to the [Azure portal](https://portal.azure.com)
35
37
1. Make sure you're using the directory that contains your Azure AD B2C tenant. Select the **Directories + subscriptions** icon in the portal toolbar.
36
38
1. On the **Portal settings | Directories + subscriptions** page, find your Azure AD B2C directory in the **Directory name** list, and then select **Switch**.
37
39
1. In the left menu, select **Azure AD B2C**. Or, select **All services** and search for and select **Azure AD B2C**.
38
40
1. Under **Security**, select **Authentication methods (Preview)**, then select **Password protection**.
39
-
1. Under **Custom smart lockout**, enter your desired password protection settings:
41
+
1. Under **Custom smart lockout**, enter your desired smart lockout settings:
40
42
41
43
-**Lockout threshold**: The number of failed sign-in tries that are allowed before the account is first locked out. If the first sign-in after a lockout also fails, the account locks again.
42
44
-**Lockout duration in seconds**: The minimum duration of each lockout in seconds. If an account locks repeatedly, this duration increases.
@@ -46,7 +48,7 @@ To manage password protection settings, including the lockout threshold:
46
48
47
49
1. Select **Save**.
48
50
49
-
## Testing the password protection settings
51
+
## Testing smart lockout
50
52
51
53
The smart lockout feature uses many factors to determine when an account should be locked, but the primary factor is the password pattern. The smart lockout feature considers slight variations of a password as a set, and they’re counted as a single try. For example:
0 commit comments