Skip to content

Commit c7d6dd1

Browse files
authored
Update attack-surface-reduction-rules-reference.md
1 parent f591591 commit c7d6dd1

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

defender-endpoint/attack-surface-reduction-rules-reference.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
- m365-security
1616
- tier2
1717
- mde-asr
18-
ms.date: 05/02/2024
18+
ms.date: 09/07/2024
1919
search.appverid: met150
2020
---
2121

@@ -109,7 +109,6 @@ The following ASR rules DO NOT honor Microsoft Defender for Endpoint Indicators
109109
The following table lists the supported operating systems for rules that are currently released to general availability. The rules are listed alphabetical order in this table.
110110

111111
> [!NOTE]
112-
>
113112
> Unless otherwise indicated, the minimum Windows 10 build is version 1709 (RS3, build 16299) or later; the minimum Windows Server build is version 1809 or later.
114113
>
115114
> Attack surface reduction rules in Windows Server 2012 R2 and Windows Server 2016 are available for devices onboarded using the modern unified solution package. For more information, see [New Windows Server 2012 R2 and 2016 functionality in the modern unified solution](configure-server-endpoints.md#functionality-in-the-modern-unified-solution).
@@ -257,7 +256,6 @@ This rule prevents an application from writing a vulnerable signed driver to dis
257256
The **Block abuse of exploited vulnerable signed drivers** rule doesn't block a driver already existing on the system from being loaded.
258257

259258
> [!NOTE]
260-
>
261259
> You can configure this rule using Intune OMA-URI. See [Intune OMA-URI](enable-attack-surface-reduction.md#custom-profile-in-intune) for configuring custom rules.
262260
>
263261
> You can also configure this rule using [PowerShell](enable-attack-surface-reduction.md#powershell).
@@ -323,7 +321,8 @@ Dependencies: Microsoft Defender Antivirus
323321
### Block credential stealing from the Windows local security authority subsystem
324322

325323
> [!NOTE]
326-
> If you have [LSA protection](/windows-server/security/credentials-protection-and-management/configuring-additional-lsa-protection) enabled and [Credential Guard](/windows/security/identity-protection/credential-guard) enabled this ASR rule is not required.
324+
> If you have [LSA protection](/windows-server/security/credentials-protection-and-management/configuring-additional-lsa-protection) enabled and [Credential Guard](/windows/security/identity-protection/credential-guard) enabled, this attack surface reduction rule is not required.
325+
327326
This rule helps prevent credential stealing by locking down Local Security Authority Subsystem Service (LSASS).
328327

329328
LSASS authenticates users who sign in on a Windows computer. Microsoft Defender Credential Guard in Windows normally prevents attempts to extract credentials from LSASS. Some organizations can't enable Credential Guard on all of their computers because of compatibility issues with custom smartcard drivers or other programs that load into the Local Security Authority (LSA). In these cases, attackers can use tools like Mimikatz to scrape cleartext passwords and NTLM hashes from LSASS.

0 commit comments

Comments
 (0)