From 4b101fb56033b791d008362e0803f1a79cba11a5 Mon Sep 17 00:00:00 2001 From: Gary Moore Date: Fri, 27 Dec 2019 15:52:52 -0800 Subject: [PATCH] Changed a list from ordered to unordered to meet style guidelines --- ...ot-store-lan-manager-hash-value-on-next-password-change.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/security-policy-settings/network-security-do-not-store-lan-manager-hash-value-on-next-password-change.md b/windows/security/threat-protection/security-policy-settings/network-security-do-not-store-lan-manager-hash-value-on-next-password-change.md index 49e3824a89..32ad4fc2b7 100644 --- a/windows/security/threat-protection/security-policy-settings/network-security-do-not-store-lan-manager-hash-value-on-next-password-change.md +++ b/windows/security/threat-protection/security-policy-settings/network-security-do-not-store-lan-manager-hash-value-on-next-password-change.md @@ -38,8 +38,8 @@ By attacking the SAM file, attackers can potentially gain access to user names a ### Best practices -1. Set **Network security: Do not store LAN Manager hash value on next password change** to **Enabled**. -2. Require all users to set new passwords the next time they log on to the domain so that LAN Manager hashes are removed. + - Set **Network security: Do not store LAN Manager hash value on next password change** to **Enabled**. + - Require all users to set new passwords the next time they log on to the domain so that LAN Manager hashes are removed. ### Location