mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-20 04:43:37 +00:00
Merge branch 'main' into updateseeker-7991583
This commit is contained in:
@ -2,7 +2,7 @@
|
||||
title: Understand Windows Defender Application Control (WDAC) policy rules and file rules
|
||||
description: Learn how WDAC policy rules and file rules can control your Windows 10 and Windows 11 computers.
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 06/07/2023
|
||||
ms.date: 08/11/2023
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
@ -127,7 +127,7 @@ Filepath rules don't provide the same security guarantees that explicit signer r
|
||||
|
||||
### User-writable filepaths
|
||||
|
||||
By default, WDAC performs a user-writeability check at runtime that ensures that the current permissions on the specified filepath and its parent directories (recursively) don't allow standard users write access.
|
||||
By default, WDAC performs a user-writeability check at runtime that ensures that the current permissions on the specified filepath only allow write access for admin users.
|
||||
|
||||
There's a defined list of SIDs that WDAC recognizes as admins. If a filepath allows write permissions for any SID not in this list, the filepath is considered to be user-writeable, even if the SID is associated to a custom admin user. To handle these special cases, you can override WDAC's runtime admin-writeable check with the **Disabled:Runtime FilePath Rule Protection** option described earlier.
|
||||
|
||||
|
@ -72,7 +72,7 @@ productDirectory:
|
||||
links:
|
||||
- url: /windows/security/identity-protection/hello-for-business
|
||||
text: Windows Hello for Business
|
||||
- url: /windows/security/identity-protection/credential-guard/credentail-guard
|
||||
- url: /windows/security/identity-protection/credential-guard/credential-guard
|
||||
text: Windows Defender Credential Guard
|
||||
- url: /windows-server/identity/laps/laps-overview
|
||||
text: Windows LAPS (Local Administrator Password Solution)
|
||||
|
Reference in New Issue
Block a user