mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
updates
This commit is contained in:
parent
70a298605c
commit
373d4c43c7
@ -25,7 +25,7 @@ To create a smooth user experience that aligns with nonisolated, native Win32 ap
|
||||
- Approaches for accessing data and privacy information
|
||||
- Integrating Win32 apps for compatibility with other Windows interfaces
|
||||
|
||||
The first factor relates to implementing methods to manage access to files and privacy information within and outside the isolation boundary ([AppContainer][LINK-3]). The second factor involves integrating Win32 apps with other Windows interfaces in a way that helps enable seamless functionality without causing perplexing user consent prompts.
|
||||
The first factor relates to implementing methods to manage access to files and privacy information within and outside the isolation boundary AppContainer. The second factor involves integrating Win32 apps with other Windows interfaces in a way that helps enable seamless functionality without causing perplexing user consent prompts.
|
||||
|
||||
:::image type="icon" source="images/learn-more.svg" border="false"::: **Learn more:**
|
||||
|
||||
@ -86,7 +86,6 @@ A **Virtualization-based security enclave** is a software-based trusted executio
|
||||
|
||||
[LINK-1]: /windows/win32/secauthz/implementing-an-appcontainer
|
||||
[LINK-2]: /windows/win32/secauthz/access-control-lists
|
||||
[LINK-3]: /windows/win32/secauthz/implementing-an-appcontainer
|
||||
[LINK-4]: https://github.com/microsoft/win32-app-isolation
|
||||
[LINK-5]: https://github.com/microsoft/win32-app-isolation/blob/main/docs/profiler/application-capability-profiler.md
|
||||
[LINK-6]: https://github.com/microsoft/win32-app-isolation/blob/main/docs/packaging/packaging-with-visual-studio.md
|
||||
|
@ -16,6 +16,7 @@ We will continue to bring you new features to protect against evolving threats,
|
||||
New:
|
||||
|
||||
- [Config Refresh](operating-system-security-system-security.md#config-refresh)
|
||||
- [Passkeys](identity-protection-passwordless-sign-in.md#passkeys)
|
||||
- [Trusted signing](application-security-application-and-driver-control.md#trusted-signing)
|
||||
- [VBS Key Protection](identity-protection-advanced-credential-protection.md#vbs-key-protection)
|
||||
- [Virtualization-based security enclave](application-security-application-isolation.md#virtualization-based-security-enclave)
|
||||
|
@ -129,22 +129,21 @@ Enhanced Sign-in Security is configured by device manufacturers during the manuf
|
||||
|
||||
- [Windows Hello Enhanced Sign-in Security][LINK-5]
|
||||
|
||||
|
||||
### Passkeys
|
||||
|
||||
Windows 11 makes it much harder for hackers who exploit stolen passwords via phishing attacks by empowering users to replace passwords with passkeys. Passkeys are the cross-platform future of secure sign-in. Microsoft and other technology leaders are supporting passkeys across their platforms and services.
|
||||
|
||||
A passkey is a unique, unguessable cryptographic secret that is securely stored on the device. Instead of using a username and password to sign in to a website or application, Windows 11 users can create and use a passkey with Windows Hello, a third-party passkey provider, an external FIDO2 security key, or their mobile device.
|
||||
A passkey is a unique, unguessable cryptographic secret that is securely stored on the device. Instead of using a username and password to sign in to a website or application, Windows 11 users can create and use a passkey with Windows Hello, a third-party passkey provider, an external FIDO2 security key, or their mobile device. Passkeys on Windows work in any browsers or apps that support them for sign in.
|
||||
|
||||
Passkeys created and saved with Windows Hello are protected by Windows Hello or Windows Hello for Business and are managed on the Windows 11 device account settings. When a third-party passkey provider is used, passkeys are protected and managed by the third-party. Users can sign in to the site or app using their face, fingerprint, or device PIN. Passkeys on Windows work in any browsers or apps that support them for sign in.
|
||||
Passkeys created and saved with Windows Hello are protected by Windows Hello or Windows Hello for Business. Users can sign in to the site or app using their face, fingerprint, or device PIN. Users can manage their passkeys from **Settings** > **Accounts** > **Passkeys**.
|
||||
|
||||
🔜 Coming soon in Windows 11, version 24H2, a plug-in model for 3rd party passkey providers allows users to manage their passkeys with third-party passkey managers. This model is designed to provide a seamless platform experience, whether passkeys are managed directly by Windows or by a third-party authenticator. When a third-party passkey provider is used, passkeys are protected and managed by the third-party.
|
||||
|
||||
:::image type="icon" source="images/learn-more.svg" border="false"::: **Learn more:**
|
||||
|
||||
- [Support for passkeys in Windows][LINK-10]
|
||||
- [Enable passkeys (FIDO2) for your organization][LINK-9]
|
||||
|
||||
|
||||
## FIDO2
|
||||
|
||||
The FIDO Alliance, the Fast Identity Online industry standards body, was established to promote authentication technologies and standards that reduce reliance on passwords. FIDO Alliance and World Wide Web Consortium (W3C) have worked together to define the Client to Authenticator Protocol (CTAP2) and Web Authentication (WebAuthn) specifications, which are the industry standard for providing strong, phishing-resistant, user friendly, and privacy preserving authentication across the web and apps. FIDO standards and certifications are becoming recognized as the leading standard for creating secure authentication solutions across enterprises, governments, and consumer markets.
|
||||
|
Binary file not shown.
Before Width: | Height: | Size: 161 KiB After Width: | Height: | Size: 151 KiB |
Loading…
x
Reference in New Issue
Block a user