Skip to content

Commit 2271c16

Browse files
authored
Merge pull request #179777 from sjiang26/patch-9
Update threat-management.md
2 parents 875a579 + 486a545 commit 2271c16

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

articles/active-directory-b2c/threat-management.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -14,10 +14,12 @@ ms.author: kengaderdus
1414
ms.subservice: B2C
1515
---
1616

17-
# Mitigate credential attacks in Azure AD B2C
17+
# Mitigate credential attacks in Azure AD B2C with smart lockout
1818

1919
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.
2020

21+
## How smart lockout works
22+
2123
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.
2224

2325
> [!NOTE]
@@ -27,16 +29,16 @@ Azure AD B2C uses a sophisticated strategy to lock accounts. The accounts are lo
2729

2830
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).
2931

30-
## Manage password protection settings
32+
## Manage smart lockout settings
3133

32-
To manage password protection settings, including the lockout threshold:
34+
To manage smart lockout settings, including the lockout threshold:
3335

3436
1. Sign in to the [Azure portal](https://portal.azure.com)
3537
1. Make sure you're using the directory that contains your Azure AD B2C tenant. Select the **Directories + subscriptions** icon in the portal toolbar.
3638
1. On the **Portal settings | Directories + subscriptions** page, find your Azure AD B2C directory in the **Directory name** list, and then select **Switch**.
3739
1. In the left menu, select **Azure AD B2C**. Or, select **All services** and search for and select **Azure AD B2C**.
3840
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:
4042

4143
- **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.
4244
- **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:
4648

4749
1. Select **Save**.
4850

49-
## Testing the password protection settings
51+
## Testing smart lockout
5052

5153
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:
5254

0 commit comments

Comments
 (0)