Update hello-for-business/passwordless-strategy.md

Change in line 33: "the user knows they have a password"
replaced with "the users know they have a password"
to match the plural 'users' referenced elsewhere.
This commit is contained in:
illfated 2019-06-12 23:01:16 +02:00
parent b2336814df
commit 968acf48e9

View File

@ -30,7 +30,7 @@ Before you move away from passwords, you need something to replace them. With Wi
Deploying Windows Hello for Business is the first step towards a passwordless environment. Windows Hello for Business coexists nicely with existing password-based security. Users are likely to use Windows Hello for Business because of its convenience, especially when combined with biometrics. However, some workflows and applications may still need passwords. This early stage is about implementing an alternative and getting users used to it. Deploying Windows Hello for Business is the first step towards a passwordless environment. Windows Hello for Business coexists nicely with existing password-based security. Users are likely to use Windows Hello for Business because of its convenience, especially when combined with biometrics. However, some workflows and applications may still need passwords. This early stage is about implementing an alternative and getting users used to it.
### 2. Reduce user-visible password surface area ### 2. Reduce user-visible password surface area
With Windows Hello for Business and passwords coexisting in your environment, the next step is to reduce the password surface. The environment and workflows need to stop asking for passwords. The goal of this step is to achieve a state where the user knows they have a password, but they never use it. This state helps decondition users from providing a password any time a password prompt shows on their computer. This is how passwords are phished. Users who rarely, if at all, use their password are unlikely to provide it. Password prompts are no longer the norm. With Windows Hello for Business and passwords coexisting in your environment, the next step is to reduce the password surface. The environment and workflows need to stop asking for passwords. The goal of this step is to achieve a state where the users know they have a password, but they never use it. This state helps decondition users from providing a password any time a password prompt shows on their computer. This is how passwords are phished. Users who rarely, if at all, use their password are unlikely to provide it. Password prompts are no longer the norm.
### 3. Transition into a passwordless deployment ### 3. Transition into a passwordless deployment
Once the user-visible password surface has been eliminated, your organization can begin to transition those users into a passwordless world. A world where: Once the user-visible password surface has been eliminated, your organization can begin to transition those users into a passwordless world. A world where: