19.06.2014 Views

Windows Server 2003 Recommended Baseline Security

Windows Server 2003 Recommended Baseline Security

Windows Server 2003 Recommended Baseline Security

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Unclassified ITSG for <strong>Windows</strong> <strong>Server</strong> <strong>2003</strong><br />

4.4.3.51 Network security: Do not store LAN Manager hash value on next password<br />

change<br />

machine\system\currentcontrolset\control\lsa\nolmhash=4, 1<br />

The ‘nolmhash’ registry value determines if the LAN Manager hash value is stored on the next<br />

password change. The setting ‘1’ does not save the LAN Manager hash value. This prevents<br />

local storage of the password, which would be vulnerable to attack.<br />

NOTE:<br />

Upon enabling in operation, all passwords must be changed.<br />

4.4.3.52 Network <strong>Security</strong>: Force logoff when logon hours expire<br />

ForceLogoffWhenHourExpire = 1<br />

The ‘ForceLogoffWhenHourExpire’ keyword determines if locally logged on users are<br />

disconnected when working outside of defined hours. The setting ‘1’ disconnects the user outside<br />

of defined hours. Hours are defined within the “Active Directory Users and Computers”, the<br />

‘Computer Management” and “Local Users and Groups” interface. Account should be created<br />

with restrictions on hours of access; we recommend enforcement through disconnection outside<br />

specified hours.<br />

4.4.3.53 Network security: LAN Manager authentication level<br />

machine\system\currentcontrolset\control\lsa\lmcompatibilitylevel=4, 5<br />

The ‘lmcompatibilitylevel’ value determines the level of LAN manager authentication. The<br />

setting ‘5’ sends NTLMv2 responses only and refuses LM & NTLM. This setting ensures only<br />

the most secure authentication mechanism is permitted.<br />

4.4.3.54 Network security: LDAP client signing requirements<br />

machine\system\currentcontrolset\services\ldap\ldapclientintegrity=4, 1<br />

The ‘ldapclientintegrity’ value determines if the LDAP client negotiates signing to communicate<br />

with LDAP servers. The setting ‘2’ requires signing negotiation. This reduces the threat of a<br />

man-in-the-middle attacks.<br />

4.4.3.55 Network security: Minimum session security for NTLM SSP based (including<br />

secure RPC) clients<br />

machine\system\currentcontrolset\control\lsa\msv1_0\ntlmminclientsec=4, 537395248<br />

The ‘ntlmminclientsec’ value defines the minimum session security for NTLM SSP based<br />

(including secure RPC) clients. The setting ‘537395248’ enables all options, as recommended.<br />

This requires message integrity, confidentiality, NTLMv2 session security and 128-bit<br />

encryption be used for logon.<br />

66 March 2004 <strong>Server</strong> Policy Files

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!