From 04ca4bd929f71854c79b729f0381cab7bf2e2153 Mon Sep 17 00:00:00 2001 From: davidpaMSFT Date: Thu, 27 Jul 2017 14:07:00 -0400 Subject: [PATCH] Update network-security-minimum-session-security-for-ntlm-ssp-based-including-secure-rpc-clients.md --- ...ecurity-for-ntlm-ssp-based-including-secure-rpc-clients.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/device-security/security-policy-settings/network-security-minimum-session-security-for-ntlm-ssp-based-including-secure-rpc-clients.md b/windows/device-security/security-policy-settings/network-security-minimum-session-security-for-ntlm-ssp-based-including-secure-rpc-clients.md index b9a0e71329..3f98b0d5f2 100644 --- a/windows/device-security/security-policy-settings/network-security-minimum-session-security-for-ntlm-ssp-based-including-secure-rpc-clients.md +++ b/windows/device-security/security-policy-settings/network-security-minimum-session-security-for-ntlm-ssp-based-including-secure-rpc-clients.md @@ -24,11 +24,11 @@ This policy setting allows a client device to require the negotiation of 128-bit - Require NTLMv2 session security - The connection fails if strong encryption (128-bit) is not negotiated. + The connection fails if the NTLMv2 protocol is not negotiated. - Require 128-bit encryption - The connection fails if the NTLMv2 protocol is not negotiated. + The connection fails if strong encryption (128-bit) is not negotiated. ### Best practices