<?xml version="1.0" encoding="utf-8"?>
<SCMPackage xsi:schemaLocation="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance xtrans20-definitions-schema.xsd" xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance">
<FormatInfo>
<Version Major="1" Minor="0" />
<Description>
</Description>
</FormatInfo>
<Baseline ID="{2ba13f5e-41e4-4719-8459-7ebb3750384e}" Name="Win7SP1 Computer Security Compliance" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Description>The Computer baseline includes settings to configure desktop and mobile computers.</mssasc-core:Description>
<mssasc-core:Version Major="1" Minor="0" />
<Mode Mode="Published" />
<VersionControl>
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<OriginalBaselineID>{2ba13f5e-41e4-4719-8459-7ebb3750384e}</OriginalBaselineID>
<RevisionNumber>1</RevisionNumber>
<OriginalRevisionNumber>1</OriginalRevisionNumber>
</VersionControl>
<SettingGroup ID="{be634a0e-361d-4a73-949a-6ed7a95d011f}" Name="Authentication Types" OriginalSettingGroupID="{5bab3b52-628d-430c-8d6d-d27f5eb0ea7f}">
<mssasc-core:Description>
</mssasc-core:Description>
<mssasc-core:Version Major="1" Minor="0" />
<Author>
</Author>
<Setting Index="24" ID="{4d0beb7d-f233-4024-9ee4-4580d68e3ebe}" OriginalSettingID="{d252220c-49aa-4a96-9f39-b59eb2be29d4}" Name="Network Security: Restrict NTLM: Add remote server exceptions for NTLM authentication" LockdownDate="2011-05-02T01:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9036-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to create an exception list of remote servers to which clients are allowed to use NTLM authentication if the "Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers" policy setting is configured.</ShortDescription>
<FullDescription>This policy setting allows you to create an exception list of remote servers to which clients are allowed to use NTLM authentication if the "Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers" policy setting is configured.
The naming format for servers on this exception list is the fully qualified domain name (FQDN) or NetBIOS server name used by the application, listed one per line. To ensure exceptions the name used by all applications needs to be in the list, and to ensure an exception is accurate, the server name should be listed in both naming formats . A single asterisk (*) can be used anywhere in the string as a wildcard character.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>NTLM is a Microsoft-developed authentication protocol that uses a challenge-response mechanism for authentication, in which client computers can prove their identities without sending a password to the server. The protocol employs three types of messages to negotiate the request, challenge the authenticity of the sender, and perform the authentication. Kerberos is a more robust protocol and is the preferred method of authentication when available. </Vulnerability>
<Countermeasure>Add the FQDNs and NetBIOS names of remote servers to which you want this host to be able to authenticate via NTLM.</Countermeasure>
<PotentialImpact>If you configure this policy setting, you can define a list of remote servers to which clients are allowed to use NTLM authentication.
If you do not configure this policy setting, no exceptions will be applied.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_MULTI_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa\MSV1_0</mssasc-core:KeyPath>
<mssasc-core:ValueName>ClientAllowedNTLMServers</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Multi-String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHIEN\System\CurrentControlSet\Control\Lsa\MSV1_0\ClientAllowedNTLMServers" DataType="REG_MULTI_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="25" ID="{2cb1f8c6-e95d-4765-baab-37e1f4f9c4a9}" OriginalSettingID="{794f9728-56e1-4e5e-b697-7079757f4ac3}" Name="Network security: Do not store LAN Manager hash value on next password change" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8937-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether the LAN Manager (LM) hash value for the new password is stored when the password is changed. </ShortDescription>
<FullDescription>This policy setting determines whether the LAN Manager (LM) hash value for the new password is stored when the password is changed. The LM hash is relatively weak and prone to attack compared to the cryptographically stronger Microsoft Windows NT® hash.
Note Older operating systems and some third-party applications may fail when this policy setting is enabled. Also you will need to change the password on all accounts after you enable this setting.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>The SAM file can be targeted by attackers who seek access to username and password hashes. Such attacks use special tools to crack passwords, which can then be used to impersonate users and gain access to resources on your network. These types of attacks will not be prevented if you enable this policy setting, but it will be much more difficult for these types of attacks to succeed.</Vulnerability>
<Countermeasure>Configure the Network security: Do not store LAN Manager hash value on next password change setting to Enabled. Require all users to set new passwords the next time they log in to the domain so that LAN Manager hashes are removed.</Countermeasure>
<PotentialImpact>Earlier operating systems such as Windows 95, Windows 98, and Windows ME as well as some third-party applications will fail.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>NoLMHash</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\NoLMHash" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:95" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="26" ID="{3b89eaba-a593-4ab4-9da6-e62124a4748a}" OriginalSettingID="{8d872ca4-b77a-485e-bfad-cd8a311210a9}" Name="Network Security: Allow PKU2U authentication requests to this computer to use online identities" LockdownDate="2011-05-02T01:36:03Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9770-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy will be turned off by default on domain joined machines. This would disallow the online identities to be able to authenticate to the domain joined machine in Windows 7.</ShortDescription>
<FullDescription>Windows 7 and Windows Server 2008 R2 introduce an extension to the Negotiate authentication package, Spnego.dll. In previous versions of Windows, Negotiate decides whether to use Kerberos or NTLM for authentication. The extension SSP for Negotiate, Negoexts, which is treated as an authentication protocol by Windows, supports Microsoft SSPs including PKU2U. You can also develop or add other SSPs.
When computers are configured to accept authentication requests by using online IDs, Negoexts.dll calls the PKU2U SSP on the computer that is used to log on. The PKU2U SSP obtains a local certificate and exchanges the policy between the peer computers. When validated on the peer computer, the certificate within the metadata is sent to the logon peer for validation and associates the user's certificate to a security token and the logon process completes.
This policy will be turned off by default on domain joined machines. This would disallow the online identities to be able to authenticate to the domain joined machine in Windows 7.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>The PKU2U protocol is a peer-to-peer authentication protocol, in most managed networks authentication should be managed centrally.</Vulnerability>
<Countermeasure>Configure Network Security: Allow PKU2U authentication requests to this computer to use online identities to disabled.</Countermeasure>
<PotentialImpact>Disabling this setting will disallow the online identities to be able to authenticate to the domain joined machine in Windows 7.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa\pku2u</mssasc-core:KeyPath>
<mssasc-core:ValueName>AllowOnlineID</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\pku2u\AllowOnlineID" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="27" ID="{e7ebae2a-912a-4fb1-a92b-e2b9f346baf8}" OriginalSettingID="{ec468e43-6141-4bfe-970f-ca02d37d0ca7}" Name="Network security: LAN Manager authentication level" LockdownDate="2011-10-12T11:37:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8806-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting specifies the type of challenge/response authentication for network logons. LAN Manager (LM) authentication is the least secure method; it allows encrypted passwords to be cracked because they can be easily intercepted on the network. </ShortDescription>
<FullDescription>LAN Manager (LM) is a family of early Microsoft client/server software that allows users to link personal computers together on a single network. Network capabilities include transparent file and print sharing, user security features, and network administration tools. In Active Directory domains, the Kerberos protocol is the default authentication protocol. However, if the Kerberos protocol is not negotiated for some reason, Active Directory will use LM, NTLM, or NTLMv2.
LAN Manager authentication includes the LM, NTLM, and NTLM version 2 (NTLMv2) variants, and is the protocol that is used to authenticate all Windows clients when they perform the following operations:
• Join a domain
• Authenticate between Active Directory forests
• Authenticate to down-level domains
• Authenticate to computers that do not run Windows 2000, Windows Server 2003, or Windows XP)
• Authenticate to computers that are not in the domain
The possible values for the Network security: LAN Manager authentication level setting are:
• Send LM & NTLM responses
• Send LM & NTLM — use NTLMv2 session security if negotiated
• Send NTLM responses only
• Send NTLMv2 responses only
• Send NTLMv2 responses only\refuse LM
• Send NTLMv2 responses only\refuse LM & NTLM
• Not Defined
The Network security: LAN Manager authentication level setting determines which challenge/response authentication protocol is used for network logons. This choice affects the authentication protocol level that clients use, the session security level that the computers negotiate, and the authentication level that servers accept as follows:
• Send LM & NTLM responses. Clients use LM and NTLM authentication and never use NTLMv2 session security. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
• Send LM & NTLM – use NTLMv2 session security if negotiated. Clients use LM and NTLM authentication and use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
• Send NTLM response only. Clients use NTLM authentication only and use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
• Send NTLMv2 response only. Clients use NTLMv2 authentication only and use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
• Send NTLMv2 response only\refuse LM. Clients use NTLMv2 authentication only and use NTLMv2 session security if the server supports it. Domain controllers refuse LM (accept only NTLM and NTLMv2 authentication).
• Send NTLMv2 response only\refuse LM & NTLM. Clients use NTLMv2 authentication only and use NTLMv2 session security if the server supports it. Domain controllers refuse LM and NTLM (accept only NTLMv2 authentication).
These settings correspond to the levels discussed in other Microsoft documents as follows:
• Level 0 – Send LM and NTLM response; never use NTLMv2 session security. Clients use LM and NTLM authentication, and never use NTLMv2 session security. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
• Level 1 – Use NTLMv2 session security if negotiated. Clients use LM and NTLM authentication, and use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
• Level 2 – Send NTLM response only. Clients use only NTLM authentication, and use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
• Level 3 – Send NTLMv2 response only. Clients use NTLMv2 authentication, and use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
• Level 4 – Domain controllers refuse LM responses. Clients use NTLM authentication, and use NTLMv2 session security if the server supports it. Domain controllers refuse LM authentication, that is, they accept NTLM and NTLMv2.
• Level 5 – Domain controllers refuse LM and NTLM responses (accept only NTLMv2). Clients use NTLMv2 authentication, use and NTLMv2 session security if the server supports it. Domain controllers refuse NTLM and LM authentication (they accept only NTLMv2).</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Send NTLMv2 response only</DefaultValue>
<Vulnerability>In Windows Vista, this setting is undefined. However, in Windows 2000, Windows Server 2003, and Windows XP clients are configured by default to send LM and NTLM authentication responses (Windows 95-based and Windows 98-based clients only send LM). The default setting on servers allows all clients to authenticate with servers and use their resources. However, this means that LM responses—the weakest form of authentication response—are sent over the network, and it is potentially possible for attackers to sniff that traffic to more easily reproduce the user’s password.
The Windows 95, Windows 98, and Windows NT operating systems cannot use the Kerberos version 5 protocol for authentication. For this reason, in a Windows Server 2003 domain, these computers authenticate by default with both the LM and NTLM protocols for network authentication. You can enforce a more secure authentication protocol for Windows 95, Windows 98, and Windows NT by using NTLMv2. For the logon process, NTLMv2 uses a secure channel to protect the authentication process. Even if you use NTLMv2 for earlier clients and servers, Windows-based clients and servers that are members of the domain will use the Kerberos authentication protocol to authenticate with Windows Server 2003 domain controllers.</Vulnerability>
<Countermeasure>Configure the Network security: LAN Manager Authentication Level setting to Send NTLMv2 responses only. We and a number of independent organizations strongly recommend this level of authentication when all clients support NTLMv2.
For more information about how to enable NTLMv2 on older versions of Windows, see article 239869, How to enable NTLM 2 authentication, in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=100904). Microsoft Windows NT 4.0 requires Service Pack 4 (SP4) to support NTLMv2, and Windows 95 and Windows 98 platforms need the directory service client installed to support NTLMv2.
</Countermeasure>
<PotentialImpact>Clients that do not support NTLMv2 authentication will not be able to authenticate in the domain and access domain resources by using LM and NTLM.
Note: For information about a hotfix to ensure that this setting works in networks that include Windows NT 4.0-based computers along with Windows 2000, Windows XP, and Windows Server 2003-based computers, see article 305379, Authentication Problems in Windows 2000 with NTLM 2 Levels Above 2 in a Windows NT 4.0 Domain, in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=100907).
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Send NTLMv2 response only. Refuse LM & NTLM">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Send LM & NTLM responses">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Send LM & NTLM - use NTLMv2 session security if negotiated">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Send NTLM response only">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
<Mapping FriendlyName="Send NTLMv2 response only">
<BehaviorDescription />
<DCMValue ValueA="3" />
<SCAPValue ValueA="3" />
<GPOValue ValueA="3" />
</Mapping>
<Mapping FriendlyName="Send NTLMv2 response only. Refuse LM">
<BehaviorDescription />
<DCMValue ValueA="4" />
<SCAPValue ValueA="4" />
<GPOValue ValueA="4" />
</Mapping>
<Mapping FriendlyName="Send NTLMv2 response only. Refuse LM & NTLM">
<BehaviorDescription />
<DCMValue ValueA="5" />
<SCAPValue ValueA="5" />
<GPOValue ValueA="5" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>LmCompatibilityLevel</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\LmCompatibilityLevel" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:97, oval:gov.nist.1:def:96" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="28" ID="{97ec51b5-9da5-4043-940f-f8d8282e9af2}" OriginalSettingID="{b1b4a762-3114-438b-92cf-90f021714790}" Name="Microsoft network client: Send unencrypted password to third-party SMB servers" LockdownDate="2011-05-02T01:36:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9265-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Disable this policy setting to prevent the SMB redirector from sending plaintext passwords during authentication to third-party SMB servers that do not support password encryption. </ShortDescription>
<FullDescription>Disable this policy setting to prevent the SMB redirector from sending plaintext passwords during authentication to third-party SMB servers that do not support password encryption. Microsoft recommends that you disable this policy setting unless there is a strong business case to enable it. If this policy setting is enabled, unencrypted passwords will be allowed across the network.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>If you enable this policy setting, the server can transmit passwords in plaintext across the network to other computers that offer SMB services. These other computers may not use any of the SMB security mechanisms that are included with Windows Server 2003. </Vulnerability>
<Countermeasure>Configure the Microsoft network client: Send unencrypted password to connect to third-party SMB servers setting to Disabled. </Countermeasure>
<PotentialImpact>Some very old applications and operating systems such as MS-DOS, Windows for Workgroups 3.11, and Windows 95a may not be able to communicate with the servers in your organization by means of the SMB protocol.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanmanWorkstation\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnablePlainTextPassword</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters\EnablePlainTextPassword" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:82" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="29" ID="{00cb2759-acdf-40c1-8f0a-0983f8071c34}" OriginalSettingID="{0c907d9a-4c08-4440-abf8-8b7bbe24bfd3}" Name="Network Security: Restrict NTLM: Audit NTLM authentication in this domain" LockdownDate="2011-05-02T01:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9604-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to audit NTLM authentication in a domain from this domain controller.</ShortDescription>
<FullDescription>This policy setting allows you to audit NTLM authentication in a domain from this domain controller.
This policy is supported on at least Windows Server 2008 R2.
Note: Audit events are recorded on this computer in the "Operational" Log located under the Applications and Services Log/Microsoft/Windows/NTLM.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>NTLM is a Microsoft-developed authentication protocol that uses a challenge-response mechanism for authentication, in which client computers can prove their identities without sending a password to the server. The protocol employs three types of messages to negotiate the request, challenge the authenticity of the sender, and perform the authentication. Kerberos is a more robust protocol and is the preferred method of authentication when available. </Vulnerability>
<Countermeasure>Configure Network Security: Restrict NTLM: Audit NTLM authentication in this domain to </Countermeasure>
<PotentialImpact>
If you select "Disable" or do not configure this policy setting, the domain controller will not log events for NTLM authentication in this domain.
If you select "Enable for domain accounts to domain servers," the domain controller will log events for NTLM authentication logon attempts for domain accounts to domain servers when NTLM authentication would be denied because "Deny for domain accounts to domain servers" is selected in the "Network security: Restrict NTLM: NTLM authentication in this domain" policy setting.
If you select "Enable for domain accounts," the domain controller will log events for NTLM authentication logon attempts that use domain accounts when NTLM authentication would be denied because "Deny for domain accounts" is selected in the "Network security: Restrict NTLM: NTLM authentication in this domain" policy setting.
If you select "Enable for domain servers" the domain controller will log events for NTLM authentication requests to all servers in the domain when NTLM authentication would be denied because "Deny for domain servers" is selected in the "Network security: Restrict NTLM: NTLM authentication in this domain" policy setting.
If you select "Enable all" the domain controller will log events for NTLM pass-through authentication requests from its servers and for its accounts which would be denied because "Deny all" is selected in the "Network security: Restrict NTLM: NTLM authentication in this domain" policy setting.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disable">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enable for domain accounts to domain servers">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Enable for domain accounts">
<BehaviorDescription />
<DCMValue ValueA="3" />
<SCAPValue ValueA="3" />
<GPOValue ValueA="3" />
</Mapping>
<Mapping FriendlyName="Enable for domain servers">
<BehaviorDescription />
<DCMValue ValueA="5" />
<SCAPValue ValueA="5" />
<GPOValue ValueA="5" />
</Mapping>
<Mapping FriendlyName="Enable all">
<BehaviorDescription />
<DCMValue ValueA="7" />
<SCAPValue ValueA="7" />
<GPOValue ValueA="7" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Netlogon\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>AuditNTLMInDomain</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\AuditNTLMInDomain" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="30" ID="{34e2a485-7cf2-4009-953c-aebc160866ce}" OriginalSettingID="{9969a7db-5fd1-4713-9a26-9862c15359e9}" Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) clients" LockdownDate="2011-10-12T11:37:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9534-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Network security: Minimum session security for NTLM SSP based (including secure RPC) client applications.
</ShortDescription>
<FullDescription>This policy setting determines which behaviors are allowed for applications using the NTLM Security Support Provider (SSP). The SSP Interface (SSPI) is used by applications that need authentication services. The setting does not modify how the authentication sequence works but instead require certain behaviors in applications that use the SSPI.
The possible values for the Network security: Minimum session security for NTLM SSP based (including secure RPC) clients setting are:
• Require message confidentiality. This option is only available in Windows XP and Windows Server 2003, the connection will fail if encryption is not negotiated. Encryption converts data into a form that is not readable until decrypted.
• Require message integrity. This option is only available in Windows XP and Windows Server 2003, the connection will fail if message integrity is not negotiated. The integrity of a message can be assessed through message signing. Message signing proves that the message has not been tampered with; it attaches a cryptographic signature that identifies the sender and is a numeric representation of the contents of the message.
• Require 128-bit encryption. The connection will fail if strong encryption (128-bit) is not negotiated.
• Require NTLMv2 session security. The connection will fail if the NTLMv2 protocol is not negotiated.
• Not Defined.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Require 128-bit encryption
</DefaultValue>
<Vulnerability>You can enable all of the options for this policy setting to help protect network traffic that uses the NTLM Security Support Provider (NTLM SSP) from being exposed or tampered with by an attacker who has gained access to the same network. In other words, these options help protect against man-in-the-middle attacks.</Vulnerability>
<Countermeasure>Enable all available options for the Network security: Minimum session security for NTLM SSP based (including secure RPC) clients policy setting. </Countermeasure>
<PotentialImpact>Client applications that are enforcing these settings will be unable to communicate with older servers that do not support them. This setting could impact Windows Clustering when applied to servers running Windows Server 2003, see "How to apply more restrictive security settings on a Windows Server 2003-based cluster server" at http://support.microsoft.com/default.aspx?scid=kb;en-us;891597 and "You receive an "Error 0x8007042b" error message when you add or join a node to a cluster if you use NTLM version 2 in Windows Server 2003" at http://support.microsoft.com/kb/890761/ for more information on possible issues and how to resolve them.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Require NTLMv2 session security,Require 128-bit encryption">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No Minimum">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Require message integrity">
<BehaviorDescription />
<DCMValue ValueA="16" />
<SCAPValue ValueA="16" />
<GPOValue ValueA="16" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality">
<BehaviorDescription />
<DCMValue ValueA="32" />
<SCAPValue ValueA="32" />
<GPOValue ValueA="32" />
</Mapping>
<Mapping FriendlyName="Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524288" />
<SCAPValue ValueA="524288" />
<GPOValue ValueA="524288" />
</Mapping>
<Mapping FriendlyName="Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870912" />
<SCAPValue ValueA="536870912" />
<GPOValue ValueA="536870912" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality">
<BehaviorDescription />
<DCMValue ValueA="48" />
<SCAPValue ValueA="48" />
<GPOValue ValueA="48" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524304" />
<SCAPValue ValueA="524304" />
<GPOValue ValueA="524304" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870928" />
<SCAPValue ValueA="536870928" />
<GPOValue ValueA="536870928" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality,Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524320" />
<SCAPValue ValueA="524320" />
<GPOValue ValueA="524320" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870944" />
<SCAPValue ValueA="536870944" />
<GPOValue ValueA="536870944" />
</Mapping>
<Mapping FriendlyName="Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395200" />
<SCAPValue ValueA="537395200" />
<GPOValue ValueA="537395200" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality,Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524336" />
<SCAPValue ValueA="524336" />
<GPOValue ValueA="524336" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870966" />
<SCAPValue ValueA="536870966" />
<GPOValue ValueA="536870966" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395216" />
<SCAPValue ValueA="537395216" />
<GPOValue ValueA="537395216" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality,Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395232" />
<SCAPValue ValueA="537395232" />
<GPOValue ValueA="537395232" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality,Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395248" />
<SCAPValue ValueA="537395248" />
<GPOValue ValueA="537395248" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa\MSV1_0</mssasc-core:KeyPath>
<mssasc-core:ValueName>NTLMMinClientSec</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0\NTLMMinClientSec" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:Not Defined" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="31" ID="{1c12b886-5e73-4018-87fa-05c04d78c787}" OriginalSettingID="{931c9142-e8ac-4214-b588-554d4403b319}" Name="Network Security: Restrict NTLM: Add server exceptions in this domain" LockdownDate="2011-05-02T01:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8917-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to create an exception list of servers in this domain to which clients are allowed to use NTLM pass-through authentication if the "Network Security: Restrict NTLM: Deny NTLM authentication in this domain" is set.</ShortDescription>
<FullDescription>This policy setting allows you to create an exception list of servers in this domain to which clients are allowed to use NTLM pass-through authentication if the "Network Security: Restrict NTLM: Deny NTLM authentication in this domain" is set.
The naming format for servers on this exception list is the fully qualified domain name (FQDN) or NetBIOS server name used by the calling application listed one per line. A single asterisk (*) can be used at the beginning or end of the string as a wildcard character.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>NTLM is a Microsoft-developed authentication protocol that uses a challenge-response mechanism for authentication, in which client computers can prove their identities without sending a password to the server. The protocol employs three types of messages to negotiate the request, challenge the authenticity of the sender, and perform the authentication. Kerberos is a more robust protocol and is the preferred method of authentication when available. </Vulnerability>
<Countermeasure>Configure Network Security: Restrict NTLM: Add server exceptions in this domain as appropriate for the authentication requirements in your environment.</Countermeasure>
<PotentialImpact>If you configure this policy setting, you can define a list of servers in this domain to which clients are allowed to use NTLM authentication.
If you do not configure this policy setting, no exceptions will be applied.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_MULTI_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Netlogon\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>DCAllowedNTLMServers</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Multi-String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\DCAllowedNTLMServers" DataType="REG_MULTI_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="32" ID="{63b9260b-0551-4ccf-bd90-711d0faef7d5}" OriginalSettingID="{096b92bd-142b-4c28-985f-f3ba1322265f}" Name="Interactive logon: Require Domain Controller authentication to unlock workstation" LockdownDate="2011-05-02T01:36:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8818-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>When this policy setting is enabled, a domain controller must authenticate the domain account used to unlock the computer.</ShortDescription>
<FullDescription>Logon information is required to unlock a locked computer. For domain accounts, the Interactive logon: Require Domain Controller authentication to unlock workstation setting determines whether it is necessary to contact a domain controller to unlock a computer. If you enable this setting, a domain controller must authenticate the domain account that is being used to unlock the computer. If you disable this setting, logon information confirmation with a domain controller is not required for a user to unlock the computer. However, if you configure the Interactive logon: Number of previous logons to cache (in case domain controller is not available) setting to a value that is greater than zero, then the user's cached credentials will be used to unlock the computer.
Note: This setting applies to Windows 2000 computers, but it is not available through the Security Configuration Manager tools on these computers.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>By default, the computer caches in memory the credentials of any users who are authenticated locally. The computer uses these cached credentials to authenticate anyone who attempts to unlock the console. When cached credentials are used, any changes that have recently been made to the account—such as user rights assignments, account lockout, or the account being disabled—are not considered or applied after the account is authenticated. User privileges are not updated, and (more importantly) disabled accounts are still able to unlock the console of the computer.</Vulnerability>
<Countermeasure>Configure the Interactive logon: Require Domain Controller authentication to unlock workstation setting to Enabled and configure the Interactive logon: Number of previous logons to cache (in case domain controller is not available) setting to 0.</Countermeasure>
<PotentialImpact>When the console on a computer is locked, either by a user or automatically by a screen saver time-out, the console can only be unlocked if the user is able to re-authenticate to the domain controller. If no domain controller is available, then users cannot unlock their workstations. If you configure the Interactive logon: Number of previous logons to cache (in case domain controller is not available) setting to 0, users whose domain controllers are unavailable (such as mobile or remote users) will not be able to log on.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows NT\CurrentVersion\Winlogon</mssasc-core:KeyPath>
<mssasc-core:ValueName>ForceUnlockLogon</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ForceUnlockLogon" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:75" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="33" ID="{e2d8ec35-9c92-48eb-988c-58b7228ed1a6}" OriginalSettingID="{f4a2c795-7dc3-4deb-b76f-ef54c49da0d9}" Name="Network security: Allow Local System to use computer identity for NTLM" LockdownDate="2011-05-02T01:36:03Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9096-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows Local System services that use Negotiate to use the computer identity when reverting to NTLM authentication.</ShortDescription>
<FullDescription>This policy setting allows Local System services that use Negotiate to use the computer identity when reverting to NTLM authentication.
This policy is supported on at least Windows 7 or Windows Server 2008 R2.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>When connecting to computers running versions of Windows earlier than Windows Vista or Windows Server 2008, services running as Local System and using SPNEGO (Negotiate) that revert to NTLM use the computer identity. In Windows 7, if you are connecting to a computer running Windows Server 2008 or Windows Vista, then a system service uses either the computer identity or a NULL session. When connecting with a NULL session, a system-generated session key is created, which provides no protection but allows applications to sign and encrypt data without errors. When connecting with the computer identity, both signing and encryption is supported in order to provide data protection.</Vulnerability>
<Countermeasure>Configure Network security: Allow Local System to use computer identity for NTLM to Enabled.</Countermeasure>
<PotentialImpact>If you enable this policy setting, services running as Local System that use Negotiate will use the computer identity. This might cause some authentication requests between Windows operating systems to fail and log an error.
If you do not configure this policy setting, services running as Local System that use Negotiate when reverting to NTLM authentication will authenticate anonymously. This was the behavior in previous versions of Windows.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>UseMachineId</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\UseMachineId" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="34" ID="{d1f88718-583e-4ea8-b22c-972be135b5c7}" OriginalSettingID="{adfc53c0-573a-4b06-8a91-4dc91e830362}" Name="Interactive logon: Number of previous logons to cache (in case domain controller is not available)" LockdownDate="2011-05-15T05:26:30Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8487-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether a user can log on to a Windows domain using cached account information.</ShortDescription>
<FullDescription>This policy setting determines whether a user can log on to a Windows domain using cached account information. Logon information for domain accounts can be cached locally to allow users to log on even if a domain controller cannot be contacted. This policy setting determines the number of unique users for whom logon information is cached locally. If this value is set to 0, the logon cache feature is disabled. An attacker who is able to access the file system of the server could locate this cached information and use a brute force attack to determine user passwords.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>10 logons</DefaultValue>
<Vulnerability>The number that is assigned to this policy setting indicates the number of users whose logon information the servers will cache locally. If the number is set to 10, then the server caches logon information for 10 users. When an eleventh user logs on to the computer, the server overwrites the oldest cached logon session.
Users who access the server console will have their logon credentials cached on that server. An attacker who is able to access the file system of the server could locate this cached information and use a brute force attack to attempt to determine user passwords.
To mitigate this type of attack, Windows encrypts the information and obscures its physical location.
</Vulnerability>
<Countermeasure>Configure the Interactive logon: Number of previous logons to cache (in case domain controller is not available) setting to 0, which disables the local caching of logon information. Additional countermeasures include enforcement of strong password policies and physically secure locations for the computers.</Countermeasure>
<PotentialImpact>Users will be unable to log on to any computers if there is no domain controller available to authenticate them. Organizations may want to configure this value to 2 for end-user computers, especially for mobile users. A configuration value of 2 means that the user’s logon information will still be in the cache, even if a member of the IT department has recently logged on to their computer to perform system maintenance. This method allows users to log on to their computers when they are not connected to the organization’s network.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>logon(s)</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows NT\CurrentVersion\Winlogon</mssasc-core:KeyPath>
<mssasc-core:ValueName>cachedlogonscount</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\CachedLogonsCount" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:72" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="35" ID="{bbe3858c-766c-4c4f-a4e2-4923715ed0f1}" OriginalSettingID="{6887f38a-7719-4d15-a5cd-ab731fb28bb1}" Name="Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers" LockdownDate="2011-05-02T01:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9556-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to deny or audit outgoing NTLM traffic from this Windows 7 or this Windows Server 2008 R2 computer to any Windows remote server.</ShortDescription>
<FullDescription>This policy setting allows you to deny or audit outgoing NTLM traffic from this Windows 7 or this Windows Server 2008 R2 computer to any Windows remote server.
This policy is supported on at least Windows 7 or Windows Server 2008 R2.
Note: Audit and block events are recorded on this computer in the "Operational" Log located under the Applications and Services Log/Microsoft/Windows/NTLM.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>NTLM is a Microsoft-developed authentication protocol that uses a challenge-response mechanism for authentication, in which client computers can prove their identities without sending a password to the server. The protocol employs three types of messages to negotiate the request, challenge the authenticity of the sender, and perform the authentication. Kerberos is a more robust protocol and is the preferred method of authentication when available. </Vulnerability>
<Countermeasure>Configure Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers to Deny All.</Countermeasure>
<PotentialImpact>If you select "Allow all" or do not configure this policy setting, the client computer can authenticate identities to a remote server by using NTLM authentication.
If you select "Audit all," the client computer logs an event for each NTLM authentication request to a remote server. This allows you to identify those servers receiving NTLM authentication requests from the client computer.
If you select "Deny all," the client computer cannot authenticate identities to a remote server by using NTLM authentication. You can use the "Network security: Restrict NTLM: Add remote server exceptions for NTLM authentication" policy setting to define a list of remote servers to which clients are allowed to use NTLM authentication.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Allow all">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Audit all">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Deny all ">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa\MSV1_0</mssasc-core:KeyPath>
<mssasc-core:ValueName>RestrictSendingNTLMTraffic</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0\RestrictSendingNTLMTraffic" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="36" ID="{66a658b9-9b3c-4d08-a131-2aac9e53b5c5}" OriginalSettingID="{fbcb4ac3-1923-414f-94b3-65ec48eea6e2}" Name="Microsoft network server: Server SPN target name validation level" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8503-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting controls the level of validation a computer with shared folders or printers performs on the service principal name provided by the client computer when it establishes a session using the server message block (SMB) protocol</ShortDescription>
<FullDescription>This policy setting controls the level of validation a computer with shared folders or printers (the server) performs on the service principal name (SPN) that is provided by the client computer when it establishes a session using the server message block (SMB) protocol.
The server message block (SMB) protocol provides the basis for file and print sharing and other networking operations, such as remote Windows administration. The SMB protocol supports validating the SMB server service principal name (SPN) within the authentication blob provided by a SMB client to prevent a class of attacks against SMB servers referred to as SMB relay attacks. This setting will affect both SMB1 and SMB2.
This security setting determines the level of validation a SMB server performs on the service principal name (SPN) provided by the SMB client when trying to establish a session to an SMB server.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined
</DefaultValue>
<Vulnerability>The identity of a computer can be spoofed to gain unauthorized access to network resources.</Vulnerability>
<Countermeasure>Configuring this setting to accept or require that a connecting client send a SPN during session setup helps ensure that authorized clients are the only ones connecting to a resource.</Countermeasure>
<PotentialImpact>ll Windows operating systems support both a client-side SMB component and a server-side SMB component. This setting affects the server SMB behavior, and its implementation should be carefully evaluated and tested to prevent disruptions to file and print serving capabilities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Off">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Accept if provided by client">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Required from client">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanManServer\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>SMBServerNameHardeningLevel</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\SMBServerNameHardeningLevel" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:86" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="37" ID="{597039d5-d445-40b3-9e6c-da503f3fabb2}" OriginalSettingID="{763c80f9-f87a-4246-ab22-d0817891d5d3}" Name="Network security: Allow LocalSystem NULL session fallback" LockdownDate="2011-05-02T01:36:03Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8804-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Allow NTLM to fall back to NULL session when used with LocalSystem.</ShortDescription>
<FullDescription>Allow NTLM to fall back to NULL session when used with LocalSystem.
The default is TRUE up to Windows Vista and FALSE in Windows 7.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not Defined</DefaultValue>
<Vulnerability>NULL sessions are less secure because by definition they are unauthenticated.</Vulnerability>
<Countermeasure>Configure Network security: Allow LocalSystem NULL session fallback to Disabled.</Countermeasure>
<PotentialImpact>Any applications that require NULL sessions for LocalSystem will not work as designed.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa\MSV1_0</mssasc-core:KeyPath>
<mssasc-core:ValueName>allownullsessionfallback</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0\allownullsessionfallback" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="38" ID="{1dd11027-79c4-4100-b533-e995dd664a10}" OriginalSettingID="{786eaef9-879d-4ac0-8a9e-7ee68b4ebdff}" Name="Interactive logon: Require smart card" LockdownDate="2011-05-22T05:59:47Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9410-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting requires users to log on to a computer with a smart card.</ShortDescription>
<FullDescription>Microsoft recommends that you use this setting, if appropriate to your environment and your organization's business requirements, to help protect end user computers. This policy setting requires users to log on to a computer with a smart card.
Note: This setting applies to Windows 2000 computers, but it is not available through the Security Configuration Manager tools on these computers.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>It can be difficult to make users choose strong passwords, and even strong passwords are vulnerable to brute-force attacks if an attacker has sufficient time and computing resources. </Vulnerability>
<Countermeasure>For users with access to computers that contain sensitive data, issue smart cards to users and configure the Interactive logon: Require smart card setting to Enabled.</Countermeasure>
<PotentialImpact>All users of a computer with this setting enabled will have to use smart cards to log onto the local computer, which means that the organization will need a reliable public key infrastructure (PKI) as well as smart cards and smart card readers for these users. These requirements are significant challenges, because expertise and resources are required to plan for and deploy these technologies. However, Windows Server 2003 includes Certificate Services, a highly advanced service for implementing and managing certificates. When Certificate Services is combined with Windows XP or Windows Vista, features such as automatic user and computer enrollment and renewal become available. For more information about deploying Smart Cards with Windows Vista see the paper "Windows Vista Smart Card Infrastructure" available for download at the Microsoft Web site (http://www.microsoft.com/downloads/details.aspx?FamilyID=ac201438-3317-44d3-9638-07625fe397b9&displaylang=en).</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>scforceoption</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\ScForceOption" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="39" ID="{245197db-2fbb-426e-86c0-53fb70f633de}" OriginalSettingID="{e197f79b-a454-407c-9307-7b3210313e61}" Name="Network access: Let Everyone permissions apply to anonymous users" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8936-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines what additional permissions are assigned for anonymous connections to the computer</ShortDescription>
<FullDescription>This policy setting determines what additional permissions are assigned for anonymous connections to the computer. If you enable this policy setting, anonymous Windows users are allowed to perform certain activities, such as enumerate the names of domain accounts and network shares. An unauthorized user could anonymously list account names and shared resources and use the information to guess passwords or perform social engineering attacks.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>An unauthorized user could anonymously list account names and shared resources and use the information to attempt to guess passwords, perform social engineering attacks, or launch DoS attacks.</Vulnerability>
<Countermeasure>Configure the Network access: Let Everyone permissions apply to anonymous users setting to Disabled. </Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>EveryoneIncludesAnonymous</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\EveryoneIncludesAnonymous" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:90" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="40" ID="{f36a9b81-5174-4eee-940d-5cc98b66ca18}" OriginalSettingID="{17463ab9-ffc1-40ab-8b09-e8054ba4504c}" Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) servers" LockdownDate="2011-10-12T11:37:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9736-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Network security: Minimum session security for NTLM SSP based (including secure RPC) server applications.</ShortDescription>
<FullDescription>This policy setting determines which behaviors are allowed for applications using the NTLM Security Support Provider (SSP). The SSP Interface (SSPI) is used by applications that need authentication services. The setting does not modify how the authentication sequence works but instead require certain behaviors in applications that use the SSPI.
The possible values for the Network security: Minimum session security for NTLM SSP based (including secure RPC) servers setting are:
• Require message confidentiality. This option is only available in Windows XP and Windows Server 2003, the connection will fail if encryption is not negotiated. Encryption converts data into a form that is not readable until decrypted.
• Require message integrity. This option is only available in Windows XP and Windows Server 2003, the connection will fail if message integrity is not negotiated. The integrity of a message can be assessed through message signing. Message signing proves that the message has not been tampered with; it attaches a cryptographic signature that identifies the sender and is a numeric representation of the contents of the message.
• Require 128-bit encryption. The connection will fail if strong encryption (128-bit) is not negotiated.
• Require NTLMv2 session security. The connection will fail if the NTLMv2 protocol is not negotiated.
• Not Defined.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Require 128-bit encryption
</DefaultValue>
<Vulnerability>You can enable all of the options for this policy setting to help protect network traffic that uses the NTLM Security Support Provider (NTLM SSP) from being exposed or tampered with by an attacker who has gained access to the same network. That is, these options help protect against man-in-the-middle attacks.</Vulnerability>
<Countermeasure>Enable all available options for the Network security: Minimum session security for NTLM SSP based (including secure RPC) servers policy setting.
</Countermeasure>
<PotentialImpact>Server applications that are enforcing these settings will be unable to communicate with older servers that do not support them. This setting could impact Windows Clustering when applied to servers running Windows Server 2003, see "How to apply more restrictive security settings on a Windows Server 2003-based cluster server" at http://support.microsoft.com/default.aspx?scid=kb;en-us;891597 and "You receive an "Error 0x8007042b" error message when you add or join a node to a cluster if you use NTLM version 2 in Windows Server 2003" at http://support.microsoft.com/kb/890761/ for more information on possible issues and how to resolve them.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Require NTLMv2 session security,Require 128-bit encryption">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No Minimum">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Require message integrity">
<BehaviorDescription />
<DCMValue ValueA="16" />
<SCAPValue ValueA="16" />
<GPOValue ValueA="16" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality">
<BehaviorDescription />
<DCMValue ValueA="32" />
<SCAPValue ValueA="32" />
<GPOValue ValueA="32" />
</Mapping>
<Mapping FriendlyName="Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524288" />
<SCAPValue ValueA="524288" />
<GPOValue ValueA="524288" />
</Mapping>
<Mapping FriendlyName="Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870912" />
<SCAPValue ValueA="536870912" />
<GPOValue ValueA="536870912" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality">
<BehaviorDescription />
<DCMValue ValueA="48" />
<SCAPValue ValueA="48" />
<GPOValue ValueA="48" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524304" />
<SCAPValue ValueA="524304" />
<GPOValue ValueA="524304" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870928" />
<SCAPValue ValueA="536870928" />
<GPOValue ValueA="536870928" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality,Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524320" />
<SCAPValue ValueA="524320" />
<GPOValue ValueA="524320" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870944" />
<SCAPValue ValueA="536870944" />
<GPOValue ValueA="536870944" />
</Mapping>
<Mapping FriendlyName="Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395200" />
<SCAPValue ValueA="537395200" />
<GPOValue ValueA="537395200" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality,Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524336" />
<SCAPValue ValueA="524336" />
<GPOValue ValueA="524336" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870966" />
<SCAPValue ValueA="536870966" />
<GPOValue ValueA="536870966" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395216" />
<SCAPValue ValueA="537395216" />
<GPOValue ValueA="537395216" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality,Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395232" />
<SCAPValue ValueA="537395232" />
<GPOValue ValueA="537395232" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality,Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395248" />
<SCAPValue ValueA="537395248" />
<GPOValue ValueA="537395248" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa\MSV1_0</mssasc-core:KeyPath>
<mssasc-core:ValueName>NTLMMinServerSec</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0\NTLMMinServerSec" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="41" ID="{30afa923-5828-4ad2-85cd-817fd62e00d2}" OriginalSettingID="{b5b445ef-7dd4-405f-84b4-a3e307b1167b}" Name="Network Security: Restrict NTLM: Incoming NTLM traffic" LockdownDate="2011-05-02T01:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9494-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to deny or allow incoming NTLM traffic.</ShortDescription>
<FullDescription>This policy setting allows you to deny or allow incoming NTLM traffic.
This policy is supported on at least Windows 7 or Windows Server 2008 R2.
Note: Block events are recorded on this computer in the "Operational" Log located under the Applications and Services Log/Microsoft/Windows/NTLM.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>NTLM is a Microsoft-developed authentication protocol that uses a challenge-response mechanism for authentication, in which client computers can prove their identities without sending a password to the server. The protocol employs three types of messages to negotiate the request, challenge the authenticity of the sender, and perform the authentication. Kerberos is a more robust protocol and is the preferred method of authentication when available. </Vulnerability>
<Countermeasure>Configure Network Security: Restrict NTLM: Incoming NTLM traffic to Deny all accounts</Countermeasure>
<PotentialImpact>If you select "Allow all" or do not configure this policy setting, the server will allow all NTLM authentication requests.
If you select "Deny all domain accounts," the server will deny NTLM authentication requests for domain logon and display an NTLM blocked error, but allow local account logon.
If you select "Deny all accounts," the server will deny NTLM authentication requests from incoming traffic and display an NTLM blocked error.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Allow all">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Deny all domain accounts">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Deny all accounts">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa\MSV1_0</mssasc-core:KeyPath>
<mssasc-core:ValueName>RestrictReceivingNTLMTraffic</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0\RestrictReceivingNTLMTraffic" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="42" ID="{0f0e8a78-3087-4c4a-8f5a-c21ce15219f9}" OriginalSettingID="{520c46db-7a33-4ae2-a55f-fe10182c9398}" Name="Network Security: Restrict NTLM: NTLM authentication in this domain" LockdownDate="2011-05-02T01:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9525-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to deny or allow NTLM authentication within a domain from this domain controller. This policy does not affect interactive logon to this domain controller.</ShortDescription>
<FullDescription>This policy setting allows you to deny or allow NTLM authentication within a domain from this domain controller. This policy does not affect interactive logon to this domain controller.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>NTLM is a Microsoft-developed authentication protocol that uses a challenge-response mechanism for authentication, in which client computers can prove their identities without sending a password to the server. The protocol employs three types of messages to negotiate the request, challenge the authenticity of the sender, and perform the authentication. Kerberos is a more robust protocol and is the preferred method of authentication when available. </Vulnerability>
<Countermeasure>Configure Network Security: Restrict NTLM: NTLM authentication in this domain to Deny All</Countermeasure>
<PotentialImpact>
If you select "Disabled" or do not configure this policy setting, the domain controller will allow all NTLM pass-through authentication requests within the domain.
If you select "Deny for domain accounts to domain servers" the domain controller will deny all NTLM authentication logon attempts to all servers in the domain that are using domain accounts and return an NTLM blocked error unless the server name is on the exception list in the "Network security: Restrict NTLM: Add server exceptions for NTLM authentication in this domain" policy setting.
If you select "Deny for domain account" the domain controller will deny all NTLM authentication logon attempts from domain accounts and return an NTLM blocked error unless the server name is on the exception list in the "Network security: Restrict NTLM: Add server exceptions for NTLM authentication in this domain" policy setting.
If you select "Deny for domain servers" the domain controller will deny NTLM authentication requests to all servers in the domain and return an NTLM blocked error unless the server name is on the exception list in the "Network security: Restrict NTLM: Add server exceptions for NTLM authentication in this domain" policy setting.
If you select "Deny all," the domain controller will deny all NTLM pass-through authentication requests from its servers and for its accounts and return an NTLM blocked error unless the server name is on the exception list in the "Network security: Restrict NTLM: Add server exceptions for NTLM authentication in this domain" policy setting.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disable">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Deny for domain accounts to domain servers">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Deny for domain accounts">
<BehaviorDescription />
<DCMValue ValueA="3" />
<SCAPValue ValueA="3" />
<GPOValue ValueA="3" />
</Mapping>
<Mapping FriendlyName="Deny for domain servers">
<BehaviorDescription />
<DCMValue ValueA="5" />
<SCAPValue ValueA="5" />
<GPOValue ValueA="5" />
</Mapping>
<Mapping FriendlyName="Deny all">
<BehaviorDescription />
<DCMValue ValueA="7" />
<SCAPValue ValueA="7" />
<GPOValue ValueA="7" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Netlogon\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>RestrictNTLMInDomain</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\RestrictNTLMInDomain" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="43" ID="{05a7cc0d-0a17-4406-9896-c4cc17d0caa0}" OriginalSettingID="{402dc351-392a-4816-a26a-65a7bcc94087}" Name="Interactive logon: Smart card removal behavior" LockdownDate="2011-11-01T11:03:41Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9067-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines what happens when the smart card for a logged on user is removed from the smart card reader.</ShortDescription>
<FullDescription>This policy setting determines what happens when the smart card for a logged-on user is removed from the smart card reader.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>No Action</DefaultValue>
<Vulnerability>Users sometimes forget to lock their workstations when they are away from them, allowing the possibility for malicious users to access their computers. If smart cards are used for authentication, the computer should automatically lock itself when the card is removed to ensure that only the user with the smart card is accessing resources using those credentials.</Vulnerability>
<Countermeasure>Configure the Smart card removal behavior setting to Lock Workstation.
If you select Lock Workstation in the Properties dialog box for this policy setting, the workstation locks when the smart card is removed. Users can leave the area, take their smart card with them, and still maintain a protected session.
If you select Force Logoff in the Properties dialog box for this policy setting, the user is automatically logged off when the smart card is removed.
</Countermeasure>
<PotentialImpact>If you select Force Logoff, users will have to re-insert their smart cards and re-enter their PINs when they return to their workstations. Enforcing this setting on computers used by people who must log onto multiple computers in order to perform their duties could be frustating and lower productivity. For example, if network administrators are limited to a single account but need to log into several computers simultaneously in order to effectively manage the network enforcing this setting will limit them to logging onto one computer at a time. For these reasons Microsoft recommends that this setting only be enforced on workstations used for purposes commonly associated with typical users such as document creation and email.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Lock Workstation">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No Action">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Lock Workstation">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Force Logoff">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
<Mapping FriendlyName="Disconnect if a remote Terminal Services session">
<BehaviorDescription />
<DCMValue ValueA="3" />
<SCAPValue ValueA="3" />
<GPOValue ValueA="3" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows NT\CurrentVersion\Winlogon</mssasc-core:KeyPath>
<mssasc-core:ValueName>scremoveoption</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ScRemoveOption" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:78" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="44" ID="{129ea24b-baa4-4de0-a500-d3fb5dedc666}" OriginalSettingID="{d6de5004-d736-43b1-b965-3e63440bf4b1}" Name="Network Security: Restrict NTLM: Audit Incoming NTLM Traffic" LockdownDate="2011-05-02T01:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9340-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to audit incoming NTLM traffic.</ShortDescription>
<FullDescription>This policy setting allows you to audit incoming NTLM traffic.
This policy is supported on at least Windows 7 or Windows Server 2008 R2.
Note: Audit events are recorded on this computer in the "Operational" Log located under the Applications and Services Log/Microsoft/Windows/NTLM.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>NTLM is a Microsoft-developed authentication protocol that uses a challenge-response mechanism for authentication, in which client computers can prove their identities without sending a password to the server. The protocol employs three types of messages to negotiate the request, challenge the authenticity of the sender, and perform the authentication. Kerberos is a more robust protocol and is the preferred method of authentication when available. </Vulnerability>
<Countermeasure>When you need to audit NTLM use configure Network Security: Restrict NTLM: Audit Incoming NTLM Traffic to "Enable auditing for domain accounts" or "Enable auditing for all accounts" as appropriate for your environment.</Countermeasure>
<PotentialImpact>If you select "Disable", or do not configure this policy setting, the server will not log events for incoming NTLM traffic.
If you select "Enable auditing for domain accounts", the server will log events for NTLM pass-through authentication requests that would be blocked when the "Network Security: Restrict NTLM: Incoming NTLM traffic" policy setting is set to the "Deny all domain accounts" option.
If you select "Enable auditing for all accounts", the server will log events for all NTLM authentication requests that would be blocked when the "Network Security: Restrict NTLM: Incoming NTLM traffic" policy setting is set to the "Deny all accounts" option.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disable">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enable auditing for domain accounts">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Enable auditing for all accounts">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa\MSV1_0</mssasc-core:KeyPath>
<mssasc-core:ValueName>AuditReceivingNTLMTraffic</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0\AuditReceivingNTLMTraffic" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="45" ID="{082304a5-6006-41d3-9817-2eadc7e971bb}" OriginalSettingID="{62b84be3-b449-45f8-aaa1-a239eeee8400}" Name="Restrictions for Unauthenticated RPC clients" LockdownDate="2011-10-12T11:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9396-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting configures the RPC Runtime on an RPC server to restrict unauthenticated RPC clients from connecting to the RPC server. </ShortDescription>
<FullDescription>This policy setting configures the RPC Runtime on an RPC server to restrict unauthenticated RPC clients from connecting to the RPC server. A client will be considered an authenticated client if it uses a named pipe to communicate with the server or if it uses RPC Security. RPC interfaces that have specifically asked to be accessible by unauthenticated clients may be exempt from this restriction, depending on the selected value for this policy.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Remote Procedure Call</UIPath>
<DefaultValue>Not configured</DefaultValue>
<Vulnerability>Unauthenticated RPC communication can create a security vulnerability.</Vulnerability>
<Countermeasure> If you enable this policy setting, the following values are available:
• None. Allows all RPC clients to connect to RPC servers that run on the computer on which the policy is applied.
• Authenticated. Allows only authenticated RPC clients to connect to RPC servers that run on the computer on which the policy is applied. Interfaces that have asked to be exempt from this restriction will be granted an exemption.
• Authenticated without exceptions. Allows only authenticated RPC clients to connect to RPC servers that run on the computer on which the policy is applied. No exceptions are allowed.</Countermeasure>
<PotentialImpact>RPC applications that do not authenticate unsolicited inbound connection requests may not work properly when this configuration is applied. Ensure you test applications before you deploy this policy setting throughout your environment. Although the Authenticated value for this policy setting is not completely secure, it can be useful for providing application compatibility in your environment.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine" />
<DataType>String</DataType>
</DiscoveryInfo>
<policy name="RpcRestrictRemoteClients" class="Machine" displayName="$(string.11c98da2d9be428fac99cbf327093aab)" explainText="$(string.9fd762312d0a475abef25477b9494e5b)" presentation="$(presentation.RpcRestrictRemoteClients)" key="Software\Policies\Microsoft\Windows NT\Rpc">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:elements xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:enum id="RpcRestrictRemoteClientsList" key="Software\Policies\Microsoft\Windows NT\Rpc" valueName="RestrictRemoteClients">
<admx:item displayName="$(string.9fe9074ff7b64960b02ffb0414f387f6)">
<admx:value>
<admx:decimal value="0" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.e6744bcc94c84ce7b9eee9a979b2d36c)">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.82f7c08352974eb59776fe406e6f6a6a)">
<admx:value>
<admx:decimal value="2" />
</admx:value>
</admx:item>
</admx:enum>
</admx:elements>
</policy>
<ADMLDefinition>
<presentation id="RpcRestrictRemoteClients">
<admx:dropdownList refId="RpcRestrictRemoteClientsList" defaultItem="1" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">RPC Runtime Unauthenticated Client Restriction to Apply:</admx:dropdownList>
</presentation>
<string id="11c98da2d9be428fac99cbf327093aab">Restrictions for Unauthenticated RPC clients</string>
<string id="9fd762312d0a475abef25477b9494e5b">This policy setting configures the RPC Runtime on an RPC server to restrict unauthenticated RPC clients from connecting to the RPC server. A client will be considered an authenticated client if it uses a named pipe to communicate with the server or if it uses RPC Security. RPC interfaces that have specifically asked to be accessible by unauthenticated clients may be exempt from this restriction, depending on the selected value for this policy.</string>
<string id="9fe9074ff7b64960b02ffb0414f387f6">None</string>
<string id="e6744bcc94c84ce7b9eee9a979b2d36c">Authenticated</string>
<string id="82f7c08352974eb59776fe406e6f6a6a">Authenticated without exceptions</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional with SP2</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="46" ID="{0c1bebbb-ab69-4093-9e04-c237e1f19cf4}" OriginalSettingID="{52a525a6-fa54-4d78-9f6c-8ceb8f5e91aa}" Name="RPC Endpoint Mapper Client Authentication" LockdownDate="2011-10-12T11:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10181-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows client computers that communicate with this computer to be forced to provide authentication before an RPC communication is established.</ShortDescription>
<FullDescription>If you enable this policy setting, client computers that communicate with this computer are forced to provide authentication before RPC communication can be established. By default, RPC clients do not use authentication to communicate with the RPC Server Endpoint Mapper Service when they request the endpoint of a server.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Remote Procedure Call</UIPath>
<DefaultValue>Not configured</DefaultValue>
<Vulnerability>Anonymous access to RPC services could result in accidental disclosure of information to unauthenticated users.</Vulnerability>
<Countermeasure>Implement this setting</Countermeasure>
<PotentialImpact>RPC clients will be forced to authenticate before they can begin communicating with the desired RPC service, this means that anonymous access will not be available and RPC clients that do not support authentication will fail.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows NT\Rpc</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnableAuthEpResolution</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="RpcEnableAuthEpResolution" class="Machine" displayName="$(string.26fb9d15d31844ada00b190c23bdf3c6)" explainText="$(string.08eb3e75a08b4d3793d621d5b7d9d45e)" key="Software\Policies\Microsoft\Windows NT\Rpc" valueName="EnableAuthEpResolution">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="26fb9d15d31844ada00b190c23bdf3c6">RPC Endpoint Mapper Client Authentication</string>
<string id="08eb3e75a08b4d3793d621d5b7d9d45e">If you enable this policy setting, client computers that communicate with this computer are forced to provide authentication before RPC communication can be established. By default, RPC clients do not use authentication to communicate with the RPC Server Endpoint Mapper Service when they request the endpoint of a server.</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional with SP2</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Comment>
</Comment>
</SettingGroup>
<SettingGroup ID="{11992ce8-f5f2-4953-a5d9-74e9123eb36a}" Name="System Defaults" OriginalSettingGroupID="{9de30f0f-71a6-43a2-896b-3646304305e5}">
<mssasc-core:Description>
</mssasc-core:Description>
<mssasc-core:Version Major="1" Minor="0" />
<Author>
</Author>
<Setting Index="47" ID="{55ca8870-6e90-41c6-af69-597997f7d743}" OriginalSettingID="{9e5ba301-4a84-4069-a398-7de2932b1e8f}" Name="Accounts: Guest account status" LockdownDate="2011-08-22T10:48:30Z" GenerateDCM="false" GenerateSCAP="false" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8714-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether the Guest account is enabled or disabled. </ShortDescription>
<FullDescription>This policy setting determines whether the Guest account is enabled or disabled. The Guest account allows unauthenticated network users to gain access to the system. Note that this setting will have no impact when applied to the domain controller organizational unit via group policy because domain controllers have no local account database. It can be configured at the domain level via group policy, similar to account lockout and password policy settings.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>The default Guest account allows unauthenticated network users to log on as Guest with no password. These unauthorized users could access any resources that are accessible to the Guest account over the network. This capability means that any network shares with permissions that allow access to the Guest account, the Guests group, or the Everyone group will be accessible over the network, which could lead to the exposure or corruption of data.</Vulnerability>
<Countermeasure>Configure the Accounts: Guest account status setting to Disabled so that the built-in Guest account is no longer usable. </Countermeasure>
<PotentialImpact>All network users will need to authenticate before they can access shared resources. If you disable the Guest account and the Network Access: Sharing and Security Model option is set to Guest Only, network logons, such as those performed by the Microsoft Network Server (SMB Service), will fail. This policy setting should have little impact on most organizations because it is the default setting in Microsoft Windows® 2000, Windows XP, and Windows Server™ 2003.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Script" Scope="Machine">
<ScriptDiscoveryInfo>
<mssasc-core:ScriptType>VBScript</mssasc-core:ScriptType>
<mssasc-core:ScriptBody>'</mssasc-core:ScriptBody>
</ScriptDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="System Access" Name="EnableGuestAccount" DataType="REG_DWORD" />
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="48" ID="{3f02b561-e59c-4b87-aff0-db9f98210ac8}" OriginalSettingID="{7c6c01fd-5c0d-4398-9de0-0a8855c4cd95}" Name="Network access: Sharing and security model for local accounts" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9503-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines how network logons that use local accounts are authenticated.</ShortDescription>
<FullDescription>This policy setting determines how network logons that use local accounts are authenticated. The Classic option allows precise control over access to resources, including the ability to assign different types of access to different users for the same resource. The Guest only option allows you to treat all users equally. In this context, all users authenticate as Guest only to receive the same access level to a given resource.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Classic - local users authenticate as themselves</DefaultValue>
<Vulnerability>With the Guest only model, any user who can authenticate to your computer over the network does so with guest privileges, which probably means that they will not have write access to shared resources on that computer. Although this restriction does increase security, it makes it more difficult for authorized users to access shared resources on those computers because ACLs on those resources must include access control entries (ACEs) for the Guest account. With the Classic model, local accounts should be password protected. Otherwise, if Guest access is enabled, anyone can use those user accounts to access shared system resources.</Vulnerability>
<Countermeasure>For network servers, configure the Network access: Sharing and security model for local accounts setting to Classic – local users authenticate as themselves. On end-user computers, configure this policy setting to Guest only – local users authenticate as guest.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Classic - local users authenticate as themselves">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Classic - local users authenticate as themselves">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Guest only: Local users authenticate as Guest">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>ForceGuest</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\ForceGuest" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:94" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="49" ID="{12b049a5-9194-4a59-a6bc-3469bcdee08d}" OriginalSettingID="{92b9d876-9d87-460c-82ea-9e8bd94c21ad}" Name="System objects: Strengthen default permissions of internal system objects (e.g. Symbolic Links)" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9191-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines the strength of the default discretionary access control list (DACL) for objects.</ShortDescription>
<FullDescription>This policy setting determines the strength of the default discretionary access control list (DACL) for objects. The setting helps secure objects that can be located and shared among processes and its default configuration strengthens the DACL, because it allows users who are not administrators to read shared objects but does not allow them to modify any that they did not create.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>This setting determines the strength of the default DACL for objects. Windows Server 2003 maintains a global list of shared computer resources so that objects can be located and shared among processes. Each type of object is created with a default DACL that specifies who can access the objects and with what permissions. If you enable this setting, the default DACL is strengthened because non-administrator users are allowed to read shared objects but not modify shared objects that they did not create.</Vulnerability>
<Countermeasure>Configure the System objects: Strengthen default permissions of global system objects (for example, Symbolic Links) setting to Enabled.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Session Manager</mssasc-core:KeyPath>
<mssasc-core:ValueName>ProtectionMode</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Session Manager\ProtectionMode" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:109" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="50" ID="{c3a57a34-29ec-475e-8020-607d3a863972}" OriginalSettingID="{6ca3233b-d0a5-4d2a-9078-21618b53133d}" Name="Accounts: Rename administrator account" LockdownDate="2011-08-10T03:25:58Z" GenerateDCM="false" GenerateSCAP="false" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8484-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting provides the ability to change the default administrator user name.</ShortDescription>
<FullDescription>The built-in local administrator account is a well-known account name that attackers will target. Microsoft recommends to choose another name for this account, and to avoid names that denote administrative or elevated access accounts. Be sure to also change the default description for the local administrator (through the Computer Management console).
Note This policy setting is not configured in the baseline, nor does Microsoft suggest a user name for the account. Suggested user names are omitted to ensure that organizations that implement this guidance will not use the same new user name in their environments.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Administrator</DefaultValue>
<Vulnerability>The Administrator account exists on all computers that run the Windows 2000, Windows Server 2003, or Windows XP Professional operating systems. If you rename this account, it is slightly more difficult for unauthorized persons to guess this privileged user name and password combination.
The built-in Administrator account cannot be locked out, regardless of how many times an attacker might use a bad password. This capability makes the Administrator account a popular target for brute force attacks that attempt to guess passwords. The value of this countermeasure is lessened because this account has a well-known SID, and there are third-party tools that allow authentication by using the SID rather than the account name. Therefore, even if you rename the Administrator account, an attacker could launch a brute force attack by using the SID to log on.
</Vulnerability>
<Countermeasure>Specify a new name in the Accounts: Rename administrator account setting to rename the Administrator account.</Countermeasure>
<PotentialImpact>You will have to inform users who are authorized to use this account of the new account name. (The guidance for this setting assumes that the Administrator account was not disabled, which was recommended earlier in this chapter.) </PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Script" Scope="Machine">
<ScriptDiscoveryInfo>
<mssasc-core:ScriptType>VBScript</mssasc-core:ScriptType>
<mssasc-core:ScriptBody>'</mssasc-core:ScriptBody>
</ScriptDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="System Access" Name="NewAdministratorName" DataType="REG_SZ" />
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="51" ID="{78fdc1b1-209e-4cad-9295-b49b35e3b334}" OriginalSettingID="{d26ad9d1-e063-4c4e-bdb3-25b50cf3b184}" Name="Accounts: Rename guest account" LockdownDate="2011-08-10T03:25:58Z" GenerateDCM="false" GenerateSCAP="false" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9229-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting allows the name of the guest account to change.</ShortDescription>
<FullDescription>The built-in local guest account is another well-known name to attackers. Microsoft recommends to rename this account to something that does not indicate its purpose. Even if you disable this account, which is recommended, ensure that you rename it for added security.
Note This policy setting is not configured in the Security Templates, nor is a new user name for the account suggested here. Suggested user names are omitted to ensure that organizations that implement this guidance will not use the same new user name in their environments.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Guest</DefaultValue>
<Vulnerability>The Guest account exists on all computers that run the Windows 2000, Windows Server 2003, or Windows XP Professional operating systems. If you rename this account. it is slightly more difficult for unauthorized persons to guess this privileged user name and password combination.</Vulnerability>
<Countermeasure>Specify a new name in the Accounts: Rename guest account setting to rename the Guest account.</Countermeasure>
<PotentialImpact>There should be little impact, because the Guest account is disabled by default.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Script" Scope="Machine">
<ScriptDiscoveryInfo>
<mssasc-core:ScriptType>VBScript</mssasc-core:ScriptType>
<mssasc-core:ScriptBody>'</mssasc-core:ScriptBody>
</ScriptDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="System Access" Name="NewGuestName" DataType="REG_SZ" />
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="52" ID="{ac369d63-4dfe-4afe-bd3f-6c04c9871c39}" OriginalSettingID="{4a9b2cb6-a61b-49c4-9170-6743d9846c4f}" Name="Accounts: Administrator account status" LockdownDate="2011-10-12T11:37:55Z" GenerateDCM="false" GenerateSCAP="false" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9199-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting enables or disables the built-in Administrator account during normal operation.</ShortDescription>
<FullDescription>This policy setting enables or disables the Administrator account during normal operation. When a computer is booted into safe mode, the Administrator account is always enabled, regardless of how this setting is configured. Note that this setting will have no impact when applied to the domain controller organizational unit via group policy because domain controllers have no local account database. It can be configured at the domain level via group policy, similar to account lockout and password policy settings.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>In some organizations, it can be a daunting management challenge to maintain a regular schedule for periodic password changes for local accounts. Therefore, you may want to disable the built-in Administrator account instead of relying on regular password changes to protect it from attack. Another reason to disable this built-in account is that it cannot be locked out no matter how many failed logons it accrues, which makes it a prime target for brute force attacks that attempt to guess passwords. Also, this account has a well-known security identifier (SID) and there are third-party tools that allow authentication by using the SID rather than the account name. This capability means that even if you rename the Administrator account, an attacker could launch a brute force attack by using the SID to log on.</Vulnerability>
<Countermeasure>Configure the Accounts: Administrator account status setting to Disabled so that the built-in Administrator account is no longer usable in a normal system startup.</Countermeasure>
<PotentialImpact>Maintenance issues can arise under certain circumstances if you disable the Administrator account. For example, if the secure channel between a member computer and the domain controller fails in a domain environment for any reason and there is no other local Administrator account, you must restart in safe mode to fix the problem that broke the secure channel.
If the current Administrator password does not meet the password requirements, you will not be able to re-enable the Administrator account after it is disabled. If this situation occurs, another member of the Administrators group must set the password on the Administrator account with the Local Users and Groups tool.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Script" Scope="Machine">
<ScriptDiscoveryInfo>
<mssasc-core:ScriptType>VBScript</mssasc-core:ScriptType>
<mssasc-core:ScriptBody>'</mssasc-core:ScriptBody>
</ScriptDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="System Access" Name="EnableAdminAccount" DataType="REG_DWORD" />
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="53" ID="{a7cdd16c-4bfb-44a2-9c5f-7521bf1f640f}" OriginalSettingID="{c95a7fc1-5250-4494-9b94-3f3301b8ae7f}" Name="MSS: (NtfsDisable8dot3NameCreation) Enable the computer to stop generating 8.3 style filenames" LockdownDate="2011-08-05T08:12:53Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8784-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This registry value entry appears as MSS: (NtfsDisable8dot3NameCreation) Enable the computer to stop generating 8.3 style filenames in the SCE.</ShortDescription>
<FullDescription>Windows Server operating systems support 8.3 file name formats for backward compatibility with16-bit applications. The 8.3 file name convention is a naming format that allows file names up to eight characters long.
The registry value entry NtfsDisable8dot3NameCreation was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\FileSystem\ registry key. The entry appears as MSS: (NtfsDisable8dot3NameCreation) Enable the computer to stop generating 8.3 style filenames in the SCE.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>
</Vulnerability>
<Countermeasure>Configure the MSS: (NtfsDisable8dot3NameCreation) Enable the computer to stop generating 8.3 style filenames (recommended) entry to a value of Enabled.
The possible values for this registry entry are:
• 1 or 0. The default configuration is 0 (disabled).
In the SCE UI, these options appear as:
• Enabled
• Disabled
• Not Defined
Updated values are available for this registry entry in Windows 7 and Windows Server 2008 R2:
The possible values for this registry entry are:
• 0, 1, 2, 3. The default configuration is 2.
In the SCM UI, these options appear as:
• Enable 8dot3 name creation on all volumes
• Disable 8dot3 name creation on all volumes
• Set 8dot3 name creation per volume using FSUtil (Windows 7 or later)
• Disable 8dot 3 name creation on all volumes except system volume (Windows 7 or later)
</Countermeasure>
<PotentialImpact>The 16-bit applications in your organization will not be able to access files that are not named with the 8.3 format. Some 32-bit applications also rely on the presence of short names, because short names tend not to contain embedded spaces and therefore do not require quotation marks when used in command lines. The installation routines for some programs may fail; those that are designed to run on multiple CPU architectures are likely to be 16-bit applications. The installation of Exchange 2000 SP2 will fail if this entry is enabled. The installation of service packs for SQL 2000 will fail if this entry is enabled and the path for the system variable %temp% includes a space; a simple workaround for this problem is to redefine the variable to a path without spaces (for example, C:\temp).
Note: If you apply this entry to a server that already has files with auto-generated 8.3 file names, it does not remove them. To remove existing 8.3 file names, you will need to copy those files off the server, delete the files from the original location, and then copy the files back to their original locations.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Enable 8dot3 name creation on all volumes">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Disable 8dot3 name creation on all volumes">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Set 8dot3 name creation per volume using FSUtil (Windows 7 or later)">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
<Mapping FriendlyName="Disable 8dot3 name creation on all volumes except system volume (Windows 7 or later)">
<BehaviorDescription />
<DCMValue ValueA="3" />
<SCAPValue ValueA="3" />
<GPOValue ValueA="3" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\FileSystem</mssasc-core:KeyPath>
<mssasc-core:ValueName>NtfsDisable8dot3NameCreation</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:119" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Comment>
</Comment>
</SettingGroup>
<SettingGroup ID="{c8f0192a-1298-40a0-a2c7-b7ca83c03c7b}" Name="User Notification" OriginalSettingGroupID="{270695f4-1b4a-4a6b-9cdf-d62c777ef0e7}">
<mssasc-core:Description>
</mssasc-core:Description>
<mssasc-core:Version Major="1" Minor="0" />
<Author>
</Author>
<Setting Index="54" ID="{917896fc-f341-4c69-b52e-af2860974dce}" OriginalSettingID="{330bebb6-679e-406d-b984-dbedff171e06}" Name="Interactive logon: Message text for users attempting to log on" LockdownDate="2011-05-15T05:26:30Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8973-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting specifies a text message that displays to users when they log on. </ShortDescription>
<FullDescription>Microsoft recommends that you use this setting, if appropriate to your environment and your organization's business requirements, to help protect end user computers. This policy setting specifies a text message that displays to users when they log on. </FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>Displaying a warning message before logon may help prevent an attack by warning the attacker about the consequences of their misconduct before it happens. It may also help to reinforce corporate policy by notifying employees of the appropriate policy during the logon process. This text is often used for legal reasons—for example, to warn users about the ramifications of misusing company information or to warn them that their actions may be audited.
Note Any warning that you display should first be approved by your organization's legal and human resources representatives. </Vulnerability>
<Countermeasure>Configure the Message text for users attempting to log on and Message title for users attempting to log on settings to an appropriate value for your organization.Also, the Interactive log on: Message text for users attempting to log on and the Interactive log on: Message title for users attempting to log on settings must both be enabled for either one to work properly.</Countermeasure>
<PotentialImpact>Users will see a message in a dialog box before they can log on to the server console.
Note Windows Vista and Windows XP Professional support logon banners that can exceed 512 characters in length and that can also contain carriage-return line-feed sequences. However, Windows 2000-based clients cannot interpret and display these messages. You must use a Windows 2000-based computer to create a logon message policy that applies to Windows 2000-based computers. If you inadvertently create a logon message policy on a Windows Vista-based or Windows XP Professional-based computer and you discover that it does not display properly on Windows 2000-based computers, do the following: Change the setting to Not Defined, and then change the setting to the desired value by using a Windows 2000-based computer.
Important
If you do not reconfigure this setting to Not Defined before reconfiguring the setting using a Windows 2000-based computer, the changes will not take effect properly.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>LegalNoticeText</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\LegalNoticeText" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:70" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="55" ID="{c9b6a248-2674-42ef-984e-ee28f5ae480f}" OriginalSettingID="{26a006cd-34c3-449d-9878-2a5e17f98f4d}" Name="Interactive logon: Message title for users attempting to log on" LockdownDate="2011-05-15T05:26:30Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8740-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows text to be specified in the title bar of the window that users see when they log on to the system.</ShortDescription>
<FullDescription>Microsoft recommends that you use this setting, if appropriate to your environment and your organization's business requirements, to help protect end user computers. This policy setting allows text to be specified in the title bar of the window that users see when they log on to the system.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>Displaying a warning message before logon may help prevent an attack by warning the attacker about the consequences of their misconduct before it happens. It may also help to reinforce corporate policy by notifying employees of the appropriate policy during the logon process.</Vulnerability>
<Countermeasure>Configure the Message text for users attempting to log on and Message title for users attempting to log on settings to an appropriate value for your organization.
Note
Any warning message that displays should be approved by your organization’s legal and human resources representatives.
Also, the Interactive log on: Message text for users attempting to log on and the Interactive log on: Message title for users attempting to log on settings must both be enabled for either one to work properly.</Countermeasure>
<PotentialImpact>Users will see a message in a dialog box before they can log on to the server console.
Note Windows Vista and Windows XP Professional support logon banners that can exceed 512 characters in length and that can also contain carriage-return line-feed sequences. However, Windows 2000-based clients cannot interpret and display these messages. You must use a Windows 2000-based computer to create a logon message policy that applies to Windows 2000-based computers. If you inadvertently create a logon message policy on a Windows Vista-based or Windows XP Professional-based computer and you discover that it does not display properly on Windows 2000-based computers, do the following: Change the setting to Not Defined, and then change the setting to the desired value by using a Windows 2000-based computer.
Important
If you do not reconfigure this setting to Not Defined before reconfiguring the setting using a Windows 2000-based computer, the changes will not take effect properly.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>LegalNoticeCaption</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\LegalNoticeCaption" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Comment>
</Comment>
</SettingGroup>
<SettingGroup ID="{39f22fc9-035c-4135-ab95-d6e3a839d985}" Name="Session Configuration" OriginalSettingGroupID="{188f85e0-7b4d-4c61-99f0-6edbf0ba99c9}">
<mssasc-core:Description>
</mssasc-core:Description>
<mssasc-core:Version Major="1" Minor="0" />
<Author>
</Author>
<Setting Index="56" ID="{ec837347-60b2-4515-8290-fcbbdd02eb50}" OriginalSettingID="{68c3ff44-f8a7-4059-81d7-56749f60665b}" Name="Microsoft network server: Disconnect clients when logon hours expire" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9358-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether to disconnect users who are connected to the local computer outside their user account’s valid logon hours. It affects the SMB component.</ShortDescription>
<FullDescription>This policy setting determines whether to disconnect users who are connected to the local computer outside their user account’s valid logon hours. It affects the SMB component. If you enable this policy setting, client sessions with the SMB service will be forcibly disconnected when the client’s logon hours expire. If you disable this policy setting, established client sessions will be maintained after the client’s logon hours expire. If you enable this policy setting you should also enable Network security: Force logoff when logon hours expire.
If your organization configures logon hours for users, it makes sense to enable this policy setting.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>If your organization configures logon hours for users, then it makes sense to enable this policy setting. Otherwise, users who should not have access to network resources outside of their logon hours may actually be able to continue to use those resources with sessions that were established during allowed hours.</Vulnerability>
<Countermeasure>Enable the Microsoft network server: Disconnect clients when logon hours expire setting.</Countermeasure>
<PotentialImpact>If logon hours are not used in your organization, this policy setting will have no impact. If logon hours are used, existing user sessions will be forcibly terminated when their logon hours expire. </PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanManServer\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>enableforcedlogoff</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\enableforcedlogoff" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:86" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="57" ID="{db3f7b65-f813-48b3-abc8-f95e104eb7d4}" OriginalSettingID="{6b285a31-21ae-4b0c-813c-a8cc812c694d}" Name="Interactive logon: Do not display last user name" LockdownDate="2011-05-02T01:36:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9449-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether the account name of the last user to log on to the client computers in your organization will be displayed in each computer's respective Windows logon screen.</ShortDescription>
<FullDescription>This policy setting determines whether the account name of the last user to log on to the client computers in your organization will be displayed in each computer's respective Windows logon screen. Enable this policy setting to prevent intruders from collecting account names visually from the screens of desktop or laptop computers in your organization.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>An attacker with access to the console (for example, someone with physical access or someone who is able to connect to the server through Terminal Services) could view the name of the last user who logged on to the server. The attacker could then try to guess the password, use a dictionary, or use a brute-force attack to try and log on.</Vulnerability>
<Countermeasure>Configure the "Interactive logon: Display user information when the session is locked" setting to "Do not display user information." The possible values for this policy setting are:
● User display name, domain, and user names.
● User display name only.
● Do not display user information.
</Countermeasure>
<PotentialImpact>Users will not see their user name or domain name when unlocking their computer, they will have to enter that information.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>DontDisplayLastUserName</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\DontDisplayLastUserName" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:68" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="58" ID="{4adfec68-fb9d-4616-9e0c-2a7aa1e553d5}" OriginalSettingID="{330bebb6-679e-406d-b984-dbedff171e06}" Name="Interactive logon: Message text for users attempting to log on" LockdownDate="2011-05-15T05:26:30Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8973-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting specifies a text message that displays to users when they log on. </ShortDescription>
<FullDescription>Microsoft recommends that you use this setting, if appropriate to your environment and your organization's business requirements, to help protect end user computers. This policy setting specifies a text message that displays to users when they log on. </FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>Displaying a warning message before logon may help prevent an attack by warning the attacker about the consequences of their misconduct before it happens. It may also help to reinforce corporate policy by notifying employees of the appropriate policy during the logon process. This text is often used for legal reasons—for example, to warn users about the ramifications of misusing company information or to warn them that their actions may be audited.
Note Any warning that you display should first be approved by your organization's legal and human resources representatives. </Vulnerability>
<Countermeasure>Configure the Message text for users attempting to log on and Message title for users attempting to log on settings to an appropriate value for your organization.Also, the Interactive log on: Message text for users attempting to log on and the Interactive log on: Message title for users attempting to log on settings must both be enabled for either one to work properly.</Countermeasure>
<PotentialImpact>Users will see a message in a dialog box before they can log on to the server console.
Note Windows Vista and Windows XP Professional support logon banners that can exceed 512 characters in length and that can also contain carriage-return line-feed sequences. However, Windows 2000-based clients cannot interpret and display these messages. You must use a Windows 2000-based computer to create a logon message policy that applies to Windows 2000-based computers. If you inadvertently create a logon message policy on a Windows Vista-based or Windows XP Professional-based computer and you discover that it does not display properly on Windows 2000-based computers, do the following: Change the setting to Not Defined, and then change the setting to the desired value by using a Windows 2000-based computer.
Important
If you do not reconfigure this setting to Not Defined before reconfiguring the setting using a Windows 2000-based computer, the changes will not take effect properly.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>LegalNoticeText</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\LegalNoticeText" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:70" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="59" ID="{36e3fe86-8b1c-41bc-81bf-14ee389d1dd2}" OriginalSettingID="{d3fe2010-6fe1-401c-81e8-a635d540af09}" Name="MSS: (ScreenSaverGracePeriod) The time in seconds before the screen saver grace period expires (0 recommended)" LockdownDate="2011-05-22T06:25:35Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8591-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription> The entry appears as MSS: (ScreenSaverGracePeriod) The time in seconds before the screen saver grace period expires (0 recommended) in the SCE.</ShortDescription>
<FullDescription>The registry value entry ScreenSaverGracePeriod was added to the template file in the HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\
Windows NT\CurrentVersion\Winlogon\ registry key. The entry appears as MSS: (ScreenSaverGracePeriod) The time in seconds before the screen saver grace period expires (0 recommended) in the SCE.
Windows includes a grace period between when the screen saver is launched and when the console is actually locked automatically when screen saver locking is enabled. This setting is configured to 0 seconds for both of the environments that are discussed in this guide.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>5 seconds</DefaultValue>
<Vulnerability>The default grace period that is allowed for user movement before the screen saver lock takes effect is five seconds. If you leave the default grace period configuration, your computer is vulnerable to a potential attack from someone who could approach the console and attempt to log on to the computer before the lock takes effect. An entry to the registry can be made to adjust the length of the grace period.</Vulnerability>
<Countermeasure>Configure the MSS: (ScreenSaverGracePeriod) The time in seconds before the screen saver grace period expires (0 recommended) entry to a value of 0.
The possible values for this registry entry are:
• 0 to 255. The default value is 5 seconds.
In the SCE UI, the value for this entry appears as a text entry box:
• A user-defined number
• Not Defined
</Countermeasure>
<PotentialImpact>Users will have to enter their passwords to resume their console sessions as soon as the screen saver activates.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows NT\CurrentVersion\Winlogon</mssasc-core:KeyPath>
<mssasc-core:ValueName>ScreenSaverGracePeriod</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ScreenSaverGracePeriod" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:123" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="60" ID="{ea043c7a-f25a-4827-9e69-7ca3d03e626b}" OriginalSettingID="{4ec1a4fa-eccf-4dab-81aa-3e0a7c8f9983}" Name="Microsoft network server: Amount of idle time required before suspending session" LockdownDate="2011-05-02T01:36:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9406-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to specify the amount of continuous idle time that must pass in an SMB session before the session is suspended because of inactivity. </ShortDescription>
<FullDescription>This policy setting allows you to specify the amount of continuous idle time that must pass in an SMB session before the session is suspended because of inactivity. Administrators can use this policy setting to control when a computer suspends an inactive SMB session. If client activity resumes, the session is automatically reestablished.
A value of 0 will disconnect an idle session as quickly as possible. The maximum value is 99999, which is 208 days; in effect, this value disables the setting.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>15 minutes</DefaultValue>
<Vulnerability>Each SMB session consumes server resources, and numerous null sessions will slow the server or possibly cause it to fail. An attacker could repeatedly establish SMB sessions until the server's SMB services become slow or unresponsive.</Vulnerability>
<Countermeasure>Configure the Microsoft network server: Amount of idle time required before disconnecting session setting to 15 minutes. </Countermeasure>
<PotentialImpact>There will be little impact because SMB sessions will be re-established automatically if the client resumes activity.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="9999">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>minute(s)</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanManServer\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>autodisconnect</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\autodisconnect" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:83" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="61" ID="{ca5df750-54ac-4893-8938-32137e469af2}" OriginalSettingID="{fc1a54ef-184a-4355-9d58-f2fb588e657a}" Name="Network security: Force logoff when logon hours expire" LockdownDate="2011-06-21T02:57:00Z" GenerateDCM="false" GenerateSCAP="false" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9704-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting, which determines whether to disconnect users who are connected to the local computer outside their user account’s valid logon hours, affects the SMB component.</ShortDescription>
<FullDescription>This policy setting, which determines whether to disconnect users who are connected to the local computer outside their user account’s valid logon hours, affects the SMB component. If you enable this policy setting, client sessions with the SMB server will be disconnected when the client’s logon hours expire. If you disable this policy setting, established client sessions will be maintained after the client’s logon hours expire.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>If you disable this policy setting, a user could remain connected to the computer outside of their allotted logon hours. </Vulnerability>
<Countermeasure>If you disable this policy setting, a user could remain connected to the computer outside of their allotted logon hours.
This security setting behaves as an account policy. For domain accounts, there can be only one account policy. The account policy must be defined in the Default Domain Policy, and it is enforced by the domain controllers that make up the domain. A domain controller always pulls the account policy from the Default Domain Policy Group Policy object (GPO), even if there is a different account policy applied to the organizational unit that contains the domain controller. By default, workstations and servers that are joined to a domain (for example, member computers) also receive the same account policy for their local accounts. However, local account policies for member computers can be different from the domain account policy by defining an account policy for the organizational unit that contains the member computers. Kerberos settings are not applied to member computers.</Countermeasure>
<PotentialImpact>When a user's logon time expires, SMB sessions will terminate. The user will be unable to log on to the computer until their next scheduled access time commences.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Script" Scope="Machine">
<ScriptDiscoveryInfo>
<mssasc-core:ScriptType>VBScript</mssasc-core:ScriptType>
<mssasc-core:ScriptBody>WScript.Echo "This is questionable setting that can't get data via a easy way"</mssasc-core:ScriptBody>
</ScriptDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="System Access" Name="ForceLogoffWhenHourExpire" DataType="REG_DWORD" />
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="62" ID="{64143a46-78e1-4738-803b-726c0b71351e}" OriginalSettingID="{402dc351-392a-4816-a26a-65a7bcc94087}" Name="Interactive logon: Smart card removal behavior" LockdownDate="2011-11-01T11:03:41Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9067-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines what happens when the smart card for a logged on user is removed from the smart card reader.</ShortDescription>
<FullDescription>This policy setting determines what happens when the smart card for a logged-on user is removed from the smart card reader.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>No Action</DefaultValue>
<Vulnerability>Users sometimes forget to lock their workstations when they are away from them, allowing the possibility for malicious users to access their computers. If smart cards are used for authentication, the computer should automatically lock itself when the card is removed to ensure that only the user with the smart card is accessing resources using those credentials.</Vulnerability>
<Countermeasure>Configure the Smart card removal behavior setting to Lock Workstation.
If you select Lock Workstation in the Properties dialog box for this policy setting, the workstation locks when the smart card is removed. Users can leave the area, take their smart card with them, and still maintain a protected session.
If you select Force Logoff in the Properties dialog box for this policy setting, the user is automatically logged off when the smart card is removed.
</Countermeasure>
<PotentialImpact>If you select Force Logoff, users will have to re-insert their smart cards and re-enter their PINs when they return to their workstations. Enforcing this setting on computers used by people who must log onto multiple computers in order to perform their duties could be frustating and lower productivity. For example, if network administrators are limited to a single account but need to log into several computers simultaneously in order to effectively manage the network enforcing this setting will limit them to logging onto one computer at a time. For these reasons Microsoft recommends that this setting only be enforced on workstations used for purposes commonly associated with typical users such as document creation and email.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Lock Workstation">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No Action">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Lock Workstation">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Force Logoff">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
<Mapping FriendlyName="Disconnect if a remote Terminal Services session">
<BehaviorDescription />
<DCMValue ValueA="3" />
<SCAPValue ValueA="3" />
<GPOValue ValueA="3" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows NT\CurrentVersion\Winlogon</mssasc-core:KeyPath>
<mssasc-core:ValueName>scremoveoption</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ScRemoveOption" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:78" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="63" ID="{8d0e2f6a-cc6c-42ec-98d9-2a62156d307d}" OriginalSettingID="{6a9560be-b293-43d1-8f01-b03a8002ae75}" Name="Interactive logon: Display user information when the session is locked" LockdownDate="2012-01-31T05:08:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8541-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether the account name of the last user to log on to the client computers in your organization can display in each computer's respective Windows logon screen. </ShortDescription>
<FullDescription>This policy setting determines whether the account name of the last user to log on to the client computers in your organization can display in each computer's respective Windows logon screen. If you enable this policy setting, intruders cannot collect account names visually from the screens of desktop or laptop computers in your organization.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>An attacker with access to the console (for example, someone with physical access or someone who is able to connect to the server through Terminal Services) could view the name of the last user who logged on to the server. The attacker could then try to guess the password, use a dictionary, or use a brute-force attack to try and log on.</Vulnerability>
<Countermeasure>Configure the Do not display last user name in logon screen setting to Enabled.</Countermeasure>
<PotentialImpact>Users will always have to type their user names when they log on to the servers.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="User display name, domain and user names">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="User display name only">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
<Mapping FriendlyName="Do not display user information">
<BehaviorDescription />
<DCMValue ValueA="3" />
<SCAPValue ValueA="3" />
<GPOValue ValueA="3" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>DontDisplayLockedUserId</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\DontDisplayLockedUserId" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="64" ID="{d5f8a901-1ba3-4f5f-b8bd-da1cc11c82f3}" OriginalSettingID="{26a006cd-34c3-449d-9878-2a5e17f98f4d}" Name="Interactive logon: Message title for users attempting to log on" LockdownDate="2011-05-15T05:26:30Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8740-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows text to be specified in the title bar of the window that users see when they log on to the system.</ShortDescription>
<FullDescription>Microsoft recommends that you use this setting, if appropriate to your environment and your organization's business requirements, to help protect end user computers. This policy setting allows text to be specified in the title bar of the window that users see when they log on to the system.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>Displaying a warning message before logon may help prevent an attack by warning the attacker about the consequences of their misconduct before it happens. It may also help to reinforce corporate policy by notifying employees of the appropriate policy during the logon process.</Vulnerability>
<Countermeasure>Configure the Message text for users attempting to log on and Message title for users attempting to log on settings to an appropriate value for your organization.
Note
Any warning message that displays should be approved by your organization’s legal and human resources representatives.
Also, the Interactive log on: Message text for users attempting to log on and the Interactive log on: Message title for users attempting to log on settings must both be enabled for either one to work properly.</Countermeasure>
<PotentialImpact>Users will see a message in a dialog box before they can log on to the server console.
Note Windows Vista and Windows XP Professional support logon banners that can exceed 512 characters in length and that can also contain carriage-return line-feed sequences. However, Windows 2000-based clients cannot interpret and display these messages. You must use a Windows 2000-based computer to create a logon message policy that applies to Windows 2000-based computers. If you inadvertently create a logon message policy on a Windows Vista-based or Windows XP Professional-based computer and you discover that it does not display properly on Windows 2000-based computers, do the following: Change the setting to Not Defined, and then change the setting to the desired value by using a Windows 2000-based computer.
Important
If you do not reconfigure this setting to Not Defined before reconfiguring the setting using a Windows 2000-based computer, the changes will not take effect properly.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>LegalNoticeCaption</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\LegalNoticeCaption" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Comment>
</Comment>
</SettingGroup>
<SettingGroup ID="{02d677cd-59db-42a6-b33d-81ecec3b139d}" Name="File System" OriginalSettingGroupID="{9446ce11-7cff-4bc0-8b0e-6aaa8c880914}">
<mssasc-core:Description>
</mssasc-core:Description>
<mssasc-core:Version Major="1" Minor="0" />
<Author>
</Author>
<Setting Index="65" ID="{6b510307-672d-4eed-ae0e-6c62ca4a1a12}" OriginalSettingID="{c63e0099-758c-4b99-aecd-eb63df8559d8}" Name="Restore files and directories" LockdownDate="2011-05-22T07:27:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9124-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which users can bypass file, directory, registry, and other persistent object permissions when restoring backed up files and directories.</ShortDescription>
<FullDescription>This policy setting determines which users can bypass file, directory, registry, and other persistent object permissions when restoring backed up files and directories on computers that run Windows Vista in your environment. This user right also determines which users can set valid security principals as object owners; it is similar to the Back up files and directories user right.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators, Backup Operators</DefaultValue>
<Vulnerability>An attacker with the Restore files and directories user right could restore sensitive data to a computer and overwrite data that is more recent, which could lead to loss of important data, data corruption, or a denial of service. Attackers could overwrite executable files that are used by legitimate administrators or system services with versions that include malicious software to grant themselves elevated privileges, compromise data, or install backdoors for continued access to the computer.
Note
Even if the following countermeasure is configured, an attacker could still restore data to a computer in a domain that is controlled by the attacker. Therefore, it is critical that organizations carefully protect the media that are used to back up data.
</Vulnerability>
<Countermeasure>Ensure that only the local Administrators group is assigned the Restore files and directories user right, unless your organization has clearly defined roles for backup and for restore personnel.</Countermeasure>
<PotentialImpact>If you remove the Restore files and directories user right from the Backup Operators group and other accounts you could make it impossible for users who have been delegated specific tasks to perform those tasks. You should verify that this change won't negatively affect the ability of your organization’s personnel to do their jobs.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeRestorePrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeRestorePrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:194" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="66" ID="{f779bf0f-37cf-4a97-8a8a-1f00c23a2979}" OriginalSettingID="{10afbff0-0f2c-41b7-8b66-68bda79b77bd}" Name="Create symbolic links" LockdownDate="2011-05-02T01:36:00Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8460-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which users can create symbolic links.</ShortDescription>
<FullDescription>This policy setting determines which users can create symbolic links. In Windows Vista, existing NTFS file system objects, such as files and folders, can be accessed by referring to a new kind of file system object called a symbolic link. A symbolic link is a pointer (much like a shortcut or .lnk file) to another file system object, which can be a file, folder, shortcut or another symbolic link. The difference between a shortcut and a symbolic link is that a shortcut only works from within the Windows shell. To other programs and applications, shortcuts are just another file, whereas with symbolic links, the concept of a shortcut is implemented as a feature of the NTFS file system.
Symbolic links can potentially expose security vulnerabilities in applications that are not designed to use them. For this reason, the privilege for creating symbolic links should only be assigned to trusted users. By default, only Administrators can create symbolic links.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators</DefaultValue>
<Vulnerability>Users who have the Create Symbolic Links user right could inadvertently or maliciously expose your system to symbolic link attacks. Symbolic link attacks can be used to change the permissions on a file, to corrupt data, to destroy data, or as a Denial of Service attack.</Vulnerability>
<Countermeasure>Do not assign the Create Symbolic Links user right to standard users. Restrict this right to trusted administrators. You can use the fsutil command to establish a symlink file system setting that controls the kind of symlinks that can be created on a computer. For more information about fsutil and symbolic links, type fsutil behavior set symlinkevaluation /? at an elevated command prompt.</Countermeasure>
<PotentialImpact>In most cases there will be no impact because this is the default configuration, however, on Windows Servers with the Hyper-V server role installed this user right should also be granted to the special group "Virtual Machines" otherwise you will not be able to create new virtual machines.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeCreateSymbolicLinkPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeCreateSymbolicLinkPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="67" ID="{c223a5a2-b2e5-4d88-8d5e-0e58ed7f822f}" OriginalSettingID="{1ce3bf70-68d8-419b-96ef-d293de427cff}" Name="Back up files and directories" LockdownDate="2011-05-02T01:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9389-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows users to circumvent file and directory permissions to back up the system.</ShortDescription>
<FullDescription>This policy setting allows users to circumvent file and directory permissions to back up the system. This user right is enabled only when an application (such as NTBACKUP) attempts to access a file or directory through the NTFS file system backup application programming interface (API). Otherwise, the assigned file and directory permissions apply.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators, Backup Operators</DefaultValue>
<Vulnerability>Users who are able to back up data from a computer could take the backup media to a non-domain computer on which they have administrative privileges and restore the data. They could take ownership of the files and view any unencrypted data that is contained within the backup set.</Vulnerability>
<Countermeasure>Restrict the Back up files and directories user right to members of the IT team who need to be able to back up organizational data as part of their day-to-day job responsibilities. If you are using backup software that runs under specific service accounts, only these accounts (and not the IT staff) should have the Back up files and directories user right.</Countermeasure>
<PotentialImpact>Changes in the membership of the groups that have the Back up files and directories user right could limit the abilities of users who are assigned to specific administrative roles in your environment. You should confirm that authorized backup administrators are still able to perform backup operations.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeBackupPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeBackupPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:167, oval:gov.nist.1:def:234" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="68" ID="{1caaf822-63ea-4157-9b86-ffa544885307}" OriginalSettingID="{f540aa73-5550-4058-9209-e268908611d5}" Name="Take ownership of files or other objects" LockdownDate="2011-05-15T05:26:31Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9309-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows users to take ownership of files, folders, registry keys, processes, or threads. This user right bypasses any permissions that are in place to protect objects and give ownership to the specified user.</ShortDescription>
<FullDescription>This policy setting allows users to take ownership of files, folders, registry keys, processes, or threads. This user right bypasses any permissions that are in place to protect objects to give ownership to the specified user.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators</DefaultValue>
<Vulnerability>Any users with the Take ownership of files or other objects user right can take control of any object, regardless of the permissions on that object, and then make any changes they wish to that object. Such changes could result in exposure of data, corruption of data, or a DoS condition.</Vulnerability>
<Countermeasure>Ensure that only the local Administrators group has the Take ownership of files or other objects user right.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeTakeOwnershipPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeTakeOwnershipPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:19" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="69" ID="{e6387c64-6cce-4766-aed3-a8e973bebef1}" OriginalSettingID="{c25cfa17-7dbb-4699-a9a9-f53962a70de9}" Name="Bypass traverse checking" LockdownDate="2011-10-12T11:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8414-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows users who do not have the special "Traverse Folder" access permission to "pass through" folders when they browse an object path in the NTFS file system or the registry.</ShortDescription>
<FullDescription>This policy setting allows users who do not have the Traverse Folder access permission to pass through folders when they browse an object path in the NTFS file system or the registry. This user right does not allow users to list the contents of a folder.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Everyone, Administrators, Users, Backup Operators, Local Service, Network Service</DefaultValue>
<Vulnerability>The default configuration for the Bypass traverse checking setting is to allow all users, including the Everyone group, to bypass traverse checking. Permissions to files and folders are controlled though appropriate configuration of file system access control lists (ACLs), as the ability to traverse the folder does not provide any read or write permissions to the user. The only scenario in which the default configuration could lead to a mishap would be if the administrator who configures permissions does not understand how this policy setting works. For example, the administrator might expect that users who are unable to access a folder will be unable to access the contents of any child folders. Such a situation is unlikely, and therefore this vulnerability presents little risk.</Vulnerability>
<Countermeasure>Organizations that are extremely concerned about security may want to remove the Everyone group, or perhaps even the Users group, from the list of groups with the Bypass traverse checking user right. Taking explicit control over traversal assignments can be an effective way to limit access to sensitive information. (Also, the Access–based Enumeration feature that was added in Windows Server 2003 with SP1 can be used. If you use access–based enumeration, users cannot see any folder or file to which they do not have access. For more information about this feature, see Access-based Enumeration (http://go.microsoft.com/fwlink/?LinkId=100745).</Countermeasure>
<PotentialImpact>The Windows operating systems, as well as many applications, were designed with the expectation that anyone who can legitimately access the computer will have this user right. Therefore, we recommend that you thoroughly test any changes to assignments of the Bypass traverse checking user right before you make such changes to production systems. In particular, IIS requires this user right to be assigned to the Network Service, Local Service, IIS_WPG, IUSR_<ComputerName>, and IWAM_<ComputerName> accounts. (It must also be assigned to the ASPNET account through its membership in the Users group.) We recommend that you leave this policy setting at its default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeChangeNotifyPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeChangeNotifyPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:168" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Comment>
</Comment>
</SettingGroup>
<SettingGroup ID="{1408c433-9188-4647-be0b-5ff60ab97ab0}" Name="Encryption Configuration" OriginalSettingGroupID="{435f7747-66b4-4d5b-a532-5c0bd00892a4}">
<mssasc-core:Description>
</mssasc-core:Description>
<mssasc-core:Version Major="1" Minor="0" />
<Author>
</Author>
<Setting Index="70" ID="{5834a109-0fe4-4bb1-b48a-57697b760864}" OriginalSettingID="{c6c11e09-fbc2-408d-af70-3b47f2d2d1b8}" Name="System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" LockdownDate="2011-05-22T06:55:44Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9266-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether the Transport Layer Security/Secure Sockets Layer (TLS/SSL) Security Provider supports only the TLS_RSA_WITH_3DES_EDE_CBC_SHA cipher suite.</ShortDescription>
<FullDescription>This policy setting determines whether the Transport Layer Security/Secure Sockets Layer (TLS/SSL) Security Provider supports only the TLS_RSA_WITH_3DES_EDE_CBC_SHA cipher suite. Although this policy setting increases security, most public Web sites that are secured with TLS or SSL do not support these algorithms. Client computers that have this policy setting enabled will also be unable to connect to Terminal Services on servers that are not configured to use the FIPS compliant algorithms.
Note If you enable this policy setting, computer performance will be slower because the 3DES process is performed on each block of data in the file three times. This policy setting should only be enabled if your organization is required to be FIPS compliant.
Important: This setting is recorded in different registry locations depending upon the version of Windows being used. For Windows XP and Windows Server 2003 it is stored at HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy, with Windows Vista and later versions of Windows it is stored at HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\Enabled. This means that you must use Windows XP or Windows Server 2003 to edit group policies and security templates which will be applied to computers running Windows XP or Windows Server 2003. However, when editing group policies or security templates which will be applied to computers running Windows Vista or Windows Server 2008 you must use Windows Vista or Windows Server 2008.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>You can enable this policy setting to ensure that the computer will use the most powerful algorithms that are available for digital encryption, hashing and signing. Use of these algorithms will minimize the risk of compromise of digitally encrypted or signed data by an unauthorized user.</Vulnerability>
<Countermeasure>Enable the System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing setting.</Countermeasure>
<PotentialImpact>Client computers that have this policy setting enabled will be unable to communicate by means of digitally encrypted or signed protocols with servers that do not support these algorithms. Network clients that do not support these algorithms will not be able to use servers that require them for network communications. For example, many Apache-based Web servers are not configured to support TLS. If you enable this setting, you also need to configure Internet Explorer to use TLS. This policy setting also affects the encryption level that is used for the Remote Desktop Protocol (RDP). The Remote Desktop Connection tool uses the RDP protocol to communicate with servers that run Terminal Services and client computers that are configured for remote control; RDP connections will fail if both computers are not configured to use the same encryption algorithms.
To enable Internet Explore to use TLS
1. On the Internet Explorer Tools menu, click Internet Options.
2. Click the Advanced tab.
3. Select the Use TLS 1.0 check box.
It is also possible to configure this policy setting through Group Policy or by using the Internet Explorer Administrators Kit.
Client computers running Windows XP, Windows XP SP1 and Windows XP SP2 that try to connect to a Terminal Services server that has this setting enabled will be unable to communicate with the server until an updated version of the Terminal Services client is installed. This issue could aslo affect Remote Assistance and Remote Desktop connections. For more information about the issue and how to resolve it see "Remote Assistance connection to Windows Server 2003 with FIPS encryption does not work" at http://support.microsoft.com/default.aspx?scid=kb;en-us;811770.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy</mssasc-core:KeyPath>
<mssasc-core:ValueName>Enabled</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\Enabled" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:105" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="71" ID="{1a20f423-f1fa-40e4-9f2a-980c0c928e96}" OriginalSettingID="{b1b4a762-3114-438b-92cf-90f021714790}" Name="Microsoft network client: Send unencrypted password to third-party SMB servers" LockdownDate="2011-05-02T01:36:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9265-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Disable this policy setting to prevent the SMB redirector from sending plaintext passwords during authentication to third-party SMB servers that do not support password encryption. </ShortDescription>
<FullDescription>Disable this policy setting to prevent the SMB redirector from sending plaintext passwords during authentication to third-party SMB servers that do not support password encryption. Microsoft recommends that you disable this policy setting unless there is a strong business case to enable it. If this policy setting is enabled, unencrypted passwords will be allowed across the network.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>If you enable this policy setting, the server can transmit passwords in plaintext across the network to other computers that offer SMB services. These other computers may not use any of the SMB security mechanisms that are included with Windows Server 2003. </Vulnerability>
<Countermeasure>Configure the Microsoft network client: Send unencrypted password to connect to third-party SMB servers setting to Disabled. </Countermeasure>
<PotentialImpact>Some very old applications and operating systems such as MS-DOS, Windows for Workgroups 3.11, and Windows 95a may not be able to communicate with the servers in your organization by means of the SMB protocol.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanmanWorkstation\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnablePlainTextPassword</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters\EnablePlainTextPassword" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:82" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="72" ID="{2c8cc955-6210-469f-a3e7-eac4923307f4}" OriginalSettingID="{ed734c3b-b27f-4515-9154-9f6f414e6564}" Name="Microsoft network client: Digitally sign communications (always)" LockdownDate="2011-05-02T01:36:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9327-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether packet signing is required by the SMB client component. </ShortDescription>
<FullDescription>This policy setting determines whether packet signing is required by the SMB client component. If you enable this policy setting, the Microsoft network client computer cannot communicate with a Microsoft network server unless that server agrees to sign SMB packets. In mixed environments with legacy client computers, set this option to Disabled because these computers will not be able to authenticate or gain access to domain controllers. However, you can use this policy setting in Windows 2000 or later environments.
Note When Windows Vista–based computers have this policy setting enabled and they connect to file or print shares on remote servers, it is important that the setting is synchronized with its companion setting, Microsoft network server: Digitally sign communications (always), on those servers. For more information about these settings, see the "Microsoft network client and server: Digitally sign communications (four related settings)" section in Chapter 5 of the Threats and Countermeasures guide.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Session hijacking uses tools that allow attackers who have access to the same network as the client or server to interrupt, end, or steal a session in progress. Attackers can potentially intercept and modify unsigned SMB packets and then modify the traffic and forward it so that the server might perform undesirable actions. Alternatively, the attacker could pose as the server or client after legitimate authentication and gain unauthorized access to data.
SMB is the resource sharing protocol that is supported by many Windows operating systems. It is the basis of NetBIOS and many other protocols. SMB signatures authenticate both users and the servers that host the data. If either side fails the authentication process, data transmission will not take place.
</Vulnerability>
<Countermeasure>Configure the settings as follows:
• Disable Microsoft Network Client: Digitally Sign Communications (Always).
• Disable Microsoft Network Server: Digitally Sign Communications (Always).
• Microsoft Network Client: Digitally Sign \Communications (If Server Agrees) to Enabled.
• Microsoft Network Server: Digitally Sign Communications (If Client Agrees) to Enabled.
In highly secure environments we recommend that you configure all of these settings to Enabled. However, that configuration may cause slower performance on client computers and prevent communications with earlier SMB applications and operating systems.
Note
An alternative countermeasure that could protect all network traffic would be to implement digital signatures with Internet Protocol security (IPsec). There are hardware-based accelerators for IPsec encryption and signing that could be used to minimize the performance impact on the servers’ CPUs. No such accelerators are available for SMB signing.
</Countermeasure>
<PotentialImpact>The Windows 2000 Server, Windows 2000 Professional, Windows Server 2003, Windows XP Professional and Windows Vista implementations of the SMB file and print sharing protocol support mutual authentication, which prevents session hijacking attacks and supports message authentication to prevent man-in-the-middle attacks. SMB signing provides this authentication by placing a digital signature into each SMB, which is then verified by both the client and the server.
Implementation of SMB signing may negatively affect performance, because each packet needs to be signed and verified. If these settings are enabled on a server that is performing multiple roles, such as a small business server that is serving as a domain controller, file server, print server, and application server performance may be substantially slowed. Additionally, if you configure computers to ignore all unsigned SMB communications, older applications and operating systems will not be able to connect. However, if you completely disable all SMB signing, computers will be vulnerable to session hijacking attacks.
When SMB signing policies are enabled on domain controllers running Windows Server 2003 and member computers running Windows Vista SP1 or Windows Server 2008 group policy processing will fail. A hotfix is available from Microsoft that resolves this issue; see Microsoft Knowledgebase Article 950876 for more details: http://support.microsoft.com/default.aspx/kb/950876/.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanmanWorkstation\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>RequireSecuritySignature</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters\RequireSecuritySignature" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:79" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="73" ID="{58638d9b-8c66-4f4c-81be-4ba18ce17b27}" OriginalSettingID="{b106bcb1-2b74-4287-8587-6cd92d337be8}" Name="Domain member: Digitally encrypt secure channel data (when possible)" LockdownDate="2011-05-02T01:36:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9251-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether a domain member should attempt to negotiate encryption for all secure channel traffic that it initiates.</ShortDescription>
<FullDescription>This policy setting determines whether a domain member should attempt to negotiate encryption for all secure channel traffic that it initiates. If you enable this policy setting, the domain member will request encryption of all secure channel traffic. If you disable this policy setting, the domain member will be prevented from negotiating secure channel encryption.
Microsoft recommends to configure the Domain member: Digitally encrypt secure channel data (when possible) setting to Enabled.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>When a Windows Server 2003, Windows XP, Windows 2000, or Windows NT computer joins a domain, a computer account is created. After it joins the domain, the computer uses the password for that account to create a secure channel with the domain controller for its domain every time that it restarts. Requests that are sent on the secure channel are authenticated—and sensitive information such as passwords are encrypted—but the channel is not integrity-checked, and not all information is encrypted. If a computer is configured to always encrypt or sign secure channel data but the domain controller cannot sign or encrypt any portion of the secure channel data, the computer and domain controller cannot establish a secure channel. If the computer is configured to encrypt or sign secure channel data when possible, a secure channel can be established, but the level of encryption and signing is negotiated.</Vulnerability>
<Countermeasure>• Enable the Domain member: Digitally encrypt or sign secure channel data (always) setting.
• Enable the Domain member: Digitally encrypt secure channel data (when possible) setting.
• Enable the Domain member: Digitally sign secure channel data (when possible) setting.
</Countermeasure>
<PotentialImpact>Digital encryption and signing of the “secure channel” is a good idea where it is supported. The secure channel protects domain credentials as they are sent to the domain controller. However, only Windows NT 4.0 Service Pack 6a (SP6a) and subsequent versions of the Windows operating system support digital encryption and signing of the secure channel. Windows 98 Second Edition clients do not support it unless they have the Dsclient installed. Therefore, you cannot enable the Domain member: Digitally encrypt or sign secure channel data (always) setting on domain controllers that support Windows 98 clients as members of the domain. Potential impacts can include the following:</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Netlogon\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>sealsecurechannel</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\sealsecurechannel" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="74" ID="{5845ddb2-f798-49f0-a020-202700be3972}" OriginalSettingID="{04b278da-3245-43ec-9d5a-a5a68805027b}" Name="Domain member: Digitally encrypt or sign secure channel data (always)" LockdownDate="2011-05-02T01:36:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8974-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether all secure channel traffic that is initiated by the domain member must be signed or encrypted.</ShortDescription>
<FullDescription>This policy setting determines whether all secure channel traffic that is initiated by the domain member must be signed or encrypted. If a system is set to always encrypt or sign secure channel data, it cannot establish a secure channel with a domain controller that is not capable of signing or encrypting all secure channel traffic, because all secure channel data must be signed and encrypted.
Microsoft recommends to configure the Domain member: Digitally encrypt or sign secure channel data (always) setting to Enabled.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>When a computer joins a domain, a computer account is created. After it joins the domain, the computer uses the password for that account to create a secure channel with the domain controller for its domain every time that it restarts. Requests that are sent on the secure channel are authenticated—and sensitive information such as passwords are encrypted—but the channel is not integrity-checked, and not all information is encrypted. If a computer is configured to always encrypt or sign secure channel data but the domain controller cannot sign or encrypt any portion of the secure channel data, the computer and domain controller cannot establish a secure channel. If the computer is configured to encrypt or sign secure channel data when possible, a secure channel can be established, but the level of encryption and signing is negotiated.</Vulnerability>
<Countermeasure>• Enable the Domain member: Digitally encrypt or sign secure channel data (always) setting.
• Enable the Domain member: Digitally encrypt secure channel data (when possible) setting.
• Enable the Domain member: Digitally sign secure channel data (when possible) setting.
</Countermeasure>
<PotentialImpact>Digital encryption and signing of the “secure channel” is a good idea where it is supported. The secure channel protects domain credentials as they are sent to the domain controller. However, only Windows NT 4.0 with Service Pack 6a (SP6a) and subsequent versions of the Windows operating system support digital encryption and signing of the secure channel. Windows 98 Second Edition clients do not support it unless they have the Dsclient installed. Therefore, you cannot enable the Domain member: Digitally encrypt or sign secure channel data (always) setting on domain controllers that support Windows 98 clients as members of the domain. Potential impacts can include the following:
• The ability to create or delete trust relationships with clients running versions of Windows earlier than Windows NT 4.0 with SP6a will be disabled.
• Logons from clients running versions of Windows earlier than Windows NT 4.0 with SP6a will be disabled.
• The ability to authenticate other domains’ users from a domain controller running a version of Windows earlier than Windows NT 4.0 with SP6a in a trusted domain will be disabled.
You can enable this policy setting after you eliminate all Windows 9x clients from the domain and upgrade all Windows NT 4.0 servers and domain controllers from trusted/trusting domains to Windows NT 4.0 with SP6a. You can enable the other two policy settings, Domain member: Digitally encrypt secure channel data (when possible) and Domain member: Digitally encrypt sign channel data (when possible), on all computers in the domain that support them and clients running versions of Windows earlier than Windows NT 4.0 with SP6a and applications that run on these versions of Windows will not be affected.
Digital encryption and signing of the “secure channel” is a good idea where it is supported. The secure channel protects domain credentials as they are sent to the domain controller. However, only Windows NT 4.0 with Service Pack 6a (SP6a) and subsequent versions of the Windows operating system support digital encryption and signing of the secure channel. Windows 98 Second Edition clients do not support it unless they have the Dsclient installed. Therefore, you cannot enable the Domain member: Digitally encrypt or sign secure channel data (always) setting on domain controllers that support Windows 98 clients as members of the domain. Potential impacts can include the following:
• The ability to create or delete trust relationships with clients running versions of Windows earlier than Windows NT 4.0 with SP6a will be disabled.
• Logons from clients running versions of Windows earlier than Windows NT 4.0 with SP6a will be disabled.
• The ability to authenticate other domains’ users from a domain controller running a version of Windows earlier than Windows NT 4.0 with SP6a in a trusted domain will be disabled.
You can enable this policy setting after you eliminate all Windows 9x clients from the domain and upgrade all Windows NT 4.0 servers and domain controllers from trusted/trusting domains to Windows NT 4.0 with SP6a. You can enable the other two policy settings, Domain member: Digitally encrypt secure channel data (when possible) and Domain member: Digitally encrypt sign channel data (when possible), on all computers in the domain that support them and clients running versions of Windows earlier than Windows NT 4.0 with SP6a and applications that run on these versions of Windows will not be affected.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Netlogon\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>requiresignorseal</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\requiresignorseal" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="75" ID="{28a3d4ca-a5c6-48d5-94d9-624b8f1db163}" OriginalSettingID="{577a19bc-6d69-45f1-9806-b413d522b05a}" Name="Domain member: Require strong (Windows 2000 or later) session key" LockdownDate="2011-08-05T07:16:32Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9387-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>When this policy setting is enabled, a secure channel can only be established with domain controllers that are capable of encrypting secure channel data with a strong (128-bit) session key.</ShortDescription>
<FullDescription>When this policy setting is enabled, a secure channel can only be established with domain controllers that are capable of encrypting secure channel data with a strong (128-bit) session key.
To enable this policy setting, all domain controllers in the domain must be able to encrypt secure channel data with a strong key, which means all domain controllers must be running Microsoft Windows 2000 or later. If communication to non-Windows 2000–based domains is required, Microsoft recommends that you disable this policy setting.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Session keys that are used to establish secure channel communications between domain controllers and member computers are much stronger in Windows 2000 than they were in previous Microsoft operating systems.
Whenever possible, you should take advantage of these stronger session keys to help protect secure channel communications from attacks that attempt to hijack network sessions and eavesdropping. (Eavesdropping is a form of hacking in which network data is read or altered in transit. The data can be modified to hide or change the sender, or be redirected.)
</Vulnerability>
<Countermeasure>Enable the Domain member: Require strong (Windows 2000 or later) session key setting.
If you enable this policy setting, all outgoing secure channel traffic will require a strong, Windows 2000 or later encryption key. If you disable this policy setting, the key strength is negotiated. You should only enable this policy setting if the domain controllers in all trusted domains support strong keys. By default, this policy setting is disabled.
</Countermeasure>
<PotentialImpact>Computers that have this policy setting enabled will not be able to join Windows NT 4.0 domains, and trusts between Active Directory domains and Windows NT-style domains may not work properly. Also, computers that do not support this policy setting will not be able to join domains in which the domain controllers have this policy setting enabled.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Netlogon\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>requirestrongkey</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\requirestrongkey" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:66" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="76" ID="{22ade905-3209-4235-8006-517167adb188}" OriginalSettingID="{9969a7db-5fd1-4713-9a26-9862c15359e9}" Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) clients" LockdownDate="2011-10-12T11:37:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9534-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Network security: Minimum session security for NTLM SSP based (including secure RPC) client applications.
</ShortDescription>
<FullDescription>This policy setting determines which behaviors are allowed for applications using the NTLM Security Support Provider (SSP). The SSP Interface (SSPI) is used by applications that need authentication services. The setting does not modify how the authentication sequence works but instead require certain behaviors in applications that use the SSPI.
The possible values for the Network security: Minimum session security for NTLM SSP based (including secure RPC) clients setting are:
• Require message confidentiality. This option is only available in Windows XP and Windows Server 2003, the connection will fail if encryption is not negotiated. Encryption converts data into a form that is not readable until decrypted.
• Require message integrity. This option is only available in Windows XP and Windows Server 2003, the connection will fail if message integrity is not negotiated. The integrity of a message can be assessed through message signing. Message signing proves that the message has not been tampered with; it attaches a cryptographic signature that identifies the sender and is a numeric representation of the contents of the message.
• Require 128-bit encryption. The connection will fail if strong encryption (128-bit) is not negotiated.
• Require NTLMv2 session security. The connection will fail if the NTLMv2 protocol is not negotiated.
• Not Defined.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Require 128-bit encryption
</DefaultValue>
<Vulnerability>You can enable all of the options for this policy setting to help protect network traffic that uses the NTLM Security Support Provider (NTLM SSP) from being exposed or tampered with by an attacker who has gained access to the same network. In other words, these options help protect against man-in-the-middle attacks.</Vulnerability>
<Countermeasure>Enable all available options for the Network security: Minimum session security for NTLM SSP based (including secure RPC) clients policy setting. </Countermeasure>
<PotentialImpact>Client applications that are enforcing these settings will be unable to communicate with older servers that do not support them. This setting could impact Windows Clustering when applied to servers running Windows Server 2003, see "How to apply more restrictive security settings on a Windows Server 2003-based cluster server" at http://support.microsoft.com/default.aspx?scid=kb;en-us;891597 and "You receive an "Error 0x8007042b" error message when you add or join a node to a cluster if you use NTLM version 2 in Windows Server 2003" at http://support.microsoft.com/kb/890761/ for more information on possible issues and how to resolve them.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Require NTLMv2 session security,Require 128-bit encryption">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No Minimum">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Require message integrity">
<BehaviorDescription />
<DCMValue ValueA="16" />
<SCAPValue ValueA="16" />
<GPOValue ValueA="16" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality">
<BehaviorDescription />
<DCMValue ValueA="32" />
<SCAPValue ValueA="32" />
<GPOValue ValueA="32" />
</Mapping>
<Mapping FriendlyName="Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524288" />
<SCAPValue ValueA="524288" />
<GPOValue ValueA="524288" />
</Mapping>
<Mapping FriendlyName="Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870912" />
<SCAPValue ValueA="536870912" />
<GPOValue ValueA="536870912" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality">
<BehaviorDescription />
<DCMValue ValueA="48" />
<SCAPValue ValueA="48" />
<GPOValue ValueA="48" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524304" />
<SCAPValue ValueA="524304" />
<GPOValue ValueA="524304" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870928" />
<SCAPValue ValueA="536870928" />
<GPOValue ValueA="536870928" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality,Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524320" />
<SCAPValue ValueA="524320" />
<GPOValue ValueA="524320" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870944" />
<SCAPValue ValueA="536870944" />
<GPOValue ValueA="536870944" />
</Mapping>
<Mapping FriendlyName="Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395200" />
<SCAPValue ValueA="537395200" />
<GPOValue ValueA="537395200" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality,Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524336" />
<SCAPValue ValueA="524336" />
<GPOValue ValueA="524336" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870966" />
<SCAPValue ValueA="536870966" />
<GPOValue ValueA="536870966" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395216" />
<SCAPValue ValueA="537395216" />
<GPOValue ValueA="537395216" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality,Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395232" />
<SCAPValue ValueA="537395232" />
<GPOValue ValueA="537395232" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality,Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395248" />
<SCAPValue ValueA="537395248" />
<GPOValue ValueA="537395248" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa\MSV1_0</mssasc-core:KeyPath>
<mssasc-core:ValueName>NTLMMinClientSec</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0\NTLMMinClientSec" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:Not Defined" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="77" ID="{3fbec02a-7a63-4b24-b0a9-442cdf75ef19}" OriginalSettingID="{502cd61a-fec9-42f0-a096-1ac097bbdf73}" Name="Microsoft network server: Digitally sign communications (always)" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9040-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines if the server side SMB service is required to perform SMB packet signing. </ShortDescription>
<FullDescription>This policy setting determines if the server side SMB service is required to perform SMB packet signing. Enable this policy setting in a mixed environment to prevent downstream clients from using the workstation as a network server.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Session hijacking uses tools that allow attackers who have access to the same network as the client or server to interrupt, end, or steal a session in progress. Attackers can potentially intercept and modify unsigned SMB packets and then modify the traffic and forward it so that the server might perform undesirable actions. Alternatively, the attacker could pose as the server or client after legitimate authentication and gain unauthorized access to data.
SMB is the resource sharing protocol that is supported by many Windows operating systems. It is the basis of NetBIOS and many other protocols. SMB signatures authenticate both users and the servers that host the data. If either side fails the authentication process, data transmission will not take place.
</Vulnerability>
<Countermeasure>Configure the settings as follows:
• Disable Microsoft Network Client: Digitally Sign Communications (Always).
• Disable Microsoft Network Server: Digitally Sign Communications (Always).
• Microsoft Network Client: Digitally Sign \Communications (If Server Agrees) to Enabled.
• Microsoft Network Server: Digitally Sign Communications (If Client Agrees) to Enabled.
In highly secure environments we recommend that you configure all of these settings to Enabled. However, that configuration may cause slower performance on client computers and prevent communications with earlier SMB applications and operating systems.
Note
An alternative countermeasure that could protect all network traffic would be to implement digital signatures with Internet Protocol security (IPsec). There are hardware-based accelerators for IPsec encryption and signing that could be used to minimize the performance impact on the servers’ CPUs. No such accelerators are available for SMB signing.
</Countermeasure>
<PotentialImpact>The Windows 2000 Server, Windows 2000 Professional, Windows Server 2003, Windows XP Professional and Windows Vista implementations of the SMB file and print sharing protocol support mutual authentication, which prevents session hijacking attacks and supports message authentication to prevent man-in-the-middle attacks. SMB signing provides this authentication by placing a digital signature into each SMB, which is then verified by both the client and the server.
Implementation of SMB signing may negatively affect performance, because each packet needs to be signed and verified. If these settings are enabled on a server that is performing multiple roles, such as a small business server that is serving as a domain controller, file server, print server, and application server performance may be substantially slowed. Additionally, if you configure computers to ignore all unsigned SMB communications, older applications and operating systems will not be able to connect. However, if you completely disable all SMB signing, computers will be vulnerable to session hijacking attacks.
When SMB signing policies are enabled on domain controllers running Windows Server 2003 and member computers running Windows Vista SP1 or Windows Server 2008 group policy processing will fail. A hotfix is available from Microsoft that resolves this issue; see Microsoft Knowledgebase Article 950876 for more details: http://support.microsoft.com/default.aspx/kb/950876/.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanManServer\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>requiresecuritysignature</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\requiresecuritysignature" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:84" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="78" ID="{fb9da3eb-fe5b-4c60-b97f-94718ee51363}" OriginalSettingID="{817b2f4e-1f03-4bcc-927b-816ddd4777f9}" Name="Microsoft network client: Digitally sign communications (if server agrees)" LockdownDate="2011-05-02T01:36:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9344-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether the SMB client will attempt to negotiate SMB packet signing.</ShortDescription>
<FullDescription>This policy setting determines whether the SMB client will attempt to negotiate SMB packet signing. The implementation of digital signing in Windows–based networks helps to prevent sessions from being hijacked. If you enable this policy setting, the Microsoft network client will use signing only if the server with which it communicates accepts digitally signed communication.
Microsoft recommends to enable The Microsoft network client: Digitally sign communications (if server agrees) setting.
Note Enabling this policy setting on SMB clients on your network makes them fully effective for packet signing with all clients and servers in your environment.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>Session hijacking uses tools that allow attackers who have access to the same network as the client or server to interrupt, end, or steal a session in progress. Attackers can potentially intercept and modify unsigned SMB packets and then modify the traffic and forward it so that the server might perform undesirable actions. Alternatively, the attacker could pose as the server or client after legitimate authentication and gain unauthorized access to data.
SMB is the resource sharing protocol that is supported by many Windows operating systems. It is the basis of NetBIOS and many other protocols. SMB signatures authenticate both users and the servers that host the data. If either side fails the authentication process, data transmission will not take place.
</Vulnerability>
<Countermeasure>Configure the settings as follows:
• Disable Microsoft Network Client: Digitally Sign Communications (Always).
• Disable Microsoft Network Server: Digitally Sign Communications (Always).
• Microsoft Network Client: Digitally Sign \Communications (If Server Agrees) to Enabled.
• Microsoft Network Server: Digitally Sign Communications (If Client Agrees) to Enabled.
In highly secure environments we recommend that you configure all of these settings to Enabled. However, that configuration may cause slower performance on client computers and prevent communications with earlier SMB applications and operating systems.
Note
An alternative countermeasure that could protect all network traffic would be to implement digital signatures with Internet Protocol security (IPsec). There are hardware-based accelerators for IPsec encryption and signing that could be used to minimize the performance impact on the servers’ CPUs. No such accelerators are available for SMB signing.
</Countermeasure>
<PotentialImpact>The Windows 2000 Server, Windows 2000 Professional, Windows Server 2003, Windows XP Professional and Windows Vista implementations of the SMB file and print sharing protocol support mutual authentication, which prevents session hijacking attacks and supports message authentication to prevent man-in-the-middle attacks. SMB signing provides this authentication by placing a digital signature into each SMB, which is then verified by both the client and the server.
Implementation of SMB signing may negatively affect performance, because each packet needs to be signed and verified. If these settings are enabled on a server that is performing multiple roles, such as a small business server that is serving as a domain controller, file server, print server, and application server performance may be substantially slowed. Additionally, if you configure computers to ignore all unsigned SMB communications, older applications and operating systems will not be able to connect. However, if you completely disable all SMB signing, computers will be vulnerable to session hijacking attacks.
When SMB signing policies are enabled on domain controllers running Windows Server 2003 and member computers running Windows Vista SP1 or Windows Server 2008 group policy processing will fail. A hotfix is available from Microsoft that resolves this issue; see Microsoft Knowledgebase Article 950876 for more details: http://support.microsoft.com/default.aspx/kb/950876/.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanmanWorkstation\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnableSecuritySignature</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters\EnableSecuritySignature" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:81" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="79" ID="{c2472de5-9781-4495-a0ec-914a64814c78}" OriginalSettingID="{17463ab9-ffc1-40ab-8b09-e8054ba4504c}" Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) servers" LockdownDate="2011-10-12T11:37:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9736-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Network security: Minimum session security for NTLM SSP based (including secure RPC) server applications.</ShortDescription>
<FullDescription>This policy setting determines which behaviors are allowed for applications using the NTLM Security Support Provider (SSP). The SSP Interface (SSPI) is used by applications that need authentication services. The setting does not modify how the authentication sequence works but instead require certain behaviors in applications that use the SSPI.
The possible values for the Network security: Minimum session security for NTLM SSP based (including secure RPC) servers setting are:
• Require message confidentiality. This option is only available in Windows XP and Windows Server 2003, the connection will fail if encryption is not negotiated. Encryption converts data into a form that is not readable until decrypted.
• Require message integrity. This option is only available in Windows XP and Windows Server 2003, the connection will fail if message integrity is not negotiated. The integrity of a message can be assessed through message signing. Message signing proves that the message has not been tampered with; it attaches a cryptographic signature that identifies the sender and is a numeric representation of the contents of the message.
• Require 128-bit encryption. The connection will fail if strong encryption (128-bit) is not negotiated.
• Require NTLMv2 session security. The connection will fail if the NTLMv2 protocol is not negotiated.
• Not Defined.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Require 128-bit encryption
</DefaultValue>
<Vulnerability>You can enable all of the options for this policy setting to help protect network traffic that uses the NTLM Security Support Provider (NTLM SSP) from being exposed or tampered with by an attacker who has gained access to the same network. That is, these options help protect against man-in-the-middle attacks.</Vulnerability>
<Countermeasure>Enable all available options for the Network security: Minimum session security for NTLM SSP based (including secure RPC) servers policy setting.
</Countermeasure>
<PotentialImpact>Server applications that are enforcing these settings will be unable to communicate with older servers that do not support them. This setting could impact Windows Clustering when applied to servers running Windows Server 2003, see "How to apply more restrictive security settings on a Windows Server 2003-based cluster server" at http://support.microsoft.com/default.aspx?scid=kb;en-us;891597 and "You receive an "Error 0x8007042b" error message when you add or join a node to a cluster if you use NTLM version 2 in Windows Server 2003" at http://support.microsoft.com/kb/890761/ for more information on possible issues and how to resolve them.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Require NTLMv2 session security,Require 128-bit encryption">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No Minimum">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Require message integrity">
<BehaviorDescription />
<DCMValue ValueA="16" />
<SCAPValue ValueA="16" />
<GPOValue ValueA="16" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality">
<BehaviorDescription />
<DCMValue ValueA="32" />
<SCAPValue ValueA="32" />
<GPOValue ValueA="32" />
</Mapping>
<Mapping FriendlyName="Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524288" />
<SCAPValue ValueA="524288" />
<GPOValue ValueA="524288" />
</Mapping>
<Mapping FriendlyName="Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870912" />
<SCAPValue ValueA="536870912" />
<GPOValue ValueA="536870912" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality">
<BehaviorDescription />
<DCMValue ValueA="48" />
<SCAPValue ValueA="48" />
<GPOValue ValueA="48" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524304" />
<SCAPValue ValueA="524304" />
<GPOValue ValueA="524304" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870928" />
<SCAPValue ValueA="536870928" />
<GPOValue ValueA="536870928" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality,Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524320" />
<SCAPValue ValueA="524320" />
<GPOValue ValueA="524320" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870944" />
<SCAPValue ValueA="536870944" />
<GPOValue ValueA="536870944" />
</Mapping>
<Mapping FriendlyName="Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395200" />
<SCAPValue ValueA="537395200" />
<GPOValue ValueA="537395200" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality,Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524336" />
<SCAPValue ValueA="524336" />
<GPOValue ValueA="524336" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870966" />
<SCAPValue ValueA="536870966" />
<GPOValue ValueA="536870966" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395216" />
<SCAPValue ValueA="537395216" />
<GPOValue ValueA="537395216" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality,Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395232" />
<SCAPValue ValueA="537395232" />
<GPOValue ValueA="537395232" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality,Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395248" />
<SCAPValue ValueA="537395248" />
<GPOValue ValueA="537395248" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa\MSV1_0</mssasc-core:KeyPath>
<mssasc-core:ValueName>NTLMMinServerSec</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0\NTLMMinServerSec" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="80" ID="{3688dfbf-8a81-43b1-b5f6-1d450a2ad0a5}" OriginalSettingID="{aa6c8875-0777-4685-9f37-193e9f16af51}" Name="System cryptography: Force strong key protection for user keys stored on the computer" LockdownDate="2011-08-22T07:13:47Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9381-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether users' private keys (such as their S-MIME keys) require a password to be used. </ShortDescription>
<FullDescription>This policy setting determines whether users' private keys (such as their S-MIME keys) require a password to be used. If you configure this policy setting so that users must provide a password—distinct from their domain password—every time that they use a key, then it will be more difficult for an attacker to access locally stored keys, even an attacker who discovers logon passwords.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>If a users account is compromised or their computer is inadvertently left unsecured the malicious user can use the keys stored for the user to access protected resources. You can configure this policy setting so that users must provide a password that is distinct from their domain password every time they use a key. This configuration makes it more difficult for an attacker to access locally stored user keys, even if the attacker takes control of the user’s computer and determines their logon password.</Vulnerability>
<Countermeasure>Configure the System cryptography: Force strong key protection for user keys stored on the computer setting to User must enter a password each time they use a key.</Countermeasure>
<PotentialImpact>Users will have to enter their password every time they access a key that is stored on their computer. For example, if users use an S-MIME certificate to digitally sign their e-mail they will be forced to enter the password for that certificate every time they send a signed e-mail message. For some organizations the overhead that is involved using this configuration may be too high.
For end user computers that are used to access sensitive data this setting could be set to "User is prompted when the key is first used," but Microsoft does not recommend enforcing this setting on servers due to the significant impact on manageability. For example, if this setting is configured to "User is prompted when the key is first used" you may not be able to configure Remote Desktop Services to use SSL certificates. More information is available in the Windows PKI blog: http://blogs.technet.com/b/pki/archive/2009/06/17/what-is-a-strong-key-protection-in-windows.aspx.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="User input is not required when new key are stored and used">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="User is prompted when the key is first used">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="User must enter a password each time they use a key">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Cryptography</mssasc-core:KeyPath>
<mssasc-core:ValueName>ForceKeyProtection</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Policies\Microsoft\Cryptography\ForceKeyProtection" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="81" ID="{98c92a2d-77fb-42b5-836a-bcb6530961d2}" OriginalSettingID="{aadb8b38-715d-470b-b67c-b2158ac6c9f7}" Name="Set client connection encryption level" LockdownDate="2011-10-12T11:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9764-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting specifies whether the computer that is about to host the remote connection will enforce an encryption level for all data sent between it and the client computer for the remote session.</ShortDescription>
<FullDescription>This policy setting specifies whether the computer that is about to host the remote connection will enforce an encryption level for all data sent between it and the client computer for the remote session.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security</UIPath>
<DefaultValue>Not configured</DefaultValue>
<Vulnerability>If Terminal Server client connections are allowed that use low level encryption, it is more likely that an attacker will be able to decrypt any captured Terminal Services network traffic.</Vulnerability>
<Countermeasure>Configure the Set Client Connection Encryption Level setting to High Level.</Countermeasure>
<PotentialImpact>Clients that do not support 128-bit encryption will be unable to establish Terminal Server sessions.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine" />
<DataType>String</DataType>
</DiscoveryInfo>
<policy name="TS_ENCRYPTION_POLICY" class="Machine" displayName="$(string.b7bc07d2602046d5a0b3fd5f76d52ebb)" explainText="$(string.4b5062d86bc0427f9022d64844830089)" presentation="$(presentation.TS_ENCRYPTION_POLICY)" key="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:elements xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:enum id="TS_ENCRYPTION_LEVEL" key="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" valueName="MinEncryptionLevel">
<admx:item displayName="$(string.addadd00f1e84c428e3a31453e977b33)">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.3f1bae5744b4428c992fe4812eb974f8)">
<admx:value>
<admx:decimal value="2" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.c7c2c16080314e20b138a74cb1e8b1dd)">
<admx:value>
<admx:decimal value="3" />
</admx:value>
</admx:item>
</admx:enum>
</admx:elements>
</policy>
<ADMLDefinition>
<presentation id="TS_ENCRYPTION_POLICY">
<admx:dropdownList refId="TS_ENCRYPTION_LEVEL" defaultItem="1" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Encryption Level</admx:dropdownList>
<admx:text xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Choose the encryption level from the drop-down list.</admx:text>
</presentation>
<string id="b7bc07d2602046d5a0b3fd5f76d52ebb">Set client connection encryption level</string>
<string id="4b5062d86bc0427f9022d64844830089">This policy setting specifies whether the computer that is about to host the remote connection will enforce an encryption level for all data sent between it and the client computer for the remote session.</string>
<string id="addadd00f1e84c428e3a31453e977b33">Low Level</string>
<string id="3f1bae5744b4428c992fe4812eb974f8">Client Compatible</string>
<string id="c7c2c16080314e20b138a74cb1e8b1dd">High Level</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional or Windows Server 2003 family</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="oval:com.secure-elements.oval:def:6600" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="82" ID="{f3ac882d-c27b-40a1-abb0-cf6c0eac88da}" OriginalSettingID="{1c96e719-94c8-4333-9165-6efb6a9c6210}" Name="Microsoft network server: Digitally sign communications (if client agrees)" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8825-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines if the server side SMB service is able to sign SMB packets if it is requested to do so by a client that attempts to establish a connection. </ShortDescription>
<FullDescription>This policy setting determines if the server side SMB service is able to sign SMB packets if it is requested to do so by a client that attempts to establish a connection. If no signing request comes from the client, a connection will be allowed without a signature if the Microsoft network server: Digitally sign communications (always) setting is not enabled.
Note Enable this policy setting on SMB clients on your network to make them fully effective for packet signing with all clients and servers in your environment.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Session hijacking uses tools that allow attackers who have access to the same network as the client or server to interrupt, end, or steal a session in progress. Attackers can potentially intercept and modify unsigned SMB packets and then modify the traffic and forward it so that the server might perform undesirable actions. Alternatively, the attacker could pose as the server or client after legitimate authentication and gain unauthorized access to data.
SMB is the resource sharing protocol that is supported by many Windows operating systems. It is the basis of NetBIOS and many other protocols. SMB signatures authenticate both users and the servers that host the data. If either side fails the authentication process, data transmission will not take place.
</Vulnerability>
<Countermeasure>Configure the settings as follows:
• Disable Microsoft Network Client: Digitally Sign Communications (Always).
• Disable Microsoft Network Server: Digitally Sign Communications (Always).
• Microsoft Network Client: Digitally Sign \Communications (If Server Agrees) to Enabled.
• Microsoft Network Server: Digitally Sign Communications (If Client Agrees) to Enabled.
In highly secure environments we recommend that you configure all of these settings to Enabled. However, that configuration may cause slower performance on client computers and prevent communications with earlier SMB applications and operating systems.
Note
An alternative countermeasure that could protect all network traffic would be to implement digital signatures with Internet Protocol security (IPsec). There are hardware-based accelerators for IPsec encryption and signing that could be used to minimize the performance impact on the servers’ CPUs. No such accelerators are available for SMB signing.
</Countermeasure>
<PotentialImpact>The Windows 2000 Server, Windows 2000 Professional, Windows Server 2003, Windows XP Professional and Windows Vista implementations of the SMB file and print sharing protocol support mutual authentication, which prevents session hijacking attacks and supports message authentication to prevent man-in-the-middle attacks. SMB signing provides this authentication by placing a digital signature into each SMB, which is then verified by both the client and the server.
Implementation of SMB signing may negatively affect performance, because each packet needs to be signed and verified. If these settings are enabled on a server that is performing multiple roles, such as a small business server that is serving as a domain controller, file server, print server, and application server performance may be substantially slowed. Additionally, if you configure computers to ignore all unsigned SMB communications, older applications and operating systems will not be able to connect. However, if you completely disable all SMB signing, computers will be vulnerable to session hijacking attacks.
When SMB signing policies are enabled on domain controllers running Windows Server 2003 and member computers running Windows Vista SP1 or Windows Server 2008 group policy processing will fail. A hotfix is available from Microsoft that resolves this issue; see Microsoft Knowledgebase Article 950876 for more details: http://support.microsoft.com/default.aspx/kb/950876/.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanManServer\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>enablesecuritysignature</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\enablesecuritysignature" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:85" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="83" ID="{6af41287-d664-4623-8f5d-fef63ef6e8f6}" OriginalSettingID="{7ab7ae06-f9bd-4252-a282-8fd3a06a73df}" Name="Domain member: Digitally sign secure channel data (when possible)" LockdownDate="2011-06-21T02:57:00Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9375-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether a domain member should attempt to negotiate whether all secure channel traffic that it initiates must be digitally signed.</ShortDescription>
<FullDescription>This policy setting determines whether a domain member should attempt to negotiate whether all secure channel traffic that it initiates must be digitally signed. Digital signatures protect the traffic from being modified by anyone who captures the data as it traverses the network.
Microsoft recommends to configure the Domain member: Digitally sign secure channel data (when possible) setting to Enabled.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>When a computer joins a domain, a computer account is created. After it joins the domain, the computer uses the password for that account to create a secure channel with the domain controller for its domain every time that it restarts. Requests that are sent on the secure channel are authenticated—and sensitive information such as passwords are encrypted—but the channel is not integrity-checked, and not all information is encrypted. If a computer is configured to always encrypt or sign secure channel data but the domain controller cannot sign or encrypt any portion of the secure channel data, the computer and domain controller cannot establish a secure channel. If the computer is configured to encrypt or sign secure channel data when possible, a secure channel can be established, but the level of encryption and signing is negotiated.</Vulnerability>
<Countermeasure>• Enable the Domain member: Digitally encrypt or sign secure channel data (always) setting.
• Enable the Domain member: Digitally encrypt secure channel data (when possible) setting.
• Enable the Domain member: Digitally sign secure channel data (when possible) setting.
</Countermeasure>
<PotentialImpact>Digital encryption and signing of the “secure channel” is a good idea where it is supported. The secure channel protects domain credentials as they are sent to the domain controller. However, only Windows NT 4.0 with Service Pack 6a (SP6a) and subsequent versions of the Windows operating system support digital encryption and signing of the secure channel. Windows 98 Second Edition clients do not support it unless they have the Dsclient installed. Therefore, you cannot enable the Domain member: Digitally encrypt or sign secure channel data (always) setting on domain controllers that support Windows 98 clients as members of the domain. Potential impacts can include the following:
• The ability to create or delete trust relationships with clients running versions of Windows earlier than Windows NT 4.0 with SP6a will be disabled.
• Logons from clients running versions of Windows earlier than Windows NT 4.0 with SP6a will be disabled.
• The ability to authenticate other domains’ users from a domain controller running a version of Windows earlier than Windows NT 4.0 with SP6a in a trusted domain will be disabled.
You can enable this policy setting after you eliminate all Windows 9x clients from the domain and upgrade all Windows NT 4.0 servers and domain controllers from trusted/trusting domains to Windows NT 4.0 with SP6a. You can enable the other two policy settings, Domain member: Digitally encrypt secure channel data (when possible) and Domain member: Digitally encrypt sign channel data (when possible), on all computers in the domain that support them and clients running versions of Windows earlier than Windows NT 4.0 with SP6a and applications that run on these versions of Windows will not be affected.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Netlogon\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>signsecurechannel</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\signsecurechannel" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="84" ID="{80dc8338-8465-4e26-8f45-46bf141932aa}" OriginalSettingID="{c425f126-29a9-4e35-b20b-532e4428c96f}" Name="Network Security: Configure encryption types allowed for Kerberos" LockdownDate="2011-05-02T01:36:03Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9532-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to set the encryption types that Kerberos is allowed to use.</ShortDescription>
<FullDescription>This policy setting allows you to set the encryption types that Kerberos is allowed to use.
This policy is supported on at least Windows 7 or Windows Server 2008 R2.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>The strength of each encryption algorithm varies from one to the next, choosing stronger algorithms will reduce the risk of compromise however doing so may cause issues when the computer attempts to authenticate with systems that do not support them.</Vulnerability>
<Countermeasure>Restrict the allowed encryption types to match your organization's policies.</Countermeasure>
<PotentialImpact>If not selected, the encryption type will not be allowed. This setting may affect compatibility with client computers or services and applications. Multiple selections are permitted.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="9999">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>SupportedEncryptionTypes</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\SupportedEncryptionTypes" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Comment>
</Comment>
</SettingGroup>
<SettingGroup ID="{86190c41-d6e0-40e6-82f4-7cc58a7022e9}" Name="System Integrity" OriginalSettingGroupID="{297c5f53-5aac-425d-ad1c-ef0ddc9d6cf4}">
<mssasc-core:Description>
</mssasc-core:Description>
<mssasc-core:Version Major="1" Minor="0" />
<Author>
</Author>
<Setting Index="85" ID="{b4b2894f-5c26-4f35-ba9e-e08ad22fc40f}" OriginalSettingID="{5a0c69d4-3f9a-4c0c-afe9-89a70342a2f7}" Name="User Account Control: Behavior of the elevation prompt for standard users" LockdownDate="2011-10-25T01:48:30Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8813-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting controls the behavior of the elevation prompt for standard users on computers running Windows 7, Windows Server 2008 R2, and later versions of Windows.
</ShortDescription>
<FullDescription>This policy setting controls the behavior of the elevation prompt for standard users.
The options are:
• Prompt for credentials: When an operation requires elevation of privilege, the user is prompted to enter an administrative user name and password. If the user enters valid credentials, the operation continues with the applicable privilege.
• Automatically deny elevation requests: When an operation requires elevation of privilege, a configurable access denied error message is displayed. An enterprise that is running desktops as standard user may choose this setting to reduce help desk calls.
• Prompt for credentials on the secure desktop: (Default) When an operation requires elevation of privilege, the user is prompted on the secure desktop to enter a different user name and password. If the user enters valid credentials, the operation continues with the applicable privilege. Note that this option was introduced in Windows 7 and it is not applicable to computers running Windows Vista or Windows Server 2008.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Prompt for credentials</DefaultValue>
<Vulnerability>One of the risks that the User Account Control feature introduced with Windows Vista is trying to mitigate is that of malicious programs running under elevated credentials without the user or administrator being aware of their activity. This setting raises awareness to the user that a program requires the use of elevated privilege operations and requires that the user be able to supply administrative credentials in order for the program to run. </Vulnerability>
<Countermeasure>Configure the User Account Control: Behavior of the elevation prompt for standard users to Automatically deny elevation requests. This setting will require the user to login with an administrative account to run programs that require elevation of privilege. As a security best practice, standard users should not have knowledge of administrative passwords. However, if your users have both standard and administrator level accounts, then the Prompt for credentials setting is recommended so that the users will not choose to always log in with their administrator accounts and will shift their behavior to using the standard user account.</Countermeasure>
<PotentialImpact>Users will need to provide administrative passwords to be able to run programs with elevated privileges. This could cause an increased load on IT staff while the programs that are impacted are identified and standard operating procedures are modified to support least privilege operations.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Automatically deny elevation requests">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Prompt for credentials">
<BehaviorDescription />
<DCMValue ValueA="3" />
<SCAPValue ValueA="3" />
<GPOValue ValueA="3" />
</Mapping>
<Mapping FriendlyName="Automatically deny elevation requests">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Prompt for credentials on the secure desktop">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>ConsentPromptBehaviorUser</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\ConsentPromptBehaviorUser" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="86" ID="{54415948-2d82-4269-ab18-d0919318813e}" OriginalSettingID="{c0e16984-8027-4753-af37-e7ed6f8d5aa9}" Name="Require trusted path for credential entry." LockdownDate="2011-10-12T11:37:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10092-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether users must first press CTRL+ALT+DEL to establish a trusted path before typing account and password information to log on to computers in the environment.</ShortDescription>
<FullDescription>If you enable this policy setting, users are required to enter Windows credentials on the Secure Desktop by means of the trusted path mechanism. This means that before entering account and password information to authorize an elevation request, a user first need to press CTRL+ALT+DEL.
</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Credential User Interface</UIPath>
<DefaultValue>Not configured</DefaultValue>
<Vulnerability>Requiring the use of a trusted path helps prevent a Trojan horse or other types of malicious code from stealing the user’s Windows credentials.</Vulnerability>
<Countermeasure>Enable this setting.</Countermeasure>
<PotentialImpact>If you disable or do not configure this policy setting, users can enter Windows credentials within the user’s desktop session, potentially allowing malicious code access to the user’s Windows credentials.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnableSecureCredentialPrompting</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="EnableSecureCredentialPrompting" class="Machine" displayName="$(string.3cdad371738b4d0abc2aabfe0a9f69b2)" explainText="$(string.e7a4d9807ee9434a854f7b024d019ed7)" key="SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI" valueName="EnableSecureCredentialPrompting">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="3cdad371738b4d0abc2aabfe0a9f69b2">Require trusted path for credential entry.</string>
<string id="e7a4d9807ee9434a854f7b024d019ed7">If you enable this policy setting, users are required to enter Windows credentials on the Secure Desktop by means of the trusted path mechanism. This means that before entering account and password information to authorize an elevation request, a user first need to press CTRL+ALT+DEL.
</string>
</ADMLDefinition>
<supportedOn>At least Windows Vista</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="87" ID="{60784c55-d964-4ede-bbaf-40334e512ee6}" OriginalSettingID="{444439f0-8c54-4a1f-9e91-03533d9a69fb}" Name="User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop" LockdownDate="2011-05-02T01:36:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9301-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting controls whether User Interface Accessibility (UIAccess or UIA) programs can automatically disable the secure desktop for elevation prompts used by a standard user.</ShortDescription>
<FullDescription>This policy setting controls whether User Interface Accessibility (UIAccess or UIA) programs can automatically disable the secure desktop for elevation prompts used by a standard user.
• Enabled: UIA programs, including Windows Remote Assistance, automatically disable the secure desktop for elevation prompts. If you do not disable the "User Account Control: Switch to the secure desktop when prompting for elevation" policy setting, the prompts appear on the interactive user's desktop instead of the secure desktop.
• Disabled: (Default) The secure desktop can be disabled only by the user of the interactive desktop or by disabling the "User Account Control: Switch to the secure desktop when prompting for elevation" policy setting.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>One of the risks that the UAC feature introduced with Windows Vista is trying to mitigate is that of malicious software running under elevated credentials without the user or administrator being aware of its activity. This setting allows the administrator to perform operations that require elevated privileges while connected via Remote Assistance. This increases security in that organizations can use UAC even when end user support is provided remotely. However, it also reduces security by adding the risk that an administrator might allow an unprivileged user to share elevated privileges for an application that the adminstrator needs to use during the Remote Desktop session.</Vulnerability>
<Countermeasure>To reduce the risk of a user gaining elevated privileges disable this setting.</Countermeasure>
<PotentialImpact>If you enable this setting, ("User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop”), requests for elevation are automatically sent to the interactive desktop (not the secure desktop) and also appear on the remote administrator's view of the desktop during a Windows Remote Assistance session, and the remote administrator is able to provide the appropriate credentials for elevation. This setting does not change the behavior of the UAC elevation prompt for administrators.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnableUIADesktopToggle</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\EnableUIADesktopToggle" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="88" ID="{21cfd351-1789-4d1a-bd58-ec3ebdad8185}" OriginalSettingID="{8ae83b84-b0fd-4b08-85a5-ff3f897a2db2}" Name="Interactive logon: Do not require CTRL+ALT+DEL" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9317-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>When this setting is configured to Enabled, users are not required to use the CTRL+ALT+DEL key combination to log on to the network.</ShortDescription>
<FullDescription>This policy setting determines whether users must press CTRL+ALT+DEL before they log on. If you enable this policy setting, users can log on without this key combination. If you disable this policy setting, users must press CTRL+ALT+DEL before they log on to Windows unless they use a smart card for Windows logon. A smart card is a tamper-proof device that stores security information.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined
</DefaultValue>
<Vulnerability>Microsoft developed this feature to make it easier for users with certain types of physical impairments to log on to computers that run Windows. If users are not required to press CTRL+ALT+DEL, they are susceptible to attacks that attempt to intercept their passwords. If CTRL+ALT+DEL is required before logon, user passwords are communicated by means of a trusted path.
An attacker could install a Trojan horse program that looks like the standard Windows logon dialog box and capture the user’s password. The attacker would then be able to log on to the compromised account with whatever level of privilege that user has.
</Vulnerability>
<Countermeasure>Configure the Disable CTRL+ALT+DEL requirement for logon setting to Disabled.</Countermeasure>
<PotentialImpact>Unless they use a smart card to log on, users will have to simultaneously press three keys before the logon dialog box will display.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableCAD</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\DisableCAD" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:69" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="89" ID="{be00e277-89c8-46d0-9720-32bbbab2a034}" OriginalSettingID="{48974513-39ec-472c-9ee8-5cb8abf3cb64}" Name="User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode" LockdownDate="2011-10-25T01:48:30Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8958-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting controls the behavior of the elevation prompt for administrators on computers running Windows 7, Windows Server 2008 R2, and later versions of Windows.
</ShortDescription>
<FullDescription>This policy setting controls the behavior of the elevation prompt for administrators.
The options are:
• Elevate without prompting: Allows privileged accounts to perform an operation that requires elevation without requiring consent or credentials. Note: Use this option only in the most constrained environments.
• Prompt for credentials on the secure desktop: When an operation requires elevation of privilege, the user is prompted on the secure desktop to enter a privileged user name and password. If the user enters valid credentials, the operation continues with the user's highest available privilege.
• Prompt for consent on the secure desktop: When an operation requires elevation of privilege, the user is prompted on the secure desktop to select either Permit or Deny. If the user selects Permit, the operation continues with the user's highest available privilege.
• Prompt for credentials: When an operation requires elevation of privilege, the user is prompted to enter an administrative user name and password. If the user enters valid credentials, the operation continues with the applicable privilege.
• Prompt for consent: When an operation requires elevation of privilege, the user is prompted to select either Permit or Deny. If the user selects Permit, the operation continues with the user's highest available privilege.
• Prompt for consent for non-Windows binaries: (Default) When an operation for a non-Microsoft application requires elevation of privilege, the user is prompted on the secure desktop to select either Permit or Deny. If the user selects Permit, the operation continues with the user's highest available privilege.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Prompt for consent for non-Windows binaries</DefaultValue>
<Vulnerability>One of the risks that the UAC feature introduced with Windows Vista is trying to mitigate is that of malicious software running under elevated credentials without the user or administrator being aware of its activity. This setting raises awareness to the administrator of elevated privilege operations and permits the administrator to prevent a malicious program from elevating its privilege when the program attempts to do so. </Vulnerability>
<Countermeasure>Configure the User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode setting to Prompt for consent for non-Windows binaries</Countermeasure>
<PotentialImpact>This policy setting controls the behavior of the elevation prompt for administrators.
• Enabled: (Default for home) When an application installation package is detected that requires elevation of privilege, the user is prompted to enter an administrative user name and password. If the user enters valid credentials, the operation continues with the applicable privilege.
• Disabled: (Default for enterprise) Application installation packages are not detected and prompted for elevation. Enterprises that are running standard user desktops and use delegated installation technologies such as Group Policy Software Installation or Systems Management Server (SMS) should disable this policy setting. In this case, installer detection is unnecessary.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>Some malicious software will attempt to install itself after being given permission to run. For example, malicious software with a trusted application shell. The user may have given permission for the program to run because the program is trusted, but if they are then prompted for installation of an unknown component this provides another way of trapping the software before it can do damage</Vulnerability>
<Countermeasure>Enable the User Account Control: Detect application installations and prompt for elevation setting.</Countermeasure>
<PotentialImpact>Users will need to provide administrative passwords to be able to install programs.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnableInstallerDetection</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\EnableInstallerDetection" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="91" ID="{f89e96b8-9911-4b7e-88e8-62d8bdbd6bd6}" OriginalSettingID="{b6ae867b-3c4f-41bf-9a34-7e299732bb2c}" Name="Do not process the legacy run list" LockdownDate="2011-05-15T05:26:30Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9983-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting causes the run list, which is a list of programs that Windows Vista runs automatically when it starts, to be ignored. </ShortDescription>
<FullDescription>This policy setting causes the run list, which is a list of programs that Windows runs automatically when it starts, to be ignored. The customized run lists for Windows Vista are stored in the registry at the following locations:
• HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
• HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
You can enable the Do not process the legacy run list setting to help prevent a malicious user from running a program each time Windows Vista starts, which could compromise data on the computer or cause other harm. When this policy setting is enabled, certain system programs are prevented from running, such as antivirus software, and software distribution and monitoring software. Microsoft recommends to evaluate the threat level to your environment before you determine whether to use this policy setting for your organization.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Logon</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>A malicious user could configure a program to be run each time Windows starts that could compromise data on the computer or cause other harm. </Vulnerability>
<Countermeasure>Configure the Do not process the legacy run list setting to Enabled.</Countermeasure>
<PotentialImpact>If you enable this setting, certain computer programs such as antivirus software and software distribution and monitoring software are also prevented from execution. You should evaluate the threat level to your environment that this setting is designed to safeguard against before you decide on a strategy to use this setting for your organization.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableLocalMachineRun</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="DisableExplorerRunLegacy_2" class="Machine" displayName="$(string.90857fab3d3d4dd48ca8b84b114988eb)" explainText="$(string.d4bd707119f048a6b5950e2d18ef4024)" key="SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer" valueName="DisableLocalMachineRun">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="90857fab3d3d4dd48ca8b84b114988eb">Do not process the legacy run list</string>
<string id="d4bd707119f048a6b5950e2d18ef4024">This policy setting causes the run list, which is a list of programs that Windows runs automatically when it starts, to be ignored. The customized run lists for Windows Vista are stored in the registry at the following locations:
• HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
• HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
You can enable the Do not process the legacy run list setting to help prevent a malicious user from running a program each time Windows Vista starts, which could compromise data on the computer or cause other harm. When this policy setting is enabled, certain system programs are prevented from running, such as antivirus software, and software distribution and monitoring software. Microsoft recommends to evaluate the threat level to your environment before you determine whether to use this policy setting for your organization.</string>
</ADMLDefinition>
<supportedOn>At least Windows 2000</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="92" ID="{1b12d408-25ff-463f-a272-e3e8c8a09ad5}" OriginalSettingID="{0d380cb0-a162-4dbb-b54b-d41a2a7f9036}" Name="User Account Control: Only elevate UIAccess applications that are installed in secure locations" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9801-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting controls whether applications that request to run with a User Interface Accessibility (UIAccess) integrity level must reside in a secure location in the file system.</ShortDescription>
<FullDescription>This policy setting controls whether applications that request to run with a User Interface Accessibility (UIAccess) integrity level must reside in a secure location in the file system. Secure locations are limited to the following:
- …\Program Files\, including subfolders
- …\Windows\system32\
- …\Program Files (x86)\, including subfolders for 64-bit versions of Windows
Note: Windows enforces a public key infrastructure (PKI) signature check on any interactive application that requests to run with a UIAccess integrity level regardless of the state of this security setting.
The options are:
• Enabled: (Default) If an application resides in a secure location in the file system, it runs only with UIAccess integrity.
• Disabled: An application runs with UIAccess integrity even if it does not reside in a secure location in the file system.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>UIAccess Integrity allows an application to bypass User Interface Privilege Isolation (UIPI) restrictions when an application is elevated in privilege from a standard user to an administrator. This is required to support accessibility features such as screen readers that are transmitting user interfaces to alternative forms. A process that is started with UIAccess rights has the following abilities:
• To set the foreground window.
• To drive any application window using SendInput function.
• To use read input for all integrity levels using low-level hooks, raw input, GetKeyState, GetAsyncKeyState, and GetKeyboardInput.
• To set journal hooks.
• To uses AttachThreadInput to attach a thread to a higher integrity input queue.
</Vulnerability>
<Countermeasure>Enable the User Account Control: Only elevate UIAccess applications that are installed in secure locations setting.</Countermeasure>
<PotentialImpact>If the application that requests UIAccess meets the UIAccess setting requirements, Windows Vista starts the application with the ability to bypass most of the UIPI restrictions. If the application does not meet the security restrictions, the application will be started without UIAccess rights and can interact only with applications at the same or lower privilege level.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnableSecureUIAPaths</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\EnableSecureUIAPaths" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="93" ID="{28394e64-95ae-42dc-9eff-b2396aa16d31}" OriginalSettingID="{d3ebc555-daf1-451f-88a1-61b1b5ac71b5}" Name="User Account Control: Only elevate executables that are signed and validated" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9021-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting enables the prevention of the execution of unsigned or invalidated applications. Before enabling this setting, it is essential that administrators are certain that all required applications are signed and valid. </ShortDescription>
<FullDescription>This policy setting enforces public key infrastructure (PKI) signature checks for any interactive applications that request elevation of privilege. Enterprise administrators can control which applications are allowed to run by adding certificates to the Trusted Publishers certificate store on local computers.
The options are:
• Enabled: Enforces the PKI certification path validation for a given executable file before it is permitted to run.
• Disabled: (Default) Does not enforce PKI certification path validation before a given executable file is permitted to run.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Intellectual property, personally identifiable information, and other confidential data are normally manipulated by applications on the computer and require elevated credentials to get access to the information. Users and administrators inherently trust applications used with these information sources and provide their credentials. If one of these applications is replaced by a rogue application that appears identical to the trusted application the confidential data could be compromised and the user's administrative credentials would also be compromised.</Vulnerability>
<Countermeasure>Enable the UserAccount Control: Only elevate executables that are signed and validated. </Countermeasure>
<PotentialImpact>Enabling this setting requires that you have a PKI infrastructure and that your Enterprise administrators have populated the Trusted Root Store with the certificates for the allowed applications. Some older applications are not signed and will not be able to be used in an environment that is hardened with this setting. You should carefully test your applications in a pre-production environment before implementing this setting. For information about the steps required to test application compatibility, make application compatibility fixes, and sign installer packages to prepare your organization for deployment of Windows Vista User Account Control, see Understanding and Configuring User Account Control in Windows Vista (http://go.microsoft.com/fwlink/?LinkID=79026).
Control over the applications that are installed on the desktops and the hardware that is able to join your domain should provide similar protection from the vulnerability addressed by this setting. Additionally, the level of protection provided by this setting is not an assurance that all rogue applications will be found
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>ValidateAdminCodeSignatures</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\ValidateAdminCodeSignatures" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="94" ID="{fa10a5ad-8541-40cc-aa30-2e25eb590a4c}" OriginalSettingID="{92b9d876-9d87-460c-82ea-9e8bd94c21ad}" Name="System objects: Strengthen default permissions of internal system objects (e.g. Symbolic Links)" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9191-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines the strength of the default discretionary access control list (DACL) for objects.</ShortDescription>
<FullDescription>This policy setting determines the strength of the default discretionary access control list (DACL) for objects. The setting helps secure objects that can be located and shared among processes and its default configuration strengthens the DACL, because it allows users who are not administrators to read shared objects but does not allow them to modify any that they did not create.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>This setting determines the strength of the default DACL for objects. Windows Server 2003 maintains a global list of shared computer resources so that objects can be located and shared among processes. Each type of object is created with a default DACL that specifies who can access the objects and with what permissions. If you enable this setting, the default DACL is strengthened because non-administrator users are allowed to read shared objects but not modify shared objects that they did not create.</Vulnerability>
<Countermeasure>Configure the System objects: Strengthen default permissions of global system objects (for example, Symbolic Links) setting to Enabled.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Session Manager</mssasc-core:KeyPath>
<mssasc-core:ValueName>ProtectionMode</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Session Manager\ProtectionMode" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:109" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="95" ID="{7b69a75a-4f57-4700-9e37-2e46eedc01c1}" OriginalSettingID="{a43ef40c-3543-4204-a431-0f01df930b63}" Name="User Account Control: Switch to the secure desktop when prompting for elevation" LockdownDate="2011-05-02T01:36:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9395-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting controls whether the elevation request prompt is displayed on the interactive user's desktop or the secure desktop.</ShortDescription>
<FullDescription>This policy setting controls whether the elevation request prompt is displayed on the interactive user's desktop or the secure desktop.
The options are:
• Enabled: (Default) All elevation requests go to the secure desktop regardless of prompt behavior policy settings for administrators and standard users.
• Disabled: All elevation requests go to the interactive user's desktop. Prompt behavior policy settings for administrators and standard users are used.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>Elevation prompt dialog boxes can be spoofed, causing users to disclose their passwords to malicious software.</Vulnerability>
<Countermeasure>Enable the User Account Control: Switch to the secure desktop when prompting for elevation setting. The secure desktop helps protect against input and out spoofing by presenting the credentials dialog box in a protected section of memory which only is accessible by trusted system processes.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>PromptOnSecureDesktop</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\PromptOnSecureDesktop" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="96" ID="{75e59622-79d7-41bd-89b1-58617df2bb71}" OriginalSettingID="{ef509260-bd3a-450b-807d-16b454851c6f}" Name="User Account Control: Run all administrators in Admin Approval Mode" LockdownDate="2011-05-02T01:36:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9189-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This is the setting that turns on or off UAC. Disabling this setting effectively disables UAC.</ShortDescription>
<FullDescription>This policy setting controls the behavior of all User Account Control (UAC) policy settings for the computer. If you change this policy setting, you must restart your computer.
The options are:
• Enabled: (Default) Admin Approval Mode is enabled. This policy must be enabled and related UAC policy settings must also be set appropriately to allow the built-in Administrator account and all other users who are members of the Administrators group to run in Admin Approval Mode.
• Disabled: Admin Approval Mode and all related UAC policy settings are disabled. Note: If this policy setting is disabled, the Security Center notifies you that the overall security of the operating system has been reduced.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>This is the setting that turns on or off UAC. If this setting is disabled, UAC will not be used and any security benefits and risk mitigations that are dependent on UAC will not be present on the system.</Vulnerability>
<Countermeasure>Enable the User Account Control: Run all users, including administrators, as standard users setting. </Countermeasure>
<PotentialImpact>Users and administrators will need to learn to work with UAC prompts and adjust their work habits to use least privilege operations.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnableLUA</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="97" ID="{d8cb6429-acf3-497a-9243-bf0a1faa6655}" OriginalSettingID="{5fbabdf6-6786-46f6-b959-596af69f2650}" Name="User Account Control: Admin Approval Mode for the Built-in Administrator account" LockdownDate="2011-05-02T01:36:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8811-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting controls the behavior of Admin Approval Mode for the built-in Administrator account.</ShortDescription>
<FullDescription>This policy setting controls the behavior of Admin Approval Mode for the built-in Administrator account.
The options are:
• Enabled: The built-in Administrator account uses Admin Approval Mode. By default, any operation that requires elevation of privilege will prompt the user to approve the operation.
• Disabled: (Default) The built-in Administrator account runs all applications with full administrative privilege.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>One of the risks that the User Account Control feature introduced with Windows Vista is trying to mitigate is that of malicious software running under elevated credentials without the user or administrator being aware of its activity. An attack vector for these programs was to discover the password of the account named "Administrator" because that user account was created for all installations of Windows. To address this risk, in Windows Vista the built-in Administrator account is disabled. In a default installation of a new computer, accounts with administrative control over the computer are initially set up in one of two ways:
• If the computer is not joined to a domain, the first user account you create has the equivalent permissions as a local administrator.
• If the computer is joined to a domain, no local administrator accounts are created. The Enterprise or Domain Administrator must log on to the computer and create one if a local administrator account is warranted.
Once Windows Vista is installed, the built-in Administrator account may be enabled, but we strongly recommend that this account remain disabled.
</Vulnerability>
<Countermeasure>Enable the User Account Control: Admin Approval Mode for the Built-in Administrator account setting if you have the built-in Administrator account enabled.</Countermeasure>
<PotentialImpact>Users that log on using the local Administrator account will be prompted for consent whenever a program requests an elevation in privilege. </PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>FilterAdministratorToken</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\FilterAdministratorToken" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="98" ID="{6694acde-abc6-48a9-9f71-f3c3e8165062}" OriginalSettingID="{c57013e7-e530-4cbd-951f-2c07f2a91b73}" Name="Always install with elevated privileges" LockdownDate="2011-10-31T10:45:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-00000-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Always install with elevated privileges</ShortDescription>
<FullDescription>Directs Windows Installer to use system permissions when it installs any program on the system.
This setting extends elevated privileges to all programs. These privileges are usually reserved for programs that have been assigned to the user (offered on the desktop), assigned to the computer (installed automatically), or made available in Add or Remove Programs in Control Panel. This setting lets users install programs that require access to directories that the user might not have permission to view or change, including directories on highly restricted computers.
If you disable this setting or do not configure it, the system applies the current user's permissions when it installs programs that a system administrator does not distribute or offer.
Note: This setting appears both in the Computer Configuration and User Configuration folders. To make this setting effective, you must enable the setting in both folders.
Caution: Skilled users can take advantage of the permissions this setting grants to change their privileges and gain permanent access to restricted files and folders. Note that the User Configuration version of this setting is not guaranteed to be secure.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Windows Installer</UIPath>
<DefaultValue>Not Configured</DefaultValue>
<Vulnerability>Users with limited privileges can exploit this feature by creating a Windows Installer installation package that creates a new local account that belongs to the local built-in Administrators group, adds their current account to the local built-in Administrators group, installs malicious software, or performs other unauthorized activities.</Vulnerability>
<Countermeasure>Configure the "Always install with elevated privileges" setting to "Disabled."</Countermeasure>
<PotentialImpact>Windows Installer will apply the current user's permissions when it installs programs, this will prevent standard users from installing applications that affect system-wide configuration items.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows\Installer</mssasc-core:KeyPath>
<mssasc-core:ValueName>AlwaysInstallElevated</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="AlwaysInstallElevated_2" class="Machine" displayName="$(string.26d5c8d119bd4f0b9628af0e7b4e541f)" explainText="$(string.26d8e488275c4e9e8e6e223752768b22)" key="Software\Policies\Microsoft\Windows\Installer" valueName="AlwaysInstallElevated">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="26d5c8d119bd4f0b9628af0e7b4e541f">Always install with elevated privileges</string>
<string id="26d8e488275c4e9e8e6e223752768b22">Directs Windows Installer to use system permissions when it installs any program on the system.
This setting extends elevated privileges to all programs. These privileges are usually reserved for programs that have been assigned to the user (offered on the desktop), assigned to the computer (installed automatically), or made available in Add or Remove Programs in Control Panel. This setting lets users install programs that require access to directories that the user might not have permission to view or change, including directories on highly restricted computers.
If you disable this setting or do not configure it, the system applies the current user's permissions when it installs programs that a system administrator does not distribute or offer.
Note: This setting appears both in the Computer Configuration and User Configuration folders. To make this setting effective, you must enable the setting in both folders.
Caution: Skilled users can take advantage of the permissions this setting grants to change their privileges and gain permanent access to restricted files and folders. Note that the User Configuration version of this setting is not guaranteed to be secure.</string>
</ADMLDefinition>
<supportedOn>Unspecified</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="99" ID="{9d5286b3-4ac5-4114-8f64-1c03f0089d80}" OriginalSettingID="{aa73099d-1954-4488-b76f-72cab4588003}" Name="Turn off downloading of print drivers over HTTP" LockdownDate="2011-10-12T11:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9195-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting controls whether the computer can download print driver packages over HTTP. To set up HTTP printing, printer drivers that are not available in the standard operating system installation might need to be downloaded over HTTP.</ShortDescription>
<FullDescription>This policy setting controls whether the computer can download print driver packages over HTTP. To set up HTTP printing, printer drivers that are not available in the standard operating system installation might need to be downloaded over HTTP.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Internet Communication Management\Internet Communication settings</UIPath>
<DefaultValue>Not configured</DefaultValue>
<Vulnerability>Users might download drivers that include malicious code.</Vulnerability>
<Countermeasure>Enable this setting to prevent print drivers from being downloaded over HTTP.</Countermeasure>
<PotentialImpact> This policy setting does not prevent the client computer from printing to printers on the intranet or the Internet over HTTP. It only prohibits drivers that are not already installed locally from downloading.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows NT\Printers</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableWebPnPDownload</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="DisableWebPnPDownload_2" class="Machine" displayName="$(string.31584d1f053247a4993492ace70829e2)" explainText="$(string.cfff593b61dd4e4d9227e6f9b58d0f9c)" key="Software\Policies\Microsoft\Windows NT\Printers" valueName="DisableWebPnPDownload">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="31584d1f053247a4993492ace70829e2">Turn off downloading of print drivers over HTTP</string>
<string id="cfff593b61dd4e4d9227e6f9b58d0f9c">This policy setting controls whether the computer can download print driver packages over HTTP. To set up HTTP printing, printer drivers that are not available in the standard operating system installation might need to be downloaded over HTTP.</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional with SP2 or Windows Server 2003 family with SP1</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="100" ID="{46e26d52-9510-4c6a-8dbc-58cbfe54c857}" OriginalSettingID="{6c495e42-ef02-44ec-a811-f640f0942daf}" Name="Registry policy processing" LockdownDate="2011-10-12T11:37:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9361-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines when registry policies are updated.</ShortDescription>
<FullDescription>This policy setting determines when registry policies are updated. It affects all policies in the Administrative Templates folder, and any other policies that store values in the registry. If this policy setting is enabled, the following options are available:
• Do not apply during periodic background processing.
• Process even if the Group Policy objects have not changed.
Some settings that are configured through the Administrative Templates are made in areas of the registry that are accessible to users. User changes to these settings will be overwritten if this policy setting is enabled.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Group Policy</UIPath>
<DefaultValue>Not configured</DefaultValue>
<Vulnerability>You can enable this setting and then select the Process even if the Group Policy objects have not changed option to ensure that the policies will be reprocessed even if none have been changed. This way, any unauthorized changes that might have been configured locally are forced to match the domain–based Group Policy settings again.</Vulnerability>
<Countermeasure>Configure the Registry policy processing setting to Enabled. Then clear the Do not apply during periodic background processing check box, and select the Process even if the Group Policy objects have not changed check box.</Countermeasure>
<PotentialImpact>Group Policies will be reapplied every time they are refreshed, which could have a slight impact on performance.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine" />
<DataType>String</DataType>
</DiscoveryInfo>
<policy name="CSE_Registry" class="Machine" displayName="$(string.8910b2fe51eb4dee94b680d81a094361)" explainText="$(string.009cb1035bd94909bb4b4fe748f8ff7b)" presentation="$(presentation.CSE_Registry)" key="Software\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:elements xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:boolean id="CSE_NOBACKGROUND10" key="Software\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}" valueName="NoBackgroundPolicy">
<admx:trueValue>
<admx:decimal value="1" />
</admx:trueValue>
<admx:falseValue>
<admx:decimal value="0" />
</admx:falseValue>
</admx:boolean>
<admx:boolean id="CSE_NOCHANGES10" key="Software\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}" valueName="NoGPOListChanges">
<admx:trueValue>
<admx:decimal value="0" />
</admx:trueValue>
<admx:falseValue>
<admx:decimal value="1" />
</admx:falseValue>
</admx:boolean>
</admx:elements>
</policy>
<ADMLDefinition>
<presentation id="CSE_Registry">
<admx:checkBox refId="CSE_NOBACKGROUND10" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Do not apply during periodic background processing</admx:checkBox>
<admx:checkBox refId="CSE_NOCHANGES10" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Process even if the Group Policy objects have not changed</admx:checkBox>
</presentation>
<string id="8910b2fe51eb4dee94b680d81a094361">Registry policy processing</string>
<string id="009cb1035bd94909bb4b4fe748f8ff7b">This policy setting determines when registry policies are updated. It affects all policies in the Administrative Templates folder, and any other policies that store values in the registry. If this policy setting is enabled, the following options are available:
• Do not apply during periodic background processing.
• Process even if the Group Policy objects have not changed.
Some settings that are configured through the Administrative Templates are made in areas of the registry that are accessible to users. User changes to these settings will be overwritten if this policy setting is enabled.</string>
</ADMLDefinition>
<supportedOn>At least Windows 2000</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="101" ID="{085e1a51-4e69-47a5-8a03-5f073bb6cfe8}" OriginalSettingID="{a52b3c1b-5b21-4abf-a1cd-2dcb3338c957}" Name="Turn off Data Execution Prevention for Explorer" LockdownDate="2011-05-02T01:36:05Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9918-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Disabling data execution prevention can allow certain legacy plug-in applications to function without terminating Explorer.</ShortDescription>
<FullDescription>Disabling data execution prevention can allow certain legacy plug-in applications to function without terminating Explorer.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Windows Explorer</UIPath>
<DefaultValue>Not Configured</DefaultValue>
<Vulnerability>Data execution prevention helps reduce the risk of certain classes of attacks by blocking the execution of code stored where the system only expects data to be stored.</Vulnerability>
<Countermeasure>Configure Turn off Data Execution Prevention for Explorer to Disabled.</Countermeasure>
<PotentialImpact>Date execution prevent can cause certain plug-in applications for Windows Explorer to fail.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows\Explorer</mssasc-core:KeyPath>
<mssasc-core:ValueName>NoDataExecutionPrevention</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="NoDataExecutionPrevention" class="Machine" displayName="$(string.1abca0a63f5f464fbd438165dbf40792)" explainText="$(string.c6129f7a2dd1487dadf86fc1dc3207b2)" key="Software\Policies\Microsoft\Windows\Explorer" valueName="NoDataExecutionPrevention">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="1abca0a63f5f464fbd438165dbf40792">Turn off Data Execution Prevention for Explorer</string>
<string id="c6129f7a2dd1487dadf86fc1dc3207b2">Disabling data execution prevention can allow certain legacy plug-in applications to function without terminating Explorer.</string>
</ADMLDefinition>
<supportedOn>At least Windows 7 or Windows Server 2008 R2</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="102" ID="{545a92f8-05f8-4d8b-bb3b-c54071d59621}" OriginalSettingID="{ffdf73aa-bb21-413b-b25c-469871f03fd0}" Name="Turn off Windows Update device driver searching" LockdownDate="2011-10-12T11:38:00Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10093-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting specifies whether Windows will search Windows Update for device drivers when no local drivers for a device are present.</ShortDescription>
<FullDescription>This policy setting specifies whether Windows will search Windows Update for device drivers when no local drivers for a device are present.
Note See also Turn off Windows Update device driver search prompt in Administrative Templates/System, which governs whether an administrator is prompted before Windows Update is searched for device drivers if a driver is not found locally.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Internet Communication Management\Internet Communication settings</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>If users are able to download and install device drivers there is a small chance that they will install a driver that reduces system stability. There is an even smaller possibility that they will install a driver that includes malicious code. These risks are very low because Microsoft requires vendors to test drivers extensively before they can be published on Windows Update. </Vulnerability>
<Countermeasure>To prevent users from retrieving and installing device drivers from Windows Update enable this setting.</Countermeasure>
<PotentialImpact>Users will not be able to download new or updated device drivers from Windows Update.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows\DriverSearching</mssasc-core:KeyPath>
<mssasc-core:ValueName>DontSearchWindowsUpdate</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="DriverSearchPlaces_DontSearchWindowsUpdate" class="Machine" displayName="$(string.076055071c3340d2a01ad55c229547cc)" explainText="$(string.23f1c9ed588c48da97a012e7510a7a44)" key="Software\Policies\Microsoft\Windows\DriverSearching" valueName="DontSearchWindowsUpdate">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="076055071c3340d2a01ad55c229547cc">Turn off Windows Update device driver searching</string>
<string id="23f1c9ed588c48da97a012e7510a7a44">This policy setting specifies whether Windows will search Windows Update for device drivers when no local drivers for a device are present.
Note See also Turn off Windows Update device driver search prompt in Administrative Templates/System, which governs whether an administrator is prompted before Windows Update is searched for device drivers if a driver is not found locally.</string>
</ADMLDefinition>
<supportedOn>Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP SP2</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="103" ID="{d6003991-51df-4527-8cc9-bd0d5609e5f7}" OriginalSettingID="{f50c62f4-6c34-466b-b495-54c834820a24}" Name="User Account Control: Virtualize file and registry write failures to per-user locations" LockdownDate="2011-05-02T01:36:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8817-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting controls whether application write failures are redirected to defined registry and file system locations.</ShortDescription>
<FullDescription>This policy setting controls whether application write failures are redirected to defined registry and file system locations. This policy setting mitigates applications that run as administrator and write run-time application data to %ProgramFiles%, %Windir%, %Windir%\system32, or HKLM\Software.
The options are:
• Enabled: (Default) Application write failures are redirected at run time to defined user locations for both the file system and registry.
• Disabled: Applications that write data to protected locations fail.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>This setting reduces vulnerabilities by ensuring that legacy applications only write data to permitted locations.</Vulnerability>
<Countermeasure>Enable the User Account Control: Virtualize file and registry write failures to per-user locations setting.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnableVirtualization</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\EnableVirtualization" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="104" ID="{0ebb1667-2781-4a0d-833f-bf3872543a76}" OriginalSettingID="{d7b63d04-47af-4ba9-9e6c-9fa4bd3b23a6}" Name="Do not process the run once list" LockdownDate="2011-05-15T05:26:30Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10154-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting controls the default behavior of the AutoPlay setting.</ShortDescription>
<FullDescription>This policy setting causes the run once list, which is the list of programs that Windows Vista runs automatically when it starts, to be ignored. This policy setting differs from the Do not process the legacy run list setting in that programs on this list will run once the next time the client computer restarts and an administrator logs on. Setup and installation programs are sometimes added to this list to complete installations after a client computer restarts. If you enable this policy setting, attackers generally cannot use the run once list to launch rogue applications, which was a common method of attack in the past. A malicious user can exploit the run once list to install a program that may compromise the security of Windows Vista–based client computers, however since editing this list requires administrator privileges the importance of configuring this setting is not high.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Logon</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>A malicious user can exploit the run once list to install a program that may compromise the security of Windows clients.</Vulnerability>
<Countermeasure>Configure the Do not process the run once list setting to Enabled.</Countermeasure>
<PotentialImpact>If you enable the Do not process the run once list setting you should experience minimal functionality loss for users in your environment, especially if the clients have been configured with all of your organization's standard software before you apply this setting through Group Policy. However, this configuration may prevent some setup and installation programs, such as Internet Explorer, from working properly.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableLocalMachineRunOnce</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="DisableExplorerRunOnceLegacy_2" class="Machine" displayName="$(string.20fef51ff58e487e84707456641ae7f6)" explainText="$(string.d4152cca6fb24cb8b4d80a54b9fa33ed)" key="SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer" valueName="DisableLocalMachineRunOnce">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="20fef51ff58e487e84707456641ae7f6">Do not process the run once list</string>
<string id="d4152cca6fb24cb8b4d80a54b9fa33ed">This policy setting causes the run once list, which is the list of programs that Windows Vista runs automatically when it starts, to be ignored. This policy setting differs from the Do not process the legacy run list setting in that programs on this list will run once the next time the client computer restarts and an administrator logs on. Setup and installation programs are sometimes added to this list to complete installations after a client computer restarts. If you enable this policy setting, attackers generally cannot use the run once list to launch rogue applications, which was a common method of attack in the past. A malicious user can exploit the run once list to install a program that may compromise the security of Windows Vista–based client computers, however since editing this list requires administrator privileges the importance of configuring this setting is not high.</string>
</ADMLDefinition>
<supportedOn>At least Windows 2000</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="105" ID="{38b6ff0a-4f1e-4f44-8af8-cc0456695253}" OriginalSettingID="{45c48eca-f84e-4198-abdc-50a1e8041295}" Name="MSS: (AutoReboot) Allow Windows to automatically restart after a system crash (recommended except for highly secure environments)" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10303-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This entry appears as MSS: (AutoReboot) Allow Windows to automatically restart after a system crash (recommended except for highly secure environments) in the SCE.</ShortDescription>
<FullDescription>This entry appears as MSS: (AutoReboot) Allow Windows to automatically restart after a system crash (recommended except for highly secure environments) in the SCE.
This entry, when enabled, permits a server to automatically reboot after a fatal crash. It is enabled by default, which is undesirable on highly secure servers. You can add this registry value to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl\ subkey.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined
</DefaultValue>
<Vulnerability>There is some concern that a computer could get stuck in an endless loop of failures and reboots. However, the alternative to this entry may not be much more appealing—the computer will simply stop running.</Vulnerability>
<Countermeasure>Configure the MSS: (AutoReboot) Allow Windows to automatically restart after a system crash (recommended except for highly secure environments) entry to a value of Disabled.
The possible values for this registry entry are:
• 1 or 0. The default configuration is 1 (enabled).
For more information, see the Microsoft Knowledge Base article "How To Configure System Failure and Recovery Options in Windows" at http://support.microsoft.com/?kbid=307973.
In the SCE UI, the following options are available:
• Enabled
• Disabled
• Not Defined
</Countermeasure>
<PotentialImpact>The computer will no longer reboot automatically after a failure.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>SYSTEM\CurrentControlSet\Control\CrashControl</mssasc-core:KeyPath>
<mssasc-core:ValueName>AutoReboot</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl\AutoReboot" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Comment>
</Comment>
</SettingGroup>
<SettingGroup ID="{5d862b69-6a62-480f-86d9-c3532b6203cc}" Name="Identity Management" OriginalSettingGroupID="{379e9066-930f-4158-9262-8952ad262d44}">
<mssasc-core:Description>
</mssasc-core:Description>
<mssasc-core:Version Major="1" Minor="0" />
<Author>
</Author>
<Setting Index="106" ID="{9630f89d-f55b-4d72-85b2-9cc3739a9dfc}" OriginalSettingID="{9e5ba301-4a84-4069-a398-7de2932b1e8f}" Name="Accounts: Guest account status" LockdownDate="2011-08-22T10:48:30Z" GenerateDCM="false" GenerateSCAP="false" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8714-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether the Guest account is enabled or disabled. </ShortDescription>
<FullDescription>This policy setting determines whether the Guest account is enabled or disabled. The Guest account allows unauthenticated network users to gain access to the system. Note that this setting will have no impact when applied to the domain controller organizational unit via group policy because domain controllers have no local account database. It can be configured at the domain level via group policy, similar to account lockout and password policy settings.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>The default Guest account allows unauthenticated network users to log on as Guest with no password. These unauthorized users could access any resources that are accessible to the Guest account over the network. This capability means that any network shares with permissions that allow access to the Guest account, the Guests group, or the Everyone group will be accessible over the network, which could lead to the exposure or corruption of data.</Vulnerability>
<Countermeasure>Configure the Accounts: Guest account status setting to Disabled so that the built-in Guest account is no longer usable. </Countermeasure>
<PotentialImpact>All network users will need to authenticate before they can access shared resources. If you disable the Guest account and the Network Access: Sharing and Security Model option is set to Guest Only, network logons, such as those performed by the Microsoft Network Server (SMB Service), will fail. This policy setting should have little impact on most organizations because it is the default setting in Microsoft Windows® 2000, Windows XP, and Windows Server™ 2003.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Script" Scope="Machine">
<ScriptDiscoveryInfo>
<mssasc-core:ScriptType>VBScript</mssasc-core:ScriptType>
<mssasc-core:ScriptBody>'</mssasc-core:ScriptBody>
</ScriptDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="System Access" Name="EnableGuestAccount" DataType="REG_DWORD" />
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="107" ID="{0681de05-828d-451b-aaf9-1704c2ed8b86}" OriginalSettingID="{e197f79b-a454-407c-9307-7b3210313e61}" Name="Network access: Let Everyone permissions apply to anonymous users" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8936-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines what additional permissions are assigned for anonymous connections to the computer</ShortDescription>
<FullDescription>This policy setting determines what additional permissions are assigned for anonymous connections to the computer. If you enable this policy setting, anonymous Windows users are allowed to perform certain activities, such as enumerate the names of domain accounts and network shares. An unauthorized user could anonymously list account names and shared resources and use the information to guess passwords or perform social engineering attacks.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>An unauthorized user could anonymously list account names and shared resources and use the information to attempt to guess passwords, perform social engineering attacks, or launch DoS attacks.</Vulnerability>
<Countermeasure>Configure the Network access: Let Everyone permissions apply to anonymous users setting to Disabled. </Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>EveryoneIncludesAnonymous</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\EveryoneIncludesAnonymous" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:90" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="108" ID="{05538263-d4d3-40eb-929e-07c7fdfd8260}" OriginalSettingID="{6ca3233b-d0a5-4d2a-9078-21618b53133d}" Name="Accounts: Rename administrator account" LockdownDate="2011-08-10T03:25:58Z" GenerateDCM="false" GenerateSCAP="false" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8484-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting provides the ability to change the default administrator user name.</ShortDescription>
<FullDescription>The built-in local administrator account is a well-known account name that attackers will target. Microsoft recommends to choose another name for this account, and to avoid names that denote administrative or elevated access accounts. Be sure to also change the default description for the local administrator (through the Computer Management console).
Note This policy setting is not configured in the baseline, nor does Microsoft suggest a user name for the account. Suggested user names are omitted to ensure that organizations that implement this guidance will not use the same new user name in their environments.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Administrator</DefaultValue>
<Vulnerability>The Administrator account exists on all computers that run the Windows 2000, Windows Server 2003, or Windows XP Professional operating systems. If you rename this account, it is slightly more difficult for unauthorized persons to guess this privileged user name and password combination.
The built-in Administrator account cannot be locked out, regardless of how many times an attacker might use a bad password. This capability makes the Administrator account a popular target for brute force attacks that attempt to guess passwords. The value of this countermeasure is lessened because this account has a well-known SID, and there are third-party tools that allow authentication by using the SID rather than the account name. Therefore, even if you rename the Administrator account, an attacker could launch a brute force attack by using the SID to log on.
</Vulnerability>
<Countermeasure>Specify a new name in the Accounts: Rename administrator account setting to rename the Administrator account.</Countermeasure>
<PotentialImpact>You will have to inform users who are authorized to use this account of the new account name. (The guidance for this setting assumes that the Administrator account was not disabled, which was recommended earlier in this chapter.) </PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Script" Scope="Machine">
<ScriptDiscoveryInfo>
<mssasc-core:ScriptType>VBScript</mssasc-core:ScriptType>
<mssasc-core:ScriptBody>'</mssasc-core:ScriptBody>
</ScriptDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="System Access" Name="NewAdministratorName" DataType="REG_SZ" />
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="109" ID="{4aead19f-a276-4b88-990c-a8dfa231dae1}" OriginalSettingID="{d26ad9d1-e063-4c4e-bdb3-25b50cf3b184}" Name="Accounts: Rename guest account" LockdownDate="2011-08-10T03:25:58Z" GenerateDCM="false" GenerateSCAP="false" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9229-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting allows the name of the guest account to change.</ShortDescription>
<FullDescription>The built-in local guest account is another well-known name to attackers. Microsoft recommends to rename this account to something that does not indicate its purpose. Even if you disable this account, which is recommended, ensure that you rename it for added security.
Note This policy setting is not configured in the Security Templates, nor is a new user name for the account suggested here. Suggested user names are omitted to ensure that organizations that implement this guidance will not use the same new user name in their environments.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Guest</DefaultValue>
<Vulnerability>The Guest account exists on all computers that run the Windows 2000, Windows Server 2003, or Windows XP Professional operating systems. If you rename this account. it is slightly more difficult for unauthorized persons to guess this privileged user name and password combination.</Vulnerability>
<Countermeasure>Specify a new name in the Accounts: Rename guest account setting to rename the Guest account.</Countermeasure>
<PotentialImpact>There should be little impact, because the Guest account is disabled by default.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Script" Scope="Machine">
<ScriptDiscoveryInfo>
<mssasc-core:ScriptType>VBScript</mssasc-core:ScriptType>
<mssasc-core:ScriptBody>'</mssasc-core:ScriptBody>
</ScriptDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="System Access" Name="NewGuestName" DataType="REG_SZ" />
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="110" ID="{154408ea-0242-45d6-9230-0e0cbadd21d4}" OriginalSettingID="{4a9b2cb6-a61b-49c4-9170-6743d9846c4f}" Name="Accounts: Administrator account status" LockdownDate="2011-10-12T11:37:55Z" GenerateDCM="false" GenerateSCAP="false" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9199-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting enables or disables the built-in Administrator account during normal operation.</ShortDescription>
<FullDescription>This policy setting enables or disables the Administrator account during normal operation. When a computer is booted into safe mode, the Administrator account is always enabled, regardless of how this setting is configured. Note that this setting will have no impact when applied to the domain controller organizational unit via group policy because domain controllers have no local account database. It can be configured at the domain level via group policy, similar to account lockout and password policy settings.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>In some organizations, it can be a daunting management challenge to maintain a regular schedule for periodic password changes for local accounts. Therefore, you may want to disable the built-in Administrator account instead of relying on regular password changes to protect it from attack. Another reason to disable this built-in account is that it cannot be locked out no matter how many failed logons it accrues, which makes it a prime target for brute force attacks that attempt to guess passwords. Also, this account has a well-known security identifier (SID) and there are third-party tools that allow authentication by using the SID rather than the account name. This capability means that even if you rename the Administrator account, an attacker could launch a brute force attack by using the SID to log on.</Vulnerability>
<Countermeasure>Configure the Accounts: Administrator account status setting to Disabled so that the built-in Administrator account is no longer usable in a normal system startup.</Countermeasure>
<PotentialImpact>Maintenance issues can arise under certain circumstances if you disable the Administrator account. For example, if the secure channel between a member computer and the domain controller fails in a domain environment for any reason and there is no other local Administrator account, you must restart in safe mode to fix the problem that broke the secure channel.
If the current Administrator password does not meet the password requirements, you will not be able to re-enable the Administrator account after it is disabled. If this situation occurs, another member of the Administrators group must set the password on the Administrator account with the Local Users and Groups tool.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Script" Scope="Machine">
<ScriptDiscoveryInfo>
<mssasc-core:ScriptType>VBScript</mssasc-core:ScriptType>
<mssasc-core:ScriptBody>'</mssasc-core:ScriptBody>
</ScriptDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="System Access" Name="EnableAdminAccount" DataType="REG_DWORD" />
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Comment>
</Comment>
</SettingGroup>
<SettingGroup ID="{7bfc76fd-fcce-450e-babd-7c96a382197b}" Name="Password Attributes" OriginalSettingGroupID="{7dd08158-d7a8-4dec-afd4-f663ef644306}">
<mssasc-core:Description>
</mssasc-core:Description>
<mssasc-core:Version Major="1" Minor="0" />
<Author>
</Author>
<Setting Index="111" ID="{70ba3854-33f1-4402-b067-2bcadf0d7e66}" OriginalSettingID="{051cdac6-2234-4eb7-85eb-db391c469557}" Name="Accounts: Limit local account use of blank passwords to console logon only" LockdownDate="2011-11-01T10:59:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9418-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether local accounts that are not password protected can be used to log on from locations other than the physical computer console</ShortDescription>
<FullDescription>This policy setting determines whether local accounts that are not password protected can be used to log on from locations other than the physical computer console. If you enable this policy setting, local accounts that have blank passwords will not be able to log on to the network from remote client computers. Such accounts will only be able to log on at the keyboard of the computer.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>Blank passwords are a serious threat to computer security and should be forbidden through both organizational policy and suitable technical measures. In fact, the default settings for Active Directory® domains require complex passwords of at least seven characters. However, if users with the ability to create new accounts bypass your domain-based password policies, they could create accounts with blank passwords. For example, a user could build a stand-alone computer, create one or more accounts with blank passwords, and then join the computer to the domain. The local accounts with blank passwords would still function. Anyone who knows the name of one of these unprotected accounts could then use it to log on.</Vulnerability>
<Countermeasure>Enable the Accounts: Limit local account use of blank passwords to console logon only setting.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>LimitBlankPasswordUse</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\LimitBlankPasswordUse" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:42" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="112" ID="{d1cd54c8-2cd6-4123-b0da-e01eac9afde8}" OriginalSettingID="{794f9728-56e1-4e5e-b697-7079757f4ac3}" Name="Network security: Do not store LAN Manager hash value on next password change" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8937-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether the LAN Manager (LM) hash value for the new password is stored when the password is changed. </ShortDescription>
<FullDescription>This policy setting determines whether the LAN Manager (LM) hash value for the new password is stored when the password is changed. The LM hash is relatively weak and prone to attack compared to the cryptographically stronger Microsoft Windows NT® hash.
Note Older operating systems and some third-party applications may fail when this policy setting is enabled. Also you will need to change the password on all accounts after you enable this setting.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>The SAM file can be targeted by attackers who seek access to username and password hashes. Such attacks use special tools to crack passwords, which can then be used to impersonate users and gain access to resources on your network. These types of attacks will not be prevented if you enable this policy setting, but it will be much more difficult for these types of attacks to succeed.</Vulnerability>
<Countermeasure>Configure the Network security: Do not store LAN Manager hash value on next password change setting to Enabled. Require all users to set new passwords the next time they log in to the domain so that LAN Manager hashes are removed.</Countermeasure>
<PotentialImpact>Earlier operating systems such as Windows 95, Windows 98, and Windows ME as well as some third-party applications will fail.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>NoLMHash</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\NoLMHash" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:95" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="113" ID="{9e417a02-8f2a-4e5f-9962-5a9274616230}" OriginalSettingID="{b1b4a762-3114-438b-92cf-90f021714790}" Name="Microsoft network client: Send unencrypted password to third-party SMB servers" LockdownDate="2011-05-02T01:36:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9265-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Disable this policy setting to prevent the SMB redirector from sending plaintext passwords during authentication to third-party SMB servers that do not support password encryption. </ShortDescription>
<FullDescription>Disable this policy setting to prevent the SMB redirector from sending plaintext passwords during authentication to third-party SMB servers that do not support password encryption. Microsoft recommends that you disable this policy setting unless there is a strong business case to enable it. If this policy setting is enabled, unencrypted passwords will be allowed across the network.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>If you enable this policy setting, the server can transmit passwords in plaintext across the network to other computers that offer SMB services. These other computers may not use any of the SMB security mechanisms that are included with Windows Server 2003. </Vulnerability>
<Countermeasure>Configure the Microsoft network client: Send unencrypted password to connect to third-party SMB servers setting to Disabled. </Countermeasure>
<PotentialImpact>Some very old applications and operating systems such as MS-DOS, Windows for Workgroups 3.11, and Windows 95a may not be able to communicate with the servers in your organization by means of the SMB protocol.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanmanWorkstation\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnablePlainTextPassword</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters\EnablePlainTextPassword" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:82" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="114" ID="{dcfdbeca-9a86-4676-8137-0f0829f0a2f7}" OriginalSettingID="{c357e3e7-40b5-47db-8e88-0c071e687ffe}" Name="Require a Password When a Computer Wakes (Plugged In)" LockdownDate="2011-10-12T11:37:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9670-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Specifies whether or not the user is prompted for a password when the system resumes from sleep. </ShortDescription>
<FullDescription>Specifies whether or not the user is prompted for a password when the system resumes from sleep. </FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Power Management\Sleep Settings</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Enabling this setting ensures that anyone who wakes an unattended computer from sleep state will have to provide logon credentials before they can access the system.</Vulnerability>
<Countermeasure>Configure Require a Password When a Computer Wakes (Plugged In) to Enabled.</Countermeasure>
<PotentialImpact>If you enable this policy, or if it is not configured, the user is prompted for a password when the system resumes from sleep.
If you disable this policy, the user is not prompted for a password when the system resumes from sleep.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51</mssasc-core:KeyPath>
<mssasc-core:ValueName>ACSettingIndex</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="ACPromptForPasswordOnResume_2" class="Machine" displayName="$(string.b45f2abd316d41049747f3b9f6b3ab60)" explainText="$(string.b8d1df1b10ac423bb2149f6678213cf5)" key="Software\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51" valueName="ACSettingIndex">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="b45f2abd316d41049747f3b9f6b3ab60">Require a Password When a Computer Wakes (Plugged In)</string>
<string id="b8d1df1b10ac423bb2149f6678213cf5">Specifies whether or not the user is prompted for a password when the system resumes from sleep. </string>
</ADMLDefinition>
<supportedOn>At least Windows Vista</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="115" ID="{c65edca7-226d-4e48-a78f-c9b2f8cc7058}" OriginalSettingID="{74870acb-ad3d-4bec-a067-1b1895ce2621}" Name="Interactive logon: Prompt user to change password before expiration" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9307-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines how far in advance users are warned that their password will expire. </ShortDescription>
<FullDescription>This policy setting determines how far in advance users are warned that their password will expire. Microsoft recommends that you configure this policy setting to 14 days to sufficiently warn users when their passwords will expire.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>14 days</DefaultValue>
<Vulnerability>Microsoft recommends that user passwords be configured to expire periodically. Users will need to be warned that their passwords are going to expire, or they may inadvertently be locked out of the computer when their passwords expire. This condition could lead to confusion for users who access the network locally, or make it impossible for users to access your organization’s network through dial-up or virtual private network (VPN) connections.</Vulnerability>
<Countermeasure>Configure the Interactive logon: Prompt user to change password before expiration setting to 14 days.</Countermeasure>
<PotentialImpact>Users will see a dialog box prompt to change their password each time that they log on to the domain when their password is configured to expire in 14 or fewer days.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="9999">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>day(s)</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows NT\CurrentVersion\Winlogon</mssasc-core:KeyPath>
<mssasc-core:ValueName>passwordexpirywarning</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\PasswordExpiryWarning" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:74" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="116" ID="{013e644e-eb3a-4a43-b35b-3a003882e176}" OriginalSettingID="{33b3bd9f-1a8d-4882-94ef-47f5094df784}" Name="Require a Password When a Computer Wakes (On Battery)" LockdownDate="2011-10-12T11:37:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9829-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Specifies whether or not the user is prompted for a password when the system resumes from sleep. </ShortDescription>
<FullDescription>Specifies whether or not the user is prompted for a password when the system resumes from sleep. </FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Power Management\Sleep Settings</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Enabling this setting ensures that anyone who wakes an unattended computer from sleep state will have to provide logon credentials before they can access the system.</Vulnerability>
<Countermeasure>Configure Require a Password When a Computer Wakes (On Battery) to Enabled.</Countermeasure>
<PotentialImpact>If you enable this policy, or if it is not configured, the user is prompted for a password when the system resumes from sleep.
If you disable this policy, the user is not prompted for a password when the system resumes from sleep.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51</mssasc-core:KeyPath>
<mssasc-core:ValueName>DCSettingIndex</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="DCPromptForPasswordOnResume_2" class="Machine" displayName="$(string.0440b5d94d254183bca63b152307bd5f)" explainText="$(string.cf7e43882c1c40be9b738572e78780fe)" key="Software\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51" valueName="DCSettingIndex">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="0440b5d94d254183bca63b152307bd5f">Require a Password When a Computer Wakes (On Battery)</string>
<string id="cf7e43882c1c40be9b738572e78780fe">Specifies whether or not the user is prompted for a password when the system resumes from sleep. </string>
</ADMLDefinition>
<supportedOn>At least Windows Vista</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="117" ID="{d1c4d69f-f20e-4e51-a4bb-4df603d826bf}" OriginalSettingID="{970b184b-62b1-46d1-9262-195dec171cd9}" Name="Do not allow passwords to be saved" LockdownDate="2011-05-02T01:36:00Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10090-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting helps prevent Terminal Services clients from saving passwords on a computer.</ShortDescription>
<FullDescription>This policy setting helps prevent Terminal Services clients from saving passwords on a computer. Note If this policy setting was previously configured as Disabled or Not configured, any previously saved passwords will be deleted the first time a Terminal Services client disconnects from any server.
</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Connection Client</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>An attacker with physical access to the computer may be able to break the protection guarding saved passwords. An attacker who compromises a user's account and connects to their computer could use saved passwords to gain access to additional hosts.</Vulnerability>
<Countermeasure>Enable this setting.</Countermeasure>
<PotentialImpact>If you enable this policy setting, the password saving checkbox is disabled for Terminal Services clients and users will not be able to save passwords. </PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisablePasswordSaving</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="TS_CLIENT_DISABLE_PASSWORD_SAVING_2" class="Machine" displayName="$(string.9ccd794b3b8c40d1ae62e66c83a08e2b)" explainText="$(string.7c202b4697f646f48ece41e3af7758b6)" key="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" valueName="DisablePasswordSaving">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="9ccd794b3b8c40d1ae62e66c83a08e2b">Do not allow passwords to be saved</string>
<string id="7c202b4697f646f48ece41e3af7758b6">This policy setting helps prevent Terminal Services clients from saving passwords on a computer. Note If this policy setting was previously configured as Disabled or Not configured, any previously saved passwords will be deleted the first time a Terminal Services client disconnects from any server.
</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional with SP2 or Windows Server 2003 family with SP1</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="oval:com.secure-elements.oval:def:6596" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="118" ID="{999f78ef-2e2e-41b5-9284-ede0123c6d85}" OriginalSettingID="{5ae8ac79-c4f6-4b24-9906-12326755c58b}" Name="Domain member: Maximum machine account password age" LockdownDate="2011-08-05T07:16:32Z" GenerateDCM="true" GenerateSCAP="false" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9123-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines the maximum allowable age for a computer account password.</ShortDescription>
<FullDescription>This policy setting determines the maximum allowable age for a computer account password. By default, domain members automatically change their domain passwords every 30 days. If you increase this interval significantly or set it to 0 so that the computers no longer change their passwords, an attacker would have more time to undertake a brute force attack against one of the computer accounts.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>30 days</DefaultValue>
<Vulnerability>In Active Directory–based domains, each computer has an account and password just like every user. By default, the domain members automatically change their domain password every 30 days. If you increase this interval significantly, or set it to 0 so that the computers no longer change their passwords, an attacker will have more time to undertake a brute force attack to guess the password of one or more computer accounts.</Vulnerability>
<Countermeasure>Configure the Domain member: Maximum machine account password age setting to 30 days.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="9999">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>day(s)</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Script" Scope="Machine">
<ScriptDiscoveryInfo>
<mssasc-core:ScriptType>VBScript</mssasc-core:ScriptType>
<mssasc-core:ScriptBody>Option Explicit
WScript.Echo CheckRange("HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\maximumpasswordage", "{BaselineValue}")
Function CheckRange(RegKey, ExpectedValue)
On Error Resume Next
Err.Clear
' if "{BaselineValue}" = "No Key", CInt() will failed, set ExpectedValue = -1 in that case.
ExpectedValue = CInt(ExpectedValue)
If (Err.Number <> 0) Then
ExpectedValue = -1
Err.Clear
End If
'WScript.Echo "ExpectedValue: " & ExpectedValue
Dim Compliant, NonCompliant, CurrentValue
' Read Current value in this client
CurrentValue = GetCurrentValue(RegKey)
'WScript.Echo "CurrentValue: " & CurrentValue
' Case: Current Value = No Key
If (CurrentValue = "") Then
'WScript.Echo "CurrentValue: No Key"
CheckRange = ""
Exit Function
End If
CurrentValue = CInt(CurrentValue)
' set Compliant and NonCompliant return value
Compliant = ExpectedValue
NonCompliant = CurrentValue
' Case: If ExpectedValue = 0, Means Unlimited, any value (CurrentValue) is Compliant
If (ExpectedValue = 0) Then
CheckRange = Compliant
Exit Function
End If
' Case: If ExpectedValue <> 0, The CurrentValue should LessEqules Expected Value, that is Compliant
If (CurrentValue <= ExpectedValue) Then
CheckRange = Compliant
Exit Function
End If
' Other Case: NonCompliant
CheckRange = NonCompliant
End Function
Function GetCurrentValue(RegKey)
On Error Resume Next
Err.Clear
Dim RegObject
Set RegObject = WScript.CreateObject("WScript.Shell")
GetCurrentValue = RegObject.RegRead(RegKey)
' Case: No Key
If (Err.Number <> 0) Then
Err.Clear
GetCurrentValue = ""
Exit Function
End If
End Function</mssasc-core:ScriptBody>
</ScriptDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\maximumpasswordage" DataType="REG_DWORD" />
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="119" ID="{f77f0e76-2de7-4bdc-b549-1539f366c603}" OriginalSettingID="{2448f308-6d86-4bbd-a39f-b7503385fdd7}" Name="Always prompt for password upon connection" LockdownDate="2011-10-12T11:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10103-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting specifies whether Terminal Services always prompts the client computer for a password upon connection.</ShortDescription>
<FullDescription>This policy setting specifies whether Terminal Services always prompts the client computer for a password upon connection. You can use this policy setting to enforce a password prompt for users who log on to Terminal Services, even if they already provided the password in the Remote Desktop Connection client. By default, Terminal Services allows users to automatically log on if they enter a password in the Remote Desktop Connection client.
Note If you do not configure this policy setting, the local computer administrator can use the Terminal Services Configuration tool to either allow or prevent passwords from being automatically sent.
</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security</UIPath>
<DefaultValue>Not Configured
</DefaultValue>
<Vulnerability>Users have the option to store both their username and password when they create a new Remote Desktop connection shortcut. If the server that runs Terminal Services allows users who have used this feature to log on to the server but not enter their password, then it is possible that an attacker who has gained physical access to the user's computer could connect to a Terminal Server through the Remote Desktop connection shortcut, even though they may not know the user's password.</Vulnerability>
<Countermeasure>Configure the Always prompt client for a password on connection setting to Enabled.</Countermeasure>
<PotentialImpact>Users will always have to enter their password when they establish new Terminal Server sessions.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services</mssasc-core:KeyPath>
<mssasc-core:ValueName>fPromptForPassword</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="TS_PASSWORD" class="Machine" displayName="$(string.51930728a8784371a32ee43aaf30c46a)" explainText="$(string.a36b67959aab41b2b5b091c1a15ccaeb)" key="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" valueName="fPromptForPassword">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="51930728a8784371a32ee43aaf30c46a">Always prompt for password upon connection</string>
<string id="a36b67959aab41b2b5b091c1a15ccaeb">This policy setting specifies whether Terminal Services always prompts the client computer for a password upon connection. You can use this policy setting to enforce a password prompt for users who log on to Terminal Services, even if they already provided the password in the Remote Desktop Connection client. By default, Terminal Services allows users to automatically log on if they enter a password in the Remote Desktop Connection client.
Note If you do not configure this policy setting, the local computer administrator can use the Terminal Services Configuration tool to either allow or prevent passwords from being automatically sent.
</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional or Windows Server 2003 family</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="oval:com.secure-elements.oval:def:6599" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="120" ID="{f33945b7-f22e-4133-91e2-6ac3b34370ec}" OriginalSettingID="{b44fadd3-f7c2-45dc-98dd-5e9ba179d89d}" Name="Domain member: Disable machine account password changes" LockdownDate="2011-08-05T07:16:32Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9295-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether a domain member can periodically change its computer account password. </ShortDescription>
<FullDescription>This policy setting determines whether a domain member can periodically change its computer account password. If you enable this policy setting, the domain member will be prevented from changing its computer account password. If you disable this policy setting, the domain member can change its computer account password as specified by the Domain Member: Maximum machine account password age setting, which by default is every 30 days. Computers that cannot automatically change their account passwords are potentially vulnerable, because an attacker might be able to determine the password for the system's domain account.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>The default configuration for Windows Server 2003–based computers that belong to a domain is that they are automatically required to change the passwords for their accounts every 30 days. If you disable this policy setting, computers that run Windows Server 2003 will retain the same passwords as their computer accounts. Computers that are no longer able to automatically change their account password are at risk from an attacker who could determine the password for the computer’s domain account.</Vulnerability>
<Countermeasure>Verify that the Domain member: Disable machine account password changes setting is configured to Disabled.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Netlogon\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>disablepasswordchange</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\disablepasswordchange" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:64" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="121" ID="{605bc6fb-834b-40f0-90ff-ae131080fe70}" OriginalSettingID="{e3ac5993-d420-4039-abd9-1867cd3dfddf}" Name="Network access: Do not allow storage of passwords and credentials for network authentication" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8654-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting controls authentication credential storage and passwords on the local system.</ShortDescription>
<FullDescription>This policy setting determines whether the Stored User Names and Passwords feature may save passwords or credentials for later use when it gains domain authentication. If you enable this policy setting, the Stored User Names and Passwords feature of Windows does not store passwords and credentials.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Passwords that are cached can be accessed by the user when logged on to the computer. Although this information may sound obvious, a problem can arise if the user unknowingly executes hostile code that reads the passwords and forwards them to another, unauthorized user.</Vulnerability>
<Countermeasure>Configure the Network access: Do not allow storage of passwords and credentials for network authentication for network authentication setting to Enabled.</Countermeasure>
<PotentialImpact>Users will be forced to enter passwords whenever they log on to their Passport account or other network resources that aren’t accessible to their domain account. Testing has shown that clients running Windows Vista or Windows Server 2008 will be unable to connect to Distributed File System (DFS) shares in untrusted domains. Enabling this setting also makes it impossible to specify alternate credentials for scheduled tasks, this can cause a variety of problems. For example, some third party backup products will no longer work. This policy setting should have no impact on users who access network resources that are configured to allow access with their Active Directory–based domain account.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableDomainCreds</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\DisableDomainCreds" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:89" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Comment>
</Comment>
</SettingGroup>
<SettingGroup ID="{bc2ff884-fa9e-4657-a4ba-56449f8df97e}" Name="Network Protection" OriginalSettingGroupID="{bab83781-60db-40b1-9e42-d6ab637d1e19}">
<mssasc-core:Description>
</mssasc-core:Description>
<mssasc-core:Version Major="1" Minor="0" />
<Author>
</Author>
<Setting Index="122" ID="{ee2775b4-c93e-4c5f-9fc2-bfbeff323fe9}" OriginalSettingID="{2e65a105-5cb1-473d-b0ca-c933415d91be}" Name="Windows Firewall: Domain: Firewall state" LockdownDate="2011-05-02T01:36:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9465-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Select On to allow Windows Firewall to filter network traffic. Select Off to prevent Windows Firewall from using any firewall rules or connection security rules for this profile.</ShortDescription>
<FullDescription>Select On (recommended) to have Windows Firewall with Advanced Security use the settings for this profile to filter network traffic. If you select Off, Windows Firewall with Advanced Security will not use any of the firewall rules or connection security rules for this profile.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Domain Profile</UIPath>
<DefaultValue>On</DefaultValue>
<Vulnerability>If the firewall is turned off all traffic will be able to access the system and an attacker may be more easily able to remotely exploit a weakness in a network service.</Vulnerability>
<Countermeasure>Configure this setting to 'On.'</Countermeasure>
<PotentialImpact>None, this is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="On (recommended)">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Off">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="On (recommended)">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\WindowsFirewall\DomainProfile</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnableFirewall</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="123" ID="{0d62d8f2-6ee2-4bb5-bdb3-570ac2fd7185}" OriginalSettingID="{0091ec7e-714b-4bb3-9a36-a73412c6c1f9}" Name="Windows Firewall: Private: Display a notification" LockdownDate="2011-08-05T07:16:34Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8884-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Select this option to have Windows Firewall with Advanced Security display notifications to the user when a program is blocked from receiving inbound connections.</ShortDescription>
<FullDescription>Select this option to have Windows Firewall with Advanced Security display notifications to the user when a program is blocked from receiving inbound connections.
Note When the Apply local firewall rules setting is configured to No, Microsoft recommends also configuring the Display a notification setting to No. Otherwise, users will continue to receive messages that ask if they want to unblock a restricted inbound connection, but the user's response will be ignored.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Private Profile</UIPath>
<DefaultValue>Yes</DefaultValue>
<Vulnerability>Some organizations may prefer to avoid alarming users when firewall rules block certain types of network activity. However, notifications can be helpful when troubleshooting network issues involving the firewall.</Vulnerability>
<Countermeasure>Configure this setting as appropriate to allow or prevent the display of these notifications.</Countermeasure>
<PotentialImpact>If you configure this policy setting to Yes, Windows Firewall will display these notifications. </PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Yes (default)">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Yes (default)">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\WindowsFirewall\PrivateProfile</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableNotifications</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="124" ID="{97711f97-8b54-4a4c-b635-71b943d2d853}" OriginalSettingID="{8998a3ee-1763-4627-9251-e473ec7e4c41}" Name="MSS: (TcpMaxDataRetransmissions) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)" LockdownDate="2011-05-22T06:25:35Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9456-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This registry value entry appears as MSS: (TcpMaxDataRetransmissions) How many times unacknowledged data is retransmitted (3 recommended, 5 is default) in the SCE.</ShortDescription>
<FullDescription>The registry value entry TCPMaxDataRetransmissions was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip
\Parameters\ registry key. The entry appears as MSS: (TcpMaxDataRetransmissions) How many times unacknowledged data is retransmitted (3 recommended, 5 is default) in the SCE.
This setting controls the number of times that TCP retransmits an individual data segment (non-connect segment) before the connection is aborted. The retransmission time-out is doubled with each successive retransmission on a connection. It is reset when responses resume. The base time-out value is dynamically determined by the measured round-trip time on the connection.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>5</DefaultValue>
<Vulnerability>A malicious user could exhaust a target computer's resources if it never sent any acknowledgment messages for data that was transmitted by the target computer.</Vulnerability>
<Countermeasure>Configure the MSS: (TcpMaxDataRetransmissions) How many times unacknowledged data is retransmitted (3 recommended, 5 is default) entry to a value of 3. The possible values for this registry entry are:
• 0 to 0xFFFFFFFF. The default configuration is 5.
In the SCE UI, this setting can be adjusted using a text entry box:
• A user-defined number
• Not Defined
</Countermeasure>
<PotentialImpact>TCP starts a retransmission timer when each outbound segment is passed to the IP. If no acknowledgment is received for the data in a given segment before the timer expires, then the segment is retransmitted up to three times.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="9999">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Tcpip\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>TcpMaxDataRetransmissions</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\TcpMaxDataRetransmissions" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:126" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="125" ID="{23f9a43b-a364-4b30-9ccb-5aef1d033433}" OriginalSettingID="{902a957b-c9b3-4302-883a-394555087509}" Name="Windows Firewall: Public: Display a notification" LockdownDate="2011-05-10T12:35:38Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9742-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Setting displays notifications to the user when a program is blocked from receiving inbound connections.</ShortDescription>
<FullDescription>Select this option to have Windows Firewall with Advanced Security display notifications to the user when a program is blocked from receiving inbound connections.
Note When the Apply local firewall rules setting is configured to No, Microsoft recommends also configuring the Display a notification setting to No. Otherwise, users will continue to receive messages that ask if they want to unblock a restricted inbound connection, but the user's response will be ignored.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Public Profile</UIPath>
<DefaultValue>Yes</DefaultValue>
<Vulnerability>Some organizations may prefer to avoid alarming users when firewall rules block certain types of network activity. However, notifications can be helpful when troubleshooting network issues involving the firewall.</Vulnerability>
<Countermeasure>Configure this setting as appropriate to allow or prevent the display of these notifications.</Countermeasure>
<PotentialImpact>If you configure this policy setting to Yes, Windows Firewall will display these notifications. </PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Yes">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\WindowsFirewall\PublicProfile</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableNotifications</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="126" ID="{2e371982-9233-40c0-83ab-291434fab365}" OriginalSettingID="{533bf252-df1b-4b5a-9320-8da18b19bcd2}" Name="Windows Firewall: Private: Apply local firewall rules" LockdownDate="2011-08-05T07:16:34Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9663-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting controls whether local administrators are allowed to create local firewall rules that apply together with firewall rules configured by Group Policy. </ShortDescription>
<FullDescription>This setting controls whether local administrators are allowed to create local firewall rules that apply together with firewall rules configured by Group Policy. </FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Private Profile</UIPath>
<DefaultValue>Yes</DefaultValue>
<Vulnerability>Users with administrative privileges might create firewall rules that expose the system to remote attack.</Vulnerability>
<Countermeasure>Disable this setting to override firewall rules created locally by administrators.</Countermeasure>
<PotentialImpact>If you configure this setting to No, administrators can still create firewall rules, but the rules will not be applied. This setting is available only when configuring the policy through Group Policy.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Yes (default)">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Yes (default)">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\WindowsFirewall\PrivateProfile</mssasc-core:KeyPath>
<mssasc-core:ValueName>AllowLocalPolicyMerge</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="127" ID="{204580f7-4e41-4efb-9874-e84a0f122cb4}" OriginalSettingID="{21d226de-3201-414e-a16a-b626b6d0cc26}" Name="MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)" LockdownDate="2011-05-22T06:25:35Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8655-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The entry appears as MSS: (DisableIPSourceRouting) IPv6 source routing protection level (protects against packet spoofing) in the SCE.</ShortDescription>
<FullDescription>This entry appears as MSS: (DisableIPSourceRouting) IPv6 source routing protection level (protects against packet spoofing) in the SCE. IP source routing is a mechanism that allows the sender to determine the IP route that a datagram should follow through the network.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not Defined</DefaultValue>
<Vulnerability>An attacker could use source routed packets to obscure their identity and location. Source routing allows a computer that sends a packet to specify the route that the packet takes.</Vulnerability>
<Countermeasure>Configure the MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing) entry to a value of Highest protection, source routing is completely disabled.
The possible values for this registry entry are:
• 0, 1, or 2. The default configuration is 1 (source routed packets are not forwarded).
In the SCE UI, the following list of options appears:
• No additional protection, source routed packets are allowed.
• Medium, source routed packets ignored when IP forwarding is enabled.
• Highest protection, source routing is completely disabled.
• Not Defined.
</Countermeasure>
<PotentialImpact>If you configure this value to 2, all incoming source routed packets will be dropped.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Highest protection, source routing is completely disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No additional protection, source routed packets are allowed">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Medium, source routed packets ignored when IP forwarding is enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Highest protection, source routing is completely disabled">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Tcpip6\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableIPSourceRouting</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Tcpip6\Parameters\DisableIPSourceRouting" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:111" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="128" ID="{c138280d-0c23-4b35-a6fc-87c47fda667e}" OriginalSettingID="{f5513338-0fa1-484e-83fb-9a5bd3954d44}" Name="Windows Firewall: Private: Apply local connection security rules" LockdownDate="2011-08-05T07:16:34Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9712-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting controls whether local administrators are allowed to create connection security rules that apply together with connection security rules configured by Group Policy.</ShortDescription>
<FullDescription>This setting controls whether local administrators are allowed to create connection security rules that apply together with connection security rules configured by Group Policy.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Private Profile</UIPath>
<DefaultValue>Yes</DefaultValue>
<Vulnerability>Users with administrative privileges might create firewall rules that expose the system to remote attack.</Vulnerability>
<Countermeasure>Disable this setting to override firewall rules created locally by administrators.</Countermeasure>
<PotentialImpact>If you configure this setting to No, administrators can still create firewall rules, but the rules will not be applied. This setting is available only when configuring the policy through Group Policy.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Yes (default)">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Yes (default)">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\WindowsFirewall\PrivateProfile</mssasc-core:KeyPath>
<mssasc-core:ValueName>AllowLocalIPsecPolicyMerge</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="129" ID="{3db1f779-3892-4d8d-a7d8-9c98f0ca1ffb}" OriginalSettingID="{d493f92b-2fe2-4489-a4e6-03fd2e3710cd}" Name="Windows Firewall: Private: Firewall state" LockdownDate="2011-08-05T07:16:34Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9739-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Windows Firewall with Advanced Security uses the settings for this profile to filter network traffic.</ShortDescription>
<FullDescription>Select On (recommended) to have Windows Firewall with Advanced Security use the settings for this profile to filter network traffic. If you select Off, Windows Firewall with Advanced Security will not use any of the firewall rules or connection security rules for this profile.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Private Profile</UIPath>
<DefaultValue>On</DefaultValue>
<Vulnerability>If the firewall is turned off all traffic will be able to access the system and an attacker may be more easily able to remotely exploit a weakness in a network service.</Vulnerability>
<Countermeasure>Configure this setting to 'On.'</Countermeasure>
<PotentialImpact>None, this is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="On (recommended)">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Off">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="On (recommended)">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\WindowsFirewall\PrivateProfile</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnableFirewall</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="130" ID="{f26658af-ce03-4505-8263-1a598ebfe27c}" OriginalSettingID="{1582b4ec-79f8-46f1-a4d6-901dd6e7d3ce}" Name="Windows Firewall: Public: Inbound connections" LockdownDate="2011-08-05T07:16:34Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9007-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting determines the behavior for inbound connections that do not match an inbound firewall rule. The default behavior is to block connections unless there are firewall rules to allow the connection. </ShortDescription>
<FullDescription>This setting determines the behavior for inbound connections that do not match an inbound firewall rule. The default behavior is to block connections unless there are firewall rules to allow the connection. </FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Public Profile</UIPath>
<DefaultValue>Block</DefaultValue>
<Vulnerability>If the firewall allows all traffic to access the system then an attacker may be more easily able to remotely exploit a weakness in a network service.</Vulnerability>
<Countermeasure>Configure this setting to block inbound connections by default.</Countermeasure>
<PotentialImpact>None, this is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine" />
<DataType>String</DataType>
</DiscoveryInfo>
<policy name="Public_Inbound_Connections" class="Machine" displayName="$(string.9f1c46b0f55e47afaa6e799ac48f8996)" explainText="$(string.bc2180e7a85145c0a16b1f1d3d53088d)" presentation="$(presentation.Public_Inbound_Connections)" key="Software\Policies\Microsoft\WindowsFirewall\PublicProfile">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:elements xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:enum id="DefaultInboundActions" key="Software\Policies\Microsoft\WindowsFirewall\PublicProfile" valueName="DefaultInboundAction">
<admx:item displayName="$(string.ac1a7471dc154e72b11333ca4d0ba7fd)">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.7eaac7d719c144f5bb9c3d0b6584f970)">
<admx:value>
<admx:decimal value="1" />
</admx:value>
<admx:valueList>
<admx:item key="Software\Policies\Microsoft\WindowsFirewall\PublicProfile" valueName="DoNotAllowExceptions">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
</admx:valueList>
</admx:item>
<admx:item displayName="$(string.db3e011b2c404199ab0abd7305edbd6d)">
<admx:value>
<admx:decimal value="0" />
</admx:value>
</admx:item>
</admx:enum>
</admx:elements>
</policy>
<ADMLDefinition>
<presentation id="Public_Inbound_Connections">
<admx:dropdownList refId="DefaultInboundActions" noSort="true" defaultItem="0" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Inbound connections</admx:dropdownList>
</presentation>
<string id="9f1c46b0f55e47afaa6e799ac48f8996">Windows Firewall: Public: Inbound connections</string>
<string id="bc2180e7a85145c0a16b1f1d3d53088d">This setting determines the behavior for inbound connections that do not match an inbound firewall rule. The default behavior is to block connections unless there are firewall rules to allow the connection. </string>
<string id="ac1a7471dc154e72b11333ca4d0ba7fd">Block (default)</string>
<string id="7eaac7d719c144f5bb9c3d0b6584f970">Block all connections</string>
<string id="db3e011b2c404199ab0abd7305edbd6d">Allow</string>
</ADMLDefinition>
<supportedOn>At least Windows Vista</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="131" ID="{ee7799ac-d3c4-4061-bc72-701fa8963916}" OriginalSettingID="{4558d6d1-85c5-4c90-b09c-d263d9833e5e}" Name="MSS: (TcpMaxDataRetransmissions IPv6) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)" LockdownDate="2011-05-22T06:25:35Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9487-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This registry value entry appears as MSS: (TcpMaxDataRetransmissions) IPv6 How many times unacknowledged data is retransmitted (3 recommended, 5 is default) in the SCE.</ShortDescription>
<FullDescription>The registry value entry TCPMaxDataRetransmissions for IPv6 was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip6
\Parameters\ registry key. The entry appears as MSS: (TcpMaxDataRetransmissions) IPv6 How many times unacknowledged data is retransmitted (3 recommended, 5 is default) in the SCE.
This setting controls the number of times that TCP retransmits an individual data segment (non-connect segment) before the connection is aborted. The retransmission time-out is doubled with each successive retransmission on a connection. It is reset when responses resume. The base time-out value is dynamically determined by the measured round-trip time on the connection.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>5</DefaultValue>
<Vulnerability>A malicious user could exhaust a target computer's resources if it never sent any acknowledgment messages for data that was transmitted by the target computer.</Vulnerability>
<Countermeasure>Configure the MSS: (TcpMaxDataRetransmissions) IPv6 How many times unacknowledged data is retransmitted (3 recommended, 5 is default) entry to a value of 3. The possible values for this registry entry are:
• 0 to 0xFFFFFFFF. The default configuration is 5.
In the SCE UI, this setting can be adjusted using a text entry box:
• A user-defined number
• Not Defined
</Countermeasure>
<PotentialImpact>TCP starts a retransmission timer when each outbound segment is passed to the IP. If no acknowledgment is received for the data in a given segment before the timer expires, then the segment is retransmitted up to three times.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="9999">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Tcpip6\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>TcpMaxDataRetransmissions</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Tcpip6\Parameters\TcpMaxDataRetransmissions" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="132" ID="{d4b34b26-3436-4ca9-9883-9df57f1192a7}" OriginalSettingID="{691c581a-3b42-408b-abbe-f0bea9de3156}" Name="Windows Firewall: Private: Outbound connections" LockdownDate="2011-08-05T07:16:34Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8870-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting determines the behavior for outbound connections that do not match an outbound firewall rule. If Outbound connections are set to Block and deploy the firewall policy by using a GPO, cannot receive subsequent Group Policy updates. </ShortDescription>
<FullDescription>This setting determines the behavior for outbound connections that do not match an outbound firewall rule. The default behavior is to allow connections unless there are firewall rules that block the connection.
Important If you set Outbound connections to Block and then deploy the firewall policy by using a GPO, computers that receive the GPO settings cannot receive subsequent Group Policy updates unless you create and deploy an outbound rule that enables Group Policy to work. Predefined rules for Core Networking include outbound rules that enable Group Policy to work. Ensure that these outbound rules are active, and thoroughly test firewall profiles before deploying.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Private Profile</UIPath>
<DefaultValue>Allow</DefaultValue>
<Vulnerability>Some people believe that it is prudent to block all outbound connections except those specifically approved by the user or administrator. Microsoft disagrees with this opinion, blocking outbound connections by default will force users to deal with a large number of dialog boxes prompting them to authorize or block applications such as their web browser or instant messaging software. Additionally, blocking outbound traffic has little value because if an attacker has compromised the system they can reconfigure the firewall anyway.</Vulnerability>
<Countermeasure>Configure this setting to allow outbound connections.</Countermeasure>
<PotentialImpact>None, this is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Allow (default)">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Block">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Allow (default)">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\WindowsFirewall\PrivateProfile</mssasc-core:KeyPath>
<mssasc-core:ValueName>DefaultOutboundAction</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="133" ID="{e58f7b1a-f57f-46ab-a8d2-1a1eb7095a4a}" OriginalSettingID="{01cfd956-48cc-4ad6-94ff-b8f7ca488a91}" Name="Windows Firewall: Public: Allow unicast response" LockdownDate="2011-11-01T11:08:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9773-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Controls whether computer receives unicast responses to its outgoing multicast or broadcast messages.</ShortDescription>
<FullDescription>This option is useful if you need to control whether this computer receives unicast responses to its outgoing multicast or broadcast messages.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Public Profile</UIPath>
<DefaultValue>Yes</DefaultValue>
<Vulnerability>An attacker could respond to broadcast or multicast message with malicious payloads.</Vulnerability>
<Countermeasure>Disable this setting to prevent the client from receiving unicast responses.</Countermeasure>
<PotentialImpact> If you enable this setting and this computer sends multicast or broadcast messages to other computers, Windows Firewall with Advanced Security waits as long as three seconds for unicast responses from the other computers and then blocks all later responses. If you disable this setting and this computer sends a multicast or broadcast message to other computers, Windows Firewall with Advanced Security blocks the unicast responses sent by those other computers.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Yes">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\WindowsFirewall\PublicProfile</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableUnicastResponsesToMulticastBroadcast</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="134" ID="{80feb8df-d6d2-4bb2-9900-05ab7470aca8}" OriginalSettingID="{968787a1-6a19-4c96-82dd-ca531f84666d}" Name="Windows Firewall: Public: Apply local firewall rules" LockdownDate="2011-05-02T01:36:07Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9786-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting controls whether local administrators are allowed to create local firewall rules that apply with other firewall rules enforced by Group Policy.</ShortDescription>
<FullDescription>This setting controls whether local administrators are allowed to create local firewall rules that apply together with firewall rules configured by Group Policy. </FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Public Profile</UIPath>
<DefaultValue>Yes</DefaultValue>
<Vulnerability>Users with administrative privileges might create firewall rules that expose the system to remote attack.</Vulnerability>
<Countermeasure>Disable this setting to override firewall rules created locally by administrators.</Countermeasure>
<PotentialImpact>If you configure this setting to No, administrators can still create firewall rules, but the rules will not be applied. This setting is available only when configuring the policy through Group Policy.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Yes (default)">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Yes (default)">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\WindowsFirewall\PublicProfile</mssasc-core:KeyPath>
<mssasc-core:ValueName>AllowLocalPolicyMerge</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="135" ID="{b9b9852d-d5dd-4818-90c5-030a9fa1ae1a}" OriginalSettingID="{856f9866-0378-4952-a164-4d524770bb2a}" Name="Windows Firewall: Public: Firewall state" LockdownDate="2011-05-02T01:36:07Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9593-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Windows Firewall with Advanced Security uses the settings for this profile to filter network traffic.</ShortDescription>
<FullDescription>Select On (recommended) to have Windows Firewall with Advanced Security use the settings for this profile to filter network traffic. If you select Off, Windows Firewall with Advanced Security will not use any of the firewall rules or connection security rules for this profile.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Public Profile</UIPath>
<DefaultValue>On</DefaultValue>
<Vulnerability>If the firewall is turned off all traffic will be able to access the system and an attacker may be more easily able to remotely exploit a weakness in a network service.</Vulnerability>
<Countermeasure>Configure this setting to 'On.'</Countermeasure>
<PotentialImpact>None, this is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="On (recommended)">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Off">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="On (recommended)">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\WindowsFirewall\PublicProfile</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnableFirewall</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="136" ID="{a6fa9373-0401-4ce7-aa44-3649c9b5b21b}" OriginalSettingID="{7f8c238a-8a21-44e0-8704-0dabc0e02ae5}" Name="MSS: (PerformRouterDiscovery) Allow IRDP to detect and configure Default Gateway addresses (could lead to DoS)" LockdownDate="2011-05-22T06:25:35Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9458-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This registry value entry appears as MSS: (PerformRouterDiscovery) Allow IRDP to detect and configure Default Gateway addresses (could lead to DoS) in the SCE.</ShortDescription>
<FullDescription>The registry value entry PerformRouterDiscovery was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\ registry key. The entry appears as MSS: (PerformRouterDiscovery) Allow IRDP to detect and configure Default Gateway addresses (could lead to DoS) in the SCE.
This setting is used to enable or disable the Internet Router Discovery Protocol (IRDP), which allows the system to detect and configure default gateway addresses automatically as described in RFC 1256 on a per-interface basis.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enable only if DHCP sends the Perform Router Discovery option</DefaultValue>
<Vulnerability>An attacker who has gained control of a computer on the same network segment could configure a computer on the network to impersonate a router. Other computers with IRDP enabled would then attempt to route their traffic through the already compromised computer.</Vulnerability>
<Countermeasure>Configure the MSS: (PerformRouterDiscovery) Allow IRDP to detect and configure Default Gateway addresses (could lead to DoS) entry to a value of Disabled.
The possible values for this registry entry are:
• 0, 1, or 2. The default configuration is 2 (enable only if DHCP sends the Perform Router Discovery option).
In the SCE UI, these options appear as:
• 0 (Disabled)
• 1 (Enabled)
• 2 (enable only if DHCP sends the Perform Router Discovery option)
• Not Defined
</Countermeasure>
<PotentialImpact>If you disable this entry, Windows Server 2003 (which supports the IRDP) cannot automatically detect and configure default gateway addresses on the computer.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Tcpip\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>PerformRouterDiscovery</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\PerformRouterDiscovery" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:121" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="137" ID="{e527bd6d-fa91-474d-9b8f-45b623024bd8}" OriginalSettingID="{838a6c32-08ab-4aa1-9c18-540fb154de6a}" Name="MSS: (NoDefaultExempt) Configure IPSec exemptions for various types of network traffic." LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9439-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The entry appears as MSS: (NoDefaultExempt) Configure IPSec exemptions for various types of network traffic in the SCE.</ShortDescription>
<FullDescription>The registry value entry NoDefaultExempt was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\IPSEC\ registry key. The entry appears as MSS: (NoDefaultExempt) Configure IPSec exemptions for various types of network traffic in the SCE.
The default exemptions to IPsec policy filters are documented in the online help for the specific operating system. These filters make it possible for Internet Key Exchange (IKE) and the Kerberos authentication protocol to function. The filters also make it possible for the network Quality of Service (QoS) to be signaled (RSVP) when the data traffic is secured by IPsec, and for traffic that IPsec might not secure such as multicast and broadcast traffic.
IPsec is increasingly used for basic host-firewall packet filtering, particularly in Internet-exposed scenarios, and the affect of these default exemptions has not been fully understood. Therefore, some IPsec administrators may create IPsec policies that they think are secure, but are not actually secure against inbound attacks that use the default exemptions.
For additional information, see the Knowledge Base article 811832, "IPSec Default Exemptions Can Be Used to Bypass IPsec Protection in Some Scenarios."
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not Defined</DefaultValue>
<Vulnerability>As IPsec is increasingly used for basic host-firewall packet filtering, particularly in Internet-exposed scenarios, the affect of these default exemptions has not been fully understood. Some IPsec administrators may create IPsec policies that they think are secure, but are not actually secure against inbound attacks that use the default exemptions. Attackers could forge network traffic that appears to consist of legitimate IKE, RSVP, or Kerberos protocol packets but direct them to other network services on the host.</Vulnerability>
<Countermeasure>Do not configure the MSS: (NoDefaultExempt) Enable NoDefaultExempt for IPSec Filtering (recommended) entry except on computers that use IPsec filters, where this entry should be configured to a value of Enabled.
The possible values for this registry entry are:
• A value of 0 specifies that multicast, broadcast, RSVP, Kerberos, and IKE (ISAKMP) traffic are exempt from IPsec filters, which is the default configuration for Windows 2000 and Windows XP. Use this setting only if you require compatibility with an IPsec policy that already exists or Windows 2000 and Windows XP.
• A value of 1 specifies that Kerberos protocol and RSVP traffic are not exempt from IPsec filters, but multicast, broadcast, and IKE traffic are exempt. This setting is the recommended value for Windows 2000 and Windows XP.
• A value of 2 specifies that multicast and broadcast traffic are not exempt from IPsec filters, but RSVP, Kerberos, and IKE traffic are exempt. This setting is supported only in Windows Server 2003.
• A value of 3 specifies that only IKE traffic is exempt from IPsec filters. This setting is supported only in Windows Server 2003, which contains this default behavior although the registry key does not exist by default.
In the SCE UI, these options appear as:
• 0
• 1
• 2
• 3
</Countermeasure>
<PotentialImpact>After you enable this entry, security policies that already exist may have to be changed to work correctly. For details, refer to the Microsoft Knowledge Base article "IPSec Default Exemptions Can Be Used to Bypass IPsec Protection in Some Scenarios" at http://support.microsoft.com/default.aspx?kbid=811832,which was referenced earlier in this section.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Allow all exceptions (lease secure)">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Multicast, broadcast, and ISAKMP are exempt (Best for Windows XP)">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="RSVP, Kerberos, and ISAKMP are exempt">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
<Mapping FriendlyName="Only ISAKMP is exempt (recommended for Windows Server 2003)">
<BehaviorDescription />
<DCMValue ValueA="3" />
<SCAPValue ValueA="3" />
<GPOValue ValueA="3" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\IPSEC</mssasc-core:KeyPath>
<mssasc-core:ValueName>NoDefaultExempt</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\IPSEC\NoDefaultExempt" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="138" ID="{19e95a46-d240-4df0-8b1e-70d2014fbec1}" OriginalSettingID="{567434c1-c73f-4a24-8553-eaf1fd70fc90}" Name="Windows Firewall: Domain: Allow unicast response" LockdownDate="2011-05-02T01:36:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9069-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This option determines if this computer can receive unicast responses to multicast or broadcast messages that it initiates. Unsolicited unicast responses are blocked regardless of this setting.</ShortDescription>
<FullDescription>This option is useful if you need to control whether this computer receives unicast responses to its outgoing multicast or broadcast messages.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Domain Profile</UIPath>
<DefaultValue>Yes</DefaultValue>
<Vulnerability>An attacker could respond to broadcast or multicast message with malicious payloads.</Vulnerability>
<Countermeasure>Disable this setting to prevent the client from receiving unicast responses.</Countermeasure>
<PotentialImpact> If you enable this setting and this computer sends multicast or broadcast messages to other computers, Windows Firewall with Advanced Security waits as long as three seconds for unicast responses from the other computers and then blocks all later responses. If you disable this setting and this computer sends a multicast or broadcast message to other computers, Windows Firewall with Advanced Security blocks the unicast responses sent by those other computers.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Yes">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\WindowsFirewall\DomainProfile</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableUnicastResponsesToMulticastBroadcast</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="139" ID="{7449ec76-fe13-40d7-9336-6087547ff5ba}" OriginalSettingID="{db12a482-5822-44ba-b35d-e944d3ddd528}" Name="Windows Firewall: Domain: Apply local connection security rules" LockdownDate="2011-05-02T01:36:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9329-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting controls whether local administrators are allowed to create connection security rules that apply with other connection security rules enforced by Group Policy.</ShortDescription>
<FullDescription>This setting controls whether local administrators are allowed to create connection security rules that apply together with connection security rules configured by Group Policy.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Domain Profile</UIPath>
<DefaultValue>Yes</DefaultValue>
<Vulnerability>Users with administrative privileges might create firewall rules that expose the system to remote attack.</Vulnerability>
<Countermeasure>Disable this setting to override firewall rules created locally by administrators.</Countermeasure>
<PotentialImpact>If you configure this setting to No, administrators can still create firewall rules, but the rules will not be applied. This setting is available only when configuring the policy through Group Policy.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Yes (default)">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Yes (default)">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\WindowsFirewall\DomainProfile</mssasc-core:KeyPath>
<mssasc-core:ValueName>AllowLocalIPsecPolicyMerge</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="140" ID="{31fc7cb9-90a1-4095-a254-14a8dd75ee26}" OriginalSettingID="{0a80cfc2-0dcd-4566-b4be-6d8224961f83}" Name="Windows Firewall: Domain: Apply local firewall rules" LockdownDate="2011-05-02T01:36:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9686-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting controls whether local administrators are allowed to create local firewall rules that apply together with firewall rules configured by Group Policy.</ShortDescription>
<FullDescription>This setting controls whether local administrators are allowed to create local firewall rules that apply together with firewall rules configured by Group Policy. </FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Domain Profile</UIPath>
<DefaultValue>Yes</DefaultValue>
<Vulnerability>Users with administrative privileges might create firewall rules that expose the system to remote attack.</Vulnerability>
<Countermeasure>Disable this setting to override firewall rules created locally by administrators.</Countermeasure>
<PotentialImpact>If you configure this setting to No, administrators can still create firewall rules, but the rules will not be applied. This setting is available only when configuring the policy through Group Policy.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Yes (default)">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Yes (default)">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\WindowsFirewall\DomainProfile</mssasc-core:KeyPath>
<mssasc-core:ValueName>AllowLocalPolicyMerge</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="141" ID="{50bc83e9-55b7-49cc-87ec-d4faa56c69a8}" OriginalSettingID="{b2dd11f1-f8e5-41d5-928a-44858db8616e}" Name="MSS: (Hidden) Hide Computer From the Browse List (not recommended except for highly secure environments)" LockdownDate="2011-06-01T01:16:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8560-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The registry value entry appears as MSS: (Hidden) Hide Computer From the Browse List (not recommended except for highly secure environments) in the SCE.</ShortDescription>
<FullDescription>The registry value entry Hidden was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanserver\Parameters\ registry key. The entry appears as MSS: (Hidden) Hide Computer From the Browse List (not recommended except for highly secure environments) in the SCE.
You can configure a computer so that it does not send announcements to browsers on the domain. If you do so, you hide the computer from the Browse list, which means that the computer will stop announcing itself to other computers on the same network. An attacker who knows the name of a computer can more easily gather additional information about the system. You can enable this setting to remove one method that an attacker might use to gather information about computers on the network. Also, this setting can help reduce network traffic when enabled. However, the security benefits of this setting are small because attackers can use alternative methods to identify and locate potential targets. For this reason, Microsoft recommends to configure this setting to Enabled in high security environments, and to configure it to Not Defined in enterprise environments.
For additional information, see the Knowledge Base article 321710, "HOW TO: Hide a Windows 2000-Based Computer from the Browser List."
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not Defined</DefaultValue>
<Vulnerability>An attacker who knows the name of a computer can more easily gather additional information about the computer. If you enable this entry, you remove one method that an attacker might use to gather information about computers on the network. Also, if you enable this entry you can help reduce network traffic. However, the vulnerability is small because attackers can use alternative methods to identify and locate potential targets.</Vulnerability>
<Countermeasure>Do not configure the MSS: (Hidden) Hide Computer From the Browse List (not recommended except for highly secure environments) entry except on highly secure computers, where it should be configured to a value of Enabled.
The possible values for this registry entry are:
● 1 or 0. The default configuration is 0 (disabled).
In the SCE UI, these options appear as:
● Enabled
● Disabled
● Not Defined
</Countermeasure>
<PotentialImpact>The computer will no longer appear on the Browser list or in Network Neighborhood on other computers on the same network.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Lanmanserver\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>Hidden</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Lanmanserver\Parameters\Hidden" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:114" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="142" ID="{9ed01778-21e7-4b1e-b88e-6939d117f08a}" OriginalSettingID="{3fe3c052-d096-4bc2-8d03-7ddb03f3b1f6}" Name="Windows Firewall: Private: Allow unicast response" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9522-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This is an advanced security setting for the Windows Firewall that you can use to allow unicast responses on computers running Windows Vista or later.</ShortDescription>
<FullDescription>This option is useful if you need to control whether this computer receives unicast responses to its outgoing multicast or broadcast messages.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Private Profile</UIPath>
<DefaultValue>Yes</DefaultValue>
<Vulnerability>An attacker could respond to broadcast or multicast message with malicious payloads.</Vulnerability>
<Countermeasure>Disable this setting to prevent the client from receiving unicast responses.</Countermeasure>
<PotentialImpact> If you enable this setting and this computer sends multicast or broadcast messages to other computers, Windows Firewall with Advanced Security waits as long as three seconds for unicast responses from the other computers and then blocks all later responses. If you disable this setting and this computer sends a multicast or broadcast message to other computers, Windows Firewall with Advanced Security blocks the unicast responses sent by those other computers.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Yes">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\WindowsFirewall\PrivateProfile</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableUnicastResponsesToMulticastBroadcast</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="143" ID="{b6329fe9-70d3-4c68-9bf5-98f602ed36b2}" OriginalSettingID="{96596e24-66e0-4347-961c-c52d6a410804}" Name="Windows Firewall: Domain: Inbound connections" LockdownDate="2011-05-02T01:36:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9620-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting determines the behavior for inbound connections that do not match an inbound firewall rule.</ShortDescription>
<FullDescription>This setting determines the behavior for inbound connections that do not match an inbound firewall rule. The default behavior is to block connections unless there are firewall rules to allow the connection. </FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Domain Profile</UIPath>
<DefaultValue>Block</DefaultValue>
<Vulnerability>If the firewall allows all traffic to access the system then an attacker may be more easily able to remotely exploit a weakness in a network service.</Vulnerability>
<Countermeasure>Configure this setting to block inbound connections by default.</Countermeasure>
<PotentialImpact>None, this is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine" />
<DataType>String</DataType>
</DiscoveryInfo>
<policy name="Domain_Inbound_Connections" class="Machine" displayName="$(string.e4cb88eac6fb4214a00a3aaa4ff96481)" explainText="$(string.f7d7f95f5e7c49d1b854e835c0e99ee6)" presentation="$(presentation.Domain_Inbound_Connections)" key="Software\Policies\Microsoft\WindowsFirewall\DomainProfile">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:elements xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:enum id="DefaultInboundActions" key="Software\Policies\Microsoft\WindowsFirewall\DomainProfile" valueName="DefaultInboundAction">
<admx:item displayName="$(string.3dc8e9cfabac4a4d9dc4e289fdf262da)">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.5b909c6772ee4e94a42982964ba1339e)">
<admx:value>
<admx:decimal value="1" />
</admx:value>
<admx:valueList>
<admx:item key="Software\Policies\Microsoft\WindowsFirewall\DomainProfile" valueName="DoNotAllowExceptions">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
</admx:valueList>
</admx:item>
<admx:item displayName="$(string.41b15bca0b8e428fafb97f090511ae78)">
<admx:value>
<admx:decimal value="0" />
</admx:value>
</admx:item>
</admx:enum>
</admx:elements>
</policy>
<ADMLDefinition>
<presentation id="Domain_Inbound_Connections">
<admx:dropdownList refId="DefaultInboundActions" noSort="true" defaultItem="0" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Inbound connections</admx:dropdownList>
</presentation>
<string id="e4cb88eac6fb4214a00a3aaa4ff96481">Windows Firewall: Domain: Inbound connections</string>
<string id="f7d7f95f5e7c49d1b854e835c0e99ee6">This setting determines the behavior for inbound connections that do not match an inbound firewall rule. The default behavior is to block connections unless there are firewall rules to allow the connection. </string>
<string id="3dc8e9cfabac4a4d9dc4e289fdf262da">Block (default)</string>
<string id="5b909c6772ee4e94a42982964ba1339e">Block all connections</string>
<string id="41b15bca0b8e428fafb97f090511ae78">Allow</string>
</ADMLDefinition>
<supportedOn>At least Windows Vista</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="144" ID="{8bb50fdf-497a-407e-8b90-2355b7fba2c1}" OriginalSettingID="{27abca4f-4873-490c-87b6-e84d2533ba13}" Name="Windows Firewall: Domain: Display a notification" LockdownDate="2011-05-10T12:35:38Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9774-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Select this option to have Windows Firewall with Advanced Security display notifications to the user when a program is blocked from receiving inbound connections.</ShortDescription>
<FullDescription>Select this option to have Windows Firewall with Advanced Security display notifications to the user when a program is blocked from receiving inbound connections.
Note When the Apply local firewall rules setting is configured to No, Microsoft recommends also configuring the Display a notification setting to No. Otherwise, users will continue to receive messages that ask if they want to unblock a restricted inbound connection, but the user's response will be ignored.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Domain Profile</UIPath>
<DefaultValue>Yes</DefaultValue>
<Vulnerability>Some organizations may prefer to avoid alarming users when firewall rules block certain types of network activity. However, notifications can be helpful when troubleshooting network issues involving the firewall.</Vulnerability>
<Countermeasure>Configure this setting as appropriate to allow or prevent the display of these notifications.</Countermeasure>
<PotentialImpact>If you configure this policy setting to Yes, Windows Firewall will display these notifications. </PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Yes (default)">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Yes (default)">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\WindowsFirewall\DomainProfile</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableNotifications</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="145" ID="{f8f37b46-5b7e-48d9-92a4-408f28c7b30e}" OriginalSettingID="{849952c3-4163-4e4d-9320-138c4af87134}" Name="Windows Firewall: Public: Apply local connection security rules" LockdownDate="2011-05-02T01:36:07Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9817-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting controls whether local administrators are allowed to create connection security rules that apply with other connection security rules enforced by Group Policy.</ShortDescription>
<FullDescription>This setting controls whether local administrators are allowed to create connection security rules that apply together with connection security rules configured by Group Policy.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Public Profile</UIPath>
<DefaultValue>Yes</DefaultValue>
<Vulnerability>Users with administrative privileges might create firewall rules that expose the system to remote attack.</Vulnerability>
<Countermeasure>Disable this setting to override firewall rules created locally by administrators.</Countermeasure>
<PotentialImpact>If you configure this setting to No, administrators can still create firewall rules, but the rules will not be applied. This setting is available only when configuring the policy through Group Policy.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Yes">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\WindowsFirewall\PublicProfile</mssasc-core:KeyPath>
<mssasc-core:ValueName>AllowLocalIPsecPolicyMerge</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="146" ID="{91bb8506-e5c5-4221-a58f-e836f736208f}" OriginalSettingID="{d23eb0d5-b330-4ad7-b489-bcb975e1e2d5}" Name="MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes" LockdownDate="2011-05-22T06:25:35Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8513-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The entry appears as MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes in the SCE.</ShortDescription>
<FullDescription>The registry value entry EnableICMPRedirect was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\ registry key. The entry appears as MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes in the SCE.
Internet Control Message Protocol (ICMP) redirects cause the stack to plumb host routes. These routes override the Open Shortest Path First (OSPF)–generated routes. Microsoft recommends to configure this setting to Not Defined for enterprise environments and to Disabled for high security environments.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>This behavior is expected. The problem is that the 10 minute time-out period for the ICMP redirect-plumbed routes temporarily creates a network situation in which traffic will no longer be routed properly for the affected host. </Vulnerability>
<Countermeasure>Configure the MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes entry to a value of Disabled.
The possible values for this registry entry are:
• 1 or 0. The default configuration is 1 (enabled).
In the SCE UI, these options appear as:
• Enabled
• Disabled
• Not Defined
</Countermeasure>
<PotentialImpact>When Routing and Remote Access Service (RRAS) is configured as an autonomous system boundary router (ASBR), it does not correctly import connected interface subnet routes. Instead, this router injects host routes into the OSPF routes. However, the OSPF router can not be used as an ASBR router, and when connected interface subnet routes are imported into OSPF the result is confusing routing tables with strange routing paths.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Tcpip\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnableICMPRedirect</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\EnableICMPRedirect" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:113" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="147" ID="{194ff3d9-ba8a-481f-b8b9-002760e1276c}" OriginalSettingID="{6cd6ebda-aa2e-472a-8ea7-580e704c47d3}" Name="MSS: (KeepAliveTime) How often keep-alive packets are sent in milliseconds" LockdownDate="2011-05-22T06:25:35Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9426-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The registry value entry appears as MSS: (KeepAliveTime) How often keep-alive packets are sent in milliseconds (300,000 is recommended) in the SCE.</ShortDescription>
<FullDescription>The registry value entry KeepAliveTime was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\ registry key. The entry appears as MSS: (KeepAliveTime) How often keep-alive packets are sent in milliseconds (300,000 is recommended) in the SCE.
This value controls how often TCP attempts to verify that an idle connection is still intact by sending a keep-alive packet. If the remote computer is still reachable, it acknowledges the keep-alive packet.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not Defined</DefaultValue>
<Vulnerability>An attacker who is able to connect to network applications could establish numerous connections to cause a DoS condition.</Vulnerability>
<Countermeasure>Configure the MSS: (KeepAliveTime) How often keep-alive packets are sent in milliseconds (300,000 is recommended) entry to a value of 300000 or 5 minutes.
The possible values for this registry entry are:
• 1 through 0xFFFFFFFF. The default configuration is 7,200,000 (two hours).
In the SCE UI, the following list of options appears:
• 150000 or 2.5 minutes
• 300000 or 5 minutes (recommended)
• 600000 or 10 minutes
• 1200000 or 20 minutes
• 2400000 or 40 minutes
• 3600000 or 1 hour
• 7200000 or 2 hours (default value)
• Not Defined
</Countermeasure>
<PotentialImpact>Keep-alive packets are not sent by default by Windows. However, some applications may configure the TCP stack flag that requests keep-alive packets. For such configurations, you can lower this value from the default setting of two hours to five minutes to disconnect inactive sessions more quickly.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="150000 or 2.5 minutes">
<BehaviorDescription />
<DCMValue ValueA="150000" />
<SCAPValue ValueA="150000" />
<GPOValue ValueA="150000" />
</Mapping>
<Mapping FriendlyName="300000 or 5 minutes (recommended)">
<BehaviorDescription />
<DCMValue ValueA="300000" />
<SCAPValue ValueA="300000" />
<GPOValue ValueA="300000" />
</Mapping>
<Mapping FriendlyName="600000 or 10 minutes">
<BehaviorDescription />
<DCMValue ValueA="600000" />
<SCAPValue ValueA="600000" />
<GPOValue ValueA="600000" />
</Mapping>
<Mapping FriendlyName="1200000 or 20 minute">
<BehaviorDescription />
<DCMValue ValueA="1200000" />
<SCAPValue ValueA="1200000" />
<GPOValue ValueA="1200000" />
</Mapping>
<Mapping FriendlyName="2400000 or 40 minutes">
<BehaviorDescription />
<DCMValue ValueA="2400000" />
<SCAPValue ValueA="2400000" />
<GPOValue ValueA="2400000" />
</Mapping>
<Mapping FriendlyName="3600000 or 1 hour">
<BehaviorDescription />
<DCMValue ValueA="3600000" />
<SCAPValue ValueA="3600000" />
<GPOValue ValueA="3600000" />
</Mapping>
<Mapping FriendlyName="7200000 or 2 hours (default value)">
<BehaviorDescription />
<DCMValue ValueA="7200000" />
<SCAPValue ValueA="7200000" />
<GPOValue ValueA="7200000" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Tcpip\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>KeepAliveTime</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:115" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="148" ID="{ad6d56d7-4087-4287-aa24-23e6f0ab2eeb}" OriginalSettingID="{21e5ee29-51b2-4719-b979-af03e47a128e}" Name="MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)" LockdownDate="2011-05-22T06:25:35Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9496-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The entry appears as MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing) in the SCE.</ShortDescription>
<FullDescription>The registry value entry DisableIPSourceRouting was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\ registry key. The entry appears as MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing) in the SCE.
IP source routing is a mechanism that allows the sender to determine the IP route that a datagram should take through the network. Microsoft recommends to configure this setting to Not Defined for enterprise environments and to Highest Protection for high security environments to completely disable source routing.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not Defined</DefaultValue>
<Vulnerability>An attacker could use source routed packets to obscure their identity and location. Source routing allows a computer that sends a packet to specify the route that the packet takes.</Vulnerability>
<Countermeasure>Configure the MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing) entry to a value of Highest protection, source routing is completely disabled.
The possible values for this registry entry are:
• 0, 1, or 2. The default configuration is 1 (source routed packets are not forwarded).
In the SCE UI, the following list of options appears:
• No additional protection, source routed packets are allowed.
• Medium, source routed packets ignored when IP forwarding is enabled.
• Highest protection, source routing is completely disabled.
• Not Defined.</Countermeasure>
<PotentialImpact>If you configure this value to 2, all incoming source routed packets will be dropped.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Highest protection, source routing is completely disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No additional protection, source routed packets are allowed">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Medium, source routed packets ignored when IP forwarding is enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Highest protection, source routing is completely disabled">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Tcpip\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableIPSourceRouting</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\DisableIPSourceRouting" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:111" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="149" ID="{eb2729bd-189e-4e49-8f12-f72cd675ff82}" OriginalSettingID="{4d558e02-b2d3-44bf-928a-17fba6a3af45}" Name="MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers" LockdownDate="2011-06-01T01:16:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8562-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The registry value entry appears as MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers in the SCE.</ShortDescription>
<FullDescription>The registry value entry NoNameReleaseOnDemand was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netbt\
Parameters\ registry key. The entry appears as MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers in the SCE.
NetBIOS over TCP/IP is a network protocol that among other things provides a way to easily resolve NetBIOS names that are registered on Windows–based systems to the IP addresses that are configured on those systems. This setting determines whether the computer releases its NetBIOS name when it receives a name-release request.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not Defined</DefaultValue>
<Vulnerability>The NetBT protocol is designed not to use authentication, and is therefore vulnerable to spoofing. Spoofing makes a transmission appear to come from a user other than the user who performed the action. A malicious user could exploit the unauthenticated nature of the protocol to send a name-conflict datagram to a target computer, which would cause the computer to relinquish its name and not respond to queries.
The result of such an attack could be to cause intermittent connectivity issues on the target computer, or even to prevent the use of Network Neighborhood, domain logons, the NET SEND command, or additional NetBIOS name resolution.
For more information, see the Microsoft Knowledge Base article "MS00-047: NetBIOS Vulnerability May Cause Duplicate Name on the Network Conflicts" at http://support.microsoft.com/default.aspx?kbid=269239.
</Vulnerability>
<Countermeasure>Configure the MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers (Only recommended for servers) entry to a value of Enabled.
The possible values for this registry entry are:
• 1 or 0. The default configuration is 1 (enabled).
In the SCE UI, these options appear as:
• Enabled
• Disabled
• Not Defined
Alternatively, you could disable the use of WINS in your environment, and further ensure that all applications rely upon DNS for name resolution services. Although this approach is a recommended long-term strategy, it is generally impractical for most organizations to attempt as a short-term solution. Organizations that still run WINS generally have application dependencies that cannot be quickly resolved without upgrades and software rollouts, which require careful plans and significant time commitments.
If you cannot deploy this countermeasure and you want to guarantee NetBIOS name resolution, you can take the additional step of "pre-loading" NetBIOS names in the LMHOSTS file on certain computers. For more information about how to pre-load the LMHOSTS file, see the Microsoft Knowledge Base article "MS00-047: NetBIOS Vulnerability May Cause Duplicate Name on the Network Conflicts" that was referenced earlier in this section.
Note: Maintenance of LMHOSTS files in most environments requires a significant amount of effort. Microsoft encourages the use of WINS instead of LMHOSTS.
</Countermeasure>
<PotentialImpact>An attacker could send a request over the network and query a computer to release its NetBIOS name. As with any change that could affect applications, Microsoft recommends that you test this change in a non-production environment before you change the production environment.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Netbt\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>NoNameReleaseOnDemand</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Netbt\Parameters\NoNameReleaseOnDemand" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:118" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="150" ID="{e86c5885-b74c-4438-bae6-d655b5d6c002}" OriginalSettingID="{e95c4963-098c-4bd8-bc1a-2980c12b506c}" Name="Windows Firewall: Private: Inbound connections" LockdownDate="2011-08-05T07:16:34Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9694-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting determines the behavior for inbound connections that do not match an inbound firewall rule. The default behavior is to block connections unless there are firewall rules to allow the connection. </ShortDescription>
<FullDescription>This setting determines the behavior for inbound connections that do not match an inbound firewall rule. The default behavior is to block connections unless there are firewall rules to allow the connection. </FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Private Profile</UIPath>
<DefaultValue>Block</DefaultValue>
<Vulnerability>If the firewall allows all traffic to access the system then an attacker may be more easily able to remotely exploit a weakness in a network service.</Vulnerability>
<Countermeasure>Configure this setting to block inbound connections by default.</Countermeasure>
<PotentialImpact>None, this is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine" />
<DataType>String</DataType>
</DiscoveryInfo>
<policy name="Private_Inbound_Connections" class="Machine" displayName="$(string.a539d4656a8d46beb0c02421820ef768)" explainText="$(string.e5cd19c4c45647b3928099e47f9f2c0f)" presentation="$(presentation.Private_Inbound_Connections)" key="Software\Policies\Microsoft\WindowsFirewall\PrivateProfile">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:elements xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:enum id="DefaultInboundActions" key="Software\Policies\Microsoft\WindowsFirewall\PrivateProfile" valueName="DefaultInboundAction">
<admx:item displayName="$(string.43bcf2ef7f9e4f21a3222e0b58894de8)">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.d0bc2a3f6ddc47a8b9223d512f3ac51a)">
<admx:value>
<admx:decimal value="1" />
</admx:value>
<admx:valueList>
<admx:item key="Software\Policies\Microsoft\WindowsFirewall\PrivateProfile" valueName="DoNotAllowExceptions">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
</admx:valueList>
</admx:item>
<admx:item displayName="$(string.9ba5c39c6f5c426ea41a4ad740a2cda9)">
<admx:value>
<admx:decimal value="0" />
</admx:value>
</admx:item>
</admx:enum>
</admx:elements>
</policy>
<ADMLDefinition>
<presentation id="Private_Inbound_Connections">
<admx:dropdownList refId="DefaultInboundActions" noSort="true" defaultItem="0" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Inbound connections</admx:dropdownList>
</presentation>
<string id="a539d4656a8d46beb0c02421820ef768">Windows Firewall: Private: Inbound connections</string>
<string id="e5cd19c4c45647b3928099e47f9f2c0f">This setting determines the behavior for inbound connections that do not match an inbound firewall rule. The default behavior is to block connections unless there are firewall rules to allow the connection. </string>
<string id="43bcf2ef7f9e4f21a3222e0b58894de8">Block (default)</string>
<string id="d0bc2a3f6ddc47a8b9223d512f3ac51a">Block all connections</string>
<string id="9ba5c39c6f5c426ea41a4ad740a2cda9">Allow</string>
</ADMLDefinition>
<supportedOn>At least Windows Vista</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="151" ID="{19fcb177-e639-4400-9683-9918461cdd31}" OriginalSettingID="{75208064-559a-4412-8ca6-5da2d0e10cfd}" Name="Windows Firewall: Public: Outbound connections" LockdownDate="2011-05-02T01:36:07Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9588-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting determines the behavior for outbound connections that do not match an outbound firewall rule. If Outbound connections are set to Block and deploy the firewall policy by using a GPO, cannot receive subsequent Group Policy updates.</ShortDescription>
<FullDescription>This setting determines the behavior for outbound connections that do not match an outbound firewall rule. The default behavior is to allow connections unless there are firewall rules that block the connection.
Important If you set Outbound connections to Block and then deploy the firewall policy by using a GPO, computers that receive the GPO settings cannot receive subsequent Group Policy updates unless you create and deploy an outbound rule that enables Group Policy to work. Predefined rules for Core Networking include outbound rules that enable Group Policy to work. Ensure that these outbound rules are active, and thoroughly test firewall profiles before deploying.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Public Profile</UIPath>
<DefaultValue>Allow</DefaultValue>
<Vulnerability>Some people believe that it is prudent to block all outbound connections except those specifically approved by the user or administrator. Microsoft disagrees with this opinion, blocking outbound connections by default will force users to deal with a large number of dialog boxes prompting them to authorize or block applications such as their web browser or instant messaging software. Additionally, blocking outbound traffic has little value because if an attacker has compromised the system they can reconfigure the firewall anyway.</Vulnerability>
<Countermeasure>Configure this setting to allow outbound connections.</Countermeasure>
<PotentialImpact>None, this is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Allow (default)">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Block">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Allow (default)">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\WindowsFirewall\PublicProfile</mssasc-core:KeyPath>
<mssasc-core:ValueName>DefaultOutboundAction</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="152" ID="{c3fa4e56-78ce-4ed7-96de-e4565196cebf}" OriginalSettingID="{62c711b9-cd72-4fd2-8596-bb90387278da}" Name="Windows Firewall: Domain: Outbound connections" LockdownDate="2011-05-02T01:36:07Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9509-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting determines the behavior for outbound connections that do not match an outbound firewall rule.</ShortDescription>
<FullDescription>This setting determines the behavior for outbound connections that do not match an outbound firewall rule. In Windows Vista, the default behavior is to allow connections unless there are firewall rules that block the connection.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Domain Profile</UIPath>
<DefaultValue>Allow</DefaultValue>
<Vulnerability>Some people believe that it is prudent to block all outbound connections except those specifically approved by the user or administrator. Microsoft disagrees with this opinion, blocking outbound connections by default will force users to deal with a large number of dialog boxes prompting them to authorize or block applications such as their web browser or instant messaging software. Additionally, blocking outbound traffic has little value because if an attacker has compromised the system they can reconfigure the firewall anyway.</Vulnerability>
<Countermeasure>Configure this setting to allow outbound connections.</Countermeasure>
<PotentialImpact>None, this is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Allow (default)">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Block">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Allow (default)">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\WindowsFirewall\DomainProfile</mssasc-core:KeyPath>
<mssasc-core:ValueName>DefaultOutboundAction</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Comment>
</Comment>
</SettingGroup>
<SettingGroup ID="{efb279c5-5734-464d-b3b4-c590e46545e7}" Name="Log Access Limitation" OriginalSettingGroupID="{333f7dd4-949c-4fb8-bb5c-3bcdba3b1001}">
<mssasc-core:Description>
</mssasc-core:Description>
<mssasc-core:Version Major="1" Minor="0" />
<Author>
</Author>
<Setting Index="153" ID="{c60773c7-68a6-4461-b569-1a3a71b74ce9}" OriginalSettingID="{6630b24b-754a-49a5-9750-188ae53c13b9}" Name="Manage auditing and security log" LockdownDate="2011-05-02T01:36:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9223-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which users can change the auditing options for files and directories and clear the Security log.</ShortDescription>
<FullDescription>This policy setting determines which users can change the auditing options for files and directories and clear the Security log.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators</DefaultValue>
<Vulnerability>The ability to manage the Security event log is a powerful user right and it should be closely guarded. Anyone with this user right can clear the Security log to erase important evidence of unauthorized activity.</Vulnerability>
<Countermeasure>Ensure that only the local Administrators group has the Manage auditing and security log user right.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeSecurityPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeSecurityPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:187, oval:gov.nist.1:def:235" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Comment>
</Comment>
</SettingGroup>
<SettingGroup ID="{28f89589-fb46-4a3b-ab91-dc02c7dd33bd}" Name="Remote Access" OriginalSettingGroupID="{8e84e03a-e7cc-4ab6-8f5c-0e3937ccfe8a}">
<mssasc-core:Description>
</mssasc-core:Description>
<mssasc-core:Version Major="1" Minor="0" />
<Author>
</Author>
<Setting Index="154" ID="{c0a0e44c-bb20-47ff-ab30-bdbe6a73ca2d}" OriginalSettingID="{78c974e6-940e-4fec-8697-73d0ed54943c}" Name="Allow log on through Remote Desktop Services" LockdownDate="2011-05-15T05:27:14Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9107-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which users or groups have the right to log on as a Terminal Services client.</ShortDescription>
<FullDescription>This policy setting determines which users or groups have the right to log on as a Terminal Services client. Remote desktop users require this user right. If your organization uses Remote Assistance as part of its help desk strategy, create a group and assign it this user right through Group Policy. If the help desk in your organization does not use Remote Assistance, assign this user right only to the Administrators group or use the restricted groups feature to ensure that no user accounts are part of the Remote Desktop Users group.
Restrict this user right to the Administrators group, and possibly the Remote Desktop Users group, to prevent unwanted users from gaining access to computers on your network by means of the Remote Assistance feature.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators, Remote Desktop Users</DefaultValue>
<Vulnerability>Any account with the Allow log on through Terminal Services user right can log on to the remote console of the computer. If you do not restrict this user right to legitimate users who need to log on to the console of the computer, unauthorized users could download and run malicious software to elevate their privileges.</Vulnerability>
<Countermeasure>For domain controllers, assign the Allow log on through Terminal Services user right only to the Administrators group. For other server roles and end-user computers, add the Remote Desktop Users group. For Terminal Servers that do not run in Application Server mode, ensure that only authorized IT personnel who need to manage the computers remotely belong to either of these groups.
Caution
For Terminal Servers that do run in Application Server mode, ensure that only users who require access to the server have accounts that belong to the Remote Desktop Users group, because this built-in group has this logon right by default.
Alternatively, you can assign the Deny Logon Through Terminal Services user right to groups such as Account Operators, Server Operators, and Guests. However, be careful when you use this method because you could block access to legitimate administrators who also happen to belong to a group that has the Deny Logon Through Terminal Services user right.
</Countermeasure>
<PotentialImpact>Removal of the Allow log on through Terminal Services user right from other groups or membership changes in these default groups could limit the abilities of users who perform specific administrative roles in your environment. You should confirm that delegated activities will not be adversely affected.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeRemoteInteractiveLogonRight' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeRemoteInteractiveLogonRight" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:166" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="155" ID="{e92b4d3c-832b-4381-9fcf-34d9e9124720}" OriginalSettingID="{eaa6e376-dcd2-4094-96ea-a9f404a50d51}" Name="Allow users to connect remotely using Remote Desktop Services" LockdownDate="2011-10-12T11:37:55Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9985-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to control if users can connect to a computer using Terminal Services or Remote Desktop.</ShortDescription>
<FullDescription>This policy setting allows you to control if users can connect to a computer using Terminal Services or Remote Desktop.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections</UIPath>
<DefaultValue>Not Configured</DefaultValue>
<Vulnerability>Any account with the Allow log on through Terminal Services user right can log on to the remote console of the computer. If you do not restrict access to legitimate users who need to log on to the console of the computer, unauthorized users could download and execute malicious code to elevate their privileges.</Vulnerability>
<Countermeasure>To protect against this risk configure this setting to disabled.</Countermeasure>
<PotentialImpact>If this setting is enabled legitimate users will be unable to use Terminal Services or Remote Desktop, this could make it more difficult for help desk technicians to troubleshoot and resolve problems remotely. It would also make it impossible to use Terminal Services for hosting shared applications.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine" />
<DataType>String</DataType>
</DiscoveryInfo>
<policy name="TS_DISABLE_CONNECTIONS" class="Machine" displayName="$(string.06e5c8e768674411b9605c9886a01169)" explainText="$(string.a483a2a9ae094975b32a695226d97ac6)" key="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledList xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:item key="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" valueName="fDenyTSConnections">
<admx:value>
<admx:decimal value="0" />
</admx:value>
</admx:item>
</admx:enabledList>
<admx:disabledList xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:item key="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" valueName="fDenyTSConnections">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
</admx:disabledList>
</policy>
<ADMLDefinition>
<string id="06e5c8e768674411b9605c9886a01169">Allow users to connect remotely using Remote Desktop Services</string>
<string id="a483a2a9ae094975b32a695226d97ac6">This policy setting allows you to control if users can connect to a computer using Terminal Services or Remote Desktop.</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional or Windows Server 2003 family</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:166" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="156" ID="{5393d3c1-df1c-4edb-b4a7-502fd56d3fb2}" OriginalSettingID="{72808c0e-3873-4c91-b9e6-4eba1b90e20f}" Name="Allow Remote Shell Access" LockdownDate="2011-08-17T12:23:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10077-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to manage configuration of remote access to all supported shells to execute scripts and commands.</ShortDescription>
<FullDescription>This policy setting allows you to manage configuration of remote access to all supported shells to execute scripts and commands.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Windows Remote Shell</UIPath>
<DefaultValue>Not Configured</DefaultValue>
<Vulnerability>Any feature is a potential avenue of attack, those that enable inbound network connections are particularly risky. Only enable the use of the Windows Remote Shell on trusted networks and when feasible employ additional controls such as IPsec.</Vulnerability>
<Countermeasure>Configure Allow Remote Shell Access to Disabled.</Countermeasure>
<PotentialImpact>If you enable this policy setting, remote access is allowed to all supported shells to execute scripts and commands. If you disable or do not configure this policy setting, remote access is not allowed to all supported shells to execute scripts and commands.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows\WinRM\Service\WinRS</mssasc-core:KeyPath>
<mssasc-core:ValueName>AllowRemoteShellAccess</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="AllowRemoteShellAccess" class="Machine" displayName="$(string.6267411f0895438c935b83d96cae183a)" explainText="$(string.79827f0567a34dd4b701f295b760d072)" key="Software\Policies\Microsoft\Windows\WinRM\Service\WinRS" valueName="AllowRemoteShellAccess">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="6267411f0895438c935b83d96cae183a">Allow Remote Shell Access</string>
<string id="79827f0567a34dd4b701f295b760d072">This policy setting allows you to manage configuration of remote access to all supported shells to execute scripts and commands.</string>
</ADMLDefinition>
<supportedOn>At least Windows Vista</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="157" ID="{b994a95d-8cfc-4eb9-beef-135cb64fbfce}" OriginalSettingID="{49862b02-e96e-4ebc-8cac-129f07b1298e}" Name="Deny log on through Remote Desktop Services" LockdownDate="2011-05-25T12:12:50Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9274-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether users can log on as Terminal Services clients.</ShortDescription>
<FullDescription>This policy setting determines whether users can log on as Terminal Services clients. After the baseline member server is joined to a domain environment, there is no need to use local accounts to access the server from the network. Domain accounts can access the server for administration and end-user processing.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>No One</DefaultValue>
<Vulnerability>Any account with the right to log on through Terminal Services could be used to log on to the remote console of the computer. If this user right is not restricted to legitimate users who need to log on to the console of the computer, unauthorized users might download and run malicious software that elevates their privileges.</Vulnerability>
<Countermeasure>Assign the Deny log on through Terminal Services logon right to the built-in local Administrator account and all service accounts. If you have installed optional components such as ASP.NET, you may want to assign this logon right to additional accounts that are required by those components.</Countermeasure>
<PotentialImpact>If you assign the Deny log on through Terminal Services user right to other groups, you could limit the abilities of users who are assigned to specific administrative roles in your environment. Accounts that have this user right will be unable to connect to the computer through either Terminal Services or Remote Assistance. You should confirm that delegated tasks will not be negatively impacted.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeDenyRemoteInteractiveLogonRight' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeDenyRemoteInteractiveLogonRight" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:178" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Comment>
</Comment>
</SettingGroup>
<SettingGroup ID="{881b2001-4600-4bf4-9caf-4001add1cf94}" Name="Key Management" OriginalSettingGroupID="{393d12ea-b8a6-4a4a-ad07-c1fe359e9894}">
<mssasc-core:Description>
</mssasc-core:Description>
<mssasc-core:Version Major="1" Minor="0" />
<Author>
</Author>
<Setting Index="158" ID="{aa7a0ab6-45c2-4e18-aaa3-ab523ca477ff}" OriginalSettingID="{577a19bc-6d69-45f1-9806-b413d522b05a}" Name="Domain member: Require strong (Windows 2000 or later) session key" LockdownDate="2011-08-05T07:16:32Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9387-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>When this policy setting is enabled, a secure channel can only be established with domain controllers that are capable of encrypting secure channel data with a strong (128-bit) session key.</ShortDescription>
<FullDescription>When this policy setting is enabled, a secure channel can only be established with domain controllers that are capable of encrypting secure channel data with a strong (128-bit) session key.
To enable this policy setting, all domain controllers in the domain must be able to encrypt secure channel data with a strong key, which means all domain controllers must be running Microsoft Windows 2000 or later. If communication to non-Windows 2000–based domains is required, Microsoft recommends that you disable this policy setting.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Session keys that are used to establish secure channel communications between domain controllers and member computers are much stronger in Windows 2000 than they were in previous Microsoft operating systems.
Whenever possible, you should take advantage of these stronger session keys to help protect secure channel communications from attacks that attempt to hijack network sessions and eavesdropping. (Eavesdropping is a form of hacking in which network data is read or altered in transit. The data can be modified to hide or change the sender, or be redirected.)
</Vulnerability>
<Countermeasure>Enable the Domain member: Require strong (Windows 2000 or later) session key setting.
If you enable this policy setting, all outgoing secure channel traffic will require a strong, Windows 2000 or later encryption key. If you disable this policy setting, the key strength is negotiated. You should only enable this policy setting if the domain controllers in all trusted domains support strong keys. By default, this policy setting is disabled.
</Countermeasure>
<PotentialImpact>Computers that have this policy setting enabled will not be able to join Windows NT 4.0 domains, and trusts between Active Directory domains and Windows NT-style domains may not work properly. Also, computers that do not support this policy setting will not be able to join domains in which the domain controllers have this policy setting enabled.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Netlogon\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>requirestrongkey</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\requirestrongkey" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:66" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="159" ID="{a36ea21c-cf4f-45f5-bd89-f0cb226af50d}" OriginalSettingID="{aa6c8875-0777-4685-9f37-193e9f16af51}" Name="System cryptography: Force strong key protection for user keys stored on the computer" LockdownDate="2011-08-22T07:13:47Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9381-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether users' private keys (such as their S-MIME keys) require a password to be used. </ShortDescription>
<FullDescription>This policy setting determines whether users' private keys (such as their S-MIME keys) require a password to be used. If you configure this policy setting so that users must provide a password—distinct from their domain password—every time that they use a key, then it will be more difficult for an attacker to access locally stored keys, even an attacker who discovers logon passwords.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>If a users account is compromised or their computer is inadvertently left unsecured the malicious user can use the keys stored for the user to access protected resources. You can configure this policy setting so that users must provide a password that is distinct from their domain password every time they use a key. This configuration makes it more difficult for an attacker to access locally stored user keys, even if the attacker takes control of the user’s computer and determines their logon password.</Vulnerability>
<Countermeasure>Configure the System cryptography: Force strong key protection for user keys stored on the computer setting to User must enter a password each time they use a key.</Countermeasure>
<PotentialImpact>Users will have to enter their password every time they access a key that is stored on their computer. For example, if users use an S-MIME certificate to digitally sign their e-mail they will be forced to enter the password for that certificate every time they send a signed e-mail message. For some organizations the overhead that is involved using this configuration may be too high.
For end user computers that are used to access sensitive data this setting could be set to "User is prompted when the key is first used," but Microsoft does not recommend enforcing this setting on servers due to the significant impact on manageability. For example, if this setting is configured to "User is prompted when the key is first used" you may not be able to configure Remote Desktop Services to use SSL certificates. More information is available in the Windows PKI blog: http://blogs.technet.com/b/pki/archive/2009/06/17/what-is-a-strong-key-protection-in-windows.aspx.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="User input is not required when new key are stored and used">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="User is prompted when the key is first used">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="User must enter a password each time they use a key">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Cryptography</mssasc-core:KeyPath>
<mssasc-core:ValueName>ForceKeyProtection</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Policies\Microsoft\Cryptography\ForceKeyProtection" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Comment>
</Comment>
</SettingGroup>
<SettingGroup ID="{7e49f76e-f2c3-4450-9279-bd28320903a8}" Name="Protocol Configuration" OriginalSettingGroupID="{cdde5033-32b0-47b9-833b-3fe0b37e4d0d}">
<mssasc-core:Description>
</mssasc-core:Description>
<mssasc-core:Version Major="1" Minor="0" />
<Author>
</Author>
<Setting Index="160" ID="{e3d255b0-001b-4207-8120-f52f76e2181f}" OriginalSettingID="{d252220c-49aa-4a96-9f39-b59eb2be29d4}" Name="Network Security: Restrict NTLM: Add remote server exceptions for NTLM authentication" LockdownDate="2011-05-02T01:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9036-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to create an exception list of remote servers to which clients are allowed to use NTLM authentication if the "Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers" policy setting is configured.</ShortDescription>
<FullDescription>This policy setting allows you to create an exception list of remote servers to which clients are allowed to use NTLM authentication if the "Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers" policy setting is configured.
The naming format for servers on this exception list is the fully qualified domain name (FQDN) or NetBIOS server name used by the application, listed one per line. To ensure exceptions the name used by all applications needs to be in the list, and to ensure an exception is accurate, the server name should be listed in both naming formats . A single asterisk (*) can be used anywhere in the string as a wildcard character.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>NTLM is a Microsoft-developed authentication protocol that uses a challenge-response mechanism for authentication, in which client computers can prove their identities without sending a password to the server. The protocol employs three types of messages to negotiate the request, challenge the authenticity of the sender, and perform the authentication. Kerberos is a more robust protocol and is the preferred method of authentication when available. </Vulnerability>
<Countermeasure>Add the FQDNs and NetBIOS names of remote servers to which you want this host to be able to authenticate via NTLM.</Countermeasure>
<PotentialImpact>If you configure this policy setting, you can define a list of remote servers to which clients are allowed to use NTLM authentication.
If you do not configure this policy setting, no exceptions will be applied.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_MULTI_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa\MSV1_0</mssasc-core:KeyPath>
<mssasc-core:ValueName>ClientAllowedNTLMServers</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Multi-String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHIEN\System\CurrentControlSet\Control\Lsa\MSV1_0\ClientAllowedNTLMServers" DataType="REG_MULTI_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="161" ID="{73e61ff1-beea-4870-a7b3-71e48a59b29c}" OriginalSettingID="{8998a3ee-1763-4627-9251-e473ec7e4c41}" Name="MSS: (TcpMaxDataRetransmissions) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)" LockdownDate="2011-05-22T06:25:35Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9456-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This registry value entry appears as MSS: (TcpMaxDataRetransmissions) How many times unacknowledged data is retransmitted (3 recommended, 5 is default) in the SCE.</ShortDescription>
<FullDescription>The registry value entry TCPMaxDataRetransmissions was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip
\Parameters\ registry key. The entry appears as MSS: (TcpMaxDataRetransmissions) How many times unacknowledged data is retransmitted (3 recommended, 5 is default) in the SCE.
This setting controls the number of times that TCP retransmits an individual data segment (non-connect segment) before the connection is aborted. The retransmission time-out is doubled with each successive retransmission on a connection. It is reset when responses resume. The base time-out value is dynamically determined by the measured round-trip time on the connection.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>5</DefaultValue>
<Vulnerability>A malicious user could exhaust a target computer's resources if it never sent any acknowledgment messages for data that was transmitted by the target computer.</Vulnerability>
<Countermeasure>Configure the MSS: (TcpMaxDataRetransmissions) How many times unacknowledged data is retransmitted (3 recommended, 5 is default) entry to a value of 3. The possible values for this registry entry are:
• 0 to 0xFFFFFFFF. The default configuration is 5.
In the SCE UI, this setting can be adjusted using a text entry box:
• A user-defined number
• Not Defined
</Countermeasure>
<PotentialImpact>TCP starts a retransmission timer when each outbound segment is passed to the IP. If no acknowledgment is received for the data in a given segment before the timer expires, then the segment is retransmitted up to three times.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="9999">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Tcpip\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>TcpMaxDataRetransmissions</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\TcpMaxDataRetransmissions" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:126" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="162" ID="{da93aa84-62b1-4e95-af91-a0bc5b32d22a}" OriginalSettingID="{794f9728-56e1-4e5e-b697-7079757f4ac3}" Name="Network security: Do not store LAN Manager hash value on next password change" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8937-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether the LAN Manager (LM) hash value for the new password is stored when the password is changed. </ShortDescription>
<FullDescription>This policy setting determines whether the LAN Manager (LM) hash value for the new password is stored when the password is changed. The LM hash is relatively weak and prone to attack compared to the cryptographically stronger Microsoft Windows NT® hash.
Note Older operating systems and some third-party applications may fail when this policy setting is enabled. Also you will need to change the password on all accounts after you enable this setting.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>The SAM file can be targeted by attackers who seek access to username and password hashes. Such attacks use special tools to crack passwords, which can then be used to impersonate users and gain access to resources on your network. These types of attacks will not be prevented if you enable this policy setting, but it will be much more difficult for these types of attacks to succeed.</Vulnerability>
<Countermeasure>Configure the Network security: Do not store LAN Manager hash value on next password change setting to Enabled. Require all users to set new passwords the next time they log in to the domain so that LAN Manager hashes are removed.</Countermeasure>
<PotentialImpact>Earlier operating systems such as Windows 95, Windows 98, and Windows ME as well as some third-party applications will fail.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>NoLMHash</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\NoLMHash" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:95" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="163" ID="{2f56ef7d-0613-47f4-ab88-060b0a534a52}" OriginalSettingID="{8d872ca4-b77a-485e-bfad-cd8a311210a9}" Name="Network Security: Allow PKU2U authentication requests to this computer to use online identities" LockdownDate="2011-05-02T01:36:03Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9770-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy will be turned off by default on domain joined machines. This would disallow the online identities to be able to authenticate to the domain joined machine in Windows 7.</ShortDescription>
<FullDescription>Windows 7 and Windows Server 2008 R2 introduce an extension to the Negotiate authentication package, Spnego.dll. In previous versions of Windows, Negotiate decides whether to use Kerberos or NTLM for authentication. The extension SSP for Negotiate, Negoexts, which is treated as an authentication protocol by Windows, supports Microsoft SSPs including PKU2U. You can also develop or add other SSPs.
When computers are configured to accept authentication requests by using online IDs, Negoexts.dll calls the PKU2U SSP on the computer that is used to log on. The PKU2U SSP obtains a local certificate and exchanges the policy between the peer computers. When validated on the peer computer, the certificate within the metadata is sent to the logon peer for validation and associates the user's certificate to a security token and the logon process completes.
This policy will be turned off by default on domain joined machines. This would disallow the online identities to be able to authenticate to the domain joined machine in Windows 7.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>The PKU2U protocol is a peer-to-peer authentication protocol, in most managed networks authentication should be managed centrally.</Vulnerability>
<Countermeasure>Configure Network Security: Allow PKU2U authentication requests to this computer to use online identities to disabled.</Countermeasure>
<PotentialImpact>Disabling this setting will disallow the online identities to be able to authenticate to the domain joined machine in Windows 7.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa\pku2u</mssasc-core:KeyPath>
<mssasc-core:ValueName>AllowOnlineID</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\pku2u\AllowOnlineID" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="164" ID="{f5e35cb8-8c62-41c8-9953-ee1052ccb877}" OriginalSettingID="{ec468e43-6141-4bfe-970f-ca02d37d0ca7}" Name="Network security: LAN Manager authentication level" LockdownDate="2011-10-12T11:37:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8806-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting specifies the type of challenge/response authentication for network logons. LAN Manager (LM) authentication is the least secure method; it allows encrypted passwords to be cracked because they can be easily intercepted on the network. </ShortDescription>
<FullDescription>LAN Manager (LM) is a family of early Microsoft client/server software that allows users to link personal computers together on a single network. Network capabilities include transparent file and print sharing, user security features, and network administration tools. In Active Directory domains, the Kerberos protocol is the default authentication protocol. However, if the Kerberos protocol is not negotiated for some reason, Active Directory will use LM, NTLM, or NTLMv2.
LAN Manager authentication includes the LM, NTLM, and NTLM version 2 (NTLMv2) variants, and is the protocol that is used to authenticate all Windows clients when they perform the following operations:
• Join a domain
• Authenticate between Active Directory forests
• Authenticate to down-level domains
• Authenticate to computers that do not run Windows 2000, Windows Server 2003, or Windows XP)
• Authenticate to computers that are not in the domain
The possible values for the Network security: LAN Manager authentication level setting are:
• Send LM & NTLM responses
• Send LM & NTLM — use NTLMv2 session security if negotiated
• Send NTLM responses only
• Send NTLMv2 responses only
• Send NTLMv2 responses only\refuse LM
• Send NTLMv2 responses only\refuse LM & NTLM
• Not Defined
The Network security: LAN Manager authentication level setting determines which challenge/response authentication protocol is used for network logons. This choice affects the authentication protocol level that clients use, the session security level that the computers negotiate, and the authentication level that servers accept as follows:
• Send LM & NTLM responses. Clients use LM and NTLM authentication and never use NTLMv2 session security. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
• Send LM & NTLM – use NTLMv2 session security if negotiated. Clients use LM and NTLM authentication and use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
• Send NTLM response only. Clients use NTLM authentication only and use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
• Send NTLMv2 response only. Clients use NTLMv2 authentication only and use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
• Send NTLMv2 response only\refuse LM. Clients use NTLMv2 authentication only and use NTLMv2 session security if the server supports it. Domain controllers refuse LM (accept only NTLM and NTLMv2 authentication).
• Send NTLMv2 response only\refuse LM & NTLM. Clients use NTLMv2 authentication only and use NTLMv2 session security if the server supports it. Domain controllers refuse LM and NTLM (accept only NTLMv2 authentication).
These settings correspond to the levels discussed in other Microsoft documents as follows:
• Level 0 – Send LM and NTLM response; never use NTLMv2 session security. Clients use LM and NTLM authentication, and never use NTLMv2 session security. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
• Level 1 – Use NTLMv2 session security if negotiated. Clients use LM and NTLM authentication, and use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
• Level 2 – Send NTLM response only. Clients use only NTLM authentication, and use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
• Level 3 – Send NTLMv2 response only. Clients use NTLMv2 authentication, and use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
• Level 4 – Domain controllers refuse LM responses. Clients use NTLM authentication, and use NTLMv2 session security if the server supports it. Domain controllers refuse LM authentication, that is, they accept NTLM and NTLMv2.
• Level 5 – Domain controllers refuse LM and NTLM responses (accept only NTLMv2). Clients use NTLMv2 authentication, use and NTLMv2 session security if the server supports it. Domain controllers refuse NTLM and LM authentication (they accept only NTLMv2).</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Send NTLMv2 response only</DefaultValue>
<Vulnerability>In Windows Vista, this setting is undefined. However, in Windows 2000, Windows Server 2003, and Windows XP clients are configured by default to send LM and NTLM authentication responses (Windows 95-based and Windows 98-based clients only send LM). The default setting on servers allows all clients to authenticate with servers and use their resources. However, this means that LM responses—the weakest form of authentication response—are sent over the network, and it is potentially possible for attackers to sniff that traffic to more easily reproduce the user’s password.
The Windows 95, Windows 98, and Windows NT operating systems cannot use the Kerberos version 5 protocol for authentication. For this reason, in a Windows Server 2003 domain, these computers authenticate by default with both the LM and NTLM protocols for network authentication. You can enforce a more secure authentication protocol for Windows 95, Windows 98, and Windows NT by using NTLMv2. For the logon process, NTLMv2 uses a secure channel to protect the authentication process. Even if you use NTLMv2 for earlier clients and servers, Windows-based clients and servers that are members of the domain will use the Kerberos authentication protocol to authenticate with Windows Server 2003 domain controllers.</Vulnerability>
<Countermeasure>Configure the Network security: LAN Manager Authentication Level setting to Send NTLMv2 responses only. We and a number of independent organizations strongly recommend this level of authentication when all clients support NTLMv2.
For more information about how to enable NTLMv2 on older versions of Windows, see article 239869, How to enable NTLM 2 authentication, in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=100904). Microsoft Windows NT 4.0 requires Service Pack 4 (SP4) to support NTLMv2, and Windows 95 and Windows 98 platforms need the directory service client installed to support NTLMv2.
</Countermeasure>
<PotentialImpact>Clients that do not support NTLMv2 authentication will not be able to authenticate in the domain and access domain resources by using LM and NTLM.
Note: For information about a hotfix to ensure that this setting works in networks that include Windows NT 4.0-based computers along with Windows 2000, Windows XP, and Windows Server 2003-based computers, see article 305379, Authentication Problems in Windows 2000 with NTLM 2 Levels Above 2 in a Windows NT 4.0 Domain, in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=100907).
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Send NTLMv2 response only. Refuse LM & NTLM">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Send LM & NTLM responses">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Send LM & NTLM - use NTLMv2 session security if negotiated">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Send NTLM response only">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
<Mapping FriendlyName="Send NTLMv2 response only">
<BehaviorDescription />
<DCMValue ValueA="3" />
<SCAPValue ValueA="3" />
<GPOValue ValueA="3" />
</Mapping>
<Mapping FriendlyName="Send NTLMv2 response only. Refuse LM">
<BehaviorDescription />
<DCMValue ValueA="4" />
<SCAPValue ValueA="4" />
<GPOValue ValueA="4" />
</Mapping>
<Mapping FriendlyName="Send NTLMv2 response only. Refuse LM & NTLM">
<BehaviorDescription />
<DCMValue ValueA="5" />
<SCAPValue ValueA="5" />
<GPOValue ValueA="5" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>LmCompatibilityLevel</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\LmCompatibilityLevel" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:97, oval:gov.nist.1:def:96" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="165" ID="{b2131895-e20b-4442-9c5e-c7b70e1b2794}" OriginalSettingID="{21d226de-3201-414e-a16a-b626b6d0cc26}" Name="MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)" LockdownDate="2011-05-22T06:25:35Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8655-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The entry appears as MSS: (DisableIPSourceRouting) IPv6 source routing protection level (protects against packet spoofing) in the SCE.</ShortDescription>
<FullDescription>This entry appears as MSS: (DisableIPSourceRouting) IPv6 source routing protection level (protects against packet spoofing) in the SCE. IP source routing is a mechanism that allows the sender to determine the IP route that a datagram should follow through the network.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not Defined</DefaultValue>
<Vulnerability>An attacker could use source routed packets to obscure their identity and location. Source routing allows a computer that sends a packet to specify the route that the packet takes.</Vulnerability>
<Countermeasure>Configure the MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing) entry to a value of Highest protection, source routing is completely disabled.
The possible values for this registry entry are:
• 0, 1, or 2. The default configuration is 1 (source routed packets are not forwarded).
In the SCE UI, the following list of options appears:
• No additional protection, source routed packets are allowed.
• Medium, source routed packets ignored when IP forwarding is enabled.
• Highest protection, source routing is completely disabled.
• Not Defined.
</Countermeasure>
<PotentialImpact>If you configure this value to 2, all incoming source routed packets will be dropped.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Highest protection, source routing is completely disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No additional protection, source routed packets are allowed">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Medium, source routed packets ignored when IP forwarding is enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Highest protection, source routing is completely disabled">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Tcpip6\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableIPSourceRouting</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Tcpip6\Parameters\DisableIPSourceRouting" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:111" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="166" ID="{7867b62c-7e11-4f8b-a452-fb2d0d4dd1b8}" OriginalSettingID="{4558d6d1-85c5-4c90-b09c-d263d9833e5e}" Name="MSS: (TcpMaxDataRetransmissions IPv6) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)" LockdownDate="2011-05-22T06:25:35Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9487-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This registry value entry appears as MSS: (TcpMaxDataRetransmissions) IPv6 How many times unacknowledged data is retransmitted (3 recommended, 5 is default) in the SCE.</ShortDescription>
<FullDescription>The registry value entry TCPMaxDataRetransmissions for IPv6 was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip6
\Parameters\ registry key. The entry appears as MSS: (TcpMaxDataRetransmissions) IPv6 How many times unacknowledged data is retransmitted (3 recommended, 5 is default) in the SCE.
This setting controls the number of times that TCP retransmits an individual data segment (non-connect segment) before the connection is aborted. The retransmission time-out is doubled with each successive retransmission on a connection. It is reset when responses resume. The base time-out value is dynamically determined by the measured round-trip time on the connection.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>5</DefaultValue>
<Vulnerability>A malicious user could exhaust a target computer's resources if it never sent any acknowledgment messages for data that was transmitted by the target computer.</Vulnerability>
<Countermeasure>Configure the MSS: (TcpMaxDataRetransmissions) IPv6 How many times unacknowledged data is retransmitted (3 recommended, 5 is default) entry to a value of 3. The possible values for this registry entry are:
• 0 to 0xFFFFFFFF. The default configuration is 5.
In the SCE UI, this setting can be adjusted using a text entry box:
• A user-defined number
• Not Defined
</Countermeasure>
<PotentialImpact>TCP starts a retransmission timer when each outbound segment is passed to the IP. If no acknowledgment is received for the data in a given segment before the timer expires, then the segment is retransmitted up to three times.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="9999">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Tcpip6\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>TcpMaxDataRetransmissions</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Tcpip6\Parameters\TcpMaxDataRetransmissions" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="167" ID="{309aee2a-d7e8-4813-8ed6-89bf1fc7c8fb}" OriginalSettingID="{7f8c238a-8a21-44e0-8704-0dabc0e02ae5}" Name="MSS: (PerformRouterDiscovery) Allow IRDP to detect and configure Default Gateway addresses (could lead to DoS)" LockdownDate="2011-05-22T06:25:35Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9458-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This registry value entry appears as MSS: (PerformRouterDiscovery) Allow IRDP to detect and configure Default Gateway addresses (could lead to DoS) in the SCE.</ShortDescription>
<FullDescription>The registry value entry PerformRouterDiscovery was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\ registry key. The entry appears as MSS: (PerformRouterDiscovery) Allow IRDP to detect and configure Default Gateway addresses (could lead to DoS) in the SCE.
This setting is used to enable or disable the Internet Router Discovery Protocol (IRDP), which allows the system to detect and configure default gateway addresses automatically as described in RFC 1256 on a per-interface basis.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enable only if DHCP sends the Perform Router Discovery option</DefaultValue>
<Vulnerability>An attacker who has gained control of a computer on the same network segment could configure a computer on the network to impersonate a router. Other computers with IRDP enabled would then attempt to route their traffic through the already compromised computer.</Vulnerability>
<Countermeasure>Configure the MSS: (PerformRouterDiscovery) Allow IRDP to detect and configure Default Gateway addresses (could lead to DoS) entry to a value of Disabled.
The possible values for this registry entry are:
• 0, 1, or 2. The default configuration is 2 (enable only if DHCP sends the Perform Router Discovery option).
In the SCE UI, these options appear as:
• 0 (Disabled)
• 1 (Enabled)
• 2 (enable only if DHCP sends the Perform Router Discovery option)
• Not Defined
</Countermeasure>
<PotentialImpact>If you disable this entry, Windows Server 2003 (which supports the IRDP) cannot automatically detect and configure default gateway addresses on the computer.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Tcpip\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>PerformRouterDiscovery</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\PerformRouterDiscovery" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:121" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="168" ID="{712d0c6e-7783-4341-a63b-4f3d011237ef}" OriginalSettingID="{b1b4a762-3114-438b-92cf-90f021714790}" Name="Microsoft network client: Send unencrypted password to third-party SMB servers" LockdownDate="2011-05-02T01:36:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9265-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Disable this policy setting to prevent the SMB redirector from sending plaintext passwords during authentication to third-party SMB servers that do not support password encryption. </ShortDescription>
<FullDescription>Disable this policy setting to prevent the SMB redirector from sending plaintext passwords during authentication to third-party SMB servers that do not support password encryption. Microsoft recommends that you disable this policy setting unless there is a strong business case to enable it. If this policy setting is enabled, unencrypted passwords will be allowed across the network.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>If you enable this policy setting, the server can transmit passwords in plaintext across the network to other computers that offer SMB services. These other computers may not use any of the SMB security mechanisms that are included with Windows Server 2003. </Vulnerability>
<Countermeasure>Configure the Microsoft network client: Send unencrypted password to connect to third-party SMB servers setting to Disabled. </Countermeasure>
<PotentialImpact>Some very old applications and operating systems such as MS-DOS, Windows for Workgroups 3.11, and Windows 95a may not be able to communicate with the servers in your organization by means of the SMB protocol.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanmanWorkstation\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnablePlainTextPassword</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters\EnablePlainTextPassword" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:82" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="169" ID="{6ddfe646-fbff-4401-b44e-1ff7565457b9}" OriginalSettingID="{838a6c32-08ab-4aa1-9c18-540fb154de6a}" Name="MSS: (NoDefaultExempt) Configure IPSec exemptions for various types of network traffic." LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9439-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The entry appears as MSS: (NoDefaultExempt) Configure IPSec exemptions for various types of network traffic in the SCE.</ShortDescription>
<FullDescription>The registry value entry NoDefaultExempt was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\IPSEC\ registry key. The entry appears as MSS: (NoDefaultExempt) Configure IPSec exemptions for various types of network traffic in the SCE.
The default exemptions to IPsec policy filters are documented in the online help for the specific operating system. These filters make it possible for Internet Key Exchange (IKE) and the Kerberos authentication protocol to function. The filters also make it possible for the network Quality of Service (QoS) to be signaled (RSVP) when the data traffic is secured by IPsec, and for traffic that IPsec might not secure such as multicast and broadcast traffic.
IPsec is increasingly used for basic host-firewall packet filtering, particularly in Internet-exposed scenarios, and the affect of these default exemptions has not been fully understood. Therefore, some IPsec administrators may create IPsec policies that they think are secure, but are not actually secure against inbound attacks that use the default exemptions.
For additional information, see the Knowledge Base article 811832, "IPSec Default Exemptions Can Be Used to Bypass IPsec Protection in Some Scenarios."
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not Defined</DefaultValue>
<Vulnerability>As IPsec is increasingly used for basic host-firewall packet filtering, particularly in Internet-exposed scenarios, the affect of these default exemptions has not been fully understood. Some IPsec administrators may create IPsec policies that they think are secure, but are not actually secure against inbound attacks that use the default exemptions. Attackers could forge network traffic that appears to consist of legitimate IKE, RSVP, or Kerberos protocol packets but direct them to other network services on the host.</Vulnerability>
<Countermeasure>Do not configure the MSS: (NoDefaultExempt) Enable NoDefaultExempt for IPSec Filtering (recommended) entry except on computers that use IPsec filters, where this entry should be configured to a value of Enabled.
The possible values for this registry entry are:
• A value of 0 specifies that multicast, broadcast, RSVP, Kerberos, and IKE (ISAKMP) traffic are exempt from IPsec filters, which is the default configuration for Windows 2000 and Windows XP. Use this setting only if you require compatibility with an IPsec policy that already exists or Windows 2000 and Windows XP.
• A value of 1 specifies that Kerberos protocol and RSVP traffic are not exempt from IPsec filters, but multicast, broadcast, and IKE traffic are exempt. This setting is the recommended value for Windows 2000 and Windows XP.
• A value of 2 specifies that multicast and broadcast traffic are not exempt from IPsec filters, but RSVP, Kerberos, and IKE traffic are exempt. This setting is supported only in Windows Server 2003.
• A value of 3 specifies that only IKE traffic is exempt from IPsec filters. This setting is supported only in Windows Server 2003, which contains this default behavior although the registry key does not exist by default.
In the SCE UI, these options appear as:
• 0
• 1
• 2
• 3
</Countermeasure>
<PotentialImpact>After you enable this entry, security policies that already exist may have to be changed to work correctly. For details, refer to the Microsoft Knowledge Base article "IPSec Default Exemptions Can Be Used to Bypass IPsec Protection in Some Scenarios" at http://support.microsoft.com/default.aspx?kbid=811832,which was referenced earlier in this section.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Allow all exceptions (lease secure)">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Multicast, broadcast, and ISAKMP are exempt (Best for Windows XP)">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="RSVP, Kerberos, and ISAKMP are exempt">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
<Mapping FriendlyName="Only ISAKMP is exempt (recommended for Windows Server 2003)">
<BehaviorDescription />
<DCMValue ValueA="3" />
<SCAPValue ValueA="3" />
<GPOValue ValueA="3" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\IPSEC</mssasc-core:KeyPath>
<mssasc-core:ValueName>NoDefaultExempt</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\IPSEC\NoDefaultExempt" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="170" ID="{c4f93ad9-c4cc-46a9-82c7-2fc9e9f94340}" OriginalSettingID="{0c907d9a-4c08-4440-abf8-8b7bbe24bfd3}" Name="Network Security: Restrict NTLM: Audit NTLM authentication in this domain" LockdownDate="2011-05-02T01:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9604-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to audit NTLM authentication in a domain from this domain controller.</ShortDescription>
<FullDescription>This policy setting allows you to audit NTLM authentication in a domain from this domain controller.
This policy is supported on at least Windows Server 2008 R2.
Note: Audit events are recorded on this computer in the "Operational" Log located under the Applications and Services Log/Microsoft/Windows/NTLM.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>NTLM is a Microsoft-developed authentication protocol that uses a challenge-response mechanism for authentication, in which client computers can prove their identities without sending a password to the server. The protocol employs three types of messages to negotiate the request, challenge the authenticity of the sender, and perform the authentication. Kerberos is a more robust protocol and is the preferred method of authentication when available. </Vulnerability>
<Countermeasure>Configure Network Security: Restrict NTLM: Audit NTLM authentication in this domain to </Countermeasure>
<PotentialImpact>
If you select "Disable" or do not configure this policy setting, the domain controller will not log events for NTLM authentication in this domain.
If you select "Enable for domain accounts to domain servers," the domain controller will log events for NTLM authentication logon attempts for domain accounts to domain servers when NTLM authentication would be denied because "Deny for domain accounts to domain servers" is selected in the "Network security: Restrict NTLM: NTLM authentication in this domain" policy setting.
If you select "Enable for domain accounts," the domain controller will log events for NTLM authentication logon attempts that use domain accounts when NTLM authentication would be denied because "Deny for domain accounts" is selected in the "Network security: Restrict NTLM: NTLM authentication in this domain" policy setting.
If you select "Enable for domain servers" the domain controller will log events for NTLM authentication requests to all servers in the domain when NTLM authentication would be denied because "Deny for domain servers" is selected in the "Network security: Restrict NTLM: NTLM authentication in this domain" policy setting.
If you select "Enable all" the domain controller will log events for NTLM pass-through authentication requests from its servers and for its accounts which would be denied because "Deny all" is selected in the "Network security: Restrict NTLM: NTLM authentication in this domain" policy setting.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disable">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enable for domain accounts to domain servers">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Enable for domain accounts">
<BehaviorDescription />
<DCMValue ValueA="3" />
<SCAPValue ValueA="3" />
<GPOValue ValueA="3" />
</Mapping>
<Mapping FriendlyName="Enable for domain servers">
<BehaviorDescription />
<DCMValue ValueA="5" />
<SCAPValue ValueA="5" />
<GPOValue ValueA="5" />
</Mapping>
<Mapping FriendlyName="Enable all">
<BehaviorDescription />
<DCMValue ValueA="7" />
<SCAPValue ValueA="7" />
<GPOValue ValueA="7" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Netlogon\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>AuditNTLMInDomain</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\AuditNTLMInDomain" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="171" ID="{b63916c3-146d-4ad3-aa3a-35404b0a5ace}" OriginalSettingID="{c4f13e60-0fae-4766-bba1-00b4c33d54b7}" Name="Network access: Do not allow anonymous enumeration of SAM accounts" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9249-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting controls the ability of anonymous users to enumerate the accounts in the Security Accounts Manager (SAM).</ShortDescription>
<FullDescription>This policy setting controls the ability of anonymous users to enumerate the accounts in the Security Accounts Manager (SAM). If you enable this policy setting, users with anonymous connections cannot enumerate domain account user names on the workstations in your environment. This policy setting also allows additional restrictions on anonymous connections.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>An unauthorized user could anonymously list account names and use the information to perform social engineering attacks or attempt to guess passwords. (Social engineering attacks try to deceive users in some way to obtain passwords or some form of security information.)</Vulnerability>
<Countermeasure>Configure the Network access: Do not allow anonymous enumeration of SAM accounts setting to Enabled.</Countermeasure>
<PotentialImpact>It will be impossible to establish trusts with Windows NT 4.0–based domains. Also, client computers that run older versions of the Windows operating system such as Windows NT 3.51 and Windows 95 will experience problems when they try to use resources on the server.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>RestrictAnonymousSAM</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\RestrictAnonymousSAM" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:88" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="172" ID="{47f57ddd-49c2-49ee-af8b-c20ea20ca1f7}" OriginalSettingID="{ed734c3b-b27f-4515-9154-9f6f414e6564}" Name="Microsoft network client: Digitally sign communications (always)" LockdownDate="2011-05-02T01:36:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9327-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether packet signing is required by the SMB client component. </ShortDescription>
<FullDescription>This policy setting determines whether packet signing is required by the SMB client component. If you enable this policy setting, the Microsoft network client computer cannot communicate with a Microsoft network server unless that server agrees to sign SMB packets. In mixed environments with legacy client computers, set this option to Disabled because these computers will not be able to authenticate or gain access to domain controllers. However, you can use this policy setting in Windows 2000 or later environments.
Note When Windows Vista–based computers have this policy setting enabled and they connect to file or print shares on remote servers, it is important that the setting is synchronized with its companion setting, Microsoft network server: Digitally sign communications (always), on those servers. For more information about these settings, see the "Microsoft network client and server: Digitally sign communications (four related settings)" section in Chapter 5 of the Threats and Countermeasures guide.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Session hijacking uses tools that allow attackers who have access to the same network as the client or server to interrupt, end, or steal a session in progress. Attackers can potentially intercept and modify unsigned SMB packets and then modify the traffic and forward it so that the server might perform undesirable actions. Alternatively, the attacker could pose as the server or client after legitimate authentication and gain unauthorized access to data.
SMB is the resource sharing protocol that is supported by many Windows operating systems. It is the basis of NetBIOS and many other protocols. SMB signatures authenticate both users and the servers that host the data. If either side fails the authentication process, data transmission will not take place.
</Vulnerability>
<Countermeasure>Configure the settings as follows:
• Disable Microsoft Network Client: Digitally Sign Communications (Always).
• Disable Microsoft Network Server: Digitally Sign Communications (Always).
• Microsoft Network Client: Digitally Sign \Communications (If Server Agrees) to Enabled.
• Microsoft Network Server: Digitally Sign Communications (If Client Agrees) to Enabled.
In highly secure environments we recommend that you configure all of these settings to Enabled. However, that configuration may cause slower performance on client computers and prevent communications with earlier SMB applications and operating systems.
Note
An alternative countermeasure that could protect all network traffic would be to implement digital signatures with Internet Protocol security (IPsec). There are hardware-based accelerators for IPsec encryption and signing that could be used to minimize the performance impact on the servers’ CPUs. No such accelerators are available for SMB signing.
</Countermeasure>
<PotentialImpact>The Windows 2000 Server, Windows 2000 Professional, Windows Server 2003, Windows XP Professional and Windows Vista implementations of the SMB file and print sharing protocol support mutual authentication, which prevents session hijacking attacks and supports message authentication to prevent man-in-the-middle attacks. SMB signing provides this authentication by placing a digital signature into each SMB, which is then verified by both the client and the server.
Implementation of SMB signing may negatively affect performance, because each packet needs to be signed and verified. If these settings are enabled on a server that is performing multiple roles, such as a small business server that is serving as a domain controller, file server, print server, and application server performance may be substantially slowed. Additionally, if you configure computers to ignore all unsigned SMB communications, older applications and operating systems will not be able to connect. However, if you completely disable all SMB signing, computers will be vulnerable to session hijacking attacks.
When SMB signing policies are enabled on domain controllers running Windows Server 2003 and member computers running Windows Vista SP1 or Windows Server 2008 group policy processing will fail. A hotfix is available from Microsoft that resolves this issue; see Microsoft Knowledgebase Article 950876 for more details: http://support.microsoft.com/default.aspx/kb/950876/.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanmanWorkstation\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>RequireSecuritySignature</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters\RequireSecuritySignature" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:79" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="173" ID="{f18bcc17-1664-4b85-9538-39ae9c8c0e62}" OriginalSettingID="{b106bcb1-2b74-4287-8587-6cd92d337be8}" Name="Domain member: Digitally encrypt secure channel data (when possible)" LockdownDate="2011-05-02T01:36:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9251-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether a domain member should attempt to negotiate encryption for all secure channel traffic that it initiates.</ShortDescription>
<FullDescription>This policy setting determines whether a domain member should attempt to negotiate encryption for all secure channel traffic that it initiates. If you enable this policy setting, the domain member will request encryption of all secure channel traffic. If you disable this policy setting, the domain member will be prevented from negotiating secure channel encryption.
Microsoft recommends to configure the Domain member: Digitally encrypt secure channel data (when possible) setting to Enabled.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>When a Windows Server 2003, Windows XP, Windows 2000, or Windows NT computer joins a domain, a computer account is created. After it joins the domain, the computer uses the password for that account to create a secure channel with the domain controller for its domain every time that it restarts. Requests that are sent on the secure channel are authenticated—and sensitive information such as passwords are encrypted—but the channel is not integrity-checked, and not all information is encrypted. If a computer is configured to always encrypt or sign secure channel data but the domain controller cannot sign or encrypt any portion of the secure channel data, the computer and domain controller cannot establish a secure channel. If the computer is configured to encrypt or sign secure channel data when possible, a secure channel can be established, but the level of encryption and signing is negotiated.</Vulnerability>
<Countermeasure>• Enable the Domain member: Digitally encrypt or sign secure channel data (always) setting.
• Enable the Domain member: Digitally encrypt secure channel data (when possible) setting.
• Enable the Domain member: Digitally sign secure channel data (when possible) setting.
</Countermeasure>
<PotentialImpact>Digital encryption and signing of the “secure channel” is a good idea where it is supported. The secure channel protects domain credentials as they are sent to the domain controller. However, only Windows NT 4.0 Service Pack 6a (SP6a) and subsequent versions of the Windows operating system support digital encryption and signing of the secure channel. Windows 98 Second Edition clients do not support it unless they have the Dsclient installed. Therefore, you cannot enable the Domain member: Digitally encrypt or sign secure channel data (always) setting on domain controllers that support Windows 98 clients as members of the domain. Potential impacts can include the following:</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Netlogon\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>sealsecurechannel</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\sealsecurechannel" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="174" ID="{8b3b77ec-ee5d-420d-bd6d-7393154e5edb}" OriginalSettingID="{04b278da-3245-43ec-9d5a-a5a68805027b}" Name="Domain member: Digitally encrypt or sign secure channel data (always)" LockdownDate="2011-05-02T01:36:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8974-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether all secure channel traffic that is initiated by the domain member must be signed or encrypted.</ShortDescription>
<FullDescription>This policy setting determines whether all secure channel traffic that is initiated by the domain member must be signed or encrypted. If a system is set to always encrypt or sign secure channel data, it cannot establish a secure channel with a domain controller that is not capable of signing or encrypting all secure channel traffic, because all secure channel data must be signed and encrypted.
Microsoft recommends to configure the Domain member: Digitally encrypt or sign secure channel data (always) setting to Enabled.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>When a computer joins a domain, a computer account is created. After it joins the domain, the computer uses the password for that account to create a secure channel with the domain controller for its domain every time that it restarts. Requests that are sent on the secure channel are authenticated—and sensitive information such as passwords are encrypted—but the channel is not integrity-checked, and not all information is encrypted. If a computer is configured to always encrypt or sign secure channel data but the domain controller cannot sign or encrypt any portion of the secure channel data, the computer and domain controller cannot establish a secure channel. If the computer is configured to encrypt or sign secure channel data when possible, a secure channel can be established, but the level of encryption and signing is negotiated.</Vulnerability>
<Countermeasure>• Enable the Domain member: Digitally encrypt or sign secure channel data (always) setting.
• Enable the Domain member: Digitally encrypt secure channel data (when possible) setting.
• Enable the Domain member: Digitally sign secure channel data (when possible) setting.
</Countermeasure>
<PotentialImpact>Digital encryption and signing of the “secure channel” is a good idea where it is supported. The secure channel protects domain credentials as they are sent to the domain controller. However, only Windows NT 4.0 with Service Pack 6a (SP6a) and subsequent versions of the Windows operating system support digital encryption and signing of the secure channel. Windows 98 Second Edition clients do not support it unless they have the Dsclient installed. Therefore, you cannot enable the Domain member: Digitally encrypt or sign secure channel data (always) setting on domain controllers that support Windows 98 clients as members of the domain. Potential impacts can include the following:
• The ability to create or delete trust relationships with clients running versions of Windows earlier than Windows NT 4.0 with SP6a will be disabled.
• Logons from clients running versions of Windows earlier than Windows NT 4.0 with SP6a will be disabled.
• The ability to authenticate other domains’ users from a domain controller running a version of Windows earlier than Windows NT 4.0 with SP6a in a trusted domain will be disabled.
You can enable this policy setting after you eliminate all Windows 9x clients from the domain and upgrade all Windows NT 4.0 servers and domain controllers from trusted/trusting domains to Windows NT 4.0 with SP6a. You can enable the other two policy settings, Domain member: Digitally encrypt secure channel data (when possible) and Domain member: Digitally encrypt sign channel data (when possible), on all computers in the domain that support them and clients running versions of Windows earlier than Windows NT 4.0 with SP6a and applications that run on these versions of Windows will not be affected.
Digital encryption and signing of the “secure channel” is a good idea where it is supported. The secure channel protects domain credentials as they are sent to the domain controller. However, only Windows NT 4.0 with Service Pack 6a (SP6a) and subsequent versions of the Windows operating system support digital encryption and signing of the secure channel. Windows 98 Second Edition clients do not support it unless they have the Dsclient installed. Therefore, you cannot enable the Domain member: Digitally encrypt or sign secure channel data (always) setting on domain controllers that support Windows 98 clients as members of the domain. Potential impacts can include the following:
• The ability to create or delete trust relationships with clients running versions of Windows earlier than Windows NT 4.0 with SP6a will be disabled.
• Logons from clients running versions of Windows earlier than Windows NT 4.0 with SP6a will be disabled.
• The ability to authenticate other domains’ users from a domain controller running a version of Windows earlier than Windows NT 4.0 with SP6a in a trusted domain will be disabled.
You can enable this policy setting after you eliminate all Windows 9x clients from the domain and upgrade all Windows NT 4.0 servers and domain controllers from trusted/trusting domains to Windows NT 4.0 with SP6a. You can enable the other two policy settings, Domain member: Digitally encrypt secure channel data (when possible) and Domain member: Digitally encrypt sign channel data (when possible), on all computers in the domain that support them and clients running versions of Windows earlier than Windows NT 4.0 with SP6a and applications that run on these versions of Windows will not be affected.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Netlogon\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>requiresignorseal</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\requiresignorseal" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="175" ID="{13cd9999-b480-411f-ac83-e8da24d907e9}" OriginalSettingID="{577a19bc-6d69-45f1-9806-b413d522b05a}" Name="Domain member: Require strong (Windows 2000 or later) session key" LockdownDate="2011-08-05T07:16:32Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9387-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>When this policy setting is enabled, a secure channel can only be established with domain controllers that are capable of encrypting secure channel data with a strong (128-bit) session key.</ShortDescription>
<FullDescription>When this policy setting is enabled, a secure channel can only be established with domain controllers that are capable of encrypting secure channel data with a strong (128-bit) session key.
To enable this policy setting, all domain controllers in the domain must be able to encrypt secure channel data with a strong key, which means all domain controllers must be running Microsoft Windows 2000 or later. If communication to non-Windows 2000–based domains is required, Microsoft recommends that you disable this policy setting.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Session keys that are used to establish secure channel communications between domain controllers and member computers are much stronger in Windows 2000 than they were in previous Microsoft operating systems.
Whenever possible, you should take advantage of these stronger session keys to help protect secure channel communications from attacks that attempt to hijack network sessions and eavesdropping. (Eavesdropping is a form of hacking in which network data is read or altered in transit. The data can be modified to hide or change the sender, or be redirected.)
</Vulnerability>
<Countermeasure>Enable the Domain member: Require strong (Windows 2000 or later) session key setting.
If you enable this policy setting, all outgoing secure channel traffic will require a strong, Windows 2000 or later encryption key. If you disable this policy setting, the key strength is negotiated. You should only enable this policy setting if the domain controllers in all trusted domains support strong keys. By default, this policy setting is disabled.
</Countermeasure>
<PotentialImpact>Computers that have this policy setting enabled will not be able to join Windows NT 4.0 domains, and trusts between Active Directory domains and Windows NT-style domains may not work properly. Also, computers that do not support this policy setting will not be able to join domains in which the domain controllers have this policy setting enabled.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Netlogon\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>requirestrongkey</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\requirestrongkey" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:66" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="176" ID="{422c9a4a-e8cb-49ce-ba4c-673187357703}" OriginalSettingID="{9969a7db-5fd1-4713-9a26-9862c15359e9}" Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) clients" LockdownDate="2011-10-12T11:37:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9534-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Network security: Minimum session security for NTLM SSP based (including secure RPC) client applications.
</ShortDescription>
<FullDescription>This policy setting determines which behaviors are allowed for applications using the NTLM Security Support Provider (SSP). The SSP Interface (SSPI) is used by applications that need authentication services. The setting does not modify how the authentication sequence works but instead require certain behaviors in applications that use the SSPI.
The possible values for the Network security: Minimum session security for NTLM SSP based (including secure RPC) clients setting are:
• Require message confidentiality. This option is only available in Windows XP and Windows Server 2003, the connection will fail if encryption is not negotiated. Encryption converts data into a form that is not readable until decrypted.
• Require message integrity. This option is only available in Windows XP and Windows Server 2003, the connection will fail if message integrity is not negotiated. The integrity of a message can be assessed through message signing. Message signing proves that the message has not been tampered with; it attaches a cryptographic signature that identifies the sender and is a numeric representation of the contents of the message.
• Require 128-bit encryption. The connection will fail if strong encryption (128-bit) is not negotiated.
• Require NTLMv2 session security. The connection will fail if the NTLMv2 protocol is not negotiated.
• Not Defined.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Require 128-bit encryption
</DefaultValue>
<Vulnerability>You can enable all of the options for this policy setting to help protect network traffic that uses the NTLM Security Support Provider (NTLM SSP) from being exposed or tampered with by an attacker who has gained access to the same network. In other words, these options help protect against man-in-the-middle attacks.</Vulnerability>
<Countermeasure>Enable all available options for the Network security: Minimum session security for NTLM SSP based (including secure RPC) clients policy setting. </Countermeasure>
<PotentialImpact>Client applications that are enforcing these settings will be unable to communicate with older servers that do not support them. This setting could impact Windows Clustering when applied to servers running Windows Server 2003, see "How to apply more restrictive security settings on a Windows Server 2003-based cluster server" at http://support.microsoft.com/default.aspx?scid=kb;en-us;891597 and "You receive an "Error 0x8007042b" error message when you add or join a node to a cluster if you use NTLM version 2 in Windows Server 2003" at http://support.microsoft.com/kb/890761/ for more information on possible issues and how to resolve them.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Require NTLMv2 session security,Require 128-bit encryption">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No Minimum">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Require message integrity">
<BehaviorDescription />
<DCMValue ValueA="16" />
<SCAPValue ValueA="16" />
<GPOValue ValueA="16" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality">
<BehaviorDescription />
<DCMValue ValueA="32" />
<SCAPValue ValueA="32" />
<GPOValue ValueA="32" />
</Mapping>
<Mapping FriendlyName="Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524288" />
<SCAPValue ValueA="524288" />
<GPOValue ValueA="524288" />
</Mapping>
<Mapping FriendlyName="Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870912" />
<SCAPValue ValueA="536870912" />
<GPOValue ValueA="536870912" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality">
<BehaviorDescription />
<DCMValue ValueA="48" />
<SCAPValue ValueA="48" />
<GPOValue ValueA="48" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524304" />
<SCAPValue ValueA="524304" />
<GPOValue ValueA="524304" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870928" />
<SCAPValue ValueA="536870928" />
<GPOValue ValueA="536870928" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality,Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524320" />
<SCAPValue ValueA="524320" />
<GPOValue ValueA="524320" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870944" />
<SCAPValue ValueA="536870944" />
<GPOValue ValueA="536870944" />
</Mapping>
<Mapping FriendlyName="Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395200" />
<SCAPValue ValueA="537395200" />
<GPOValue ValueA="537395200" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality,Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524336" />
<SCAPValue ValueA="524336" />
<GPOValue ValueA="524336" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870966" />
<SCAPValue ValueA="536870966" />
<GPOValue ValueA="536870966" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395216" />
<SCAPValue ValueA="537395216" />
<GPOValue ValueA="537395216" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality,Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395232" />
<SCAPValue ValueA="537395232" />
<GPOValue ValueA="537395232" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality,Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395248" />
<SCAPValue ValueA="537395248" />
<GPOValue ValueA="537395248" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa\MSV1_0</mssasc-core:KeyPath>
<mssasc-core:ValueName>NTLMMinClientSec</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0\NTLMMinClientSec" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:Not Defined" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="177" ID="{e379af24-45be-4a32-bd3d-5991cf9d4ada}" OriginalSettingID="{7c6c01fd-5c0d-4398-9de0-0a8855c4cd95}" Name="Network access: Sharing and security model for local accounts" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9503-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines how network logons that use local accounts are authenticated.</ShortDescription>
<FullDescription>This policy setting determines how network logons that use local accounts are authenticated. The Classic option allows precise control over access to resources, including the ability to assign different types of access to different users for the same resource. The Guest only option allows you to treat all users equally. In this context, all users authenticate as Guest only to receive the same access level to a given resource.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Classic - local users authenticate as themselves</DefaultValue>
<Vulnerability>With the Guest only model, any user who can authenticate to your computer over the network does so with guest privileges, which probably means that they will not have write access to shared resources on that computer. Although this restriction does increase security, it makes it more difficult for authorized users to access shared resources on those computers because ACLs on those resources must include access control entries (ACEs) for the Guest account. With the Classic model, local accounts should be password protected. Otherwise, if Guest access is enabled, anyone can use those user accounts to access shared system resources.</Vulnerability>
<Countermeasure>For network servers, configure the Network access: Sharing and security model for local accounts setting to Classic – local users authenticate as themselves. On end-user computers, configure this policy setting to Guest only – local users authenticate as guest.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Classic - local users authenticate as themselves">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Classic - local users authenticate as themselves">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Guest only: Local users authenticate as Guest">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>ForceGuest</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\ForceGuest" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:94" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="178" ID="{c6373a1c-e5d6-4e55-aa4e-b17017aed0a3}" OriginalSettingID="{931c9142-e8ac-4214-b588-554d4403b319}" Name="Network Security: Restrict NTLM: Add server exceptions in this domain" LockdownDate="2011-05-02T01:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8917-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to create an exception list of servers in this domain to which clients are allowed to use NTLM pass-through authentication if the "Network Security: Restrict NTLM: Deny NTLM authentication in this domain" is set.</ShortDescription>
<FullDescription>This policy setting allows you to create an exception list of servers in this domain to which clients are allowed to use NTLM pass-through authentication if the "Network Security: Restrict NTLM: Deny NTLM authentication in this domain" is set.
The naming format for servers on this exception list is the fully qualified domain name (FQDN) or NetBIOS server name used by the calling application listed one per line. A single asterisk (*) can be used at the beginning or end of the string as a wildcard character.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>NTLM is a Microsoft-developed authentication protocol that uses a challenge-response mechanism for authentication, in which client computers can prove their identities without sending a password to the server. The protocol employs three types of messages to negotiate the request, challenge the authenticity of the sender, and perform the authentication. Kerberos is a more robust protocol and is the preferred method of authentication when available. </Vulnerability>
<Countermeasure>Configure Network Security: Restrict NTLM: Add server exceptions in this domain as appropriate for the authentication requirements in your environment.</Countermeasure>
<PotentialImpact>If you configure this policy setting, you can define a list of servers in this domain to which clients are allowed to use NTLM authentication.
If you do not configure this policy setting, no exceptions will be applied.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_MULTI_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Netlogon\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>DCAllowedNTLMServers</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Multi-String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\DCAllowedNTLMServers" DataType="REG_MULTI_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="179" ID="{63b25c87-2f6e-4c0b-b544-365a617572d0}" OriginalSettingID="{576fb5ee-178c-4117-a4fe-ef3cbe30ce64}" Name="Network access: Named Pipes that can be accessed anonymously" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9218-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which communication sessions, or pipes, will have attributes and permissions that allow anonymous access.</ShortDescription>
<FullDescription>This policy setting determines which communication sessions, or pipes, will have attributes and permissions that allow anonymous access.
Note: When you configure this setting you specify a list of one or more objects. The delimiter used when entering the list is a line feed or carriage return, that is, type the first object on the list, press the Enter button, type the next object, press Enter again, etc. The setting value is stored as a comma-delimited list in group policy security templates. It is also rendered as a comma-delimited list in Group Policy Editor’s display pane and the Resultant Set of Policy console. It is recorded in the registry as a line-feed delimited list in a REG_MULTI_SZ value.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>
</DefaultValue>
<Vulnerability>You can restrict access over named pipes such as COMNAP and LOCATOR to help prevent unauthorized access to the network. The default list of named pipes and their purpose is provided in the following list:
COMNAP - SNABase named pipe. Systems Network Architecture (SNA) is a collection of network protocols that were originally developed for IBM mainframe computers.
COMNODE - SNA Server named pipe.
SQL\QUERY - Default named pipe for SQL Server.
SPOOLSS - Named pipe for the Print Spooler service.
EPMAPPER - End Point Mapper named pipe.
LOCATOR - Remote Procedure Call Locator service named pipe.
TrkWks - Distributed Link Tracking Client named pipe.
TrkSvr - Distributed Link Tracking Server named pipe.
</Vulnerability>
<Countermeasure>Configure the Network access: Named Pipes that can be accessed anonymously setting to a null value (enable the setting but do not enter named pipes in the text box).</Countermeasure>
<PotentialImpact>This configuration will disable null session access over named pipes, and applications that rely on this feature or on unauthenticated access to named pipes will no longer function. For example, with Microsoft Commercial Internet System 1.0, the Internet Mail Service runs under the Inetinfo process. Inetinfo starts in the context of the System account. When Internet Mail Service needs to query the Microsoft SQL Server database, it uses the System account, which uses null credentials to access a SQL pipe on the computer that runs SQL Server.
To avoid this problem, refer to the Microsoft Knowledge Base article “How to access network files from IIS applications,” which is located at http://support.microsoft.com/default.aspx?scid=207671.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_MULTI_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanManServer\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>NullSessionPipes</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Multi-String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\NullSessionPipes" DataType="REG_MULTI_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:91" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="180" ID="{d285a7a0-4548-4270-b4b1-3e551a6048fc}" OriginalSettingID="{096b92bd-142b-4c28-985f-f3ba1322265f}" Name="Interactive logon: Require Domain Controller authentication to unlock workstation" LockdownDate="2011-05-02T01:36:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8818-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>When this policy setting is enabled, a domain controller must authenticate the domain account used to unlock the computer.</ShortDescription>
<FullDescription>Logon information is required to unlock a locked computer. For domain accounts, the Interactive logon: Require Domain Controller authentication to unlock workstation setting determines whether it is necessary to contact a domain controller to unlock a computer. If you enable this setting, a domain controller must authenticate the domain account that is being used to unlock the computer. If you disable this setting, logon information confirmation with a domain controller is not required for a user to unlock the computer. However, if you configure the Interactive logon: Number of previous logons to cache (in case domain controller is not available) setting to a value that is greater than zero, then the user's cached credentials will be used to unlock the computer.
Note: This setting applies to Windows 2000 computers, but it is not available through the Security Configuration Manager tools on these computers.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>By default, the computer caches in memory the credentials of any users who are authenticated locally. The computer uses these cached credentials to authenticate anyone who attempts to unlock the console. When cached credentials are used, any changes that have recently been made to the account—such as user rights assignments, account lockout, or the account being disabled—are not considered or applied after the account is authenticated. User privileges are not updated, and (more importantly) disabled accounts are still able to unlock the console of the computer.</Vulnerability>
<Countermeasure>Configure the Interactive logon: Require Domain Controller authentication to unlock workstation setting to Enabled and configure the Interactive logon: Number of previous logons to cache (in case domain controller is not available) setting to 0.</Countermeasure>
<PotentialImpact>When the console on a computer is locked, either by a user or automatically by a screen saver time-out, the console can only be unlocked if the user is able to re-authenticate to the domain controller. If no domain controller is available, then users cannot unlock their workstations. If you configure the Interactive logon: Number of previous logons to cache (in case domain controller is not available) setting to 0, users whose domain controllers are unavailable (such as mobile or remote users) will not be able to log on.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows NT\CurrentVersion\Winlogon</mssasc-core:KeyPath>
<mssasc-core:ValueName>ForceUnlockLogon</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ForceUnlockLogon" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:75" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="181" ID="{5238d7fe-6006-4482-8aa5-23875627eece}" OriginalSettingID="{f4a2c795-7dc3-4deb-b76f-ef54c49da0d9}" Name="Network security: Allow Local System to use computer identity for NTLM" LockdownDate="2011-05-02T01:36:03Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9096-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows Local System services that use Negotiate to use the computer identity when reverting to NTLM authentication.</ShortDescription>
<FullDescription>This policy setting allows Local System services that use Negotiate to use the computer identity when reverting to NTLM authentication.
This policy is supported on at least Windows 7 or Windows Server 2008 R2.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>When connecting to computers running versions of Windows earlier than Windows Vista or Windows Server 2008, services running as Local System and using SPNEGO (Negotiate) that revert to NTLM use the computer identity. In Windows 7, if you are connecting to a computer running Windows Server 2008 or Windows Vista, then a system service uses either the computer identity or a NULL session. When connecting with a NULL session, a system-generated session key is created, which provides no protection but allows applications to sign and encrypt data without errors. When connecting with the computer identity, both signing and encryption is supported in order to provide data protection.</Vulnerability>
<Countermeasure>Configure Network security: Allow Local System to use computer identity for NTLM to Enabled.</Countermeasure>
<PotentialImpact>If you enable this policy setting, services running as Local System that use Negotiate will use the computer identity. This might cause some authentication requests between Windows operating systems to fail and log an error.
If you do not configure this policy setting, services running as Local System that use Negotiate when reverting to NTLM authentication will authenticate anonymously. This was the behavior in previous versions of Windows.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>UseMachineId</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\UseMachineId" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="182" ID="{a9d5b56b-3174-4227-8004-e817118d7442}" OriginalSettingID="{adfc53c0-573a-4b06-8a91-4dc91e830362}" Name="Interactive logon: Number of previous logons to cache (in case domain controller is not available)" LockdownDate="2011-05-15T05:26:30Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8487-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether a user can log on to a Windows domain using cached account information.</ShortDescription>
<FullDescription>This policy setting determines whether a user can log on to a Windows domain using cached account information. Logon information for domain accounts can be cached locally to allow users to log on even if a domain controller cannot be contacted. This policy setting determines the number of unique users for whom logon information is cached locally. If this value is set to 0, the logon cache feature is disabled. An attacker who is able to access the file system of the server could locate this cached information and use a brute force attack to determine user passwords.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>10 logons</DefaultValue>
<Vulnerability>The number that is assigned to this policy setting indicates the number of users whose logon information the servers will cache locally. If the number is set to 10, then the server caches logon information for 10 users. When an eleventh user logs on to the computer, the server overwrites the oldest cached logon session.
Users who access the server console will have their logon credentials cached on that server. An attacker who is able to access the file system of the server could locate this cached information and use a brute force attack to attempt to determine user passwords.
To mitigate this type of attack, Windows encrypts the information and obscures its physical location.
</Vulnerability>
<Countermeasure>Configure the Interactive logon: Number of previous logons to cache (in case domain controller is not available) setting to 0, which disables the local caching of logon information. Additional countermeasures include enforcement of strong password policies and physically secure locations for the computers.</Countermeasure>
<PotentialImpact>Users will be unable to log on to any computers if there is no domain controller available to authenticate them. Organizations may want to configure this value to 2 for end-user computers, especially for mobile users. A configuration value of 2 means that the user’s logon information will still be in the cache, even if a member of the IT department has recently logged on to their computer to perform system maintenance. This method allows users to log on to their computers when they are not connected to the organization’s network.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>logon(s)</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows NT\CurrentVersion\Winlogon</mssasc-core:KeyPath>
<mssasc-core:ValueName>cachedlogonscount</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\CachedLogonsCount" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:72" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="183" ID="{9ab95317-895a-4e6e-a2ee-d063eb3fa587}" OriginalSettingID="{502cd61a-fec9-42f0-a096-1ac097bbdf73}" Name="Microsoft network server: Digitally sign communications (always)" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9040-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines if the server side SMB service is required to perform SMB packet signing. </ShortDescription>
<FullDescription>This policy setting determines if the server side SMB service is required to perform SMB packet signing. Enable this policy setting in a mixed environment to prevent downstream clients from using the workstation as a network server.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Session hijacking uses tools that allow attackers who have access to the same network as the client or server to interrupt, end, or steal a session in progress. Attackers can potentially intercept and modify unsigned SMB packets and then modify the traffic and forward it so that the server might perform undesirable actions. Alternatively, the attacker could pose as the server or client after legitimate authentication and gain unauthorized access to data.
SMB is the resource sharing protocol that is supported by many Windows operating systems. It is the basis of NetBIOS and many other protocols. SMB signatures authenticate both users and the servers that host the data. If either side fails the authentication process, data transmission will not take place.
</Vulnerability>
<Countermeasure>Configure the settings as follows:
• Disable Microsoft Network Client: Digitally Sign Communications (Always).
• Disable Microsoft Network Server: Digitally Sign Communications (Always).
• Microsoft Network Client: Digitally Sign \Communications (If Server Agrees) to Enabled.
• Microsoft Network Server: Digitally Sign Communications (If Client Agrees) to Enabled.
In highly secure environments we recommend that you configure all of these settings to Enabled. However, that configuration may cause slower performance on client computers and prevent communications with earlier SMB applications and operating systems.
Note
An alternative countermeasure that could protect all network traffic would be to implement digital signatures with Internet Protocol security (IPsec). There are hardware-based accelerators for IPsec encryption and signing that could be used to minimize the performance impact on the servers’ CPUs. No such accelerators are available for SMB signing.
</Countermeasure>
<PotentialImpact>The Windows 2000 Server, Windows 2000 Professional, Windows Server 2003, Windows XP Professional and Windows Vista implementations of the SMB file and print sharing protocol support mutual authentication, which prevents session hijacking attacks and supports message authentication to prevent man-in-the-middle attacks. SMB signing provides this authentication by placing a digital signature into each SMB, which is then verified by both the client and the server.
Implementation of SMB signing may negatively affect performance, because each packet needs to be signed and verified. If these settings are enabled on a server that is performing multiple roles, such as a small business server that is serving as a domain controller, file server, print server, and application server performance may be substantially slowed. Additionally, if you configure computers to ignore all unsigned SMB communications, older applications and operating systems will not be able to connect. However, if you completely disable all SMB signing, computers will be vulnerable to session hijacking attacks.
When SMB signing policies are enabled on domain controllers running Windows Server 2003 and member computers running Windows Vista SP1 or Windows Server 2008 group policy processing will fail. A hotfix is available from Microsoft that resolves this issue; see Microsoft Knowledgebase Article 950876 for more details: http://support.microsoft.com/default.aspx/kb/950876/.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanManServer\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>requiresecuritysignature</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\requiresecuritysignature" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:84" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="184" ID="{60effdd2-b86e-469a-b456-ef77b6223157}" OriginalSettingID="{b2dd11f1-f8e5-41d5-928a-44858db8616e}" Name="MSS: (Hidden) Hide Computer From the Browse List (not recommended except for highly secure environments)" LockdownDate="2011-06-01T01:16:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8560-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The registry value entry appears as MSS: (Hidden) Hide Computer From the Browse List (not recommended except for highly secure environments) in the SCE.</ShortDescription>
<FullDescription>The registry value entry Hidden was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanserver\Parameters\ registry key. The entry appears as MSS: (Hidden) Hide Computer From the Browse List (not recommended except for highly secure environments) in the SCE.
You can configure a computer so that it does not send announcements to browsers on the domain. If you do so, you hide the computer from the Browse list, which means that the computer will stop announcing itself to other computers on the same network. An attacker who knows the name of a computer can more easily gather additional information about the system. You can enable this setting to remove one method that an attacker might use to gather information about computers on the network. Also, this setting can help reduce network traffic when enabled. However, the security benefits of this setting are small because attackers can use alternative methods to identify and locate potential targets. For this reason, Microsoft recommends to configure this setting to Enabled in high security environments, and to configure it to Not Defined in enterprise environments.
For additional information, see the Knowledge Base article 321710, "HOW TO: Hide a Windows 2000-Based Computer from the Browser List."
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not Defined</DefaultValue>
<Vulnerability>An attacker who knows the name of a computer can more easily gather additional information about the computer. If you enable this entry, you remove one method that an attacker might use to gather information about computers on the network. Also, if you enable this entry you can help reduce network traffic. However, the vulnerability is small because attackers can use alternative methods to identify and locate potential targets.</Vulnerability>
<Countermeasure>Do not configure the MSS: (Hidden) Hide Computer From the Browse List (not recommended except for highly secure environments) entry except on highly secure computers, where it should be configured to a value of Enabled.
The possible values for this registry entry are:
● 1 or 0. The default configuration is 0 (disabled).
In the SCE UI, these options appear as:
● Enabled
● Disabled
● Not Defined
</Countermeasure>
<PotentialImpact>The computer will no longer appear on the Browser list or in Network Neighborhood on other computers on the same network.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Lanmanserver\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>Hidden</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Lanmanserver\Parameters\Hidden" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:114" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="185" ID="{da041203-cfc1-44ed-ad6a-c505d620c35d}" OriginalSettingID="{817b2f4e-1f03-4bcc-927b-816ddd4777f9}" Name="Microsoft network client: Digitally sign communications (if server agrees)" LockdownDate="2011-05-02T01:36:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9344-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether the SMB client will attempt to negotiate SMB packet signing.</ShortDescription>
<FullDescription>This policy setting determines whether the SMB client will attempt to negotiate SMB packet signing. The implementation of digital signing in Windows–based networks helps to prevent sessions from being hijacked. If you enable this policy setting, the Microsoft network client will use signing only if the server with which it communicates accepts digitally signed communication.
Microsoft recommends to enable The Microsoft network client: Digitally sign communications (if server agrees) setting.
Note Enabling this policy setting on SMB clients on your network makes them fully effective for packet signing with all clients and servers in your environment.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>Session hijacking uses tools that allow attackers who have access to the same network as the client or server to interrupt, end, or steal a session in progress. Attackers can potentially intercept and modify unsigned SMB packets and then modify the traffic and forward it so that the server might perform undesirable actions. Alternatively, the attacker could pose as the server or client after legitimate authentication and gain unauthorized access to data.
SMB is the resource sharing protocol that is supported by many Windows operating systems. It is the basis of NetBIOS and many other protocols. SMB signatures authenticate both users and the servers that host the data. If either side fails the authentication process, data transmission will not take place.
</Vulnerability>
<Countermeasure>Configure the settings as follows:
• Disable Microsoft Network Client: Digitally Sign Communications (Always).
• Disable Microsoft Network Server: Digitally Sign Communications (Always).
• Microsoft Network Client: Digitally Sign \Communications (If Server Agrees) to Enabled.
• Microsoft Network Server: Digitally Sign Communications (If Client Agrees) to Enabled.
In highly secure environments we recommend that you configure all of these settings to Enabled. However, that configuration may cause slower performance on client computers and prevent communications with earlier SMB applications and operating systems.
Note
An alternative countermeasure that could protect all network traffic would be to implement digital signatures with Internet Protocol security (IPsec). There are hardware-based accelerators for IPsec encryption and signing that could be used to minimize the performance impact on the servers’ CPUs. No such accelerators are available for SMB signing.
</Countermeasure>
<PotentialImpact>The Windows 2000 Server, Windows 2000 Professional, Windows Server 2003, Windows XP Professional and Windows Vista implementations of the SMB file and print sharing protocol support mutual authentication, which prevents session hijacking attacks and supports message authentication to prevent man-in-the-middle attacks. SMB signing provides this authentication by placing a digital signature into each SMB, which is then verified by both the client and the server.
Implementation of SMB signing may negatively affect performance, because each packet needs to be signed and verified. If these settings are enabled on a server that is performing multiple roles, such as a small business server that is serving as a domain controller, file server, print server, and application server performance may be substantially slowed. Additionally, if you configure computers to ignore all unsigned SMB communications, older applications and operating systems will not be able to connect. However, if you completely disable all SMB signing, computers will be vulnerable to session hijacking attacks.
When SMB signing policies are enabled on domain controllers running Windows Server 2003 and member computers running Windows Vista SP1 or Windows Server 2008 group policy processing will fail. A hotfix is available from Microsoft that resolves this issue; see Microsoft Knowledgebase Article 950876 for more details: http://support.microsoft.com/default.aspx/kb/950876/.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanmanWorkstation\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnableSecuritySignature</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters\EnableSecuritySignature" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:81" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="186" ID="{fe3742e8-779a-4f52-80d5-c556f80c8c35}" OriginalSettingID="{6887f38a-7719-4d15-a5cd-ab731fb28bb1}" Name="Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers" LockdownDate="2011-05-02T01:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9556-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to deny or audit outgoing NTLM traffic from this Windows 7 or this Windows Server 2008 R2 computer to any Windows remote server.</ShortDescription>
<FullDescription>This policy setting allows you to deny or audit outgoing NTLM traffic from this Windows 7 or this Windows Server 2008 R2 computer to any Windows remote server.
This policy is supported on at least Windows 7 or Windows Server 2008 R2.
Note: Audit and block events are recorded on this computer in the "Operational" Log located under the Applications and Services Log/Microsoft/Windows/NTLM.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>NTLM is a Microsoft-developed authentication protocol that uses a challenge-response mechanism for authentication, in which client computers can prove their identities without sending a password to the server. The protocol employs three types of messages to negotiate the request, challenge the authenticity of the sender, and perform the authentication. Kerberos is a more robust protocol and is the preferred method of authentication when available. </Vulnerability>
<Countermeasure>Configure Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers to Deny All.</Countermeasure>
<PotentialImpact>If you select "Allow all" or do not configure this policy setting, the client computer can authenticate identities to a remote server by using NTLM authentication.
If you select "Audit all," the client computer logs an event for each NTLM authentication request to a remote server. This allows you to identify those servers receiving NTLM authentication requests from the client computer.
If you select "Deny all," the client computer cannot authenticate identities to a remote server by using NTLM authentication. You can use the "Network security: Restrict NTLM: Add remote server exceptions for NTLM authentication" policy setting to define a list of remote servers to which clients are allowed to use NTLM authentication.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Allow all">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Audit all">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Deny all ">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa\MSV1_0</mssasc-core:KeyPath>
<mssasc-core:ValueName>RestrictSendingNTLMTraffic</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0\RestrictSendingNTLMTraffic" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="187" ID="{6d7f98ad-c893-4a7f-b930-1366364f8388}" OriginalSettingID="{fbcb4ac3-1923-414f-94b3-65ec48eea6e2}" Name="Microsoft network server: Server SPN target name validation level" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8503-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting controls the level of validation a computer with shared folders or printers performs on the service principal name provided by the client computer when it establishes a session using the server message block (SMB) protocol</ShortDescription>
<FullDescription>This policy setting controls the level of validation a computer with shared folders or printers (the server) performs on the service principal name (SPN) that is provided by the client computer when it establishes a session using the server message block (SMB) protocol.
The server message block (SMB) protocol provides the basis for file and print sharing and other networking operations, such as remote Windows administration. The SMB protocol supports validating the SMB server service principal name (SPN) within the authentication blob provided by a SMB client to prevent a class of attacks against SMB servers referred to as SMB relay attacks. This setting will affect both SMB1 and SMB2.
This security setting determines the level of validation a SMB server performs on the service principal name (SPN) provided by the SMB client when trying to establish a session to an SMB server.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined
</DefaultValue>
<Vulnerability>The identity of a computer can be spoofed to gain unauthorized access to network resources.</Vulnerability>
<Countermeasure>Configuring this setting to accept or require that a connecting client send a SPN during session setup helps ensure that authorized clients are the only ones connecting to a resource.</Countermeasure>
<PotentialImpact>ll Windows operating systems support both a client-side SMB component and a server-side SMB component. This setting affects the server SMB behavior, and its implementation should be carefully evaluated and tested to prevent disruptions to file and print serving capabilities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Off">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Accept if provided by client">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Required from client">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanManServer\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>SMBServerNameHardeningLevel</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\SMBServerNameHardeningLevel" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:86" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="188" ID="{dbeb6cdd-12ce-4c09-8ed7-50e83d8efec8}" OriginalSettingID="{763c80f9-f87a-4246-ab22-d0817891d5d3}" Name="Network security: Allow LocalSystem NULL session fallback" LockdownDate="2011-05-02T01:36:03Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8804-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Allow NTLM to fall back to NULL session when used with LocalSystem.</ShortDescription>
<FullDescription>Allow NTLM to fall back to NULL session when used with LocalSystem.
The default is TRUE up to Windows Vista and FALSE in Windows 7.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not Defined</DefaultValue>
<Vulnerability>NULL sessions are less secure because by definition they are unauthenticated.</Vulnerability>
<Countermeasure>Configure Network security: Allow LocalSystem NULL session fallback to Disabled.</Countermeasure>
<PotentialImpact>Any applications that require NULL sessions for LocalSystem will not work as designed.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa\MSV1_0</mssasc-core:KeyPath>
<mssasc-core:ValueName>allownullsessionfallback</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0\allownullsessionfallback" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="189" ID="{0c2f431a-9641-4342-89e6-da8735a689c2}" OriginalSettingID="{eaa6e376-dcd2-4094-96ea-a9f404a50d51}" Name="Allow users to connect remotely using Remote Desktop Services" LockdownDate="2011-10-12T11:37:55Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9985-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to control if users can connect to a computer using Terminal Services or Remote Desktop.</ShortDescription>
<FullDescription>This policy setting allows you to control if users can connect to a computer using Terminal Services or Remote Desktop.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections</UIPath>
<DefaultValue>Not Configured</DefaultValue>
<Vulnerability>Any account with the Allow log on through Terminal Services user right can log on to the remote console of the computer. If you do not restrict access to legitimate users who need to log on to the console of the computer, unauthorized users could download and execute malicious code to elevate their privileges.</Vulnerability>
<Countermeasure>To protect against this risk configure this setting to disabled.</Countermeasure>
<PotentialImpact>If this setting is enabled legitimate users will be unable to use Terminal Services or Remote Desktop, this could make it more difficult for help desk technicians to troubleshoot and resolve problems remotely. It would also make it impossible to use Terminal Services for hosting shared applications.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine" />
<DataType>String</DataType>
</DiscoveryInfo>
<policy name="TS_DISABLE_CONNECTIONS" class="Machine" displayName="$(string.06e5c8e768674411b9605c9886a01169)" explainText="$(string.a483a2a9ae094975b32a695226d97ac6)" key="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledList xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:item key="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" valueName="fDenyTSConnections">
<admx:value>
<admx:decimal value="0" />
</admx:value>
</admx:item>
</admx:enabledList>
<admx:disabledList xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:item key="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" valueName="fDenyTSConnections">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
</admx:disabledList>
</policy>
<ADMLDefinition>
<string id="06e5c8e768674411b9605c9886a01169">Allow users to connect remotely using Remote Desktop Services</string>
<string id="a483a2a9ae094975b32a695226d97ac6">This policy setting allows you to control if users can connect to a computer using Terminal Services or Remote Desktop.</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional or Windows Server 2003 family</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:166" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="190" ID="{698413e7-00fd-459c-8fef-1a843679751f}" OriginalSettingID="{0f319931-aa36-4313-9320-86311c0fa623}" Name="Network access: Restrict anonymous access to Named Pipes and Shares" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9540-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>When enabled, this policy setting restricts anonymous access to only those shares and pipes that are named in the Network access: Named pipes that can be accessed anonymously and Network access: Shares that can be accessed anonymously settings.</ShortDescription>
<FullDescription>When enabled, this policy setting restricts anonymous access to only those shares and pipes that are named in the Network access: Named pipes that can be accessed anonymously and Network access: Shares that can be accessed anonymously settings. This policy setting controls null session access to shares on your computers by adding RestrictNullSessAccess with the value 1 in the HKLM\System
\CurrentControlSet\Services\LanManServer\Parameters registry key. This registry value toggles null session shares on or off to control whether the server service restricts unauthenticated clients' access to named resources. Null sessions are a weakness that can be exploited through shares (including the default shares) on computers in your environment.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled
</DefaultValue>
<Vulnerability>Null sessions are a weakness that can be exploited through shares (including the default shares) on computers in your environment.</Vulnerability>
<Countermeasure>Configure the Network access: Restrict anonymous access to Named Pipes and Shares setting to Enabled. </Countermeasure>
<PotentialImpact>You can enable this policy setting to restrict null session access for unauthenticated users to all server pipes and shared folders except those that are listed in the NullSessionPipes and NullSessionShares entries.
If you choose to enable this setting and are supporting Windows NT 4.0 domains, you should check if any of the named pipes are required to maintain trust relationships between the domains, and then add the pipe to the Network access: Named pipes that can be accessed anonymously:
• COMNAP–SNA session access
• COMNODE–SNA session access
• SQL\QUERY–SQL instance access
• SPOOLSS–Spooler service
• LLSRPC–License Logging service
• Netlogon–Net Logon service
• Lsarpc–LSA access
• Samr–Remote access to SAM objects
• browser–Computer Browser service
Previous to the release of Windows Server 2003 with Service Pack 1 (SP1) these named pipes were allowed anonymous access by default, but with the increased hardening in Windows Server 2003 with SP1 these pipes must be explicitly added if needed.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanManServer\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>restrictnullsessaccess</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\RestrictNullSessAccess" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="191" ID="{b9a7f6be-bcf1-40d1-8624-fbb82988fd7e}" OriginalSettingID="{e197f79b-a454-407c-9307-7b3210313e61}" Name="Network access: Let Everyone permissions apply to anonymous users" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8936-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines what additional permissions are assigned for anonymous connections to the computer</ShortDescription>
<FullDescription>This policy setting determines what additional permissions are assigned for anonymous connections to the computer. If you enable this policy setting, anonymous Windows users are allowed to perform certain activities, such as enumerate the names of domain accounts and network shares. An unauthorized user could anonymously list account names and shared resources and use the information to guess passwords or perform social engineering attacks.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>An unauthorized user could anonymously list account names and shared resources and use the information to attempt to guess passwords, perform social engineering attacks, or launch DoS attacks.</Vulnerability>
<Countermeasure>Configure the Network access: Let Everyone permissions apply to anonymous users setting to Disabled. </Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>EveryoneIncludesAnonymous</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\EveryoneIncludesAnonymous" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:90" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="192" ID="{44ed2d85-622a-4818-bc2b-f662f1110895}" OriginalSettingID="{17463ab9-ffc1-40ab-8b09-e8054ba4504c}" Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) servers" LockdownDate="2011-10-12T11:37:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9736-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Network security: Minimum session security for NTLM SSP based (including secure RPC) server applications.</ShortDescription>
<FullDescription>This policy setting determines which behaviors are allowed for applications using the NTLM Security Support Provider (SSP). The SSP Interface (SSPI) is used by applications that need authentication services. The setting does not modify how the authentication sequence works but instead require certain behaviors in applications that use the SSPI.
The possible values for the Network security: Minimum session security for NTLM SSP based (including secure RPC) servers setting are:
• Require message confidentiality. This option is only available in Windows XP and Windows Server 2003, the connection will fail if encryption is not negotiated. Encryption converts data into a form that is not readable until decrypted.
• Require message integrity. This option is only available in Windows XP and Windows Server 2003, the connection will fail if message integrity is not negotiated. The integrity of a message can be assessed through message signing. Message signing proves that the message has not been tampered with; it attaches a cryptographic signature that identifies the sender and is a numeric representation of the contents of the message.
• Require 128-bit encryption. The connection will fail if strong encryption (128-bit) is not negotiated.
• Require NTLMv2 session security. The connection will fail if the NTLMv2 protocol is not negotiated.
• Not Defined.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Require 128-bit encryption
</DefaultValue>
<Vulnerability>You can enable all of the options for this policy setting to help protect network traffic that uses the NTLM Security Support Provider (NTLM SSP) from being exposed or tampered with by an attacker who has gained access to the same network. That is, these options help protect against man-in-the-middle attacks.</Vulnerability>
<Countermeasure>Enable all available options for the Network security: Minimum session security for NTLM SSP based (including secure RPC) servers policy setting.
</Countermeasure>
<PotentialImpact>Server applications that are enforcing these settings will be unable to communicate with older servers that do not support them. This setting could impact Windows Clustering when applied to servers running Windows Server 2003, see "How to apply more restrictive security settings on a Windows Server 2003-based cluster server" at http://support.microsoft.com/default.aspx?scid=kb;en-us;891597 and "You receive an "Error 0x8007042b" error message when you add or join a node to a cluster if you use NTLM version 2 in Windows Server 2003" at http://support.microsoft.com/kb/890761/ for more information on possible issues and how to resolve them.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Require NTLMv2 session security,Require 128-bit encryption">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No Minimum">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Require message integrity">
<BehaviorDescription />
<DCMValue ValueA="16" />
<SCAPValue ValueA="16" />
<GPOValue ValueA="16" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality">
<BehaviorDescription />
<DCMValue ValueA="32" />
<SCAPValue ValueA="32" />
<GPOValue ValueA="32" />
</Mapping>
<Mapping FriendlyName="Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524288" />
<SCAPValue ValueA="524288" />
<GPOValue ValueA="524288" />
</Mapping>
<Mapping FriendlyName="Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870912" />
<SCAPValue ValueA="536870912" />
<GPOValue ValueA="536870912" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality">
<BehaviorDescription />
<DCMValue ValueA="48" />
<SCAPValue ValueA="48" />
<GPOValue ValueA="48" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524304" />
<SCAPValue ValueA="524304" />
<GPOValue ValueA="524304" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870928" />
<SCAPValue ValueA="536870928" />
<GPOValue ValueA="536870928" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality,Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524320" />
<SCAPValue ValueA="524320" />
<GPOValue ValueA="524320" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870944" />
<SCAPValue ValueA="536870944" />
<GPOValue ValueA="536870944" />
</Mapping>
<Mapping FriendlyName="Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395200" />
<SCAPValue ValueA="537395200" />
<GPOValue ValueA="537395200" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality,Require NTLMv2 session security">
<BehaviorDescription />
<DCMValue ValueA="524336" />
<SCAPValue ValueA="524336" />
<GPOValue ValueA="524336" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="536870966" />
<SCAPValue ValueA="536870966" />
<GPOValue ValueA="536870966" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395216" />
<SCAPValue ValueA="537395216" />
<GPOValue ValueA="537395216" />
</Mapping>
<Mapping FriendlyName="Require message confidentiality,Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395232" />
<SCAPValue ValueA="537395232" />
<GPOValue ValueA="537395232" />
</Mapping>
<Mapping FriendlyName="Require message integrity,Require message confidentiality,Require NTLMv2 session security,Require 128-bit encryption">
<BehaviorDescription />
<DCMValue ValueA="537395248" />
<SCAPValue ValueA="537395248" />
<GPOValue ValueA="537395248" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa\MSV1_0</mssasc-core:KeyPath>
<mssasc-core:ValueName>NTLMMinServerSec</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0\NTLMMinServerSec" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="193" ID="{1e8b628d-efd5-4db9-a40d-549dde9fd0f3}" OriginalSettingID="{d23eb0d5-b330-4ad7-b489-bcb975e1e2d5}" Name="MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes" LockdownDate="2011-05-22T06:25:35Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8513-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The entry appears as MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes in the SCE.</ShortDescription>
<FullDescription>The registry value entry EnableICMPRedirect was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\ registry key. The entry appears as MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes in the SCE.
Internet Control Message Protocol (ICMP) redirects cause the stack to plumb host routes. These routes override the Open Shortest Path First (OSPF)–generated routes. Microsoft recommends to configure this setting to Not Defined for enterprise environments and to Disabled for high security environments.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>This behavior is expected. The problem is that the 10 minute time-out period for the ICMP redirect-plumbed routes temporarily creates a network situation in which traffic will no longer be routed properly for the affected host. </Vulnerability>
<Countermeasure>Configure the MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes entry to a value of Disabled.
The possible values for this registry entry are:
• 1 or 0. The default configuration is 1 (enabled).
In the SCE UI, these options appear as:
• Enabled
• Disabled
• Not Defined
</Countermeasure>
<PotentialImpact>When Routing and Remote Access Service (RRAS) is configured as an autonomous system boundary router (ASBR), it does not correctly import connected interface subnet routes. Instead, this router injects host routes into the OSPF routes. However, the OSPF router can not be used as an ASBR router, and when connected interface subnet routes are imported into OSPF the result is confusing routing tables with strange routing paths.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Tcpip\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnableICMPRedirect</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\EnableICMPRedirect" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:113" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="194" ID="{0994b843-ee52-4cf0-8b3d-496c85b0bc3c}" OriginalSettingID="{b5b445ef-7dd4-405f-84b4-a3e307b1167b}" Name="Network Security: Restrict NTLM: Incoming NTLM traffic" LockdownDate="2011-05-02T01:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9494-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to deny or allow incoming NTLM traffic.</ShortDescription>
<FullDescription>This policy setting allows you to deny or allow incoming NTLM traffic.
This policy is supported on at least Windows 7 or Windows Server 2008 R2.
Note: Block events are recorded on this computer in the "Operational" Log located under the Applications and Services Log/Microsoft/Windows/NTLM.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>NTLM is a Microsoft-developed authentication protocol that uses a challenge-response mechanism for authentication, in which client computers can prove their identities without sending a password to the server. The protocol employs three types of messages to negotiate the request, challenge the authenticity of the sender, and perform the authentication. Kerberos is a more robust protocol and is the preferred method of authentication when available. </Vulnerability>
<Countermeasure>Configure Network Security: Restrict NTLM: Incoming NTLM traffic to Deny all accounts</Countermeasure>
<PotentialImpact>If you select "Allow all" or do not configure this policy setting, the server will allow all NTLM authentication requests.
If you select "Deny all domain accounts," the server will deny NTLM authentication requests for domain logon and display an NTLM blocked error, but allow local account logon.
If you select "Deny all accounts," the server will deny NTLM authentication requests from incoming traffic and display an NTLM blocked error.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Allow all">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Deny all domain accounts">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Deny all accounts">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa\MSV1_0</mssasc-core:KeyPath>
<mssasc-core:ValueName>RestrictReceivingNTLMTraffic</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0\RestrictReceivingNTLMTraffic" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="195" ID="{852d2467-045b-49ef-9d0c-a421477830c7}" OriginalSettingID="{6cd6ebda-aa2e-472a-8ea7-580e704c47d3}" Name="MSS: (KeepAliveTime) How often keep-alive packets are sent in milliseconds" LockdownDate="2011-05-22T06:25:35Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9426-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The registry value entry appears as MSS: (KeepAliveTime) How often keep-alive packets are sent in milliseconds (300,000 is recommended) in the SCE.</ShortDescription>
<FullDescription>The registry value entry KeepAliveTime was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\ registry key. The entry appears as MSS: (KeepAliveTime) How often keep-alive packets are sent in milliseconds (300,000 is recommended) in the SCE.
This value controls how often TCP attempts to verify that an idle connection is still intact by sending a keep-alive packet. If the remote computer is still reachable, it acknowledges the keep-alive packet.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not Defined</DefaultValue>
<Vulnerability>An attacker who is able to connect to network applications could establish numerous connections to cause a DoS condition.</Vulnerability>
<Countermeasure>Configure the MSS: (KeepAliveTime) How often keep-alive packets are sent in milliseconds (300,000 is recommended) entry to a value of 300000 or 5 minutes.
The possible values for this registry entry are:
• 1 through 0xFFFFFFFF. The default configuration is 7,200,000 (two hours).
In the SCE UI, the following list of options appears:
• 150000 or 2.5 minutes
• 300000 or 5 minutes (recommended)
• 600000 or 10 minutes
• 1200000 or 20 minutes
• 2400000 or 40 minutes
• 3600000 or 1 hour
• 7200000 or 2 hours (default value)
• Not Defined
</Countermeasure>
<PotentialImpact>Keep-alive packets are not sent by default by Windows. However, some applications may configure the TCP stack flag that requests keep-alive packets. For such configurations, you can lower this value from the default setting of two hours to five minutes to disconnect inactive sessions more quickly.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="150000 or 2.5 minutes">
<BehaviorDescription />
<DCMValue ValueA="150000" />
<SCAPValue ValueA="150000" />
<GPOValue ValueA="150000" />
</Mapping>
<Mapping FriendlyName="300000 or 5 minutes (recommended)">
<BehaviorDescription />
<DCMValue ValueA="300000" />
<SCAPValue ValueA="300000" />
<GPOValue ValueA="300000" />
</Mapping>
<Mapping FriendlyName="600000 or 10 minutes">
<BehaviorDescription />
<DCMValue ValueA="600000" />
<SCAPValue ValueA="600000" />
<GPOValue ValueA="600000" />
</Mapping>
<Mapping FriendlyName="1200000 or 20 minute">
<BehaviorDescription />
<DCMValue ValueA="1200000" />
<SCAPValue ValueA="1200000" />
<GPOValue ValueA="1200000" />
</Mapping>
<Mapping FriendlyName="2400000 or 40 minutes">
<BehaviorDescription />
<DCMValue ValueA="2400000" />
<SCAPValue ValueA="2400000" />
<GPOValue ValueA="2400000" />
</Mapping>
<Mapping FriendlyName="3600000 or 1 hour">
<BehaviorDescription />
<DCMValue ValueA="3600000" />
<SCAPValue ValueA="3600000" />
<GPOValue ValueA="3600000" />
</Mapping>
<Mapping FriendlyName="7200000 or 2 hours (default value)">
<BehaviorDescription />
<DCMValue ValueA="7200000" />
<SCAPValue ValueA="7200000" />
<GPOValue ValueA="7200000" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Tcpip\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>KeepAliveTime</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:115" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="196" ID="{66759ffc-15e5-4a70-90ff-f9c347e76516}" OriginalSettingID="{c067da7d-80a9-4b00-9414-d98d37139490}" Name="Network access: Shares that can be accessed anonymously" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9196-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which network shares can be accessed by anonymous users. </ShortDescription>
<FullDescription>This policy setting determines which network shares can be accessed by anonymous users. The default configuration for this policy setting has little effect because all users have to be authenticated before they can access shared resources on the server.
Note: It can be very dangerous to add other shares to this Group Policy setting. Any network user can access any shares that are listed, which could exposure or corrupt sensitive data.
Note: When you configure this setting you specify a list of one or more objects. The delimiter used when entering the list is a line feed or carriage return, that is, type the first object on the list, press the Enter button, type the next object, press Enter again, etc. The setting value is stored as a comma-delimited list in group policy security templates. It is also rendered as a comma-delimited list in Group Policy Editor’s display pane and the Resultant Set of Policy console. It is recorded in the registry as a line-feed delimited list in a REG_MULTI_SZ value.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined
</DefaultValue>
<Vulnerability>It is very dangerous to enable this setting. Any shares that are listed can be accessed by any network user, which could lead to the exposure or corruption of sensitive data.</Vulnerability>
<Countermeasure>Configure the Network access: Shares that can be accessed anonymously setting to a null value. </Countermeasure>
<PotentialImpact>There should be little impact because this is the default configuration. Only authenticated users will have access to shared resources on the server.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_MULTI_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanManServer\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>NullSessionShares</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Multi-String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\NullSessionShares" DataType="REG_MULTI_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:93" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="197" ID="{5850e810-a38a-44ca-baee-5466141360eb}" OriginalSettingID="{520c46db-7a33-4ae2-a55f-fe10182c9398}" Name="Network Security: Restrict NTLM: NTLM authentication in this domain" LockdownDate="2011-05-02T01:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9525-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to deny or allow NTLM authentication within a domain from this domain controller. This policy does not affect interactive logon to this domain controller.</ShortDescription>
<FullDescription>This policy setting allows you to deny or allow NTLM authentication within a domain from this domain controller. This policy does not affect interactive logon to this domain controller.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>NTLM is a Microsoft-developed authentication protocol that uses a challenge-response mechanism for authentication, in which client computers can prove their identities without sending a password to the server. The protocol employs three types of messages to negotiate the request, challenge the authenticity of the sender, and perform the authentication. Kerberos is a more robust protocol and is the preferred method of authentication when available. </Vulnerability>
<Countermeasure>Configure Network Security: Restrict NTLM: NTLM authentication in this domain to Deny All</Countermeasure>
<PotentialImpact>
If you select "Disabled" or do not configure this policy setting, the domain controller will allow all NTLM pass-through authentication requests within the domain.
If you select "Deny for domain accounts to domain servers" the domain controller will deny all NTLM authentication logon attempts to all servers in the domain that are using domain accounts and return an NTLM blocked error unless the server name is on the exception list in the "Network security: Restrict NTLM: Add server exceptions for NTLM authentication in this domain" policy setting.
If you select "Deny for domain account" the domain controller will deny all NTLM authentication logon attempts from domain accounts and return an NTLM blocked error unless the server name is on the exception list in the "Network security: Restrict NTLM: Add server exceptions for NTLM authentication in this domain" policy setting.
If you select "Deny for domain servers" the domain controller will deny NTLM authentication requests to all servers in the domain and return an NTLM blocked error unless the server name is on the exception list in the "Network security: Restrict NTLM: Add server exceptions for NTLM authentication in this domain" policy setting.
If you select "Deny all," the domain controller will deny all NTLM pass-through authentication requests from its servers and for its accounts and return an NTLM blocked error unless the server name is on the exception list in the "Network security: Restrict NTLM: Add server exceptions for NTLM authentication in this domain" policy setting.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disable">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Deny for domain accounts to domain servers">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Deny for domain accounts">
<BehaviorDescription />
<DCMValue ValueA="3" />
<SCAPValue ValueA="3" />
<GPOValue ValueA="3" />
</Mapping>
<Mapping FriendlyName="Deny for domain servers">
<BehaviorDescription />
<DCMValue ValueA="5" />
<SCAPValue ValueA="5" />
<GPOValue ValueA="5" />
</Mapping>
<Mapping FriendlyName="Deny all">
<BehaviorDescription />
<DCMValue ValueA="7" />
<SCAPValue ValueA="7" />
<GPOValue ValueA="7" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Netlogon\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>RestrictNTLMInDomain</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\RestrictNTLMInDomain" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="198" ID="{12be7e2c-242d-4b65-b48d-19732c753cb5}" OriginalSettingID="{6e48c65a-e5dd-4d64-a6e9-dfd86742f91e}" Name="Network security: LDAP client signing requirements" LockdownDate="2011-05-02T01:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9768-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines the level of data signing that is requested on behalf of clients that issue LDAP BIND requests.</ShortDescription>
<FullDescription>This policy setting determines the level of data signing that is requested on behalf of clients that issue LDAP BIND requests, as follows:
• None. The LDAP BIND request is issued with the caller-specified options.
• Negotiate signing. If Transport Layer Security/Secure Sockets Layer (TLS/SSL) has not been started, the LDAP BIND request is initiated with the LDAP data signing option set in addition to the caller-specified options. If TLS/SSL has been started, the LDAP BIND request is initiated with the caller-specified options.
• Require signature. This level is the same as Negotiate signing. However, if the LDAP server’s intermediate saslBindInProgress response does not indicate that LDAP traffic signing is required, the caller is told that the LDAP BIND command request failed.
Note: This policy setting does not have any impact on ldap_simple_bind or ldap_simple_bind_s. No Microsoft LDAP clients that are included with Windows XP Professional use ldap_simple_bind or ldap_simple_bind_s to communicate with a domain controller.
The possible values for the Network security: LDAP client signing requirements setting are:
• None
• Negotiate signing
• Require signature
• Not Defined
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Negotiate signing</DefaultValue>
<Vulnerability>Unsigned network traffic is susceptible to man-in-the-middle attacks in which an intruder captures the packets between the client and server, modifies them, and then forwards them to the server. For an LDAP server, this susceptibility means that an attacker could cause a server to make decisions that are based on false or altered data from the LDAP queries. To lower this risk in your network, you can implement strong physical security measures to protect the network infrastructure. Also, you can make all types of man-in-the-middle attacks extremely difficult if you require digital signatures on all network packets by means of IPsec authentication headers.</Vulnerability>
<Countermeasure>Configure the Network Security: LDAP server signing requirements setting to Require signature.</Countermeasure>
<PotentialImpact>If you configure the server to require LDAP signatures you must also configure the client. If you do not configure the client it will not be able to communicate with the server, which could cause many features to fail, including user authentication, Group Policy, and logon scripts. </PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Negotiate signing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="None">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Negotiate signing">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Require signature">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LDAP</mssasc-core:KeyPath>
<mssasc-core:ValueName>LDAPClientIntegrity</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LDAP\LDAPClientIntegrity" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:98" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="199" ID="{0fc438da-9248-4f6b-9850-6d87df1e23bc}" OriginalSettingID="{107f578e-ad55-4bf9-b108-a6477bb35892}" Name="Network access: Allow anonymous SID/Name translation" LockdownDate="2011-06-02T12:12:36Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9531-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether an anonymous user can request security identifier (SID) attributes for another user, or use a SID to obtain its corresponding user name. </ShortDescription>
<FullDescription>This policy setting determines whether an anonymous user can request security identifier (SID) attributes for another user, or use a SID to obtain its corresponding user name. Disable this policy setting to prevent unauthenticated users from obtaining user names that are associated with their respective SIDs.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>If this policy setting is enabled, a user with local access could use the well-known Administrator's SID to learn the real name of the built-in Administrator account, even if it has been renamed. That person could then use the account name to initiate a password guessing attack.</Vulnerability>
<Countermeasure>Configure the Network access: Allow anonymous SID/Name translation setting to Disabled.</Countermeasure>
<PotentialImpact>Disabled is the default configuration for this policy setting on member computers; therefore it will have no impact on them. The default configuration for domain controllers is Enabled. If you disable this policy setting on domain controllers, legacy computers may be unable to communicate with Windows Server 2003–based domains. For example, the following computers may not work:
• Windows NT 4.0–based Remote Access Service servers.
• Microsoft SQL Servers™ that run on Windows NT 3.x–based or Windows NT 4.0–based computers.
• Remote Access Service or Microsoft SQL servers that run on Windows 2000–based computers and are located in Windows NT 3.x domains or Windows NT 4.0 domains.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="False" />
<SCAPValue ValueA="False" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="True" />
<SCAPValue ValueA="True" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="WMI" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_SecuritySettingBoolean</mssasc-core:Class>
<mssasc-core:Property>Setting</mssasc-core:Property>
<mssasc-core:Where>KeyName='LSAAnonymousNameLookup' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="System Access" Name="LSAAnonymousNameLookup" DataType="WMI_Boolean" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="200" ID="{09a43a14-05fe-4857-a63d-fb577d6d8152}" OriginalSettingID="{aadb8b38-715d-470b-b67c-b2158ac6c9f7}" Name="Set client connection encryption level" LockdownDate="2011-10-12T11:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9764-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting specifies whether the computer that is about to host the remote connection will enforce an encryption level for all data sent between it and the client computer for the remote session.</ShortDescription>
<FullDescription>This policy setting specifies whether the computer that is about to host the remote connection will enforce an encryption level for all data sent between it and the client computer for the remote session.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security</UIPath>
<DefaultValue>Not configured</DefaultValue>
<Vulnerability>If Terminal Server client connections are allowed that use low level encryption, it is more likely that an attacker will be able to decrypt any captured Terminal Services network traffic.</Vulnerability>
<Countermeasure>Configure the Set Client Connection Encryption Level setting to High Level.</Countermeasure>
<PotentialImpact>Clients that do not support 128-bit encryption will be unable to establish Terminal Server sessions.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine" />
<DataType>String</DataType>
</DiscoveryInfo>
<policy name="TS_ENCRYPTION_POLICY" class="Machine" displayName="$(string.b7bc07d2602046d5a0b3fd5f76d52ebb)" explainText="$(string.4b5062d86bc0427f9022d64844830089)" presentation="$(presentation.TS_ENCRYPTION_POLICY)" key="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:elements xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:enum id="TS_ENCRYPTION_LEVEL" key="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" valueName="MinEncryptionLevel">
<admx:item displayName="$(string.addadd00f1e84c428e3a31453e977b33)">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.3f1bae5744b4428c992fe4812eb974f8)">
<admx:value>
<admx:decimal value="2" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.c7c2c16080314e20b138a74cb1e8b1dd)">
<admx:value>
<admx:decimal value="3" />
</admx:value>
</admx:item>
</admx:enum>
</admx:elements>
</policy>
<ADMLDefinition>
<presentation id="TS_ENCRYPTION_POLICY">
<admx:dropdownList refId="TS_ENCRYPTION_LEVEL" defaultItem="1" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Encryption Level</admx:dropdownList>
<admx:text xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Choose the encryption level from the drop-down list.</admx:text>
</presentation>
<string id="b7bc07d2602046d5a0b3fd5f76d52ebb">Set client connection encryption level</string>
<string id="4b5062d86bc0427f9022d64844830089">This policy setting specifies whether the computer that is about to host the remote connection will enforce an encryption level for all data sent between it and the client computer for the remote session.</string>
<string id="addadd00f1e84c428e3a31453e977b33">Low Level</string>
<string id="3f1bae5744b4428c992fe4812eb974f8">Client Compatible</string>
<string id="c7c2c16080314e20b138a74cb1e8b1dd">High Level</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional or Windows Server 2003 family</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="oval:com.secure-elements.oval:def:6600" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="201" ID="{cc756843-7c32-4d11-8e35-a84ce3a1ae59}" OriginalSettingID="{1c96e719-94c8-4333-9165-6efb6a9c6210}" Name="Microsoft network server: Digitally sign communications (if client agrees)" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8825-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines if the server side SMB service is able to sign SMB packets if it is requested to do so by a client that attempts to establish a connection. </ShortDescription>
<FullDescription>This policy setting determines if the server side SMB service is able to sign SMB packets if it is requested to do so by a client that attempts to establish a connection. If no signing request comes from the client, a connection will be allowed without a signature if the Microsoft network server: Digitally sign communications (always) setting is not enabled.
Note Enable this policy setting on SMB clients on your network to make them fully effective for packet signing with all clients and servers in your environment.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Session hijacking uses tools that allow attackers who have access to the same network as the client or server to interrupt, end, or steal a session in progress. Attackers can potentially intercept and modify unsigned SMB packets and then modify the traffic and forward it so that the server might perform undesirable actions. Alternatively, the attacker could pose as the server or client after legitimate authentication and gain unauthorized access to data.
SMB is the resource sharing protocol that is supported by many Windows operating systems. It is the basis of NetBIOS and many other protocols. SMB signatures authenticate both users and the servers that host the data. If either side fails the authentication process, data transmission will not take place.
</Vulnerability>
<Countermeasure>Configure the settings as follows:
• Disable Microsoft Network Client: Digitally Sign Communications (Always).
• Disable Microsoft Network Server: Digitally Sign Communications (Always).
• Microsoft Network Client: Digitally Sign \Communications (If Server Agrees) to Enabled.
• Microsoft Network Server: Digitally Sign Communications (If Client Agrees) to Enabled.
In highly secure environments we recommend that you configure all of these settings to Enabled. However, that configuration may cause slower performance on client computers and prevent communications with earlier SMB applications and operating systems.
Note
An alternative countermeasure that could protect all network traffic would be to implement digital signatures with Internet Protocol security (IPsec). There are hardware-based accelerators for IPsec encryption and signing that could be used to minimize the performance impact on the servers’ CPUs. No such accelerators are available for SMB signing.
</Countermeasure>
<PotentialImpact>The Windows 2000 Server, Windows 2000 Professional, Windows Server 2003, Windows XP Professional and Windows Vista implementations of the SMB file and print sharing protocol support mutual authentication, which prevents session hijacking attacks and supports message authentication to prevent man-in-the-middle attacks. SMB signing provides this authentication by placing a digital signature into each SMB, which is then verified by both the client and the server.
Implementation of SMB signing may negatively affect performance, because each packet needs to be signed and verified. If these settings are enabled on a server that is performing multiple roles, such as a small business server that is serving as a domain controller, file server, print server, and application server performance may be substantially slowed. Additionally, if you configure computers to ignore all unsigned SMB communications, older applications and operating systems will not be able to connect. However, if you completely disable all SMB signing, computers will be vulnerable to session hijacking attacks.
When SMB signing policies are enabled on domain controllers running Windows Server 2003 and member computers running Windows Vista SP1 or Windows Server 2008 group policy processing will fail. A hotfix is available from Microsoft that resolves this issue; see Microsoft Knowledgebase Article 950876 for more details: http://support.microsoft.com/default.aspx/kb/950876/.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanManServer\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>enablesecuritysignature</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\enablesecuritysignature" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:85" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="202" ID="{d8f7d3e9-c767-4d9e-8f2b-b38c44780bf2}" OriginalSettingID="{21e5ee29-51b2-4719-b979-af03e47a128e}" Name="MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)" LockdownDate="2011-05-22T06:25:35Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9496-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The entry appears as MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing) in the SCE.</ShortDescription>
<FullDescription>The registry value entry DisableIPSourceRouting was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\ registry key. The entry appears as MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing) in the SCE.
IP source routing is a mechanism that allows the sender to determine the IP route that a datagram should take through the network. Microsoft recommends to configure this setting to Not Defined for enterprise environments and to Highest Protection for high security environments to completely disable source routing.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not Defined</DefaultValue>
<Vulnerability>An attacker could use source routed packets to obscure their identity and location. Source routing allows a computer that sends a packet to specify the route that the packet takes.</Vulnerability>
<Countermeasure>Configure the MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing) entry to a value of Highest protection, source routing is completely disabled.
The possible values for this registry entry are:
• 0, 1, or 2. The default configuration is 1 (source routed packets are not forwarded).
In the SCE UI, the following list of options appears:
• No additional protection, source routed packets are allowed.
• Medium, source routed packets ignored when IP forwarding is enabled.
• Highest protection, source routing is completely disabled.
• Not Defined.</Countermeasure>
<PotentialImpact>If you configure this value to 2, all incoming source routed packets will be dropped.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Highest protection, source routing is completely disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="No additional protection, source routed packets are allowed">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Medium, source routed packets ignored when IP forwarding is enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Highest protection, source routing is completely disabled">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Tcpip\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableIPSourceRouting</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\DisableIPSourceRouting" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:111" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="203" ID="{00a154a4-682f-4e15-a548-eb63ce62e039}" OriginalSettingID="{d6de5004-d736-43b1-b965-3e63440bf4b1}" Name="Network Security: Restrict NTLM: Audit Incoming NTLM Traffic" LockdownDate="2011-05-02T01:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9340-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to audit incoming NTLM traffic.</ShortDescription>
<FullDescription>This policy setting allows you to audit incoming NTLM traffic.
This policy is supported on at least Windows 7 or Windows Server 2008 R2.
Note: Audit events are recorded on this computer in the "Operational" Log located under the Applications and Services Log/Microsoft/Windows/NTLM.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>NTLM is a Microsoft-developed authentication protocol that uses a challenge-response mechanism for authentication, in which client computers can prove their identities without sending a password to the server. The protocol employs three types of messages to negotiate the request, challenge the authenticity of the sender, and perform the authentication. Kerberos is a more robust protocol and is the preferred method of authentication when available. </Vulnerability>
<Countermeasure>When you need to audit NTLM use configure Network Security: Restrict NTLM: Audit Incoming NTLM Traffic to "Enable auditing for domain accounts" or "Enable auditing for all accounts" as appropriate for your environment.</Countermeasure>
<PotentialImpact>If you select "Disable", or do not configure this policy setting, the server will not log events for incoming NTLM traffic.
If you select "Enable auditing for domain accounts", the server will log events for NTLM pass-through authentication requests that would be blocked when the "Network Security: Restrict NTLM: Incoming NTLM traffic" policy setting is set to the "Deny all domain accounts" option.
If you select "Enable auditing for all accounts", the server will log events for all NTLM authentication requests that would be blocked when the "Network Security: Restrict NTLM: Incoming NTLM traffic" policy setting is set to the "Deny all accounts" option.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disable">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enable auditing for domain accounts">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Enable auditing for all accounts">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa\MSV1_0</mssasc-core:KeyPath>
<mssasc-core:ValueName>AuditReceivingNTLMTraffic</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0\AuditReceivingNTLMTraffic" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="204" ID="{2c26183e-a136-4f39-b229-5a2f868104ab}" OriginalSettingID="{4d558e02-b2d3-44bf-928a-17fba6a3af45}" Name="MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers" LockdownDate="2011-06-01T01:16:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8562-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The registry value entry appears as MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers in the SCE.</ShortDescription>
<FullDescription>The registry value entry NoNameReleaseOnDemand was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netbt\
Parameters\ registry key. The entry appears as MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers in the SCE.
NetBIOS over TCP/IP is a network protocol that among other things provides a way to easily resolve NetBIOS names that are registered on Windows–based systems to the IP addresses that are configured on those systems. This setting determines whether the computer releases its NetBIOS name when it receives a name-release request.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not Defined</DefaultValue>
<Vulnerability>The NetBT protocol is designed not to use authentication, and is therefore vulnerable to spoofing. Spoofing makes a transmission appear to come from a user other than the user who performed the action. A malicious user could exploit the unauthenticated nature of the protocol to send a name-conflict datagram to a target computer, which would cause the computer to relinquish its name and not respond to queries.
The result of such an attack could be to cause intermittent connectivity issues on the target computer, or even to prevent the use of Network Neighborhood, domain logons, the NET SEND command, or additional NetBIOS name resolution.
For more information, see the Microsoft Knowledge Base article "MS00-047: NetBIOS Vulnerability May Cause Duplicate Name on the Network Conflicts" at http://support.microsoft.com/default.aspx?kbid=269239.
</Vulnerability>
<Countermeasure>Configure the MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers (Only recommended for servers) entry to a value of Enabled.
The possible values for this registry entry are:
• 1 or 0. The default configuration is 1 (enabled).
In the SCE UI, these options appear as:
• Enabled
• Disabled
• Not Defined
Alternatively, you could disable the use of WINS in your environment, and further ensure that all applications rely upon DNS for name resolution services. Although this approach is a recommended long-term strategy, it is generally impractical for most organizations to attempt as a short-term solution. Organizations that still run WINS generally have application dependencies that cannot be quickly resolved without upgrades and software rollouts, which require careful plans and significant time commitments.
If you cannot deploy this countermeasure and you want to guarantee NetBIOS name resolution, you can take the additional step of "pre-loading" NetBIOS names in the LMHOSTS file on certain computers. For more information about how to pre-load the LMHOSTS file, see the Microsoft Knowledge Base article "MS00-047: NetBIOS Vulnerability May Cause Duplicate Name on the Network Conflicts" that was referenced earlier in this section.
Note: Maintenance of LMHOSTS files in most environments requires a significant amount of effort. Microsoft encourages the use of WINS instead of LMHOSTS.
</Countermeasure>
<PotentialImpact>An attacker could send a request over the network and query a computer to release its NetBIOS name. As with any change that could affect applications, Microsoft recommends that you test this change in a non-production environment before you change the production environment.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Netbt\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>NoNameReleaseOnDemand</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Netbt\Parameters\NoNameReleaseOnDemand" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:118" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="205" ID="{4414146f-11e4-4afc-bbfa-314e2795c05d}" OriginalSettingID="{62b84be3-b449-45f8-aaa1-a239eeee8400}" Name="Restrictions for Unauthenticated RPC clients" LockdownDate="2011-10-12T11:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9396-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting configures the RPC Runtime on an RPC server to restrict unauthenticated RPC clients from connecting to the RPC server. </ShortDescription>
<FullDescription>This policy setting configures the RPC Runtime on an RPC server to restrict unauthenticated RPC clients from connecting to the RPC server. A client will be considered an authenticated client if it uses a named pipe to communicate with the server or if it uses RPC Security. RPC interfaces that have specifically asked to be accessible by unauthenticated clients may be exempt from this restriction, depending on the selected value for this policy.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Remote Procedure Call</UIPath>
<DefaultValue>Not configured</DefaultValue>
<Vulnerability>Unauthenticated RPC communication can create a security vulnerability.</Vulnerability>
<Countermeasure> If you enable this policy setting, the following values are available:
• None. Allows all RPC clients to connect to RPC servers that run on the computer on which the policy is applied.
• Authenticated. Allows only authenticated RPC clients to connect to RPC servers that run on the computer on which the policy is applied. Interfaces that have asked to be exempt from this restriction will be granted an exemption.
• Authenticated without exceptions. Allows only authenticated RPC clients to connect to RPC servers that run on the computer on which the policy is applied. No exceptions are allowed.</Countermeasure>
<PotentialImpact>RPC applications that do not authenticate unsolicited inbound connection requests may not work properly when this configuration is applied. Ensure you test applications before you deploy this policy setting throughout your environment. Although the Authenticated value for this policy setting is not completely secure, it can be useful for providing application compatibility in your environment.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine" />
<DataType>String</DataType>
</DiscoveryInfo>
<policy name="RpcRestrictRemoteClients" class="Machine" displayName="$(string.11c98da2d9be428fac99cbf327093aab)" explainText="$(string.9fd762312d0a475abef25477b9494e5b)" presentation="$(presentation.RpcRestrictRemoteClients)" key="Software\Policies\Microsoft\Windows NT\Rpc">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:elements xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:enum id="RpcRestrictRemoteClientsList" key="Software\Policies\Microsoft\Windows NT\Rpc" valueName="RestrictRemoteClients">
<admx:item displayName="$(string.9fe9074ff7b64960b02ffb0414f387f6)">
<admx:value>
<admx:decimal value="0" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.e6744bcc94c84ce7b9eee9a979b2d36c)">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.82f7c08352974eb59776fe406e6f6a6a)">
<admx:value>
<admx:decimal value="2" />
</admx:value>
</admx:item>
</admx:enum>
</admx:elements>
</policy>
<ADMLDefinition>
<presentation id="RpcRestrictRemoteClients">
<admx:dropdownList refId="RpcRestrictRemoteClientsList" defaultItem="1" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">RPC Runtime Unauthenticated Client Restriction to Apply:</admx:dropdownList>
</presentation>
<string id="11c98da2d9be428fac99cbf327093aab">Restrictions for Unauthenticated RPC clients</string>
<string id="9fd762312d0a475abef25477b9494e5b">This policy setting configures the RPC Runtime on an RPC server to restrict unauthenticated RPC clients from connecting to the RPC server. A client will be considered an authenticated client if it uses a named pipe to communicate with the server or if it uses RPC Security. RPC interfaces that have specifically asked to be accessible by unauthenticated clients may be exempt from this restriction, depending on the selected value for this policy.</string>
<string id="9fe9074ff7b64960b02ffb0414f387f6">None</string>
<string id="e6744bcc94c84ce7b9eee9a979b2d36c">Authenticated</string>
<string id="82f7c08352974eb59776fe406e6f6a6a">Authenticated without exceptions</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional with SP2</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="206" ID="{e3ef6df9-606f-448a-bdda-983541e66709}" OriginalSettingID="{7ab7ae06-f9bd-4252-a282-8fd3a06a73df}" Name="Domain member: Digitally sign secure channel data (when possible)" LockdownDate="2011-06-21T02:57:00Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9375-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether a domain member should attempt to negotiate whether all secure channel traffic that it initiates must be digitally signed.</ShortDescription>
<FullDescription>This policy setting determines whether a domain member should attempt to negotiate whether all secure channel traffic that it initiates must be digitally signed. Digital signatures protect the traffic from being modified by anyone who captures the data as it traverses the network.
Microsoft recommends to configure the Domain member: Digitally sign secure channel data (when possible) setting to Enabled.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>When a computer joins a domain, a computer account is created. After it joins the domain, the computer uses the password for that account to create a secure channel with the domain controller for its domain every time that it restarts. Requests that are sent on the secure channel are authenticated—and sensitive information such as passwords are encrypted—but the channel is not integrity-checked, and not all information is encrypted. If a computer is configured to always encrypt or sign secure channel data but the domain controller cannot sign or encrypt any portion of the secure channel data, the computer and domain controller cannot establish a secure channel. If the computer is configured to encrypt or sign secure channel data when possible, a secure channel can be established, but the level of encryption and signing is negotiated.</Vulnerability>
<Countermeasure>• Enable the Domain member: Digitally encrypt or sign secure channel data (always) setting.
• Enable the Domain member: Digitally encrypt secure channel data (when possible) setting.
• Enable the Domain member: Digitally sign secure channel data (when possible) setting.
</Countermeasure>
<PotentialImpact>Digital encryption and signing of the “secure channel” is a good idea where it is supported. The secure channel protects domain credentials as they are sent to the domain controller. However, only Windows NT 4.0 with Service Pack 6a (SP6a) and subsequent versions of the Windows operating system support digital encryption and signing of the secure channel. Windows 98 Second Edition clients do not support it unless they have the Dsclient installed. Therefore, you cannot enable the Domain member: Digitally encrypt or sign secure channel data (always) setting on domain controllers that support Windows 98 clients as members of the domain. Potential impacts can include the following:
• The ability to create or delete trust relationships with clients running versions of Windows earlier than Windows NT 4.0 with SP6a will be disabled.
• Logons from clients running versions of Windows earlier than Windows NT 4.0 with SP6a will be disabled.
• The ability to authenticate other domains’ users from a domain controller running a version of Windows earlier than Windows NT 4.0 with SP6a in a trusted domain will be disabled.
You can enable this policy setting after you eliminate all Windows 9x clients from the domain and upgrade all Windows NT 4.0 servers and domain controllers from trusted/trusting domains to Windows NT 4.0 with SP6a. You can enable the other two policy settings, Domain member: Digitally encrypt secure channel data (when possible) and Domain member: Digitally encrypt sign channel data (when possible), on all computers in the domain that support them and clients running versions of Windows earlier than Windows NT 4.0 with SP6a and applications that run on these versions of Windows will not be affected.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\Netlogon\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>signsecurechannel</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\signsecurechannel" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="207" ID="{df35bbb2-b762-4a25-a841-5d64ed7268a3}" OriginalSettingID="{9c88cdfc-58ad-4666-9e8a-d84099d42fdd}" Name="Network access: Remotely accessible registry paths and sub-paths" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9386-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which registry paths and sub-paths will be accessible when an application or process references the WinReg key to determine access permissions.</ShortDescription>
<FullDescription>This policy setting determines which registry paths and sub-paths will be accessible when an application or process references the WinReg key to determine access permissions.
Note: In Windows XP this setting is called "Network access: Remotely accessible registry paths," the setting with that same name in Windows Vista, Windows Server 2008, and Windows Server 2003 does not exist in Windows XP.
Note: When you configure this setting you specify a list of one or more objects. The delimiter used when entering the list is a line feed or carriage return, that is, type the first object on the list, press the Enter button, type the next object, press Enter again, etc. The setting value is stored as a comma-delimited list in group policy security templates. It is also rendered as a comma-delimited list in Group Policy Editor’s display pane and the Resultant Set of Policy console. It is recorded in the registry as a line-feed delimited list in a REG_MULTI_SZ value.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>System\CurrentControlSet\Control\Print\Printers,System\CurrentControlSet\Services\Eventlog,Software\Microsoft\OLAP Server,Software\Microsoft\Windows NT\CurrentVersion\Print,Software\Microsoft\Windows NT\CurrentVersion\Windows,System\CurrentControlSet\Control\ContentIndex,System\CurrentControlSet\Control\Terminal Server,System\CurrentControlSet\Control\Terminal Server\UserConfig,System\CurrentControlSet\Control\Terminal Server\DefaultUserConfiguration,Software\Microsoft\Windows NT\CurrentVersion\Perflib,System\CurrentControlSet\Services\SysmonLog
</DefaultValue>
<Vulnerability>The registry contains sensitive computer configuration information that could be used by an attacker to facilitate unauthorized activities. The fact that the default ACLs assigned throughout the registry are fairly restrictive and help to protect the registry from access by unauthorized users reduces the risk of such an attack.</Vulnerability>
<Countermeasure>Configure the Network access: Remotely accessible registry paths and sub-paths setting to a null value (enable the setting but do not enter any paths in the text box). </Countermeasure>
<PotentialImpact>Remote management tools such as the Microsoft Baseline Security Analyzer and Microsoft Systems Management Server require remote access to the registry to properly monitor and manage those computers. If you remove the default registry paths from the list of accessible ones, such remote management tools could fail.
Note: If you want to allow remote access, you must also enable the Remote Registry service.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_MULTI_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\SecurePipeServers\Winreg\AllowedPaths</mssasc-core:KeyPath>
<mssasc-core:ValueName>Machine</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Multi-String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\SecurePipeServers\Winreg\AllowedPaths\Machine" DataType="REG_MULTI_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="208" ID="{ca8523ec-b32d-4cb0-bac4-9dfa139c0928}" OriginalSettingID="{52a525a6-fa54-4d78-9f6c-8ceb8f5e91aa}" Name="RPC Endpoint Mapper Client Authentication" LockdownDate="2011-10-12T11:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10181-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows client computers that communicate with this computer to be forced to provide authentication before an RPC communication is established.</ShortDescription>
<FullDescription>If you enable this policy setting, client computers that communicate with this computer are forced to provide authentication before RPC communication can be established. By default, RPC clients do not use authentication to communicate with the RPC Server Endpoint Mapper Service when they request the endpoint of a server.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Remote Procedure Call</UIPath>
<DefaultValue>Not configured</DefaultValue>
<Vulnerability>Anonymous access to RPC services could result in accidental disclosure of information to unauthenticated users.</Vulnerability>
<Countermeasure>Implement this setting</Countermeasure>
<PotentialImpact>RPC clients will be forced to authenticate before they can begin communicating with the desired RPC service, this means that anonymous access will not be available and RPC clients that do not support authentication will fail.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows NT\Rpc</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnableAuthEpResolution</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="RpcEnableAuthEpResolution" class="Machine" displayName="$(string.26fb9d15d31844ada00b190c23bdf3c6)" explainText="$(string.08eb3e75a08b4d3793d621d5b7d9d45e)" key="Software\Policies\Microsoft\Windows NT\Rpc" valueName="EnableAuthEpResolution">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="26fb9d15d31844ada00b190c23bdf3c6">RPC Endpoint Mapper Client Authentication</string>
<string id="08eb3e75a08b4d3793d621d5b7d9d45e">If you enable this policy setting, client computers that communicate with this computer are forced to provide authentication before RPC communication can be established. By default, RPC clients do not use authentication to communicate with the RPC Server Endpoint Mapper Service when they request the endpoint of a server.</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional with SP2</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="209" ID="{f0ff568e-3ac8-4b30-8ce1-64886c761bcc}" OriginalSettingID="{fbfb6cc4-d294-4884-bc3d-7f74deeb6462}" Name="Network access: Do not allow anonymous enumeration of SAM accounts and shares" LockdownDate="2011-05-02T01:36:03Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9156-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting controls the ability of anonymous users to enumerate SAM accounts as well as shares.</ShortDescription>
<FullDescription>This policy setting controls the ability of anonymous users to enumerate SAM accounts as well as shares. If you enable this policy setting, anonymous users will not be able to enumerate domain account user names and network share names on the workstations in your environment.
The Network access: Do not allow anonymous enumeration of SAM accounts and shares setting is configured to Enabled for the two environments that are discussed in this guide.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>An unauthorized user could anonymously list account names and shared resources and use the information to attempt to guess passwords or perform social engineering attacks.</Vulnerability>
<Countermeasure>Configure the Network access: Do not allow anonymous enumeration of SAM accounts and shares setting to Enabled. </Countermeasure>
<PotentialImpact>It will be impossible to grant access to users of another domain across a one-way trust because administrators in the trusting domain will be unable to enumerate lists of accounts in the other domain. Users who access file and print servers anonymously will be unable to list the shared network resources on those servers; the users will have to authenticate before they can view the lists of shared folders and printers.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>RestrictAnonymous</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\RestrictAnonymous" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:88" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="210" ID="{90264ed6-4875-4baa-829a-c07f99e0981d}" OriginalSettingID="{ab05b768-9c4c-4ff7-a22b-45af430607a8}" Name="Network access: Remotely accessible registry paths" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9121-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which registry paths will be accessible after referencing the WinReg key to determine access permissions to the paths.</ShortDescription>
<FullDescription>This policy setting determines which registry paths will be accessible after referencing the WinReg key to determine access permissions to the paths.
Note: This setting does not exist in Windows XP. There was a setting with that name in Windows XP, but it is called "Network access: Remotely accessible registry paths and subpaths" in Windows Server 2003, Windows Vista, and Windows Server 2008.
Note: When you configure this setting you specify a list of one or more objects. The delimiter used when entering the list is a line feed or carriage return, that is, type the first object on the list, press the Enter button, type the next object, press Enter again, etc. The setting value is stored as a comma-delimited list in group policy security templates. It is also rendered as a comma-delimited list in Group Policy Editor’s display pane and the Resultant Set of Policy console. It is recorded in the registry as a line-feed delimited list in a REG_MULTI_SZ value.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>System\CurrentControlSet\Control\ProductOptions,System\CurrentControlSet\Control\Server Applications,Software\Microsoft\Windows NT\CurrentVersion
</DefaultValue>
<Vulnerability>The registry is a database that contains computer configuration information, and much of the information is sensitive. An attacker could use this information to facilitate unauthorized activities. To reduce the risk of such an attack, suitable ACLs are assigned throughout the registry to help protect it from access by unauthorized users.</Vulnerability>
<Countermeasure>Configure the Network access: Remotely accessible registry paths setting to a null value (enable the setting but do not enter any paths in the text box).</Countermeasure>
<PotentialImpact>Remote management tools such as the Microsoft Baseline Security Analyzer and Microsoft Systems Management Server require remote access to the registry to properly monitor and manage those computers. If you remove the default registry paths from the list of accessible ones, such remote management tools could fail.
Note: If you want to allow remote access, you must also enable the Remote Registry service.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_MULTI_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\SecurePipeServers\Winreg\AllowedExactPaths</mssasc-core:KeyPath>
<mssasc-core:ValueName>Machine</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Multi-String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\SecurePipeServers\Winreg\AllowedExactPaths\Machine" DataType="REG_MULTI_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:92" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="211" ID="{20b8331f-728f-4cd3-bc19-08edd4ba2076}" OriginalSettingID="{c425f126-29a9-4e35-b20b-532e4428c96f}" Name="Network Security: Configure encryption types allowed for Kerberos" LockdownDate="2011-05-02T01:36:03Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9532-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to set the encryption types that Kerberos is allowed to use.</ShortDescription>
<FullDescription>This policy setting allows you to set the encryption types that Kerberos is allowed to use.
This policy is supported on at least Windows 7 or Windows Server 2008 R2.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>The strength of each encryption algorithm varies from one to the next, choosing stronger algorithms will reduce the risk of compromise however doing so may cause issues when the computer attempts to authenticate with systems that do not support them.</Vulnerability>
<Countermeasure>Restrict the allowed encryption types to match your organization's policies.</Countermeasure>
<PotentialImpact>If not selected, the encryption type will not be allowed. This setting may affect compatibility with client computers or services and applications. Multiple selections are permitted.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="9999">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>SupportedEncryptionTypes</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\SupportedEncryptionTypes" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Comment>
</Comment>
</SettingGroup>
<SettingGroup ID="{8f5c59a1-9529-44ca-bff2-cc24a67d2709}" Name="Least Functionality" OriginalSettingGroupID="{ba5e521a-c23d-45e2-8949-f69a5673d92e}">
<mssasc-core:Description>
</mssasc-core:Description>
<mssasc-core:Version Major="1" Minor="0" />
<Author>
</Author>
<Setting Index="212" ID="{b305aabb-a23d-4cab-8ed2-24d913595b24}" OriginalSettingID="{40ff3a18-ba1a-4d06-bb5f-f6ffaf35026a}" Name="DCOM: Machine Launch Restrictions in Security Descriptor Definition Language (SDDL) syntax" LockdownDate="2011-05-02T01:36:00Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8525-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which users or groups might launch or activate DCOM applications remotely or locally.</ShortDescription>
<FullDescription>This policy setting determines which users or groups might launch or activate DCOM applications remotely or locally. This setting is used to control the attack surface of the computer for DCOM applications.
You can use this Group Policy setting to grant access to all the computers to particular users for DCOM application in the enterprise. When you define this setting, and specify the users or groups that are to be given permission, the security descriptor field is populated with the Security Descriptor Definition Language representation of those groups and privileges. If the security descriptor is left blank, the policy setting is defined in the template, but it is not enforced. Users and groups can be given explicit Allow or Deny privileges on local launch, remote launch, local activation, and remote activation.
The registry settings that are created as a result of this policy take precedence over the previous registry settings in this area. RpcSs checks the new registry keys in the Policies section for the computer restrictions; these entries take precedence over the existing registry keys under OLE.
The possible values for this Group Policy setting are:
Blank. This represents the local security policy way of deleting the policy enforcement key. This value deletes the policy and then sets it to Not defined state. The Blank value is set by using the ACL editor and emptying the list, and then pressing OK.
SDDL. This is the Security Descriptor Definition Language representation of the groups and privileges you specify when you enable this policy.
Not Defined. This is the default value.
Note
If the administrator is denied access to activate and launch DCOM applications due to the changes made to DCOM in SP2, this policy setting can be used for controlling the DCOM activation and launch to the computer. The administrator can specify which users and groups can launch and activate DCOM applications on the computer both locally and remotely by using the DCOM: Machine Launch Restrictions in Security Descriptor Definition Language (SDDL) syntax policy setting. This restores control of the DCOM application to the administrator and specified users. To do this, open the DCOM: Machine Launch Restrictions in Security Descriptor Definition Language (SDDL) syntax setting, and click Edit Security. Specify the groups you want to include and the computer launch permissions for those groups. This defines the setting and sets the appropriate SDDL value.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>Many COM applications include some security-specific code (for example, to call CoInitializeSecurity) but use weak settings that often allow unauthenticated access to the process. Administrators cannot override these settings to force stronger security in earlier versions of Windows without modifying the application. An attacker could attempt to exploit weak security in an individual application by attacking it through COM calls.
Also, COM infrastructure includes the RPCSS, a system service that runs during computer startup and always runs after that. This service manages activation of COM objects and the running object table and provides helper services to DCOM remoting. It exposes RPC interfaces that can be called remotely. Because some COM servers allow unauthenticated remote component activation
</Vulnerability>
<Countermeasure>To protect individual COM-based applications or services, set this policy setting to an appropriate computer-wide ACL. The syntax for SDDL is documented here: http://msdn.microsoft.com/en-us/library/aa379567(VS.85).aspx</Countermeasure>
<PotentialImpact>Windows operating systems implement default COM ACLs when they are installed. Modifying these ACLs from the default may cause some applications to components that communicate by using DCOM to fail. If you implement a COM server and you override the default security settings, confirm that the application-specific launch permissions ACL assigns activation permission to appropriate users. If it does not, you need to change your application-specific launch permission ACL to provide appropriate users with activation rights so that applications and Windows components that use DCOM do not fail.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\policies\Microsoft\windows NT\DCOM</mssasc-core:KeyPath>
<mssasc-core:ValueName>MachineLaunchRestriction</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="Software\Policies\Microsoft\Windows NT\DCOM\MachineLaunchRestriction" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="213" ID="{1dee17e2-5c53-458f-9f20-a7c0e3cdb052}" OriginalSettingID="{c448dca7-3cd1-4f0c-a917-97359a612b72}" Name="System settings: Optional subsystems" LockdownDate="2011-05-15T05:26:31Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9579-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which subsystems are used to support applications in your environment.</ShortDescription>
<FullDescription>This policy setting determines which subsystems are used to support applications in your environment.
Note: When you configure this setting you specify a list of one or more objects. The delimiter used when entering the list is a line feed or carriage return, that is, type the first object on the list, press the Enter button, type the next object, press Enter again, etc. The setting value is stored as a comma-delimited list in group policy security templates. It is also rendered as a comma-delimited list in Group Policy Editor’s display pane and the Resultant Set of Policy console. It is recorded in the registry as a line-feed delimited list in a REG_MULTI_SZ value.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Posix</DefaultValue>
<Vulnerability>The POSIX subsystem is an Institute of Electrical and Electronic Engineers (IEEE) standard that defines a set of operating system services. The POSIX subsystem is required if the server supports applications that use that subsystem.
The POSIX subsystem introduces a security risk that relates to processes that can potentially persist across logons. If a user starts a process and then logs out, there is a potential that the next user who logs on to the computer could access the previous user's process. This potential is dangerous, because anything the second user does with that process will be performed with the privileges of the first user.
</Vulnerability>
<Countermeasure>Configure the System settings: Optional subsystems setting to a null value. The default value is POSIX.</Countermeasure>
<PotentialImpact>Applications that rely on the POSIX subsystem will no longer operate. For example, Microsoft Services for Unix (SFU) installs an updated version of the POSIX subsystem that is required, so you would need to reconfigure this setting in a Group Policy for any servers that use SFU.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_MULTI_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Session Manager\SubSystems</mssasc-core:KeyPath>
<mssasc-core:ValueName>optional</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Multi-String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\optional" DataType="REG_MULTI_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="214" ID="{995c4b02-75a4-49ca-ba15-ed2000b6c878}" OriginalSettingID="{b1d27dc2-b5e3-4dc5-9d3b-d634e7a25353}" Name="MSS: (AutoAdminLogon) Enable Automatic Logon (not recommended)" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9342-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The registry value entry AutoAdminLogon was added to the template file in the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ registry key</ShortDescription>
<FullDescription>The registry value entry AutoAdminLogon was added to the template file in the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ registry key. The entry appears as MSS: (AutoAdminLogon) Enable Automatic Logon (not recommended) in the Security Configuration Editor.
This setting is separate from the Welcome screen feature in Windows XP and Windows Vista; if that feature is disabled, this setting is not disabled. If you configure a computer for automatic logon, anyone who can physically gain access to the computer can also gain access to everything that is on the computer, including any network or networks to which the computer is connected. Also, if you enable automatic logon, the password is stored in the registry in plaintext, and the specific registry key that stores this value is remotely readable by the Authenticated Users group.
For additional information, see the Knowledge Base article 315231, "How to turn on automatic logon in Windows XP."
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not Defined</DefaultValue>
<Vulnerability>If you configure a computer for automatic logon, anyone who can physically gain access to the computer can also gain access to everything that is on the computer, including any network or networks that the computer is connected to. Also, if you enable automatic logon, the password is stored in the registry in plaintext. The specific registry key that stores this setting is remotely readable by the Authenticated Users group. As a result, this entry is appropriate only if the computer is physically secured and if you ensure that untrusted users cannot remotely see the registry.</Vulnerability>
<Countermeasure>Do not configure the MSS: (AutoAdminLogon) Enable Automatic Logon (not recommended) entry except on highly secure computers, where it should be configured to a value of Disabled.
The possible values for this registry entry are:
• 1 or 0. The default configuration is 0 (disabled).
In the SCE UI, these options appear as:
• Enabled
• Disabled
• Not Defined
</Countermeasure>
<PotentialImpact>None. By default this entry is not enabled.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows NT\CurrentVersion\Winlogon</mssasc-core:KeyPath>
<mssasc-core:ValueName>AutoAdminLogon</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\AutoAdminLogon" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:110" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="215" ID="{e0622d43-d847-4810-aa7a-11907a6f1790}" OriginalSettingID="{98b3f31f-6710-418d-a037-34b19be8dfa7}" Name="Turn off Search Companion content file updates" LockdownDate="2011-10-12T11:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10140-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting specifies whether Search Companion should automatically download content updates during local and Internet searches.</ShortDescription>
<FullDescription>This policy setting specifies whether Search Companion should automatically download content updates during local and Internet searches. </FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Internet Communication Management\Internet Communication settings</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>There is a small risk that users will unknowingly reveal sensitive information because of the topics they are searching for. This risk is very low because even if this setting is enabled users still must submit search queries to the desired search engine in order to perform searches.</Vulnerability>
<Countermeasure>Configure this policy setting to Enabled to prevent Search Companion from downloading content updates during searches.</Countermeasure>
<PotentialImpact>Internet searches will still send the search text and information about the search to Microsoft and the chosen search provider. If you select Classic Search, the Search Companion feature will be unavailable. You can select Classic Search by clicking Start, Search, Change Preferences, and then Change Internet Search Behavior.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\SearchCompanion</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableContentFileUpdates</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="SearchCompanion_DisableFileUpdates" class="Machine" displayName="$(string.2ea9500ccb464b20b7c8fa1316f1cd54)" explainText="$(string.c051df5586ad42b28b39afc74e88b80f)" key="Software\Policies\Microsoft\SearchCompanion" valueName="DisableContentFileUpdates">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="2ea9500ccb464b20b7c8fa1316f1cd54">Turn off Search Companion content file updates</string>
<string id="c051df5586ad42b28b39afc74e88b80f">This policy setting specifies whether Search Companion should automatically download content updates during local and Internet searches. </string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional with SP2 or Windows Server 2003 family with SP1</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="216" ID="{bcc1b6a1-4c4b-41d8-bdff-4671077603c6}" OriginalSettingID="{8ae83b84-b0fd-4b08-85a5-ff3f897a2db2}" Name="Interactive logon: Do not require CTRL+ALT+DEL" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9317-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>When this setting is configured to Enabled, users are not required to use the CTRL+ALT+DEL key combination to log on to the network.</ShortDescription>
<FullDescription>This policy setting determines whether users must press CTRL+ALT+DEL before they log on. If you enable this policy setting, users can log on without this key combination. If you disable this policy setting, users must press CTRL+ALT+DEL before they log on to Windows unless they use a smart card for Windows logon. A smart card is a tamper-proof device that stores security information.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined
</DefaultValue>
<Vulnerability>Microsoft developed this feature to make it easier for users with certain types of physical impairments to log on to computers that run Windows. If users are not required to press CTRL+ALT+DEL, they are susceptible to attacks that attempt to intercept their passwords. If CTRL+ALT+DEL is required before logon, user passwords are communicated by means of a trusted path.
An attacker could install a Trojan horse program that looks like the standard Windows logon dialog box and capture the user’s password. The attacker would then be able to log on to the compromised account with whatever level of privilege that user has.
</Vulnerability>
<Countermeasure>Configure the Disable CTRL+ALT+DEL requirement for logon setting to Disabled.</Countermeasure>
<PotentialImpact>Unless they use a smart card to log on, users will have to simultaneously press three keys before the logon dialog box will display.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableCAD</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\DisableCAD" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:69" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="217" ID="{7beff6b6-edff-4265-a24a-0f320306ecff}" OriginalSettingID="{c4f13e60-0fae-4766-bba1-00b4c33d54b7}" Name="Network access: Do not allow anonymous enumeration of SAM accounts" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9249-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting controls the ability of anonymous users to enumerate the accounts in the Security Accounts Manager (SAM).</ShortDescription>
<FullDescription>This policy setting controls the ability of anonymous users to enumerate the accounts in the Security Accounts Manager (SAM). If you enable this policy setting, users with anonymous connections cannot enumerate domain account user names on the workstations in your environment. This policy setting also allows additional restrictions on anonymous connections.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>An unauthorized user could anonymously list account names and use the information to perform social engineering attacks or attempt to guess passwords. (Social engineering attacks try to deceive users in some way to obtain passwords or some form of security information.)</Vulnerability>
<Countermeasure>Configure the Network access: Do not allow anonymous enumeration of SAM accounts setting to Enabled.</Countermeasure>
<PotentialImpact>It will be impossible to establish trusts with Windows NT 4.0–based domains. Also, client computers that run older versions of the Windows operating system such as Windows NT 3.51 and Windows 95 will experience problems when they try to use resources on the server.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>RestrictAnonymousSAM</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\RestrictAnonymousSAM" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:88" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="218" ID="{9143427d-93b2-46c0-a13e-934d1ff98dfc}" OriginalSettingID="{e7465053-fa53-4b77-bcb6-096a4f1d2dd1}" Name="Solicited Remote Assistance" LockdownDate="2011-10-12T11:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9506-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether remote assistance may be solicited from computers running Windows operating systems in your environment.</ShortDescription>
<FullDescription>This policy setting determines whether remote assistance may be solicited from computers running Windows operating systems in your environment. You can enable this policy setting to allow users to solicit remote assistance from IT "expert" administrators.
If the Solicited Remote Assistance setting is enabled, the following options are available:
• Allow helpers to remotely control the computer
• Allow helpers to only view the computer
Also, the following options are available to configure the amount of time that a user help request remains valid:
• Maximum ticket time (value):
• Maximum ticket time (units): hours, minutes or days
When a ticket (help request) expires, the user must send another request before an expert can connect to the computer. If you disable the Solicited Remote Assistance setting, users cannot send help requests and the expert cannot connect to their computers.
If the Solicited Remote Assistance setting is not configured, users can configure solicited remote assistance through the Control Panel. The following settings are enabled by default in the Control Panel: Solicited Remote Assistance, Buddy support, and Remote control. The value for the Maximum ticket time is set to 30 days. If this policy setting is disabled, no one will be able to access Windows Vista client computers across the network.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Remote Assistance</UIPath>
<DefaultValue>Not configured</DefaultValue>
<Vulnerability>There is slight risk that a rogue administrator will gain access to another user's desktop session, however, they cannot connect to a user’s computer unannounced or control it without permission from the user. When an expert tries to connect, the user can still choose to deny the connection or give the expert view-only privileges. The user must explicitly click the Yes button to allow the expert to remotely control the workstation.</Vulnerability>
<Countermeasure>Disable this setting to prevent the use of remote assistance.</Countermeasure>
<PotentialImpact>If you enable this policy, users on this computer can use e-mail or file transfer to ask someone for help. Also, users can use instant messaging programs to allow connections to this computer, and you can configure additional Remote Assistance settings.
If you disable this policy, users on this computer cannot use e-mail or file transfer to ask someone for help. Also, users cannot use instant messaging programs to allow connections to this computer.
If you don't configure this policy, users can enable or disable Solicited (Ask for) Remote Assistance themselves in System Properties in Control Panel. Users can also configure Remote Assistance settings.
If you enable this policy setting, you have two ways to allow helpers to provide Remote Assistance: "Allow helpers to only view the computer" or "Allow helpers to remotely control the computer."
The "Maximum ticket time" setting sets a limit on the amount of time that a Remote Assistance invitation created by using e-mail or file transfer can remain open.
The "Select the method for sending e-mail invitations" setting specifies which e-mail standard to use to send Remote Assistance invitations. Depending on your e-mail program, you can use either the Mailto standard (the invitation recipient connects through an Internet link) or the SMAPI (Simple MAPI) standard (the invitation is attached to your e-mail message). This setting is not available in Windows Vista since SMAPI is the only method supported.
If you enable this policy you should also enable appropriate firewall exceptions to allow Remote Assistance communications.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\policies\Microsoft\Windows NT\Terminal Services</mssasc-core:KeyPath>
<mssasc-core:ValueName>fAllowToGetHelp</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="RA_Solicit" class="Machine" displayName="$(string.a4d681fd8b034c96bc9dcc75fdbd6a91)" explainText="$(string.17843ed873e74b3d8133bbaa60dfd4d4)" presentation="$(presentation.RA_Solicit)" key="Software\policies\Microsoft\Windows NT\Terminal Services" valueName="fAllowToGetHelp">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
<admx:elements xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:enum id="RA_Solicit_Mailto_List" key="Software\policies\Microsoft\Windows NT\Terminal Services" valueName="fUseMailto">
<admx:item displayName="$(string.6226f110308141258dfec19ddd50aecf)">
<admx:value>
<admx:decimal value="0" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.2135add146174263a65dcbc999a37451)">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
</admx:enum>
<admx:enum id="RA_Solicit_ExpireUnits_List" key="Software\policies\Microsoft\Windows NT\Terminal Services" valueName="MaxTicketExpiryUnits">
<admx:item displayName="$(string.ced3da3b15624046a936d682006e59b8)">
<admx:value>
<admx:decimal value="0" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.1e8194b9b5c3469a99e783d26e0407d4)">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.d591c61060d34295a4124addbeb95df7)">
<admx:value>
<admx:decimal value="2" />
</admx:value>
</admx:item>
</admx:enum>
<admx:decimal id="RA_Solicit_ExpireValue_Edt" key="Software\policies\Microsoft\Windows NT\Terminal Services" valueName="MaxTicketExpiry" minValue="1" maxValue="99" />
<admx:enum id="RA_Solicit_Control_List" key="Software\policies\Microsoft\Windows NT\Terminal Services" valueName="fAllowFullControl">
<admx:item displayName="$(string.6ecea448b3dc4dc091b6d518be4f075c)">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.d9c73ecf1a814cc3bc4b70baee36a2d9)">
<admx:value>
<admx:decimal value="0" />
</admx:value>
</admx:item>
</admx:enum>
</admx:elements>
</policy>
<ADMLDefinition>
<presentation id="RA_Solicit">
<admx:dropdownList refId="RA_Solicit_Control_List" noSort="true" defaultItem="0" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Permit remote control of this computer:</admx:dropdownList>
<admx:decimalTextBox refId="RA_Solicit_ExpireValue_Edt" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Maximum ticket time (value):</admx:decimalTextBox>
<admx:dropdownList refId="RA_Solicit_ExpireUnits_List" defaultItem="1" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Maximum ticket time (units):</admx:dropdownList>
<admx:dropdownList refId="RA_Solicit_Mailto_List" defaultItem="1" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Method for sending e-mail invitations:</admx:dropdownList>
</presentation>
<string id="a4d681fd8b034c96bc9dcc75fdbd6a91">Solicited Remote Assistance</string>
<string id="17843ed873e74b3d8133bbaa60dfd4d4">This policy setting determines whether remote assistance may be solicited from computers running Windows operating systems in your environment. You can enable this policy setting to allow users to solicit remote assistance from IT "expert" administrators.
If the Solicited Remote Assistance setting is enabled, the following options are available:
• Allow helpers to remotely control the computer
• Allow helpers to only view the computer
Also, the following options are available to configure the amount of time that a user help request remains valid:
• Maximum ticket time (value):
• Maximum ticket time (units): hours, minutes or days
When a ticket (help request) expires, the user must send another request before an expert can connect to the computer. If you disable the Solicited Remote Assistance setting, users cannot send help requests and the expert cannot connect to their computers.
If the Solicited Remote Assistance setting is not configured, users can configure solicited remote assistance through the Control Panel. The following settings are enabled by default in the Control Panel: Solicited Remote Assistance, Buddy support, and Remote control. The value for the Maximum ticket time is set to 30 days. If this policy setting is disabled, no one will be able to access Windows Vista client computers across the network.</string>
<string id="6226f110308141258dfec19ddd50aecf">Simple MAPI</string>
<string id="2135add146174263a65dcbc999a37451">Mailto</string>
<string id="ced3da3b15624046a936d682006e59b8">Minutes</string>
<string id="1e8194b9b5c3469a99e783d26e0407d4">Hours</string>
<string id="d591c61060d34295a4124addbeb95df7">Days</string>
<string id="6ecea448b3dc4dc091b6d518be4f075c">Allow helpers to remotely control the computer</string>
<string id="d9c73ecf1a814cc3bc4b70baee36a2d9">Allow helpers to only view the computer</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional or Windows Server 2003 family</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="219" ID="{06192296-c01c-41c2-9ec3-400fd5a13d65}" OriginalSettingID="{436c848f-826f-4f57-b1f0-ca3237156979}" Name="Turn off the Windows Messenger Customer Experience Improvement Program" LockdownDate="2011-10-12T11:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9559-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting specifies whether Windows Messenger can collect anonymous information about how the Windows Messenger software and service is used. </ShortDescription>
<FullDescription>This policy setting specifies whether Windows Messenger can collect anonymous information about how the Windows Messenger software and service is used.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Internet Communication Management\Internet Communication settings</UIPath>
<DefaultValue>Not configured</DefaultValue>
<Vulnerability>Large enterprise environments may not want to have information collected from managed client computers.
</Vulnerability>
<Countermeasure>Enable this policy setting to ensure that Windows Messenger does not collect usage information and to prevent display of the user settings that enable the collection of usage information.
</Countermeasure>
<PotentialImpact>Microsoft uses information collected through the Customer Experience Improvement Program to detect software flaws so that they can be corrected more quickly, enabling this setting will reduce the amount of data Microsoft is able to gather for this purpose.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Messenger\Client</mssasc-core:KeyPath>
<mssasc-core:ValueName>CEIP</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="WinMSG_NoInstrumentation_2" class="Machine" displayName="$(string.30f6dcb287924251b92118dc2b2591ae)" explainText="$(string.1e78fc6d132341a8b193f7358e83295e)" key="Software\Policies\Microsoft\Messenger\Client" valueName="CEIP">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="2" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="30f6dcb287924251b92118dc2b2591ae">Turn off the Windows Messenger Customer Experience Improvement Program</string>
<string id="1e78fc6d132341a8b193f7358e83295e">This policy setting specifies whether Windows Messenger can collect anonymous information about how the Windows Messenger software and service is used.</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional with SP2 or Windows Server 2003 family</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="220" ID="{df75109b-b7a3-4f31-ba0e-898c30b1d56d}" OriginalSettingID="{02a77ac3-7791-4a57-bee0-475435d336fe}" Name="Reschedule Automatic Updates scheduled installations" LockdownDate="2011-05-02T01:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10205-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines the amount of time before previously scheduled Automatic Update installations will proceed after system startup. </ShortDescription>
<FullDescription>This policy setting determines the amount of time before previously scheduled Automatic Update installations will proceed after system startup. If you configure this policy setting to Enabled, a previously scheduled installation will begin after a specified number of minutes when you next start the computer. If you configure this policy setting to Disabled or Not configured, previously scheduled installations will occur during the next regularly scheduled installation time.
Note: This policy setting only works when Automatic Updates is configured to perform scheduled update installations. If the Configure Automatic Updates setting is Disabled, the Reschedule Automatic Updates scheduled installations setting has no effect. You can enable the latter two settings to ensure that previously missed installations will be scheduled to install each time the computer restarts.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Windows Update</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>If Automatic Updates is not forced to wait a few minutes after a restart, computers in your environment might not have enough time to completely start all of their applications and services. If you specify enough time after a restart, new update installations should not conflict with the computer's startup procedures.</Vulnerability>
<Countermeasure>Configure the Reschedule Automatic Updates scheduled installations setting to Enabled and specify 10 minutes.</Countermeasure>
<PotentialImpact>Automatic Updates will not start until 10 minutes after the computer restarts.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows\WindowsUpdate\AU</mssasc-core:KeyPath>
<mssasc-core:ValueName>RescheduleWaitTimeEnabled</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="RescheduleWaitTime_Title" class="Machine" displayName="$(string.8ec322e93c1c411f986e07dcb1d0f29d)" explainText="$(string.57e8a5addf7d4a239e2993360642ea8a)" presentation="$(presentation.RescheduleWaitTime_Title)" key="Software\Policies\Microsoft\Windows\WindowsUpdate\AU" valueName="RescheduleWaitTimeEnabled">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
<admx:elements xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal id="RescheduleWaitTime_Minutes2" key="Software\Policies\Microsoft\Windows\WindowsUpdate\AU" valueName="RescheduleWaitTime" minValue="1" maxValue="60" />
</admx:elements>
</policy>
<ADMLDefinition>
<presentation id="RescheduleWaitTime_Title">
<admx:text xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Wait after system</admx:text>
<admx:decimalTextBox refId="RescheduleWaitTime_Minutes2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">startup (minutes): </admx:decimalTextBox>
</presentation>
<string id="8ec322e93c1c411f986e07dcb1d0f29d">Reschedule Automatic Updates scheduled installations</string>
<string id="57e8a5addf7d4a239e2993360642ea8a">This policy setting determines the amount of time before previously scheduled Automatic Update installations will proceed after system startup. If you configure this policy setting to Enabled, a previously scheduled installation will begin after a specified number of minutes when you next start the computer. If you configure this policy setting to Disabled or Not configured, previously scheduled installations will occur during the next regularly scheduled installation time.
Note: This policy setting only works when Automatic Updates is configured to perform scheduled update installations. If the Configure Automatic Updates setting is Disabled, the Reschedule Automatic Updates scheduled installations setting has no effect. You can enable the latter two settings to ensure that previously missed installations will be scheduled to install each time the computer restarts.</string>
</ADMLDefinition>
<supportedOn>At least Windows 2000 Service Pack 3 or Windows XP Professional Service Pack 1</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="oval:com.secure-elements.oval:def:6606" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="221" ID="{7bd05027-314d-46be-82b8-a8fecad3b4c5}" OriginalSettingID="{7c6c01fd-5c0d-4398-9de0-0a8855c4cd95}" Name="Network access: Sharing and security model for local accounts" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9503-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines how network logons that use local accounts are authenticated.</ShortDescription>
<FullDescription>This policy setting determines how network logons that use local accounts are authenticated. The Classic option allows precise control over access to resources, including the ability to assign different types of access to different users for the same resource. The Guest only option allows you to treat all users equally. In this context, all users authenticate as Guest only to receive the same access level to a given resource.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Classic - local users authenticate as themselves</DefaultValue>
<Vulnerability>With the Guest only model, any user who can authenticate to your computer over the network does so with guest privileges, which probably means that they will not have write access to shared resources on that computer. Although this restriction does increase security, it makes it more difficult for authorized users to access shared resources on those computers because ACLs on those resources must include access control entries (ACEs) for the Guest account. With the Classic model, local accounts should be password protected. Otherwise, if Guest access is enabled, anyone can use those user accounts to access shared system resources.</Vulnerability>
<Countermeasure>For network servers, configure the Network access: Sharing and security model for local accounts setting to Classic – local users authenticate as themselves. On end-user computers, configure this policy setting to Guest only – local users authenticate as guest.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Classic - local users authenticate as themselves">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Classic - local users authenticate as themselves">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Guest only: Local users authenticate as Guest">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>ForceGuest</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\ForceGuest" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:94" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="222" ID="{62941427-df06-4408-ad1c-b4969efdb67f}" OriginalSettingID="{1662860c-c599-4fa1-a82a-8e52d2ca562e}" Name="No auto-restart with logged on users for scheduled automatic updates installations" LockdownDate="2011-05-02T01:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9672-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Setting controls the auto-restart functionality of the operating system</ShortDescription>
<FullDescription>This policy setting specifies that Automatic Updates will wait for computers to be restarted by the users who are logged on to them to complete a scheduled installation.
If you enable the No auto-restart for scheduled Automatic Updates installations setting, Automatic Updates does not restart computers automatically during scheduled installations. Instead, Automatic Updates notifies users to restart their computers to complete the installations. You should note that Automatic Updates will not be able to detect future updates until restarts occur on the affected computers. If you disable or do not configure this setting, Automatic Updates will notify users that their computers will automatically restart in 5 minutes to complete the installations.
The possible values for the No auto-restart for scheduled Automatic Updates installations setting are:
• Enabled
• Disabled
• Not Configured
Note: This setting applies only when you configure Automatic Updates to perform scheduled update installations. If you configure the Configure Automatic Updates setting to Disabled, this setting has no effect.
</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Windows Update</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>Sometimes updates require updated computers to be restarted to complete an installation. If the computer cannot restart automatically, then the most recent update will not completely install and no new updates will download to the computer until it is restarted.</Vulnerability>
<Countermeasure>Configure the No auto-restart for scheduled Automatic Updates installations setting to Disabled.</Countermeasure>
<PotentialImpact>If you enable this policy setting, the operating systems on the servers in your environment will restart themselves automatically. For critical servers this could lead to a temporary denial of service (DoS) condition.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows\WindowsUpdate\AU</mssasc-core:KeyPath>
<mssasc-core:ValueName>NoAutoRebootWithLoggedOnUsers</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="NoAutoRebootWithLoggedOnUsers_Title" class="Machine" displayName="$(string.9651a9eccd3f4fedaa8de8e6d40d15d0)" explainText="$(string.101f8f6cd0a344168991d78679a03bad)" key="Software\Policies\Microsoft\Windows\WindowsUpdate\AU" valueName="NoAutoRebootWithLoggedOnUsers">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="9651a9eccd3f4fedaa8de8e6d40d15d0">No auto-restart with logged on users for scheduled automatic updates installations</string>
<string id="101f8f6cd0a344168991d78679a03bad">This policy setting specifies that Automatic Updates will wait for computers to be restarted by the users who are logged on to them to complete a scheduled installation.
If you enable the No auto-restart for scheduled Automatic Updates installations setting, Automatic Updates does not restart computers automatically during scheduled installations. Instead, Automatic Updates notifies users to restart their computers to complete the installations. You should note that Automatic Updates will not be able to detect future updates until restarts occur on the affected computers. If you disable or do not configure this setting, Automatic Updates will notify users that their computers will automatically restart in 5 minutes to complete the installations.
The possible values for the No auto-restart for scheduled Automatic Updates installations setting are:
• Enabled
• Disabled
• Not Configured
Note: This setting applies only when you configure Automatic Updates to perform scheduled update installations. If you configure the Configure Automatic Updates setting to Disabled, this setting has no effect.
</string>
</ADMLDefinition>
<supportedOn>At least Windows 2000 Service Pack 3 or Windows XP Professional Service Pack 1</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="oval:com.secure-elements.oval:def:6605" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="223" ID="{c18eaed6-7058-449e-82de-bd53aa5de63d}" OriginalSettingID="{576fb5ee-178c-4117-a4fe-ef3cbe30ce64}" Name="Network access: Named Pipes that can be accessed anonymously" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9218-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which communication sessions, or pipes, will have attributes and permissions that allow anonymous access.</ShortDescription>
<FullDescription>This policy setting determines which communication sessions, or pipes, will have attributes and permissions that allow anonymous access.
Note: When you configure this setting you specify a list of one or more objects. The delimiter used when entering the list is a line feed or carriage return, that is, type the first object on the list, press the Enter button, type the next object, press Enter again, etc. The setting value is stored as a comma-delimited list in group policy security templates. It is also rendered as a comma-delimited list in Group Policy Editor’s display pane and the Resultant Set of Policy console. It is recorded in the registry as a line-feed delimited list in a REG_MULTI_SZ value.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>
</DefaultValue>
<Vulnerability>You can restrict access over named pipes such as COMNAP and LOCATOR to help prevent unauthorized access to the network. The default list of named pipes and their purpose is provided in the following list:
COMNAP - SNABase named pipe. Systems Network Architecture (SNA) is a collection of network protocols that were originally developed for IBM mainframe computers.
COMNODE - SNA Server named pipe.
SQL\QUERY - Default named pipe for SQL Server.
SPOOLSS - Named pipe for the Print Spooler service.
EPMAPPER - End Point Mapper named pipe.
LOCATOR - Remote Procedure Call Locator service named pipe.
TrkWks - Distributed Link Tracking Client named pipe.
TrkSvr - Distributed Link Tracking Server named pipe.
</Vulnerability>
<Countermeasure>Configure the Network access: Named Pipes that can be accessed anonymously setting to a null value (enable the setting but do not enter named pipes in the text box).</Countermeasure>
<PotentialImpact>This configuration will disable null session access over named pipes, and applications that rely on this feature or on unauthenticated access to named pipes will no longer function. For example, with Microsoft Commercial Internet System 1.0, the Internet Mail Service runs under the Inetinfo process. Inetinfo starts in the context of the System account. When Internet Mail Service needs to query the Microsoft SQL Server database, it uses the System account, which uses null credentials to access a SQL pipe on the computer that runs SQL Server.
To avoid this problem, refer to the Microsoft Knowledge Base article “How to access network files from IIS applications,” which is located at http://support.microsoft.com/default.aspx?scid=207671.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_MULTI_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanManServer\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>NullSessionPipes</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Multi-String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\NullSessionPipes" DataType="REG_MULTI_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:91" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="224" ID="{a7683d68-8eb4-429a-878c-3153f61291cc}" OriginalSettingID="{93bdf15f-cc68-4327-bab3-557b93af3976}" Name="Configure Automatic Updates" LockdownDate="2011-08-05T07:16:32Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9403-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting specifies whether computers in your environment will receive security updates from Windows Update or WSUS</ShortDescription>
<FullDescription>This policy setting specifies whether computers in your environment will receive security updates from Windows Update or WSUS. If you configure this policy setting to Enabled, the operating system will recognize when a network connection is available and then use the network connection to search Windows Update or your designated intranet site for updates that apply to them.
After you configure this policy setting to Enabled, select one of the following three options in the Configure Automatic Updates Properties dialog box to specify how the service will work:
• Notify before downloading any updates and notify again before installing them.
• Download the updates automatically and notify when they are ready to be installed. (Default setting)
• Automatically download updates and install them on the schedule specified below.
If you disable this policy setting, you will need to download and manually install any available updates from Windows Update.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Windows Update</UIPath>
<DefaultValue>Download the updates automatically and notify when they are ready to be installed</DefaultValue>
<Vulnerability>Although each version of Windows is thoroughly tested before release, it is possible that problems will be discovered after the products are shipped. The Configure Automatic Updates setting can help you ensure that the computers in your environment will always have the most recent critical operating system updates and service packs installed.</Vulnerability>
<Countermeasure>Configure the Configure Automatic Updates setting to Enabled and select 4. Automatically download updates and install them on the schedule specified below from the Configure automatic updating list box.</Countermeasure>
<PotentialImpact>Critical operating system updates and service packs will automatically download and install at 3:00 A.M. daily.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows\WindowsUpdate\AU</mssasc-core:KeyPath>
<mssasc-core:ValueName>NoAutoUpdate</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="AutoUpdateCfg" class="Machine" displayName="$(string.dedec4c2ad7d4184b27bb8ff265d65c4)" explainText="$(string.5d52c69e1f3448819546f791b5605d14)" presentation="$(presentation.AutoUpdateCfg)" key="Software\Policies\Microsoft\Windows\WindowsUpdate\AU" valueName="NoAutoUpdate">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:disabledValue>
<admx:elements xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:enum id="AutoUpdateMode" key="Software\Policies\Microsoft\Windows\WindowsUpdate\AU" valueName="AUOptions">
<admx:item displayName="$(string.fdd9ce8d75474d86be6db964a63987c3)">
<admx:value>
<admx:decimal value="2" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.55e92f3de0df4cd8a681eb1690b115ab)">
<admx:value>
<admx:decimal value="3" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.8ae3b57ac96445afbe945496531a8291)">
<admx:value>
<admx:decimal value="4" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.7d4b4471d29d457b98577a4e256106a3)">
<admx:value>
<admx:decimal value="5" />
</admx:value>
</admx:item>
</admx:enum>
<admx:enum id="AutoUpdateSchTime" key="Software\Policies\Microsoft\Windows\WindowsUpdate\AU" valueName="ScheduledInstallTime">
<admx:item displayName="$(string.dd6fbc71f2b34d28aba18cf445aa48d4)">
<admx:value>
<admx:decimal value="0" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.9829aadc689a4e03971509802d19ea5d)">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.b1eebdb6f8ac4727ae174881ac0f5add)">
<admx:value>
<admx:decimal value="2" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.12fa4f86528e41c085492cbac96da3b3)">
<admx:value>
<admx:decimal value="3" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.e02768f925b042ff9399ace77047ac04)">
<admx:value>
<admx:decimal value="4" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.895d66d2158a41a084b3f28775302184)">
<admx:value>
<admx:decimal value="5" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.f7d9f3d0a412430bb90f852fc54621d5)">
<admx:value>
<admx:decimal value="6" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.482dd51c97244eee8c4b060ca9afced9)">
<admx:value>
<admx:decimal value="7" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.5f672cbc32c34d5188d1df9e7e1ef493)">
<admx:value>
<admx:decimal value="8" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.2678eb7947504f44a7a9ccbdfab22382)">
<admx:value>
<admx:decimal value="9" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.017d3a3403a44cf091c3bc70cf5f90f6)">
<admx:value>
<admx:decimal value="10" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.3c04f7e686004bc6bded291d76e3f2c0)">
<admx:value>
<admx:decimal value="11" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.54c07326b58b4cffa3a6ebc2bc073268)">
<admx:value>
<admx:decimal value="12" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.816daa40327f457eb48e695300d39e3f)">
<admx:value>
<admx:decimal value="13" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.af462981a75448f1845da454ec396c4f)">
<admx:value>
<admx:decimal value="14" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.ad3598cdce0947a19e8e0af8b66d8aa1)">
<admx:value>
<admx:decimal value="15" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.33600fa872fa4a71b825a4a593a97657)">
<admx:value>
<admx:decimal value="16" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.9193acc9597c48a18c489d16ad92c634)">
<admx:value>
<admx:decimal value="17" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.7a658c915f7f4a3fbf61e69eef968cff)">
<admx:value>
<admx:decimal value="18" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.34b16e3893ac4434b09e130cce455283)">
<admx:value>
<admx:decimal value="19" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.e2f09cd6c91f4c4d975a40b74a9f57b7)">
<admx:value>
<admx:decimal value="20" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.645e780d63f649f8bb0674768209b268)">
<admx:value>
<admx:decimal value="21" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.d4a72599e23847349cbca7f1c53bd154)">
<admx:value>
<admx:decimal value="22" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.820e9418e6fa40e6a7d21c1a0d428f78)">
<admx:value>
<admx:decimal value="23" />
</admx:value>
</admx:item>
</admx:enum>
<admx:enum id="AutoUpdateSchDay" key="Software\Policies\Microsoft\Windows\WindowsUpdate\AU" valueName="ScheduledInstallDay">
<admx:item displayName="$(string.509b93b359e4419b9bf14dff6451c845)">
<admx:value>
<admx:decimal value="0" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.05264b69119b4453a2f2f55889dbe2c9)">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.03ac2eb3b200497687ce75138b85274f)">
<admx:value>
<admx:decimal value="2" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.7e980a926d6043369aab97695a4fad6b)">
<admx:value>
<admx:decimal value="3" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.6d7c2e0a87d74b17a7e4dad39dcdc81a)">
<admx:value>
<admx:decimal value="4" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.2bb07dccae2a4c4bae69e7c889e845c6)">
<admx:value>
<admx:decimal value="5" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.d3cb28f90e8341abb80030e2a3c6324f)">
<admx:value>
<admx:decimal value="6" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.bba98073fb84416b8cce5c5c6adcaca8)">
<admx:value>
<admx:decimal value="7" />
</admx:value>
</admx:item>
</admx:enum>
</admx:elements>
</policy>
<ADMLDefinition>
<presentation id="AutoUpdateCfg">
<admx:dropdownList refId="AutoUpdateMode" defaultItem="1" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Configure automatic updating:</admx:dropdownList>
<admx:text xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">The following settings are only required</admx:text>
<admx:text xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">and applicable if 4 is selected.</admx:text>
<admx:dropdownList refId="AutoUpdateSchDay" defaultItem="0" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Scheduled install day: </admx:dropdownList>
<admx:dropdownList refId="AutoUpdateSchTime" defaultItem="3" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Scheduled install time:</admx:dropdownList>
</presentation>
<string id="dedec4c2ad7d4184b27bb8ff265d65c4">Configure Automatic Updates</string>
<string id="5d52c69e1f3448819546f791b5605d14">This policy setting specifies whether computers in your environment will receive security updates from Windows Update or WSUS. If you configure this policy setting to Enabled, the operating system will recognize when a network connection is available and then use the network connection to search Windows Update or your designated intranet site for updates that apply to them.
After you configure this policy setting to Enabled, select one of the following three options in the Configure Automatic Updates Properties dialog box to specify how the service will work:
• Notify before downloading any updates and notify again before installing them.
• Download the updates automatically and notify when they are ready to be installed. (Default setting)
• Automatically download updates and install them on the schedule specified below.
If you disable this policy setting, you will need to download and manually install any available updates from Windows Update.</string>
<string id="fdd9ce8d75474d86be6db964a63987c3">2 - Notify for download and notify for install</string>
<string id="55e92f3de0df4cd8a681eb1690b115ab">3 - Auto download and notify for install</string>
<string id="8ae3b57ac96445afbe945496531a8291">4 - Auto download and schedule the install</string>
<string id="7d4b4471d29d457b98577a4e256106a3">5 - Allow local admin to choose setting</string>
<string id="dd6fbc71f2b34d28aba18cf445aa48d4">00:00</string>
<string id="9829aadc689a4e03971509802d19ea5d">01:00</string>
<string id="b1eebdb6f8ac4727ae174881ac0f5add">02:00</string>
<string id="12fa4f86528e41c085492cbac96da3b3">03:00</string>
<string id="e02768f925b042ff9399ace77047ac04">04:00</string>
<string id="895d66d2158a41a084b3f28775302184">05:00</string>
<string id="f7d9f3d0a412430bb90f852fc54621d5">06:00</string>
<string id="482dd51c97244eee8c4b060ca9afced9">07:00</string>
<string id="5f672cbc32c34d5188d1df9e7e1ef493">08:00</string>
<string id="2678eb7947504f44a7a9ccbdfab22382">09:00</string>
<string id="017d3a3403a44cf091c3bc70cf5f90f6">10:00</string>
<string id="3c04f7e686004bc6bded291d76e3f2c0">11:00</string>
<string id="54c07326b58b4cffa3a6ebc2bc073268">12:00</string>
<string id="816daa40327f457eb48e695300d39e3f">13:00</string>
<string id="af462981a75448f1845da454ec396c4f">14:00</string>
<string id="ad3598cdce0947a19e8e0af8b66d8aa1">15:00</string>
<string id="33600fa872fa4a71b825a4a593a97657">16:00</string>
<string id="9193acc9597c48a18c489d16ad92c634">17:00</string>
<string id="7a658c915f7f4a3fbf61e69eef968cff">18:00</string>
<string id="34b16e3893ac4434b09e130cce455283">19:00</string>
<string id="e2f09cd6c91f4c4d975a40b74a9f57b7">20:00</string>
<string id="645e780d63f649f8bb0674768209b268">21:00</string>
<string id="d4a72599e23847349cbca7f1c53bd154">22:00</string>
<string id="820e9418e6fa40e6a7d21c1a0d428f78">23:00</string>
<string id="509b93b359e4419b9bf14dff6451c845">0 - Every day</string>
<string id="05264b69119b4453a2f2f55889dbe2c9">1 - Every Sunday</string>
<string id="03ac2eb3b200497687ce75138b85274f">2 - Every Monday</string>
<string id="7e980a926d6043369aab97695a4fad6b">3 - Every Tuesday</string>
<string id="6d7c2e0a87d74b17a7e4dad39dcdc81a">4 - Every Wednesday</string>
<string id="2bb07dccae2a4c4bae69e7c889e845c6">5 - Every Thursday</string>
<string id="d3cb28f90e8341abb80030e2a3c6324f">6 - Every Friday</string>
<string id="bba98073fb84416b8cce5c5c6adcaca8">7 - Every Saturday</string>
</ADMLDefinition>
<supportedOn>At least Windows 2000 Service Pack 3 or Windows XP Professional Service Pack 1</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="oval:com.secure-elements.oval:def:6604" ref_url="" />
</OVAL>
<XCCDF>
<Reference name="Configure Automatic Updates" />
</XCCDF>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="225" ID="{dd0bbd63-cb83-4771-83e4-4c8bfb6dd31c}" OriginalSettingID="{ef246cc1-1b50-4b57-b868-7c5cf1d500d0}" Name="Enumerate administrator accounts on elevation" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9938-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>By default, all administrator accounts are displayed when you attempt to elevate a running application.</ShortDescription>
<FullDescription>By default, all administrator accounts are displayed when you attempt to elevate a running application. </FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Credential User Interface</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Users could see the list of administrator accounts, making it slightly easier for a malicious user who has logged onto a console session to try to crack the passwords of those accounts.</Vulnerability>
<Countermeasure>Enable this policy.</Countermeasure>
<PotentialImpact>If you enable this policy setting, all local administrator accounts on the machine will be displayed so the user can choose one and enter the correct password. If you disable this policy setting, users will be required to always type in a username and password to elevate.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\CredUI</mssasc-core:KeyPath>
<mssasc-core:ValueName>EnumerateAdministrators</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="EnumerateAdministrators" class="Machine" displayName="$(string.db3d4cdad67d4e72a7608df39f494c18)" explainText="$(string.2d72722d2ea54ec08c6989c7f5bea8ac)" key="Software\Microsoft\Windows\CurrentVersion\Policies\CredUI" valueName="EnumerateAdministrators">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="db3d4cdad67d4e72a7608df39f494c18">Enumerate administrator accounts on elevation</string>
<string id="2d72722d2ea54ec08c6989c7f5bea8ac">By default, all administrator accounts are displayed when you attempt to elevate a running application. </string>
</ADMLDefinition>
<supportedOn>At least Windows Vista</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="226" ID="{ca7b8d48-4e41-4e71-9a20-230da5c6ba0c}" OriginalSettingID="{4371c270-4743-4527-a8c1-b18c4c7508d6}" Name="Do not allow drive redirection" LockdownDate="2011-05-15T05:26:30Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9518-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting prevents users from sharing the local drives on their client computers to Terminal Servers that they access.</ShortDescription>
<FullDescription>This policy setting prevents users from sharing the local drives on their client computers to Terminal Servers that they access. Mapped drives appear in the session folder tree in Windows Explorer in the following format:
\\TSClient\<driveletter>$
If local drives are shared they are left vulnerable to intruders who want to exploit the data that is stored on them.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Device and Resource Redirection</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Data could be forwarded from the user's Terminal Server session to the user's local computer without any direct user interaction.</Vulnerability>
<Countermeasure>Configure the Do not allow drive redirection setting to Enabled.</Countermeasure>
<PotentialImpact>Drive redirection will not be possible.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services</mssasc-core:KeyPath>
<mssasc-core:ValueName>fDisableCdm</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="TS_CLIENT_DRIVE_M" class="Machine" displayName="$(string.3dca040ebdc14429a26dd8f62ab6b810)" explainText="$(string.b93c8d1465f64d2ab7eb155cf6f22b81)" key="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" valueName="fDisableCdm">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="3dca040ebdc14429a26dd8f62ab6b810">Do not allow drive redirection</string>
<string id="b93c8d1465f64d2ab7eb155cf6f22b81">This policy setting prevents users from sharing the local drives on their client computers to Terminal Servers that they access. Mapped drives appear in the session folder tree in Windows Explorer in the following format:
\\TSClient\<driveletter>$
If local drives are shared they are left vulnerable to intruders who want to exploit the data that is stored on them.</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional or Windows Server 2003 family</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="oval:com.secure-elements.oval:def:6598" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="227" ID="{2233fc3e-260f-449e-9e19-6f6f326e10c8}" OriginalSettingID="{b885a33c-d185-405c-b234-3f756f190eff}" Name="Devices: Restrict floppy access to locally logged-on user only" LockdownDate="2011-10-12T11:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9440-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether removable floppy media are accessible to both local and remote users simultaneously.</ShortDescription>
<FullDescription>This policy setting determines whether removable floppy media are accessible to both local and remote users simultaneously. If you enable this policy setting, only the interactively logged-on user is allowed to access removable floppy media. If this policy setting is enabled and no one is logged on interactively, the floppy media is accessible over the network.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined
</DefaultValue>
<Vulnerability>A remote user could potentially access a mounted floppy that contains sensitive information. This risk is small because floppy disk drives are not automatically shared; administrators must deliberately choose to share the drive. However, administrators may wish to deny network users the ability to view data or run applications from removable media on the server.</Vulnerability>
<Countermeasure>Enable the Devices: Restrict floppy access to locally logged-on user only setting.</Countermeasure>
<PotentialImpact>Users who connect to the server over the network will not be able to use any floppy disk drives that are installed on the server whenever anyone is logged on to the local console of the server. System tools that require access to floppy disk drives will fail. For example, the Volume Shadow Copy service attempts to access all CD-ROM and floppy disk drives present on the computer when it initializes, and if the service cannot access one of these drives it will fail. This condition will cause the Windows Backup tool to fail if volume shadow copies were specified for the backup job. Any non-Microsoft backup products that use volume shadow copies will also fail.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows NT\CurrentVersion\Winlogon</mssasc-core:KeyPath>
<mssasc-core:ValueName>AllocateFloppies</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\AllocateFloppies" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:59" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="228" ID="{106dd3a8-c846-4e8f-86aa-5c81d84e1483}" OriginalSettingID="{3849d4a1-188c-43d8-ad75-c73a82a8e0fe}" Name="Shutdown: Allow system to be shut down without having to log on" LockdownDate="2011-06-14T01:30:40Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9707-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether a computer can be shut down when a user is not logged on.</ShortDescription>
<FullDescription>This policy setting determines whether a computer can be shut down when a user is not logged on. If this policy setting is enabled, the shutdown command is available on the Windows logon screen. Microsoft recommends to disable this policy setting to restrict the ability to shut down the computer to users with credentials on the system.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>Users who can access the console locally could shut down the computer.
Attackers could also walk to the local console and restart the server, which would cause a temporary DoS condition. Attackers could also shut down the server and leave all of its applications and services unavailable.
</Vulnerability>
<Countermeasure>Disable the Allow system to be shut down without having to log on setting.</Countermeasure>
<PotentialImpact>Operators will have to log on to servers to shut them down or restart them.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>ShutdownWithoutLogon</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\ShutdownWithoutLogon" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:103" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="229" ID="{d56842e4-3659-4777-97c1-f9bbe47477df}" OriginalSettingID="{f81af9da-063b-4a21-986b-2cf433f7663b}" Name="Prevent the computer from joining a homegroup" LockdownDate="2011-10-12T11:37:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10183-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Controls if a computer can be joined to a HomeGroup</ShortDescription>
<FullDescription>By default, users can add their computer to a homegroup on a home network.
If you enable this policy setting, a user on this computer will not be able to add this computer to a homegroup. This setting does not affect other network sharing features.
If you disable or do not configure this policy setting, a user can add this computer to a homegroup. However, data on a domain-joined computer is not shared with the homegroup.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\HomeGroup</UIPath>
<DefaultValue>Disabled
</DefaultValue>
<Vulnerability>By default, domain joined computers can be joined to a HomeGroup. While resources on a domain-joined computer cannot be shared to the HomeGroup, information from the domain-joined computer can be leaked to other computers in the HomeGroup.</Vulnerability>
<Countermeasure>Enable this setting to prevent computers from joining a HomeGroup.</Countermeasure>
<PotentialImpact>Mobile users who access printers and other shared devices on their home networks will not be able to leverage the ease of use provided by HomeGroup functionality.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows\HomeGroup</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableHomeGroup</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="DisableHomeGroup" class="Machine" displayName="$(string.0e1509f4d1d54deb8fd67eec60bfd18c)" explainText="$(string.7a52f343a824407ba175ab7c9fa375bb)" key="Software\Policies\Microsoft\Windows\HomeGroup" valueName="DisableHomeGroup">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="0e1509f4d1d54deb8fd67eec60bfd18c">Prevent the computer from joining a homegroup</string>
<string id="7a52f343a824407ba175ab7c9fa375bb">By default, users can add their computer to a homegroup on a home network.
If you enable this policy setting, a user on this computer will not be able to add this computer to a homegroup. This setting does not affect other network sharing features.
If you disable or do not configure this policy setting, a user can add this computer to a homegroup. However, data on a domain-joined computer is not shared with the homegroup.</string>
</ADMLDefinition>
<supportedOn>At least Windows 7 or Windows Server 2008 R2</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="230" ID="{bad20a53-2c9b-4e1c-8a27-4c73f8adbb36}" OriginalSettingID="{c8c43367-6343-4ae7-9387-c4f24303b90d}" Name="Shutdown: Clear virtual memory pagefile" LockdownDate="2011-05-22T06:55:44Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9222-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether the virtual memory pagefile is cleared when the system is shut down. </ShortDescription>
<FullDescription>This policy setting determines whether the virtual memory pagefile is cleared when the system is shut down. When this policy setting is enabled, the system pagefile is cleared each time that the system shuts down properly. If you enable this security setting, the hibernation file (Hiberfil.sys) is zeroed out when hibernation is disabled on a portable computer system. It will take longer to shut down and restart the computer, and will be especially noticeable on computers with large paging files.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Important information that is kept in real memory may be written periodically to the page file to help Windows Server 2003 handle multitasking functions. An attacker who has physical access to a server that has been shut down could view the contents of the paging file. The attacker could move the system volume into a different computer and then analyze the contents of the paging file. Although this process is time consuming, it could expose data that is cached from random access memory (RAM) to the paging file.
Caution
An attacker who has physical access to the server could bypass this countermeasure by simply unplugging the server from its power source.
</Vulnerability>
<Countermeasure>Enable the Clear virtual memory page file when system shuts down setting. This configuration causes Windows Server 2003 to clear the page file when the computer is shut down. The amount of time that is required to complete this process depends on the size of the page file. It could be several minutes before the computer completely shuts down.</Countermeasure>
<PotentialImpact>It will take longer to shut down and restart the server, especially on servers with large paging files. For a server with 2 gigabytes (GB) of RAM and a 2-GB paging file, this policy setting could increase the shutdown process by 20 to 30 minutes, or more. For some organizations, this downtime violates their internal service level agreements. Therefore, use caution before you implement this countermeasure in your environment.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Session Manager\Memory Management</mssasc-core:KeyPath>
<mssasc-core:ValueName>ClearPageFileAtShutdown</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management\ClearPageFileAtShutdown" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:104" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="231" ID="{f0164392-334b-46cb-9b1a-e4fd2d378c56}" OriginalSettingID="{14f5fa31-1aa5-4e62-a610-5fda91fd7143}" Name="MSS: (AutoShareWks) Enable Administrative Shares (recommended except for highly secure environments)" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10814-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting controls the hidden administrative shares on a workstation. By default, when Windows networking is active on a workstation, Windows will create hidden administrative shares.</ShortDescription>
<FullDescription>This entry appears as MSS: (AutoShareWks) Enable Administrative Shares (recommended except for highly secure environments) in the SCE. By default, when Windows networking is active on a server, Windows will create hidden administrative shares.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not Defined</DefaultValue>
<Vulnerability>Because these built-in administrative shares are well-known and present on most Windows computers, malicious users often target them for brute-force attacks to guess passwords as well as other types of attacks. </Vulnerability>
<Countermeasure>Do not configure the MSS: (AutoShareWks) Enable Administrative Shares (not recommended except for highly secure environments) entry except on computers in highly secured environments where administrative shares are not required.
The possible values for this registry entry are:
● 1 or 0. The default configuration is disabled.
In the SCE UI, these options appear as:
● Enabled
● Disabled
● Not Defined
</Countermeasure>
<PotentialImpact>If you delete these shares you could cause problems for administrators and programs or services that rely on these shares. For example, both Microsoft Systems Management Server (SMS) and Microsoft Operations Manager require administrative shares for correct installation and operation. Also, many third-party network backup applications require administrative shares.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanmanServer\Parameters\</mssasc-core:KeyPath>
<mssasc-core:ValueName>AutoShareWks</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters\AutoShareWks" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="232" ID="{48fab6d9-60e1-4fe5-8c3f-7b2b728cbe2f}" OriginalSettingID="{ff93353b-e178-4aa5-bfb1-883c2e2b4af8}" Name="Turn off printing over HTTP" LockdownDate="2011-10-12T11:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10061-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to disable the client computer’s ability to print over HTTP, which allows the computer to print to printers on the intranet as well as the Internet. </ShortDescription>
<FullDescription>This policy setting allows you to disable the client computer’s ability to print over HTTP, which allows the computer to print to printers on the intranet as well as the Internet. </FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Internet Communication Management\Internet Communication settings</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Information that is transmitted over HTTP through this capability is not protected and can be intercepted by malicious users. For this reason, it is not often used in enterprise environments.</Vulnerability>
<Countermeasure>Enable this setting to prevent users from submitting print jobs via HTTP.</Countermeasure>
<PotentialImpact>If you enable this policy setting, the client computer will not be able to print to Internet printers over HTTP. This policy setting affects the client side of Internet printing only. Regardless of how it is configured, a computer could act as an Internet Printing server and make its shared printers available through HTTP.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows NT\Printers</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableHTTPPrinting</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="DisableHTTPPrinting_2" class="Machine" displayName="$(string.54706246121747c3a3f5a44c10e0189f)" explainText="$(string.1745de3ac5b54a1db1c08fd9affccc22)" key="Software\Policies\Microsoft\Windows NT\Printers" valueName="DisableHTTPPrinting">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="54706246121747c3a3f5a44c10e0189f">Turn off printing over HTTP</string>
<string id="1745de3ac5b54a1db1c08fd9affccc22">This policy setting allows you to disable the client computer’s ability to print over HTTP, which allows the computer to print to printers on the intranet as well as the Internet. </string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional with SP2 or Windows Server 2003 family with SP1</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="233" ID="{4b5df42d-5abb-4b3e-b1a6-63a54ae46e64}" OriginalSettingID="{c57013e7-e530-4cbd-951f-2c07f2a91b73}" Name="Always install with elevated privileges" LockdownDate="2011-10-31T10:45:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-00000-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Always install with elevated privileges</ShortDescription>
<FullDescription>Directs Windows Installer to use system permissions when it installs any program on the system.
This setting extends elevated privileges to all programs. These privileges are usually reserved for programs that have been assigned to the user (offered on the desktop), assigned to the computer (installed automatically), or made available in Add or Remove Programs in Control Panel. This setting lets users install programs that require access to directories that the user might not have permission to view or change, including directories on highly restricted computers.
If you disable this setting or do not configure it, the system applies the current user's permissions when it installs programs that a system administrator does not distribute or offer.
Note: This setting appears both in the Computer Configuration and User Configuration folders. To make this setting effective, you must enable the setting in both folders.
Caution: Skilled users can take advantage of the permissions this setting grants to change their privileges and gain permanent access to restricted files and folders. Note that the User Configuration version of this setting is not guaranteed to be secure.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Windows Installer</UIPath>
<DefaultValue>Not Configured</DefaultValue>
<Vulnerability>Users with limited privileges can exploit this feature by creating a Windows Installer installation package that creates a new local account that belongs to the local built-in Administrators group, adds their current account to the local built-in Administrators group, installs malicious software, or performs other unauthorized activities.</Vulnerability>
<Countermeasure>Configure the "Always install with elevated privileges" setting to "Disabled."</Countermeasure>
<PotentialImpact>Windows Installer will apply the current user's permissions when it installs programs, this will prevent standard users from installing applications that affect system-wide configuration items.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows\Installer</mssasc-core:KeyPath>
<mssasc-core:ValueName>AlwaysInstallElevated</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="AlwaysInstallElevated_2" class="Machine" displayName="$(string.26d5c8d119bd4f0b9628af0e7b4e541f)" explainText="$(string.26d8e488275c4e9e8e6e223752768b22)" key="Software\Policies\Microsoft\Windows\Installer" valueName="AlwaysInstallElevated">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="26d5c8d119bd4f0b9628af0e7b4e541f">Always install with elevated privileges</string>
<string id="26d8e488275c4e9e8e6e223752768b22">Directs Windows Installer to use system permissions when it installs any program on the system.
This setting extends elevated privileges to all programs. These privileges are usually reserved for programs that have been assigned to the user (offered on the desktop), assigned to the computer (installed automatically), or made available in Add or Remove Programs in Control Panel. This setting lets users install programs that require access to directories that the user might not have permission to view or change, including directories on highly restricted computers.
If you disable this setting or do not configure it, the system applies the current user's permissions when it installs programs that a system administrator does not distribute or offer.
Note: This setting appears both in the Computer Configuration and User Configuration folders. To make this setting effective, you must enable the setting in both folders.
Caution: Skilled users can take advantage of the permissions this setting grants to change their privileges and gain permanent access to restricted files and folders. Note that the User Configuration version of this setting is not guaranteed to be secure.</string>
</ADMLDefinition>
<supportedOn>Unspecified</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="234" ID="{5f372990-4414-4c40-b8fb-98dc76bc675c}" OriginalSettingID="{7ab41c58-8c4a-4781-9cdd-a6dc5c40fc66}" Name="System objects: Require case insensitivity for non-Windows subsystems" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9319-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Determines whether case insensitivity is enforced for all subsystems. Example is case insensitivity for other subsystems, such as the Portable Operating System Interface for UNIX (POSIX) which are normally case sensitive.</ShortDescription>
<FullDescription>This policy setting determines whether case insensitivity is enforced for all subsystems. The Microsoft Win32® subsystem is case insensitive. However, the kernel supports case sensitivity for other subsystems, such as the Portable Operating System Interface for UNIX (POSIX). Because Windows is case insensitive (but the POSIX subsystem will support case sensitivity), failure to enforce this policy setting makes it possible for a user of the POSIX subsystem to create a file with the same name as another file by using mixed case to label it. Such a situation can block access to these files by another user who uses typical Win32 tools, because only one of the files will be available.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>Because Windows is case-insensitive but the POSIX subsystem will support case sensitivity, failure to enable this policy setting would make it possible for a user of that subsystem to create a file with the same name as another file but with a different mix of upper and lower case letters. Such a situation could potentially confuse users when they try to access such files from normal Win32 tools because only one of the files will be available.</Vulnerability>
<Countermeasure>Enable the System objects: Require case insensitivity for non-Windows subsystems setting.</Countermeasure>
<PotentialImpact>All subsystems will be forced to observe case insensitivity. This configuration may confuse users who are familiar with any UNIX-based operating systems that is case-sensitive.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Session Manager\Kernel</mssasc-core:KeyPath>
<mssasc-core:ValueName>ObCaseInsensitive</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Session Manager\Kernel\ObCaseInsensitive" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:107" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="235" ID="{93cbd17d-76b9-4cb1-82d7-f43cff1bf7da}" OriginalSettingID="{71d6ee80-22f8-44e3-99ad-cbc707218ff8}" Name="Devices: Allowed to format and eject removable media" LockdownDate="2011-10-12T11:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8868-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines who is allowed to format and eject removable media.</ShortDescription>
<FullDescription>This policy setting determines who is allowed to format and eject removable media. You can use this policy setting to prevent unauthorized users from removing data on one computer to access it on another computer on which they have local administrator privileges.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined
</DefaultValue>
<Vulnerability>Users may be able to move data on removable disks to a different computer where they have administrative privileges. The user could then take ownership of any file, grant themselves full control, and view or modify any file. The fact that most removable storage devices will eject media by pressing a mechanical button diminishes the advantage of this policy setting.</Vulnerability>
<Countermeasure>Configure the Devices: Allowed to format and eject removable media setting to Administrators.</Countermeasure>
<PotentialImpact>Only Administrators will be able to format and eject removable media. If users are in the habit of using removable media for file transfers and storage, they will need to be informed of the change in policy.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Administrators and Interactive Users">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Administrators">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Administrators and Power Users">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Administrators and Interactive Users">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows NT\CurrentVersion\Winlogon</mssasc-core:KeyPath>
<mssasc-core:ValueName>AllocateDASD</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\AllocateDASD" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:43, oval:gov.nist.1:def:44" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="236" ID="{5dce86f2-da6a-4d99-ac8d-fd05b5c863ca}" OriginalSettingID="{7f8118fb-2951-4d95-82f0-7d4f170935e9}" Name="DCOM: Machine Access Restrictions in Security Descriptor Definition Language (SDDL) syntax" LockdownDate="2011-05-02T01:36:00Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9247-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which users or groups might access DCOM application remotely or locally. </ShortDescription>
<FullDescription>This policy setting determines which users or groups might access DCOM application remotely or locally. This setting is used to control the attack surface of the computer for DCOM applications.
You can use this policy setting to specify access permissions to all the computers to particular users for DCOM applications in the enterprise. When you specify the users or groups that are to be given permission, the security descriptor field is populated with the Security Descriptor Definition Language representation of those groups and privileges. If the security descriptor is left blank, the policy setting is defined in the template, but it is not enforced. Users and groups can be given explicit Allow or Deny privileges on both local access and remote access.
The registry settings that are created as a result of enabling the DCOM: Machine Access Restrictions in Security Descriptor Definition Language (SDDL) syntax policy setting take precedence over (have higher priority) the previous registry settings in this area. RpcSs checks the new registry keys in the Policies section for the computer restrictions, and these registry entries take precedence over the existing registry keys under OLE. This means that previously existing registry settings are no longer effective, and if you make changes to the existing settings, the computer access permissions for any users are not changed. You should take care to correctly configure their list of users and groups.
The possible values for this policy setting are:
Blank. This represents the local security policy way of deleting the policy enforcement key. This value deletes the policy and then sets it as Not defined state. The Blank value is set by using the ACL editor and emptying the list, and then pressing OK.
SDDL. This is the Security Descriptor Definition Language representation of the groups and privileges you specify when you enable this policy.
Not Defined. This is the default value.
Note
If the administrator is denied permission to access DCOM applications due to the changes made to DCOM in SP2, the administrator can use the DCOM: Machine Access Restrictions in Security Descriptor Definition Language (SDDL) syntax policy setting to manage DCOM access to the computer. The administrator can specify which users and groups can access the DCOM application on the computer both locally and remotely by using this setting. This will restore control of the DCOM application to the administrator and users. To do this, open the DCOM: Machine Access Restrictions in Security Descriptor Definition Language (SDDL) syntax setting, and click Edit Security. Specify the groups you want to include and the computer access permissions for those groups. This defines the setting and sets the appropriate SDDL value.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>Many COM applications include some security-specific code (for example, to call CoInitializeSecurity) but use weak settings that often allow unauthenticated access to the process. Administrators cannot override these settings to force stronger security in earlier versions of Windows without modifying the application. An attacker could attempt to exploit weak security in an individual application by attacking it through COM calls.
Also, COM infrastructure includes the Remote Procedure Call System Service (RPCSS), a system service that runs during computer startup and always runs after that. This service manages activation of COM objects and the running object table, and provides helper services to DCOM remoting. It exposes RPC interfaces that can be called remotely. Because some COM servers allow unauthenticated remote access, these interfaces can be called by anyone, including unauthenticated users. As a result, RPCSS can be attacked by malicious users who use remote, unauthenticated computers.
</Vulnerability>
<Countermeasure>To protect individual COM-based applications or services, set the DCOM: Machine Access Restrictions in Security Descriptor Definition Language (SDDL) setting to an appropriate computer-wide ACL. The syntax for SDDL is documented here: http://msdn.microsoft.com/en-us/library/aa379567(VS.85).aspx</Countermeasure>
<PotentialImpact>Windows operating systems implement default COM ACLs when they are installed. Modifying these ACLs from the default may cause some applications or components that communicate by using DCOM to fail. If you implement a COM server and you override the default security settings, confirm that the application-specific call permissions ACL assigns correct permission to appropriate users. If it does not, you need to change your application-specific permission ACL to provide appropriate users with activation rights so that applications and Windows components that use DCOM do not fail.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\policies\Microsoft\windows NT\DCOM</mssasc-core:KeyPath>
<mssasc-core:ValueName>MachineAccessRestriction</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Policies\Microsoft\Windows NT\DCOM\MachineAccessRestriction" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="237" ID="{95577ba0-26db-4064-9b27-8ef3ed080108}" OriginalSettingID="{aa73099d-1954-4488-b76f-72cab4588003}" Name="Turn off downloading of print drivers over HTTP" LockdownDate="2011-10-12T11:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9195-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting controls whether the computer can download print driver packages over HTTP. To set up HTTP printing, printer drivers that are not available in the standard operating system installation might need to be downloaded over HTTP.</ShortDescription>
<FullDescription>This policy setting controls whether the computer can download print driver packages over HTTP. To set up HTTP printing, printer drivers that are not available in the standard operating system installation might need to be downloaded over HTTP.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Internet Communication Management\Internet Communication settings</UIPath>
<DefaultValue>Not configured</DefaultValue>
<Vulnerability>Users might download drivers that include malicious code.</Vulnerability>
<Countermeasure>Enable this setting to prevent print drivers from being downloaded over HTTP.</Countermeasure>
<PotentialImpact> This policy setting does not prevent the client computer from printing to printers on the intranet or the Internet over HTTP. It only prohibits drivers that are not already installed locally from downloading.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows NT\Printers</mssasc-core:KeyPath>
<mssasc-core:ValueName>DisableWebPnPDownload</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="DisableWebPnPDownload_2" class="Machine" displayName="$(string.31584d1f053247a4993492ace70829e2)" explainText="$(string.cfff593b61dd4e4d9227e6f9b58d0f9c)" key="Software\Policies\Microsoft\Windows NT\Printers" valueName="DisableWebPnPDownload">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="31584d1f053247a4993492ace70829e2">Turn off downloading of print drivers over HTTP</string>
<string id="cfff593b61dd4e4d9227e6f9b58d0f9c">This policy setting controls whether the computer can download print driver packages over HTTP. To set up HTTP printing, printer drivers that are not available in the standard operating system installation might need to be downloaded over HTTP.</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional with SP2 or Windows Server 2003 family with SP1</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="238" ID="{2f11dbfa-2b0f-4b4a-b0eb-19ff44136ed6}" OriginalSettingID="{0f319931-aa36-4313-9320-86311c0fa623}" Name="Network access: Restrict anonymous access to Named Pipes and Shares" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9540-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>When enabled, this policy setting restricts anonymous access to only those shares and pipes that are named in the Network access: Named pipes that can be accessed anonymously and Network access: Shares that can be accessed anonymously settings.</ShortDescription>
<FullDescription>When enabled, this policy setting restricts anonymous access to only those shares and pipes that are named in the Network access: Named pipes that can be accessed anonymously and Network access: Shares that can be accessed anonymously settings. This policy setting controls null session access to shares on your computers by adding RestrictNullSessAccess with the value 1 in the HKLM\System
\CurrentControlSet\Services\LanManServer\Parameters registry key. This registry value toggles null session shares on or off to control whether the server service restricts unauthenticated clients' access to named resources. Null sessions are a weakness that can be exploited through shares (including the default shares) on computers in your environment.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled
</DefaultValue>
<Vulnerability>Null sessions are a weakness that can be exploited through shares (including the default shares) on computers in your environment.</Vulnerability>
<Countermeasure>Configure the Network access: Restrict anonymous access to Named Pipes and Shares setting to Enabled. </Countermeasure>
<PotentialImpact>You can enable this policy setting to restrict null session access for unauthenticated users to all server pipes and shared folders except those that are listed in the NullSessionPipes and NullSessionShares entries.
If you choose to enable this setting and are supporting Windows NT 4.0 domains, you should check if any of the named pipes are required to maintain trust relationships between the domains, and then add the pipe to the Network access: Named pipes that can be accessed anonymously:
• COMNAP–SNA session access
• COMNODE–SNA session access
• SQL\QUERY–SQL instance access
• SPOOLSS–Spooler service
• LLSRPC–License Logging service
• Netlogon–Net Logon service
• Lsarpc–LSA access
• Samr–Remote access to SAM objects
• browser–Computer Browser service
Previous to the release of Windows Server 2003 with Service Pack 1 (SP1) these named pipes were allowed anonymous access by default, but with the increased hardening in Windows Server 2003 with SP1 these pipes must be explicitly added if needed.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanManServer\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>restrictnullsessaccess</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\RestrictNullSessAccess" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="239" ID="{8cbb0aca-e8ea-4417-8a07-7d2293844996}" OriginalSettingID="{b89a9c6d-4c77-401f-8e1a-375f1d16c1c0}" Name="Turn off the "Publish to Web" task for files and folders" LockdownDate="2011-10-12T11:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9643-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting specifies whether the tasks Publish this file to the Web, Publish this folder to the Web, and Publish the selected items to the Web are available from File and Folder Tasks in Windows folders.</ShortDescription>
<FullDescription>This policy setting specifies whether the tasks Publish this file to the Web, Publish this folder to the Web, and Publish the selected items to the Web are available from File and Folder Tasks in Windows folders. </FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Internet Communication Management\Internet Communication settings</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Users may publish confidential or sensitive information to a public service outside of the control of the organization.</Vulnerability>
<Countermeasure>Enable the Turn off the "Publish to Web" task for files and folders setting to remove these options from the File and Folder tasks in Windows folders. By default, the option to publish to the Web is available.</Countermeasure>
<PotentialImpact>The Web Publishing wizard is used to download a list of providers and allow users to publish content to the Web.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\Explorer</mssasc-core:KeyPath>
<mssasc-core:ValueName>NoPublishingWizard</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="ShellRemovePublishToWeb_2" class="Machine" displayName="$(string.eb31306d57014d8dbf9b4a5d86ce670f)" explainText="$(string.a387acce9f314f7c94b7223bc729bf36)" key="Software\Microsoft\Windows\CurrentVersion\Policies\Explorer" valueName="NoPublishingWizard">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="eb31306d57014d8dbf9b4a5d86ce670f">Turn off the "Publish to Web" task for files and folders</string>
<string id="a387acce9f314f7c94b7223bc729bf36">This policy setting specifies whether the tasks Publish this file to the Web, Publish this folder to the Web, and Publish the selected items to the Web are available from File and Folder Tasks in Windows folders. </string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional with SP2 or Windows Server 2003 family</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="240" ID="{4a0d9ef7-a7a5-4e6d-a531-3004d37ac748}" OriginalSettingID="{c836e4ce-c2f0-410c-bbf2-2550e8d24ba8}" Name="MSS: (SafeDllSearchMode) Enable Safe DLL search mode (recommended)" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9348-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The entry appears as MSS: (SafeDllSearchMode) Enable Safe DLL search mode (recommended) in the SCE.</ShortDescription>
<FullDescription>The registry value entry SafeDllSearchMode was added to the template file in the HKEY_LOCAL_MACHINE\ SYSTEM\CurrentControlSet\Control\Session Manager\ registry key. The entry appears as MSS: (SafeDllSearchMode) Enable Safe DLL search mode (recommended) in the SCE.
The DLL search order can be configured to search for DLLs that are requested by running processes in one of two ways:
• Search folders specified in the system path first, and then search the current working folder.
• Search current working folder first, and then search the folders specified in the system path.
When enabled, the registry value is set to 1. With a setting of 1, the system first searches the folders that are specified in the system path and then searches the current working folder. When disabled the registry value is set to 0 and the system first searches the current working folder and then searches the folders that are specified in the system path.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not Defined</DefaultValue>
<Vulnerability>If a user unknowingly executes hostile code that was packaged with additional files that include modified versions of system DLLs, the hostile code could load its own versions of those DLLs and potentially increase the type and degree of damage the code can render.</Vulnerability>
<Countermeasure>Configure the MSS: (SafeDllSearchMode) Enable Safe DLL search mode (recommended) entry to a value of Enabled.
The possible values for this registry entry are:
• 1 or 0. The default configuration for Windows XP is 0 and it is 1 for Windows Server 2003.
In the SCE UI, these options appear as:
• Enabled
• Disabled
• Not Defined
</Countermeasure>
<PotentialImpact>Applications will be forced to search for DLLs in the system path first. For applications that require unique versions of these DLLs that are included with the application, this entry could cause performance or stability problems.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>SYSTEM\CurrentControlSet\Control\Session Manager</mssasc-core:KeyPath>
<mssasc-core:ValueName>SafeDllSearchMode</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SafeDllSearchMode" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:122" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="241" ID="{2bfe6f4b-aee1-47ae-b09e-0e9ecf963804}" OriginalSettingID="{ee0bd6ef-beb7-40aa-be9b-a488aee38686}" Name="Do not adjust default option to 'Install Updates and Shut Down' in Shut Down Windows dialog box" LockdownDate="2011-05-15T05:26:30Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9733-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to manage whether the Install Updates and Shut Down option is displayed in the Shut Down Windows dialog box.</ShortDescription>
<FullDescription>This policy setting allows you to manage whether the 'Install Updates and Shut Down' option is allowed to be the default choice in the Shut Down Windows dialog. Note that this policy setting has no impact if the Computer Configuration\Administrative Templates\Windows Components\Windows Update\Do not display 'Install Updates and Shut Down' option in Shut Down Windows dialog box policy setting is enabled.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Windows Update</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Updates are important for maintaining the ongoing security of a computer, therefore this setting should not be enabled.</Vulnerability>
<Countermeasure>Disable this setting.</Countermeasure>
<PotentialImpact>If you enable this policy setting, the user's last shut down choice (Hibernate, Restart, etc.) is the default option in the Shut Down Windows dialog box, regardless of whether the 'Install Updates and Shut Down' option is available in the 'What do you want the computer to do?' list.
If you disable or do not configure this policy setting, the 'Install Updates and Shut Down' option will be the default option in the Shut Down Windows dialog box if updates are available for installation at the time the user selects the Shut Down option in the Start menu.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows\WindowsUpdate\AU</mssasc-core:KeyPath>
<mssasc-core:ValueName>NoAUAsDefaultShutdownOption</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="AUNoUasDefaultPolicy_Mach" class="Machine" displayName="$(string.ecd824d7ba434e33b780d78de8de2de0)" explainText="$(string.6bb301ebc4e24176a91a85a4363dfadb)" key="Software\Policies\Microsoft\Windows\WindowsUpdate\AU" valueName="NoAUAsDefaultShutdownOption">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="ecd824d7ba434e33b780d78de8de2de0">Do not adjust default option to 'Install Updates and Shut Down' in Shut Down Windows dialog box</string>
<string id="6bb301ebc4e24176a91a85a4363dfadb">This policy setting allows you to manage whether the 'Install Updates and Shut Down' option is allowed to be the default choice in the Shut Down Windows dialog. Note that this policy setting has no impact if the Computer Configuration\Administrative Templates\Windows Components\Windows Update\Do not display 'Install Updates and Shut Down' option in Shut Down Windows dialog box policy setting is enabled.</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional with SP2</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="oval:com.secure-elements.oval:def:6603" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="242" ID="{b95c63bb-db24-4986-a958-b79fb9fb387f}" OriginalSettingID="{c067da7d-80a9-4b00-9414-d98d37139490}" Name="Network access: Shares that can be accessed anonymously" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9196-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which network shares can be accessed by anonymous users. </ShortDescription>
<FullDescription>This policy setting determines which network shares can be accessed by anonymous users. The default configuration for this policy setting has little effect because all users have to be authenticated before they can access shared resources on the server.
Note: It can be very dangerous to add other shares to this Group Policy setting. Any network user can access any shares that are listed, which could exposure or corrupt sensitive data.
Note: When you configure this setting you specify a list of one or more objects. The delimiter used when entering the list is a line feed or carriage return, that is, type the first object on the list, press the Enter button, type the next object, press Enter again, etc. The setting value is stored as a comma-delimited list in group policy security templates. It is also rendered as a comma-delimited list in Group Policy Editor’s display pane and the Resultant Set of Policy console. It is recorded in the registry as a line-feed delimited list in a REG_MULTI_SZ value.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined
</DefaultValue>
<Vulnerability>It is very dangerous to enable this setting. Any shares that are listed can be accessed by any network user, which could lead to the exposure or corruption of sensitive data.</Vulnerability>
<Countermeasure>Configure the Network access: Shares that can be accessed anonymously setting to a null value. </Countermeasure>
<PotentialImpact>There should be little impact because this is the default configuration. Only authenticated users will have access to shared resources on the server.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_MULTI_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Services\LanManServer\Parameters</mssasc-core:KeyPath>
<mssasc-core:ValueName>NullSessionShares</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Multi-String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\NullSessionShares" DataType="REG_MULTI_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:93" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="243" ID="{fc9b9d91-7a18-4238-a20c-1bdca54fd6ad}" OriginalSettingID="{ffdf73aa-bb21-413b-b25c-469871f03fd0}" Name="Turn off Windows Update device driver searching" LockdownDate="2011-10-12T11:38:00Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10093-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting specifies whether Windows will search Windows Update for device drivers when no local drivers for a device are present.</ShortDescription>
<FullDescription>This policy setting specifies whether Windows will search Windows Update for device drivers when no local drivers for a device are present.
Note See also Turn off Windows Update device driver search prompt in Administrative Templates/System, which governs whether an administrator is prompted before Windows Update is searched for device drivers if a driver is not found locally.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Internet Communication Management\Internet Communication settings</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>If users are able to download and install device drivers there is a small chance that they will install a driver that reduces system stability. There is an even smaller possibility that they will install a driver that includes malicious code. These risks are very low because Microsoft requires vendors to test drivers extensively before they can be published on Windows Update. </Vulnerability>
<Countermeasure>To prevent users from retrieving and installing device drivers from Windows Update enable this setting.</Countermeasure>
<PotentialImpact>Users will not be able to download new or updated device drivers from Windows Update.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows\DriverSearching</mssasc-core:KeyPath>
<mssasc-core:ValueName>DontSearchWindowsUpdate</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="DriverSearchPlaces_DontSearchWindowsUpdate" class="Machine" displayName="$(string.076055071c3340d2a01ad55c229547cc)" explainText="$(string.23f1c9ed588c48da97a012e7510a7a44)" key="Software\Policies\Microsoft\Windows\DriverSearching" valueName="DontSearchWindowsUpdate">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="076055071c3340d2a01ad55c229547cc">Turn off Windows Update device driver searching</string>
<string id="23f1c9ed588c48da97a012e7510a7a44">This policy setting specifies whether Windows will search Windows Update for device drivers when no local drivers for a device are present.
Note See also Turn off Windows Update device driver search prompt in Administrative Templates/System, which governs whether an administrator is prompted before Windows Update is searched for device drivers if a driver is not found locally.</string>
</ADMLDefinition>
<supportedOn>Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP SP2</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="244" ID="{a4c51a0e-bcb9-4cb1-88fa-a65e42687eb9}" OriginalSettingID="{e44bb6b6-6bf3-417b-a329-cb9604cde378}" Name="Recovery console: Allow floppy copy and access to all drives and all folders" LockdownDate="2011-05-22T06:55:44Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8945-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting makes the Recovery Console SET command available.</ShortDescription>
<FullDescription>This policy setting makes the Recovery Console SET command available, which allows you to set the following recovery console environment variables:
• AllowWildCards. Enables wildcard support for some commands (such as the DEL command).
• AllowAllPaths. Allows access to all files and folders on the computer.
• AllowRemovableMedia. Allows files to be copied to removable media, such as a floppy disk.
• NoCopyPrompt. Does not prompt when overwriting an existing file.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>An attacker who can cause the system to restart into the Recovery Console could steal sensitive data and leave no audit or access trail.</Vulnerability>
<Countermeasure>Disable the Recovery Console: Allow floppy copy and access to drives and folders setting.</Countermeasure>
<PotentialImpact>Users who have started a server through the Recovery Console and logged in with the built-in Administrator account will not be able to copy files and folders to a floppy disk.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows NT\CurrentVersion\Setup\RecoveryConsole</mssasc-core:KeyPath>
<mssasc-core:ValueName>setcommand</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Setup\RecoveryConsole\setcommand" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:102" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="245" ID="{89e0c392-8039-4a0c-824b-445fc668b123}" OriginalSettingID="{72808c0e-3873-4c91-b9e6-4eba1b90e20f}" Name="Allow Remote Shell Access" LockdownDate="2011-08-17T12:23:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10077-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to manage configuration of remote access to all supported shells to execute scripts and commands.</ShortDescription>
<FullDescription>This policy setting allows you to manage configuration of remote access to all supported shells to execute scripts and commands.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Windows Remote Shell</UIPath>
<DefaultValue>Not Configured</DefaultValue>
<Vulnerability>Any feature is a potential avenue of attack, those that enable inbound network connections are particularly risky. Only enable the use of the Windows Remote Shell on trusted networks and when feasible employ additional controls such as IPsec.</Vulnerability>
<Countermeasure>Configure Allow Remote Shell Access to Disabled.</Countermeasure>
<PotentialImpact>If you enable this policy setting, remote access is allowed to all supported shells to execute scripts and commands. If you disable or do not configure this policy setting, remote access is not allowed to all supported shells to execute scripts and commands.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows\WinRM\Service\WinRS</mssasc-core:KeyPath>
<mssasc-core:ValueName>AllowRemoteShellAccess</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="AllowRemoteShellAccess" class="Machine" displayName="$(string.6267411f0895438c935b83d96cae183a)" explainText="$(string.79827f0567a34dd4b701f295b760d072)" key="Software\Policies\Microsoft\Windows\WinRM\Service\WinRS" valueName="AllowRemoteShellAccess">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="6267411f0895438c935b83d96cae183a">Allow Remote Shell Access</string>
<string id="79827f0567a34dd4b701f295b760d072">This policy setting allows you to manage configuration of remote access to all supported shells to execute scripts and commands.</string>
</ADMLDefinition>
<supportedOn>At least Windows Vista</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="246" ID="{da991e9c-7f16-4f15-ae08-de862d02f061}" OriginalSettingID="{5ce4b236-85aa-4064-89d5-67b86994e059}" Name="Do not display 'Install Updates and Shut Down' option in Shut Down Windows dialog box" LockdownDate="2011-05-02T01:36:00Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9464-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to manage whether the Install Updates and Shut Down option is displayed in the Shut Down Windows dialog box. </ShortDescription>
<FullDescription>This policy setting allows you to manage whether the Install Updates and Shut Down option is displayed in the Shut Down Windows dialog box. This policy setting works in conjunction with the following Do not adjust default option to ‘Install Updates and Shut Down’ in Shut Down Windows Dialog box setting.
</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Windows Update</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Updates are important for maintaining the ongoing security of a computer, therefore this setting should not be enabled.</Vulnerability>
<Countermeasure>Disable this setting.</Countermeasure>
<PotentialImpact>If you disable this policy setting, the Install Updates and Shut Down option will display in the Shut Down Windows dialog box if updates are available when the user selects the Shut Down option in the Start menu.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows\WindowsUpdate\AU</mssasc-core:KeyPath>
<mssasc-core:ValueName>NoAUShutdownOption</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="AUDontShowUasPolicy" class="Machine" displayName="$(string.4421a8c6f5324f13b3b8f5e49394c877)" explainText="$(string.18383f2601d44266816fd3da22e26eb0)" key="Software\Policies\Microsoft\Windows\WindowsUpdate\AU" valueName="NoAUShutdownOption">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="4421a8c6f5324f13b3b8f5e49394c877">Do not display 'Install Updates and Shut Down' option in Shut Down Windows dialog box</string>
<string id="18383f2601d44266816fd3da22e26eb0">This policy setting allows you to manage whether the Install Updates and Shut Down option is displayed in the Shut Down Windows dialog box. This policy setting works in conjunction with the following Do not adjust default option to ‘Install Updates and Shut Down’ in Shut Down Windows Dialog box setting.
</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional with SP2</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="oval:com.secure-elements.oval:def:6602" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="247" ID="{0302bf62-c593-4921-a0ce-8f65012ea8bc}" OriginalSettingID="{2d5369da-937a-4f8c-be9e-3acd79b70585}" Name="Turn off Autoplay" LockdownDate="2011-10-12T11:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9528-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Autoplay starts to read from a drive as soon as you insert media in the drive, which causes the setup file for programs or audio media to start immediately.</ShortDescription>
<FullDescription>Autoplay starts to read from a drive as soon as you insert media in the drive, which causes the setup file for programs or audio media to start immediately. An attacker could use this feature to launch a program to damage the computer or data on the computer. You can enable the Turn off Autoplay setting to disable the Autoplay feature. Autoplay is disabled by default on some removable drive types, such as floppy disk and network drives, but not on CD-ROM drives.
Note You cannot use this policy setting to enable Autoplay on computer drives in which it is disabled by default, such as floppy disk and network drives.
</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\AutoPlay Policies</UIPath>
<DefaultValue>Not Configured</DefaultValue>
<Vulnerability>An attacker could use this feature to launch a program to damage a client computer or data on the computer. </Vulnerability>
<Countermeasure>Configure the Turn off Autoplay setting to Enabled.</Countermeasure>
<PotentialImpact>Users will have to manually launch setup or installation programs that are provided on removable media. </PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine" />
<DataType>String</DataType>
</DiscoveryInfo>
<policy name="Autorun" class="Machine" displayName="$(string.f621b48283784c5a800d50bf6e68de70)" explainText="$(string.fe70f1a26d3a4646a33b594b8f9ac90f)" presentation="$(presentation.Autorun)" key="Software\Microsoft\Windows\CurrentVersion\Policies\Explorer">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:elements xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:enum id="Autorun_Box" key="Software\Microsoft\Windows\CurrentVersion\Policies\Explorer" valueName="NoDriveTypeAutoRun">
<admx:item displayName="$(string.4dd6aa8f6ea8406f8a07952cde47952c)">
<admx:value>
<admx:decimal value="181" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.d97da86453d5448fbe2cbc4ff0b031cc)">
<admx:value>
<admx:decimal value="255" />
</admx:value>
</admx:item>
</admx:enum>
</admx:elements>
</policy>
<ADMLDefinition>
<presentation id="Autorun">
<admx:dropdownList refId="Autorun_Box" defaultItem="0" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Turn off Autoplay on:</admx:dropdownList>
</presentation>
<string id="f621b48283784c5a800d50bf6e68de70">Turn off Autoplay</string>
<string id="fe70f1a26d3a4646a33b594b8f9ac90f">Autoplay starts to read from a drive as soon as you insert media in the drive, which causes the setup file for programs or audio media to start immediately. An attacker could use this feature to launch a program to damage the computer or data on the computer. You can enable the Turn off Autoplay setting to disable the Autoplay feature. Autoplay is disabled by default on some removable drive types, such as floppy disk and network drives, but not on CD-ROM drives.
Note You cannot use this policy setting to enable Autoplay on computer drives in which it is disabled by default, such as floppy disk and network drives.
</string>
<string id="4dd6aa8f6ea8406f8a07952cde47952c">CD-ROM and removable media drives</string>
<string id="d97da86453d5448fbe2cbc4ff0b031cc">All drives</string>
</ADMLDefinition>
<supportedOn>At least Windows 2000</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="248" ID="{2e85f56e-6fb1-4b46-a0e5-4457834dbf81}" OriginalSettingID="{107f578e-ad55-4bf9-b108-a6477bb35892}" Name="Network access: Allow anonymous SID/Name translation" LockdownDate="2011-06-02T12:12:36Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9531-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether an anonymous user can request security identifier (SID) attributes for another user, or use a SID to obtain its corresponding user name. </ShortDescription>
<FullDescription>This policy setting determines whether an anonymous user can request security identifier (SID) attributes for another user, or use a SID to obtain its corresponding user name. Disable this policy setting to prevent unauthenticated users from obtaining user names that are associated with their respective SIDs.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>If this policy setting is enabled, a user with local access could use the well-known Administrator's SID to learn the real name of the built-in Administrator account, even if it has been renamed. That person could then use the account name to initiate a password guessing attack.</Vulnerability>
<Countermeasure>Configure the Network access: Allow anonymous SID/Name translation setting to Disabled.</Countermeasure>
<PotentialImpact>Disabled is the default configuration for this policy setting on member computers; therefore it will have no impact on them. The default configuration for domain controllers is Enabled. If you disable this policy setting on domain controllers, legacy computers may be unable to communicate with Windows Server 2003–based domains. For example, the following computers may not work:
• Windows NT 4.0–based Remote Access Service servers.
• Microsoft SQL Servers™ that run on Windows NT 3.x–based or Windows NT 4.0–based computers.
• Remote Access Service or Microsoft SQL servers that run on Windows 2000–based computers and are located in Windows NT 3.x domains or Windows NT 4.0 domains.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="False" />
<SCAPValue ValueA="False" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="True" />
<SCAPValue ValueA="True" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="WMI" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_SecuritySettingBoolean</mssasc-core:Class>
<mssasc-core:Property>Setting</mssasc-core:Property>
<mssasc-core:Where>KeyName='LSAAnonymousNameLookup' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="System Access" Name="LSAAnonymousNameLookup" DataType="WMI_Boolean" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="249" ID="{6d2333d9-7ed1-4b8a-a438-472c326e31b9}" OriginalSettingID="{1089fb91-5c2d-4e57-ad7a-17842fecadc9}" Name="Offer Remote Assistance" LockdownDate="2011-10-12T11:37:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9960-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether an IT support person can offer remote assistance to fix issues on computers in your environment without explicit user requests.</ShortDescription>
<FullDescription>This policy setting determines whether a support person or an IT "expert" administrator can offer remote assistance to computers in your environment if a user does not explicitly request assistance first through a channel, such as e-mail, or Instant Messenger.
Note The expert cannot connect to the computer unannounced or control it without permission from the user. When the expert tries to connect, the user can still choose to deny the connection or give the expert view-only privileges. The user must explicitly click the Yes button to allow the expert to remotely control the workstation after the Offer Remote Assistance setting is configured to Enabled.
If this policy setting is enabled the following options are available:
• Allow helpers to only view the computer
• Allow helpers to remotely control the computer
When you configure this policy setting, you can also specify a list of users or user groups known as "helpers" who may offer remote assistance.
To configure the list of helpers
1. In the Offer Remote Assistance setting configuration window, click Show. A new window will open in which you can enter helper names.
2. Add each user or group to the Helper list in one of the following formats:
• <Domain Name>\<User Name>
• <Domain Name>\<Group Name>
If this policy setting is disabled or not configured, users and or groups will not be able to offer unsolicited remote assistance to computer users in your environment.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Remote Assistance</UIPath>
<DefaultValue>Disabled
</DefaultValue>
<Vulnerability>A user might be tricked and accept an unsolicited Remote Assistance offer from a malicious user.</Vulnerability>
<Countermeasure>Configure the Offer Remote Assistance setting to Disabled. </Countermeasure>
<PotentialImpact>Help desk and support personnel will not be able to proactively offer assistance, although they can still respond to user assistance requests.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\policies\Microsoft\Windows NT\Terminal Services</mssasc-core:KeyPath>
<mssasc-core:ValueName>fAllowUnsolicited</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="RA_Unsolicit" class="Machine" displayName="$(string.RA_Unsolicit)" explainText="$(string.RA_Unsolicit_Help)" presentation="$(presentation.RA_Unsolicit)" key="Software\policies\Microsoft\Windows NT\Terminal Services" valueName="fAllowUnsolicited">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
<admx:elements xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:enum id="RA_Unsolicit_Control_List" key="Software\policies\Microsoft\Windows NT\Terminal Services" valueName="fAllowUnsolicitedFullControl">
<admx:item displayName="$(string.RA_Unsolicit_Control_Ctrl)">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
<admx:item displayName="$(string.RA_Unsolicit_Control_View)">
<admx:value>
<admx:decimal value="0" />
</admx:value>
</admx:item>
</admx:enum>
<admx:list id="RA_Unsolicit_DACL_Edit" key="Software\policies\Microsoft\Windows NT\Terminal Services\RAUnsolicit" />
</admx:elements>
</policy>
<ADMLDefinition>
<presentation id="RA_Unsolicit">
<admx:dropdownList refId="RA_Unsolicit_Control_List" noSort="true" defaultItem="0" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Permit remote control of this computer:</admx:dropdownList>
<admx:listBox refId="RA_Unsolicit_DACL_Edit" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Helpers:</admx:listBox>
</presentation>
<string id="RA_Unsolicit">Offer Remote Assistance</string>
<string id="RA_Unsolicit_Help">This policy setting determines whether a support person or an IT "expert" administrator can offer remote assistance to computers in your environment if a user does not explicitly request assistance first through a channel, such as e-mail, or Instant Messenger.
Note The expert cannot connect to the computer unannounced or control it without permission from the user. When the expert tries to connect, the user can still choose to deny the connection or give the expert view-only privileges. The user must explicitly click the Yes button to allow the expert to remotely control the workstation after the Offer Remote Assistance setting is configured to Enabled.
If this policy setting is enabled the following options are available:
• Allow helpers to only view the computer
• Allow helpers to remotely control the computer
When you configure this policy setting, you can also specify a list of users or user groups known as "helpers" who may offer remote assistance.
To configure the list of helpers
1. In the Offer Remote Assistance setting configuration window, click Show. A new window will open in which you can enter helper names.
2. Add each user or group to the Helper list in one of the following formats:
• <Domain Name>\<User Name>
• <Domain Name>\<Group Name>
If this policy setting is disabled or not configured, users and or groups will not be able to offer unsolicited remote assistance to computer users in your environment.</string>
<string id="RA_Unsolicit_Control_Ctrl">Allow helpers to remotely control the computer</string>
<string id="RA_Unsolicit_Control_View">Allow helpers to only view the computer</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional or Windows Server 2003 family</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="250" ID="{7636eb85-a48a-4d53-bde7-78ef0f9ab377}" OriginalSettingID="{1b4d4248-73f1-4950-be5c-8c2fd6d47002}" Name="Recovery console: Allow automatic administrative logon" LockdownDate="2011-05-02T01:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8807-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows the administrator account to automatically log on to the recovery console when it is invoked during startup.</ShortDescription>
<FullDescription>The recovery console is a command-line environment that is used to recover from system problems. If you enable this policy setting, the administrator account is automatically logged on to the recovery console when it is invoked during startup.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>The Recovery Console can be very useful when you need to troubleshoot and repair computers that do not start. However, it is dangerous to allow automatic logon to the console. Anyone could walk up to the server, disconnect the power to shut it down, restart it, select Recover Console from the Restart menu, and then assume full control of the server.</Vulnerability>
<Countermeasure>Disable the Recovery Console: Allow automatic administrative logon setting.</Countermeasure>
<PotentialImpact>Users will have to enter a user name and password to access the Recovery Console.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows NT\CurrentVersion\Setup\RecoveryConsole</mssasc-core:KeyPath>
<mssasc-core:ValueName>securitylevel</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Setup\RecoveryConsole\securitylevel" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:101" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="251" ID="{93993ea8-cf22-4784-a39e-4337190e71ec}" OriginalSettingID="{6e47e304-7197-4791-b16d-9a6ad3306ad4}" Name="System settings: Use Certificate Rules on Windows Executables for Software Restriction Policies" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9112-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether digital certificates are processed when software restriction policies are enabled and a user or process attempts to run software with an .exe file name extension. </ShortDescription>
<FullDescription>This policy setting determines whether digital certificates are processed when software restriction policies are enabled and a user or process attempts to run software with an .exe file name extension. It enables or disables certificate rules (a type of software restriction policies rule). With software restriction policies, you can create a certificate rule that will allow or disallow the execution of Authenticode®-signed software, based on the digital certificate that is associated with the software. For certificate rules to take effect in software restriction policies, you must enable this policy setting.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Software restriction policies help to protect users and computers because they can prevent the execution of unauthorized code, such as viruses and Trojans horses.</Vulnerability>
<Countermeasure>Configure the System settings: Use Certificate Rules on Windows Executables for Software Restriction Policies setting to Enabled.</Countermeasure>
<PotentialImpact>If you enable certificate rules, software restriction policies check a certificate revocation list (CRL) to ensure that the software’s certificate and signature are valid. This checking process may negatively affect performance when signed programs start. To disable this feature you can edit the software restriction policies in the desired GPO. On the Trusted Publishers Properties dialog box, clear the Publisher and Timestamp check boxes.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows\Safer\CodeIdentifiers</mssasc-core:KeyPath>
<mssasc-core:ValueName>AuthenticodeEnabled</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Policies\Microsoft\Windows\Safer\CodeIdentifiers\AuthenticodeEnabled" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="252" ID="{49302c49-5309-4506-b042-c99447402034}" OriginalSettingID="{4adb8423-aed2-48e0-b5f1-83ec297b68a7}" Name="Devices: Restrict CD-ROM access to locally logged-on user only" LockdownDate="2011-10-12T11:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9304-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether a CD-ROM is accessible to both local and remote users simultaneously.</ShortDescription>
<FullDescription>This policy setting determines whether a CD-ROM is accessible to both local and remote users simultaneously. If you enable this policy setting, only the interactively logged-on user is allowed to access removable CD-ROM media. When this policy setting is enabled and no one is logged on interactively, the CD-ROM is accessible over the network.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined
</DefaultValue>
<Vulnerability>A remote user could potentially access a mounted CD that contains sensitive information. This risk is small, because CD drives are not automatically made available as shared drives; administrators must deliberately choose to share the drive. However, administrators may wish to deny network users the ability to view data or run applications from removable media on the server.</Vulnerability>
<Countermeasure>Enable the Restrict CD-ROM drive access to locally logged-on user only setting.</Countermeasure>
<PotentialImpact>Users who connect to the server over the network will not be able to use any CD drives that are installed on the server whenever anyone is logged on to the local console of the server. System tools that require access to the CD drive will fail. For example, the Volume Shadow Copy service attempts to access all CD and floppy disk drives that are present on the computer when it initializes, and if the service cannot access one of these drives, it will fail. This condition will cause the Windows Backup tool to fail if volume shadow copies were specified for the backup job. Any non-Microsoft backup products that use volume shadow copies will also fail. This policy setting would not be suitable for a computer that serves as a CD jukebox for network users.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows NT\CurrentVersion\Winlogon</mssasc-core:KeyPath>
<mssasc-core:ValueName>AllocateCDRoms</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\AllocateCDRoms" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:102" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="253" ID="{f201f6ca-cafa-455d-bc30-62354cad5714}" OriginalSettingID="{fd4fd37a-e183-4b7d-ae62-14f1c7cbf2d0}" Name="Specify intranet Microsoft update service location" LockdownDate="2011-05-15T05:26:31Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-15883-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to specify an intranet server to host updates from the Microsoft Update Web site. </ShortDescription>
<FullDescription>This policy setting allows you to specify an intranet server to host updates from the Microsoft Update Web site. You can then use this update service location to automatically update computers on your network. The Automatic Updates client will search this service for updates that apply to the computers on your network.
To use the Specify intranet Microsoft update service location setting, you must set two server name values: the server from which the Automatic Updates client detects and downloads updates, and the server to which updated workstations upload statistics. You can set both values to be the same server.
If you enable the Specify intranet Microsoft update service location setting, the Automatic Updates client will connect to the specified intranet Microsoft update service server (instead of Windows Update) to search for and download updates. This configuration allows end users in your organization to avoid firewall issues, and provides you with an opportunity to test updates before you deploy them. If you disable or do not configure this policy setting, the Automatic Updates client will connect directly to the Windows Update site on the Internet (if Automatic Updates is not disabled by Group Policy or user preference).
</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Windows Update</UIPath>
<DefaultValue>Disabled </DefaultValue>
<Vulnerability>By default, Automatic Updates will attempt to download updates from the Microsoft Windows Update Web site. Some organizations want to verify that all new updates are compatible with their particular environment before they are deployed. Also, if you configure an internal Software Update Services (SUS) server you will help reduce the load on perimeter firewalls, routers, and proxy servers, as well as the load on external network links.</Vulnerability>
<Countermeasure>Configure the Specify intranet Microsoft update service location setting to Enabled. Then specify the intranet update server's name and the statistics server's name in the Properties dialog box.</Countermeasure>
<PotentialImpact>Critical updates and service packs will have to be proactively managed by the organization's IT staff.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine" />
<DataType>String</DataType>
</DiscoveryInfo>
<policy name="CorpWuURL" class="Machine" displayName="$(string.fcd60f7949f04a569165ace492397ce8)" explainText="$(string.384849141cb846df8eb6530a87abdbf2)" presentation="$(presentation.CorpWuURL)" key="Software\Policies\Microsoft\Windows\WindowsUpdate">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledList xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:item key="Software\Policies\Microsoft\Windows\WindowsUpdate\AU" valueName="UseWUServer">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
</admx:enabledList>
<admx:disabledList xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:item key="Software\Policies\Microsoft\Windows\WindowsUpdate\AU" valueName="UseWUServer">
<admx:value>
<admx:decimal value="0" />
</admx:value>
</admx:item>
</admx:disabledList>
<admx:elements xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:text id="CorpWUURL_Name" key="Software\Policies\Microsoft\Windows\WindowsUpdate" valueName="WUServer" />
<admx:text id="CorpWUStatusURL_Name" key="Software\Policies\Microsoft\Windows\WindowsUpdate" valueName="WUStatusServer" />
</admx:elements>
</policy>
<ADMLDefinition>
<presentation id="CorpWuURL">
<admx:textBox refId="CorpWUURL_Name" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:label>Set the intranet update service for detecting updates:</admx:label>
<admx:defaultValue />
</admx:textBox>
<admx:textBox refId="CorpWUStatusURL_Name" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:label>Set the intranet statistics server:</admx:label>
<admx:defaultValue />
</admx:textBox>
<admx:text xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">(example: http://IntranetUpd01)</admx:text>
</presentation>
<string id="fcd60f7949f04a569165ace492397ce8">Specify intranet Microsoft update service location</string>
<string id="384849141cb846df8eb6530a87abdbf2">This policy setting allows you to specify an intranet server to host updates from the Microsoft Update Web site. You can then use this update service location to automatically update computers on your network. The Automatic Updates client will search this service for updates that apply to the computers on your network.
To use the Specify intranet Microsoft update service location setting, you must set two server name values: the server from which the Automatic Updates client detects and downloads updates, and the server to which updated workstations upload statistics. You can set both values to be the same server.
If you enable the Specify intranet Microsoft update service location setting, the Automatic Updates client will connect to the specified intranet Microsoft update service server (instead of Windows Update) to search for and download updates. This configuration allows end users in your organization to avoid firewall issues, and provides you with an opportunity to test updates before you deploy them. If you disable or do not configure this policy setting, the Automatic Updates client will connect directly to the Windows Update site on the Internet (if Automatic Updates is not disabled by Group Policy or user preference).
</string>
</ADMLDefinition>
<supportedOn>At least Windows 2000 Service Pack 3 or Windows XP Professional Service Pack 1</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="254" ID="{dd6bf205-5777-4c03-89fb-7a825a2955ab}" OriginalSettingID="{666f7df6-e8c1-4703-8cd1-3a367d445a8a}" Name="Turn off Internet download for Web publishing and online ordering wizards" LockdownDate="2011-10-12T11:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9674-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Setting controls whether Windows will download a list of providers for the Web publishing and online ordering wizards.</ShortDescription>
<FullDescription>This policy setting controls whether Windows will download a list of providers for the Web publishing and online ordering wizards.
</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\System\Internet Communication Management\Internet Communication settings</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>Although the risk is minimal, enabling this setting will reduce the possibility of a user unknowingly downloading malicious content through this feature.</Vulnerability>
<Countermeasure>Enable this setting</Countermeasure>
<PotentialImpact>If this policy setting is enabled, Windows is prevented from downloading providers; only the service providers cached in the local registry will display.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\Explorer</mssasc-core:KeyPath>
<mssasc-core:ValueName>NoWebServices</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<policy name="ShellPreventWPWDownload_2" class="Machine" displayName="$(string.4077a05f702045f499d368102d29a583)" explainText="$(string.f2eef154b3a14b189acfc04548e3ca6a)" key="Software\Microsoft\Windows\CurrentVersion\Policies\Explorer" valueName="NoWebServices">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="1" />
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal value="0" />
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="4077a05f702045f499d368102d29a583">Turn off Internet download for Web publishing and online ordering wizards</string>
<string id="f2eef154b3a14b189acfc04548e3ca6a">This policy setting controls whether Windows will download a list of providers for the Web publishing and online ordering wizards.
</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional with SP2 or Windows Server 2003 family</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="255" ID="{e0c28680-3712-4177-914c-d0ce0efa226b}" OriginalSettingID="{9c88cdfc-58ad-4666-9e8a-d84099d42fdd}" Name="Network access: Remotely accessible registry paths and sub-paths" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9386-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which registry paths and sub-paths will be accessible when an application or process references the WinReg key to determine access permissions.</ShortDescription>
<FullDescription>This policy setting determines which registry paths and sub-paths will be accessible when an application or process references the WinReg key to determine access permissions.
Note: In Windows XP this setting is called "Network access: Remotely accessible registry paths," the setting with that same name in Windows Vista, Windows Server 2008, and Windows Server 2003 does not exist in Windows XP.
Note: When you configure this setting you specify a list of one or more objects. The delimiter used when entering the list is a line feed or carriage return, that is, type the first object on the list, press the Enter button, type the next object, press Enter again, etc. The setting value is stored as a comma-delimited list in group policy security templates. It is also rendered as a comma-delimited list in Group Policy Editor’s display pane and the Resultant Set of Policy console. It is recorded in the registry as a line-feed delimited list in a REG_MULTI_SZ value.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>System\CurrentControlSet\Control\Print\Printers,System\CurrentControlSet\Services\Eventlog,Software\Microsoft\OLAP Server,Software\Microsoft\Windows NT\CurrentVersion\Print,Software\Microsoft\Windows NT\CurrentVersion\Windows,System\CurrentControlSet\Control\ContentIndex,System\CurrentControlSet\Control\Terminal Server,System\CurrentControlSet\Control\Terminal Server\UserConfig,System\CurrentControlSet\Control\Terminal Server\DefaultUserConfiguration,Software\Microsoft\Windows NT\CurrentVersion\Perflib,System\CurrentControlSet\Services\SysmonLog
</DefaultValue>
<Vulnerability>The registry contains sensitive computer configuration information that could be used by an attacker to facilitate unauthorized activities. The fact that the default ACLs assigned throughout the registry are fairly restrictive and help to protect the registry from access by unauthorized users reduces the risk of such an attack.</Vulnerability>
<Countermeasure>Configure the Network access: Remotely accessible registry paths and sub-paths setting to a null value (enable the setting but do not enter any paths in the text box). </Countermeasure>
<PotentialImpact>Remote management tools such as the Microsoft Baseline Security Analyzer and Microsoft Systems Management Server require remote access to the registry to properly monitor and manage those computers. If you remove the default registry paths from the list of accessible ones, such remote management tools could fail.
Note: If you want to allow remote access, you must also enable the Remote Registry service.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_MULTI_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\SecurePipeServers\Winreg\AllowedPaths</mssasc-core:KeyPath>
<mssasc-core:ValueName>Machine</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Multi-String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\SecurePipeServers\Winreg\AllowedPaths\Machine" DataType="REG_MULTI_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="256" ID="{fc736f51-ff9d-48ed-8d0c-c510112b7589}" OriginalSettingID="{fbfb6cc4-d294-4884-bc3d-7f74deeb6462}" Name="Network access: Do not allow anonymous enumeration of SAM accounts and shares" LockdownDate="2011-05-02T01:36:03Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9156-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting controls the ability of anonymous users to enumerate SAM accounts as well as shares.</ShortDescription>
<FullDescription>This policy setting controls the ability of anonymous users to enumerate SAM accounts as well as shares. If you enable this policy setting, anonymous users will not be able to enumerate domain account user names and network share names on the workstations in your environment.
The Network access: Do not allow anonymous enumeration of SAM accounts and shares setting is configured to Enabled for the two environments that are discussed in this guide.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>An unauthorized user could anonymously list account names and shared resources and use the information to attempt to guess passwords or perform social engineering attacks.</Vulnerability>
<Countermeasure>Configure the Network access: Do not allow anonymous enumeration of SAM accounts and shares setting to Enabled. </Countermeasure>
<PotentialImpact>It will be impossible to grant access to users of another domain across a one-way trust because administrators in the trusting domain will be unable to enumerate lists of accounts in the other domain. Users who access file and print servers anonymously will be unable to list the shared network resources on those servers; the users will have to authenticate before they can view the lists of shared folders and printers.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>RestrictAnonymous</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\RestrictAnonymous" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:88" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="257" ID="{e17e8f70-2ed6-4cd9-98f5-a402eb36a774}" OriginalSettingID="{d5d37567-6f6c-4b86-a13a-d10b708432dc}" Name="Devices: Allow undock without having to log on" LockdownDate="2011-05-22T05:41:36Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8837-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether a portable computer can be undocked if the user does not log on to the system.</ShortDescription>
<FullDescription>This policy setting determines whether a portable computer can be undocked if the user does not log on to the system. Enable this policy setting to eliminate a Logon requirement and allow use of an external hardware eject button to undock the computer. If you disable this policy setting, a user must log on and have been assigned the Remove computer from docking station user right to undock the computer.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Enabled</DefaultValue>
<Vulnerability>If this policy setting is enabled, anyone with physical access to portable computers in docking stations could remove them and possibly tamper with them. </Vulnerability>
<Countermeasure>Disable the Devices: Allow undock without having to log on setting.</Countermeasure>
<PotentialImpact>Users who have docked their computers will have to log on to the local console before they can undock their computers. For computers that do not have docking stations, this policy setting will have no impact.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>undockwithoutlogon</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\UndockWithoutLogon" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:53" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="258" ID="{10130ac4-30f6-40f0-b85e-c078a7ccbcf9}" OriginalSettingID="{c95a7fc1-5250-4494-9b94-3f3301b8ae7f}" Name="MSS: (NtfsDisable8dot3NameCreation) Enable the computer to stop generating 8.3 style filenames" LockdownDate="2011-08-05T08:12:53Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8784-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This registry value entry appears as MSS: (NtfsDisable8dot3NameCreation) Enable the computer to stop generating 8.3 style filenames in the SCE.</ShortDescription>
<FullDescription>Windows Server operating systems support 8.3 file name formats for backward compatibility with16-bit applications. The 8.3 file name convention is a naming format that allows file names up to eight characters long.
The registry value entry NtfsDisable8dot3NameCreation was added to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\FileSystem\ registry key. The entry appears as MSS: (NtfsDisable8dot3NameCreation) Enable the computer to stop generating 8.3 style filenames in the SCE.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>
</Vulnerability>
<Countermeasure>Configure the MSS: (NtfsDisable8dot3NameCreation) Enable the computer to stop generating 8.3 style filenames (recommended) entry to a value of Enabled.
The possible values for this registry entry are:
• 1 or 0. The default configuration is 0 (disabled).
In the SCE UI, these options appear as:
• Enabled
• Disabled
• Not Defined
Updated values are available for this registry entry in Windows 7 and Windows Server 2008 R2:
The possible values for this registry entry are:
• 0, 1, 2, 3. The default configuration is 2.
In the SCM UI, these options appear as:
• Enable 8dot3 name creation on all volumes
• Disable 8dot3 name creation on all volumes
• Set 8dot3 name creation per volume using FSUtil (Windows 7 or later)
• Disable 8dot 3 name creation on all volumes except system volume (Windows 7 or later)
</Countermeasure>
<PotentialImpact>The 16-bit applications in your organization will not be able to access files that are not named with the 8.3 format. Some 32-bit applications also rely on the presence of short names, because short names tend not to contain embedded spaces and therefore do not require quotation marks when used in command lines. The installation routines for some programs may fail; those that are designed to run on multiple CPU architectures are likely to be 16-bit applications. The installation of Exchange 2000 SP2 will fail if this entry is enabled. The installation of service packs for SQL 2000 will fail if this entry is enabled and the path for the system variable %temp% includes a space; a simple workaround for this problem is to redefine the variable to a path without spaces (for example, C:\temp).
Note: If you apply this entry to a server that already has files with auto-generated 8.3 file names, it does not remove them. To remove existing 8.3 file names, you will need to copy those files off the server, delete the files from the original location, and then copy the files back to their original locations.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Enable 8dot3 name creation on all volumes">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Disable 8dot3 name creation on all volumes">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
<Mapping FriendlyName="Set 8dot3 name creation per volume using FSUtil (Windows 7 or later)">
<BehaviorDescription />
<DCMValue ValueA="2" />
<SCAPValue ValueA="2" />
<GPOValue ValueA="2" />
</Mapping>
<Mapping FriendlyName="Disable 8dot3 name creation on all volumes except system volume (Windows 7 or later)">
<BehaviorDescription />
<DCMValue ValueA="3" />
<SCAPValue ValueA="3" />
<GPOValue ValueA="3" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\FileSystem</mssasc-core:KeyPath>
<mssasc-core:ValueName>NtfsDisable8dot3NameCreation</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:119" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="259" ID="{5c7a5f8a-467c-407a-a240-385c40907929}" OriginalSettingID="{ab05b768-9c4c-4ff7-a22b-45af430607a8}" Name="Network access: Remotely accessible registry paths" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9121-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which registry paths will be accessible after referencing the WinReg key to determine access permissions to the paths.</ShortDescription>
<FullDescription>This policy setting determines which registry paths will be accessible after referencing the WinReg key to determine access permissions to the paths.
Note: This setting does not exist in Windows XP. There was a setting with that name in Windows XP, but it is called "Network access: Remotely accessible registry paths and subpaths" in Windows Server 2003, Windows Vista, and Windows Server 2008.
Note: When you configure this setting you specify a list of one or more objects. The delimiter used when entering the list is a line feed or carriage return, that is, type the first object on the list, press the Enter button, type the next object, press Enter again, etc. The setting value is stored as a comma-delimited list in group policy security templates. It is also rendered as a comma-delimited list in Group Policy Editor’s display pane and the Resultant Set of Policy console. It is recorded in the registry as a line-feed delimited list in a REG_MULTI_SZ value.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>System\CurrentControlSet\Control\ProductOptions,System\CurrentControlSet\Control\Server Applications,Software\Microsoft\Windows NT\CurrentVersion
</DefaultValue>
<Vulnerability>The registry is a database that contains computer configuration information, and much of the information is sensitive. An attacker could use this information to facilitate unauthorized activities. To reduce the risk of such an attack, suitable ACLs are assigned throughout the registry to help protect it from access by unauthorized users.</Vulnerability>
<Countermeasure>Configure the Network access: Remotely accessible registry paths setting to a null value (enable the setting but do not enter any paths in the text box).</Countermeasure>
<PotentialImpact>Remote management tools such as the Microsoft Baseline Security Analyzer and Microsoft Systems Management Server require remote access to the registry to properly monitor and manage those computers. If you remove the default registry paths from the list of accessible ones, such remote management tools could fail.
Note: If you want to allow remote access, you must also enable the Remote Registry service.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_MULTI_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\SecurePipeServers\Winreg\AllowedExactPaths</mssasc-core:KeyPath>
<mssasc-core:ValueName>Machine</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Multi-String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\SecurePipeServers\Winreg\AllowedExactPaths\Machine" DataType="REG_MULTI_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:92" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Comment>
</Comment>
</SettingGroup>
<SettingGroup ID="{080b548f-965b-409d-ba48-f9d7046da4f1}" Name="Least Privilege" OriginalSettingGroupID="{799d218c-e436-444f-97e0-32db954665e2}">
<mssasc-core:Description>
</mssasc-core:Description>
<mssasc-core:Version Major="1" Minor="0" />
<Author>
</Author>
<Setting Index="260" ID="{68bf7f2a-0937-4d22-a966-730c358209e4}" OriginalSettingID="{16e53e79-5879-477f-a7ea-2b4cd0fff5ba}" Name="Deny log on as a service" LockdownDate="2011-10-12T11:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9098-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether services can be launched in the context of the specified account.</ShortDescription>
<FullDescription>This security setting determines which service accounts are prevented from registering a process as a service. This policy setting supersedes the Log on as a service policy setting if an account is subject to both policies.Note: This security setting does not apply to the System, Local Service, or Network Service accounts.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>No one</DefaultValue>
<Vulnerability>Accounts that can log on as a service could be used to configure and start new unauthorized services, such as a keylogger or other malicious software. The benefit of the specified countermeasure is somewhat reduced by the fact that only users with administrative privileges can install and configure services, and an attacker who has already attained that level of access could configure the service to run with the System account.</Vulnerability>
<Countermeasure>We recommend that you not assign the Deny log on as a service user right to any accounts, which is the default configuration. Organizations that are extremely concerned about security may wish to assign this user right to groups and accounts that they are certain will never need to log on as a service.</Countermeasure>
<PotentialImpact>If you assign the Deny log on as a service user right to specific accounts, services may not be able to start and a DoS condition could result.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeDenyServiceLogonRight' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeDenyServiceLogonRight" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="261" ID="{1a4f18a5-e3d9-4d4c-bebf-32351b0d6d67}" OriginalSettingID="{4e63307f-262d-4242-8210-c7753d029bef}" Name="Load and unload device drivers" LockdownDate="2011-05-02T01:36:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9135-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows users to dynamically load a new device driver on a system. </ShortDescription>
<FullDescription>This policy setting allows users to dynamically load a new device driver on a system. An attacker could potentially use this capability to install malicious code that appears to be a device driver. This user right is required for users to add local printers or printer drivers in Windows Vista.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators</DefaultValue>
<Vulnerability>Device drivers run as highly privileged code. A user who has the Load and unload device drivers user right could unintentionally install malicious code that masquerades as a device driver. Administrators should exercise greater care and install only drivers with verified digital signatures.</Vulnerability>
<Countermeasure>Do not assign the Load and unload device drivers user right to any user or group other than Administrators on member servers. On domain controllers, do not assign this user tight to any user or group other than Domain Admins.</Countermeasure>
<PotentialImpact>If you remove the Load and unload device drivers user right from the Print Operators group or other accounts you could limit the abilities of users who are assigned to specific administrative roles in your environment. You should ensure that delegated tasks will not be negatively affected.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeLoadDriverPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeLoadDriverPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:183" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="262" ID="{54e4bdd4-cb65-4ab3-a011-07ce073873c8}" OriginalSettingID="{863d4d9b-d8d9-47f6-949e-061df292fea5}" Name="Log on as a batch job" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9320-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows accounts to log on using the task scheduler service.</ShortDescription>
<FullDescription>This policy setting allows accounts to log on using the task scheduler service. Because the task scheduler is often used for administrative purposes, it may be needed in enterprise environments. However, its use should be restricted in high security environments to prevent misuse of system resources or to prevent attackers from using the right to launch malicious code after gaining user level access to a computer.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators, Backup Operators,Performance Log Users
</DefaultValue>
<Vulnerability>The Log on as a batch job user right presents a low-risk vulnerability. For most organizations, the default settings are sufficient.</Vulnerability>
<Countermeasure>You should allow the computer to manage this logon right automatically if you want to allow scheduled tasks to run for specific user accounts. If you do not want to use the Task Scheduler in this manner, configure the Log on as a batch job user right for only the Local Service account and the local support account (Support_388945a0). For IIS servers, you should configure this policy locally instead of through domain–based Group Policies so that you can ensure that the local IUSR_<ComputerName> and IWAM_<ComputerName> accounts have this logon right.</Countermeasure>
<PotentialImpact>If you configure the Log on as a batch job setting through domain–based Group Policies, the computer will not be able to assign the user right to accounts that are used for scheduled jobs in the Task Scheduler. If you install optional components such as ASP.NET or IIS, you might need to assign this user right to additional accounts that are required by those components. For example, IIS requires assignment of this user right to the IIS_WPG group and the IUSR_<ComputerName>, ASPNET, and IWAM_<ComputerName> accounts. If this user right is not assigned o this group and these accounts, IIS will be unable to run some COM objects that are necessary for proper functionality.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeBatchLogonRight' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeBatchLogonRight" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:176" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="263" ID="{0183e5be-9bb3-41a0-b7d6-45611f6b1aa1}" OriginalSettingID="{87691f9f-e18e-42c3-ac3c-621c7b30bdda}" Name="Impersonate a client after authentication" LockdownDate="2011-06-01T05:17:45Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8467-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The policy setting allows programs that run on behalf of a user to impersonate that user (or another specified account) so that they can act on behalf of the user.</ShortDescription>
<FullDescription>The policy setting allows programs that run on behalf of a user to impersonate that user (or another specified account) so that they can act on behalf of the user. If this user right is required for this kind of impersonation, an unauthorized user will not be able to convince a client to connect—for example, by remote procedure call (RPC) or named pipes—to a service that they have created to impersonate that client, which could elevate the unauthorized user's permissions to administrative or system levels.
Services that are started by the Service Control Manager have the built-in Service group added by default to their access tokens. COM servers that are started by the COM infrastructure and configured to run under a specific account also have the Service group added to their access tokens. As a result, these processes are assigned this user right when they are started.
Also, a user can impersonate an access token if any of the following conditions exist:
• The access token that is being impersonated is for this user.
• The user, in this logon session, logged on to the network with explicit credentials to create the access token.
• The requested level is less than Impersonate, such as Anonymous or Identify.
An attacker with the Impersonate a client after authentication user right could create a service, trick a client to make them connect to the service, and then impersonate that client to elevate the attacker's level of access to that of the client.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators, SERVICE, Local Service, Network Service</DefaultValue>
<Vulnerability>An attacker with the Impersonate a client after authentication user right could create a service, trick a client to make them connect to the service, and then impersonate that client to elevate the attacker's level of access to that of the client.</Vulnerability>
<Countermeasure>On member servers, ensure that only the Administrators and Service groups have the Impersonate a client after authentication user right assigned to them. Computers that run IIS 6.0 must have this user right assigned to the IIS_WPG group (which grants it to the Network Service account).</Countermeasure>
<PotentialImpact>In most cases this configuration will have no impact. If you have installed optional components such as ASP.NET or IIS, you may need to assign the Impersonate a client after authentication user right to additional accounts that are required by those components, such as IUSR_<ComputerName>, IIS_WPG, ASP.NET or IWAM_<ComputerName>.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeImpersonatePrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeImpersonatePrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="264" ID="{8bf58466-78a7-4a7d-a15d-55393ef8f619}" OriginalSettingID="{44aa9ea0-873d-441e-9103-39a98f1704aa}" Name="Change the system time" LockdownDate="2011-10-12T11:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8612-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which users and groups can change the time and date on the internal clock of the computers in your environment.</ShortDescription>
<FullDescription>This policy setting determines which users and groups can change the time and date on the internal clock of the computers in your environment. Users who are assigned this user right can affect the appearance of event logs. When a computer’s time setting is changed, logged events reflect the new time, not the actual time that the events occurred.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.
Note: Discrepancies between the time on the local computer and on the domain controllers in your environment may cause problems for the Kerberos authentication protocol, which could make it impossible for users to log on to the domain or obtain authorization to access domain resources after they are logged on. Also, problems will occur when Group Policy is applied to client computers if the system time is not synchronized with the domain controllers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>LOCAL SERVICE, Administrators</DefaultValue>
<Vulnerability>Users who can change the time on a computer could cause several problems. For example, time stamps on event log entries could be made inaccurate, time stamps on files and folders that are created or modified could be incorrect, and computers that belong to a domain may not be able to authenticate themselves or users who try to log on to the domain from them. Also, because the Kerberos authentication protocol requires that the requestor and authenticator have their clocks synchronized within an administrator-defined skew period, an attacker who changes a computer's time may cause that computer to be unable to obtain or grant Kerberos tickets.
The risk from these types of events is mitigated on most domain controllers, member servers, and end-user computers because the Windows Time service automatically synchronizes time with domain controllers in the following ways:
• All client desktop computers and member servers use the authenticating domain controller as their inbound time partner.
• All domain controllers in a domain nominate the primary domain controller (PDC) emulator operations master as their inbound time partner.
• All PDC emulator operations masters follow the hierarchy of domains in the selection of their inbound time partner.
• The PDC emulator operations master at the root of the domain is authoritative for the organization. Therefore it is recommended that you configure this computer to synchronize with a reliable external time server.
This vulnerability becomes much more serious if an attacker is able to change the system time and then stop the Windows Time service or reconfigure it to synchronize with a time server that is not accurate.
</Vulnerability>
<Countermeasure>Restrict the Change the system time user right to users with a legitimate need to change the system time, such as members of the IT team.</Countermeasure>
<PotentialImpact>There should be no impact, because time synchronization for most organizations should be fully automated for all computers that belong to the domain. Computers that do not belong to the domain should be configured to synchronize with an external source.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeSystemtimePrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeSystemTimePrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:169" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="265" ID="{39d24ad9-3577-4274-b91a-6a966afe7bce}" OriginalSettingID="{6870b1f9-8535-493c-9a30-889fd01900d7}" Name="Replace a process level token" LockdownDate="2011-05-22T07:27:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8732-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows one process or service to start another service or process with a different security access token, which can be used to modify the security access token of that sub-process and result in the escalation of privileges.</ShortDescription>
<FullDescription>This policy setting allows one process or service to start another service or process with a different security access token, which can be used to modify the security access token of that sub-process and result in the escalation of privileges.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>LOCAL SERVICE, NETWORK SERVICE</DefaultValue>
<Vulnerability>User with the Replace a process level token privilege are able to start processes as other users whose credentials they know. They could use this method to hide their unauthorized actions on the computer. (On Windows 2000-based computers, use of the Replace a process level token user right also requires the user to have the Adjust memory quotas for a process user right that is discussed earlier in this section.)</Vulnerability>
<Countermeasure>For member servers, ensure that only the Local Service and Network Service accounts have the Replace a process level token user right.</Countermeasure>
<PotentialImpact>On most computers, this is the default configuration and there will be no negative impact. However, if you have installed optional components such as ASP.NET or IIS, you may need to assign the Replace a process level token privilege to additional accounts. For example, IIS requires that the Service, Network Service, and IWAM_<ComputerName> accounts be explicitly granted this user right. </PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeAssignPrimaryTokenPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeAssignPrimaryTokenPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:193" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="266" ID="{8306d62f-72db-4bee-93e2-bc55ea5c5d40}" OriginalSettingID="{3ebdc510-830f-4520-9bce-2fe8f4f88b3f}" Name="Generate security audits" LockdownDate="2011-05-02T01:36:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9226-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which users or processes can generate audit records in the Security log.</ShortDescription>
<FullDescription>This policy setting determines which users or processes can generate audit records in the Security log.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Local Service, Network Service</DefaultValue>
<Vulnerability>An attacker could use this capability to create a large number of audited events, which would make it more difficult for a system administrator to locate any illicit activity. Also, if the event log is configured to overwrite events as needed, any evidence of unauthorized activities could be overwritten by a large number of unrelated events.</Vulnerability>
<Countermeasure>Ensure that only the Service and Network Service accounts have the Generate security audits user right assigned to them.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeAuditPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeAuditPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:181" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="267" ID="{3d083179-8db5-47b4-bdd0-d630bdb0e96c}" OriginalSettingID="{4b696c3e-dd2c-4d5e-bb0a-d7190de2c322}" Name="Adjust memory quotas for a process" LockdownDate="2011-05-22T06:59:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9068-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows a user to adjust the maximum amount of memory that is available to a process. </ShortDescription>
<FullDescription>This policy setting allows a user to adjust the maximum amount of memory that is available to a process. The ability to adjust memory quotas is useful for system tuning, but it can be abused. In the wrong hands, it could be used to launch a denial of service (DoS) attack.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>LOCAL SERVICE, NETWORK SERVICE, Administrators</DefaultValue>
<Vulnerability>A user with the Adjust memory quotas for a process privilege can reduce the amount of memory that is available to any process, which could cause business-critical network applications to become slow or to fail. In the wrong hands, this privilege could be used to start a denial of service (DoS) attack.</Vulnerability>
<Countermeasure>Restrict the Adjust memory quotas for a process user right to users who require it to perform their jobs, such as application administrators who maintain database management systems or domain administrators who manage the organization’s directory and its supporting infrastructure.</Countermeasure>
<PotentialImpact>Organizations that have not restricted users to roles with limited privileges will find it difficult to impose this countermeasure. Also, if you have installed optional components such as ASP.NET or IIS, you may need to assign the Adjust memory quotas for a process user right to additional accounts that are required by those components. IIS requires that this privilege be explicitly assigned to the IWAM_<ComputerName>, Network Service, and Service accounts. Otherwise, this countermeasure should have no impact on most computers. If this user right is necessary for a user account, it can be assigned to a local computer account instead of a domain account.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeIncreaseQuotaPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeIncreaseQuotaPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:164" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="268" ID="{b2e98fde-ef4d-4b49-adee-8299ce77910b}" OriginalSettingID="{60859cb4-3ad7-4a2f-8564-fcfde3ee1768}" Name="Access Credential Manager as a trusted caller" LockdownDate="2011-05-15T05:27:14Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9380-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This security setting is used by Credential Manager during Backup and Restore.</ShortDescription>
<FullDescription>This security setting is used by Credential Manager during Backup and Restore. No accounts should have this user right, as it is only assigned to Winlogon. Users' saved credentials might be compromised if this user right is assigned to other entities.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>No One</DefaultValue>
<Vulnerability>If an account is given this right the user of the account may create an application that calls into Credential Manager and is returned the credentials for another user. </Vulnerability>
<Countermeasure>Configure this user right so that no accounts have it. </Countermeasure>
<PotentialImpact>None, this is the default configuration</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeTrustedCredManAccessPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeTrustedCredManAccessPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="269" ID="{6a793d6e-87fa-4546-be71-aec4c74e2674}" OriginalSettingID="{f921fab5-cf36-4241-b474-276fd53263a5}" Name="Profile single process" LockdownDate="2011-10-12T11:37:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9388-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which users can use tools to monitor the performance of non-system processes. if System Monitor is configured to collect data using Windows Management Instrumentation (WMI) this setting is required.</ShortDescription>
<FullDescription>This policy setting determines which users can use tools to monitor the performance of non-system processes. Typically, you do not need to configure this user right to use the Microsoft Management Console (MMC) Performance snap-in. However, you do need this user right if System Monitor is configured to collect data using Windows Management Instrumentation (WMI). Restricting the Profile single process user right prevents intruders from gaining additional information that could be used to mount an attack on the system.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators</DefaultValue>
<Vulnerability>The Profile single process user right presents a moderate vulnerability. An attacker with this user right could monitor a computer's performance to help identify critical processes that they might wish to attack directly. The attacker may also be able to determine what processes run on the computer so that they could identify countermeasures that they may need to avoid, such as antivirus software, an intrusion-detection system, or which other users are logged on to a computer.</Vulnerability>
<Countermeasure>Ensure that only the local Administrators group is assigned the Profile single process user right.</Countermeasure>
<PotentialImpact>If you remove the Profile single process user right from the Power Users group or other accounts, you could limit the abilities of users who are assigned to specific administrative roles in your environment. You should ensure that delegated tasks will not be negatively affected.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeProfileSingleProcessPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeProfileSingleProcessPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:190" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="270" ID="{0bbbb061-2b02-448e-8b5c-7db64bacdb16}" OriginalSettingID="{6630b24b-754a-49a5-9750-188ae53c13b9}" Name="Manage auditing and security log" LockdownDate="2011-05-02T01:36:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9223-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which users can change the auditing options for files and directories and clear the Security log.</ShortDescription>
<FullDescription>This policy setting determines which users can change the auditing options for files and directories and clear the Security log.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators</DefaultValue>
<Vulnerability>The ability to manage the Security event log is a powerful user right and it should be closely guarded. Anyone with this user right can clear the Security log to erase important evidence of unauthorized activity.</Vulnerability>
<Countermeasure>Ensure that only the local Administrators group has the Manage auditing and security log user right.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeSecurityPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeSecurityPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:187, oval:gov.nist.1:def:235" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="271" ID="{65a028c4-e391-45b5-87ca-27bfd1b78c03}" OriginalSettingID="{b9af2cf2-1528-469c-b7e8-3787c4513479}" Name="Deny access to this computer from the network" LockdownDate="2011-10-12T11:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9244-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting prohibits users from connecting to a computer from across the network, which would allow users to access and potentially modify data remotely.</ShortDescription>
<FullDescription>This policy setting prohibits users from connecting to a computer from across the network, which would allow users to access and potentially modify data remotely. In high security environments, there should be no need for remote users to access data on a computer. Instead, file sharing should be accomplished through the use of network servers.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Guest
</DefaultValue>
<Vulnerability>Users who can log on to the computer over the network can enumerate lists of account names, group names, and shared resources. Users with permission to access shared folders and files can connect over the network and possibly view or modify data.</Vulnerability>
<Countermeasure>Assign the Deny access to this computer from the network user right to the following accounts:
• ANONYMOUS LOGON
• Built-in local Administrator account
• Local Guest account
• Built-in Support account
• All service accounts
An important exception to this list is any service accounts that are used to start services that need to connect to the computer over the network. For example, if you have configured a shared folder for Web servers to access and present content within that folder through a Web site, you may need to allow the account that runs IIS to log on to the server with the shared folder from the network. This user right is particularly effective when you need to configure servers and workstations on which sensitive information is handled because of regulatory compliance concerns.
</Countermeasure>
<PotentialImpact>If you configure the Deny access to this computer from the network user right for other groups, you could limit the abilities of users who are assigned to specific administrative roles in your environment. You should verify that delegated tasks will not be negatively affected.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeDenyNetworkLogonRight' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeDenyNetworkLogonRight" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:175" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="272" ID="{7d8fa5d5-b0e9-479c-9807-4d095b1fd44b}" OriginalSettingID="{48cf8aee-1c72-4c3e-9f2a-c6dfe8990219}" Name="Access this computer from the network" LockdownDate="2011-10-12T11:37:55Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9253-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting allows other users on the network to connect to the computer.</ShortDescription>
<FullDescription>This policy setting allows other users on the network to connect to the computer and is required by various network protocols that include Server Message Block (SMB)–based protocols, NetBIOS, Common Internet File System (CIFS), and Component Object Model Plus (COM+).
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Everyone, Administrators, Users, Backup Operators</DefaultValue>
<Vulnerability>Users who can connect from their computer to the network can access resources on target computers for which they have permission. For example, the Access this computer from the network user right is required for users to connect to shared printers and folders. If this user right is assigned to the Everyone group, then anyone in the group will be able to read the files in those shared folders. However, this situation is unlikely for new installations of Windows Server® 2003 with Service Pack 1 (SP1), because the default share and NTFS permissions in Windows Server 2003 do not include the Everyone group. This vulnerability may have a higher level of risk for computers that you upgrade from Windows NT® 4.0 or Windows 2000, because the default permissions for these operating systems are not as restrictive as the default permissions in Windows Server 2003. </Vulnerability>
<Countermeasure>Restrict the Access this computer from the network user right to only those users who require access to the server. For example, if you configure this policy setting to the Administrators and Users groups, users who log on to the domain will be able to access resources shared from servers in the domain if members of the Domain Users group are included in the local Users group.</Countermeasure>
<PotentialImpact>If you remove the Access this computer from the network user right on domain controllers for all users, no one will be able to log on to the domain or use network resources. If you remove this user right on member servers, users will not be able to connect to those servers through the network. Successful negotiation of IPsec connections requires that the initiating machine has this right, therefor Microsoft recommends that it is assigned to the Users group.If you have installed optional components such as ASP.NET or Internet Information Services (IIS), you may need to assign this user right to additional accounts that are required by those components. It is important to verify that authorized users are assigned this user right for the computers they need to access the network.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeNetworkLogonRight' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeNetworkLogonRight" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:161, oval:gov.nist.1:def:231" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="273" ID="{1649e4fa-0cc0-4ef1-81e7-498c6a58bb79}" OriginalSettingID="{78c974e6-940e-4fec-8697-73d0ed54943c}" Name="Allow log on through Remote Desktop Services" LockdownDate="2011-05-15T05:27:14Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9107-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which users or groups have the right to log on as a Terminal Services client.</ShortDescription>
<FullDescription>This policy setting determines which users or groups have the right to log on as a Terminal Services client. Remote desktop users require this user right. If your organization uses Remote Assistance as part of its help desk strategy, create a group and assign it this user right through Group Policy. If the help desk in your organization does not use Remote Assistance, assign this user right only to the Administrators group or use the restricted groups feature to ensure that no user accounts are part of the Remote Desktop Users group.
Restrict this user right to the Administrators group, and possibly the Remote Desktop Users group, to prevent unwanted users from gaining access to computers on your network by means of the Remote Assistance feature.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators, Remote Desktop Users</DefaultValue>
<Vulnerability>Any account with the Allow log on through Terminal Services user right can log on to the remote console of the computer. If you do not restrict this user right to legitimate users who need to log on to the console of the computer, unauthorized users could download and run malicious software to elevate their privileges.</Vulnerability>
<Countermeasure>For domain controllers, assign the Allow log on through Terminal Services user right only to the Administrators group. For other server roles and end-user computers, add the Remote Desktop Users group. For Terminal Servers that do not run in Application Server mode, ensure that only authorized IT personnel who need to manage the computers remotely belong to either of these groups.
Caution
For Terminal Servers that do run in Application Server mode, ensure that only users who require access to the server have accounts that belong to the Remote Desktop Users group, because this built-in group has this logon right by default.
Alternatively, you can assign the Deny Logon Through Terminal Services user right to groups such as Account Operators, Server Operators, and Guests. However, be careful when you use this method because you could block access to legitimate administrators who also happen to belong to a group that has the Deny Logon Through Terminal Services user right.
</Countermeasure>
<PotentialImpact>Removal of the Allow log on through Terminal Services user right from other groups or membership changes in these default groups could limit the abilities of users who perform specific administrative roles in your environment. You should confirm that delegated activities will not be adversely affected.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeRemoteInteractiveLogonRight' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeRemoteInteractiveLogonRight" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:166" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="274" ID="{58789aea-c3a7-40c2-bbce-a486b411813a}" OriginalSettingID="{23a1c3b4-4d38-4153-854a-e315ad699d9b}" Name="Allow log on locally" LockdownDate="2011-10-12T11:37:55Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9345-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which users can interactively log on to computers in your environment.</ShortDescription>
<FullDescription>This policy setting determines which users can interactively log on to computers in your environment. Logons that are initiated by pressing the CTRL+ALT+DEL key sequence on the client computer keyboard require this user right. Users who attempt to log on through Terminal Services or IIS also require this user right.
The Guest account is assigned this user right by default. Although this account is disabled by default, Microsoft recommends that you enable this setting through Group Policy. However, this user right should generally be restricted to the Administrators and Users groups. Assign this user right to the Backup Operators group if your organization requires that they have this capability.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Guest, Administrators, Users, Backup Operators</DefaultValue>
<Vulnerability>Any account with the Allow log on locally user right can log on at the console of the computer. If you do not restrict this user right to legitimate users who need to be able to log on to the console of the computer, unauthorized users could download and run malicious software to elevate their privileges.</Vulnerability>
<Countermeasure>For domain controllers, assign the Allow log on locally user right only to the Administrators group. For other server roles, you may choose to add Backup Operators as well as Administrators. For end-user computers you should also assign this right to the Users group.
Alternatively, you can assign groups such as Account Operators, Server Operators, and Guests to the Deny Log on Locally user right.
</Countermeasure>
<PotentialImpact>If you remove these default groups, you could limit the abilities of users who are assigned to specific administrative roles in your environment. If you have installed optional components such as ASP.NET or Internet Information Services, you may need to assign Allow log on locally user right to additional accounts that are required by those components. IIS requires that this user right be assigned to the IUSR_<ComputerName> account. You should confirm that delegated activities will not be adversely affected by any changes that you make to the Allow log on locally user rights assignments.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeInteractiveLogonRight' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeInteractiveLogonRight" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:177" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="275" ID="{33292c81-06d4-4a1f-b2c2-eeedd154bccc}" OriginalSettingID="{8797b752-5346-436e-8502-cd5031cc77d5}" Name="Deny log on as a batch job" LockdownDate="2011-10-12T11:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9212-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which accounts will not be able to log on to the computer as a batch job.</ShortDescription>
<FullDescription>This policy setting determines which accounts will not be able to log on to the computer as a batch job. A batch job is not a batch (.bat) file, but rather a batch-queue facility. Accounts that use the Task Scheduler to schedule jobs need this user right.
The Deny log on as a batch job user right overrides the Log on as a batch job user right, which could be used to allow accounts to schedule jobs that consume excessive system resources. Such an occurrence could cause a DoS condition. Failure to assign this user right to the recommended accounts can be a security risk.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>No One</DefaultValue>
<Vulnerability>Accounts that have the Deny log on as a batch job user right could be used to schedule jobs that could consume excessive computer resources and cause a DoS condition.</Vulnerability>
<Countermeasure>Assign the Deny log on as a batch job user right to the built-in Support account and the local Guest account.</Countermeasure>
<PotentialImpact>If you assign the Deny log on as a batch job user right to other accounts, you could deny users who are assigned to specific administrative roles the ability to perform their required job activities. You should confirm that delegated tasks will not be affected adversely.
For example, if you assign this user right to the IWAM_<ComputerName> account, the MSM Management Point will fail. On a newly installed computer that runs Windows Server 2003 this account does not belong to the Guests group, but on a computer that was upgraded from Windows 2000 this account is a member of the Guests group. Therefore, it is important that you understand which accounts belong to any groups that you assign the Deny log on as a batch job user right.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeDenyBatchLogonRight' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeDenyBatchLogonRight" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:176" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="276" ID="{f13a5f62-361c-4c17-bc71-74decdb11119}" OriginalSettingID="{485ea1c9-091c-434b-b8e0-c9d8cbfde052}" Name="Enable computer and user accounts to be trusted for delegation" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8930-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows users to change the Trusted for Delegation setting on a computer object in Active Directory.</ShortDescription>
<FullDescription>This policy setting allows users to change the Trusted for Delegation setting on a computer object in Active Directory. Abuse of this privilege could allow unauthorized users to impersonate other users on the network.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>No One</DefaultValue>
<Vulnerability>Misuse of the Enable computer and user accounts to be trusted for delegation user right could allow unauthorized users to impersonate other users on the network. An attacker could exploit this privilege to gain access to network resources and make it difficult to determine what has happened after a security incident.</Vulnerability>
<Countermeasure>The Enable computer and user accounts to be trusted for delegation user right should be assigned only if there is a clear need for its functionality. When you assign this right, you should investigate the use of constrained delegation to control what the delegated accounts can do.
Note
There is no reason to assign this user right to anyone on member servers and workstations that belong to a domain because it has no meaning in those contexts; it is only relevant on domain controllers and stand-alone computers.
</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeEnableDelegationPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeEnableDelegationPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:179" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="277" ID="{2be27f71-30e4-41fe-8fe9-a243a1ce6d25}" OriginalSettingID="{63db26be-30f4-4428-9b60-ea0b0daeae0d}" Name="Modify firmware environment values" LockdownDate="2011-05-02T01:36:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9417-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows users to configure the system-wide environment variables that affect hardware configuration. This information is typically stored in the Last Known Good Configuration.</ShortDescription>
<FullDescription>This policy setting allows users to configure the system-wide environment variables that affect hardware configuration. This information is typically stored in the Last Known Good Configuration. Modification of these values and could lead to a hardware failure that would result in a denial of service condition.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators</DefaultValue>
<Vulnerability>Anyone who is assigned the Modify firmware environment values user right could configure the settings of a hardware component to cause it to fail, which could lead to data corruption or a DoS condition.</Vulnerability>
<Countermeasure>Ensure that only the local Administrators group is assigned the Modify firmware environment values user right.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeSystemEnvironmentPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeSystemEnvironmentPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:188" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="278" ID="{30a68dcc-7f6b-4d71-a668-611a6c873c2e}" OriginalSettingID="{cb3e6c7f-6d9b-4577-95df-93791481f060}" Name="Modify an object label" LockdownDate="2011-06-13T03:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9149-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This privilege determines which user accounts can modify the integrity label of objects, such as files, registry keys, or processes owned by other users.</ShortDescription>
<FullDescription>This privilege determines which user accounts can modify the integrity label of objects, such as files, registry keys, or processes owned by other users. Processes running under a user account can modify the label of an object owned by that user to a lower level without this privilege.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>None</DefaultValue>
<Vulnerability>By modifying the integrity label of an object owned by an other user a malicious user may cause them to execute code at a higher level of privilege than intended.</Vulnerability>
<Countermeasure>Configure this setting so that only authorized users are allowed to modify object labels.</Countermeasure>
<PotentialImpact>None, by default the Administrators group has this user right.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeRelabelPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeRelabelPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="279" ID="{6e05588d-1e43-4607-bad8-6ab4a0c433c8}" OriginalSettingID="{a9411a96-e13f-4b37-ab31-b84a06d63460}" Name="Devices: Prevent users from installing printer drivers" LockdownDate="2011-06-14T12:39:05Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9026-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting controls which groups has the right to install printer drivers.</ShortDescription>
<FullDescription>It is feasible for a attacker to disguise a Trojan horse program as a printer driver. The program may appear to users as if they must use it to print, but such a program could unleash malicious code on your computer network. To reduce the possibility of such an event, only administrators should be allowed to install printer drivers. However, because laptops are mobile devices, laptop users may occasionally need to install a printer driver from a remote source to continue their work. Therefore, this policy setting should be disabled for laptop users, but always enabled for desktop users.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>It may be appropriate in some organizations to allow users to install printer drivers on their own workstations. However, you should allow only Administrators, not users, to do so on servers, because printer driver installation on a server may unintentionally cause the computer to become less stable. A malicious user could install inappropriate printer drivers in a deliberate attempt to damage the computer, or a user might accidentally install malicious software that masquerades as a printer driver.</Vulnerability>
<Countermeasure>Enable the Devices: Prevent users from installing printer drivers setting.</Countermeasure>
<PotentialImpact>Only users with Administrative, Power User, or Server Operator privileges will be able to install printers on the servers. If this policy setting is enabled but the driver for a network printer already exists on the local computer, users can still add the network printer.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Print\Providers\LanMan Print Services\Servers</mssasc-core:KeyPath>
<mssasc-core:ValueName>AddPrinterDrivers</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Print\Providers\LanMan Print Services\Servers\AddPrinterDrivers" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:56" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="280" ID="{0cd825b9-23c9-4c5a-830f-51a13a3b7dd4}" OriginalSettingID="{c63e0099-758c-4b99-aecd-eb63df8559d8}" Name="Restore files and directories" LockdownDate="2011-05-22T07:27:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9124-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which users can bypass file, directory, registry, and other persistent object permissions when restoring backed up files and directories.</ShortDescription>
<FullDescription>This policy setting determines which users can bypass file, directory, registry, and other persistent object permissions when restoring backed up files and directories on computers that run Windows Vista in your environment. This user right also determines which users can set valid security principals as object owners; it is similar to the Back up files and directories user right.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators, Backup Operators</DefaultValue>
<Vulnerability>An attacker with the Restore files and directories user right could restore sensitive data to a computer and overwrite data that is more recent, which could lead to loss of important data, data corruption, or a denial of service. Attackers could overwrite executable files that are used by legitimate administrators or system services with versions that include malicious software to grant themselves elevated privileges, compromise data, or install backdoors for continued access to the computer.
Note
Even if the following countermeasure is configured, an attacker could still restore data to a computer in a domain that is controlled by the attacker. Therefore, it is critical that organizations carefully protect the media that are used to back up data.
</Vulnerability>
<Countermeasure>Ensure that only the local Administrators group is assigned the Restore files and directories user right, unless your organization has clearly defined roles for backup and for restore personnel.</Countermeasure>
<PotentialImpact>If you remove the Restore files and directories user right from the Backup Operators group and other accounts you could make it impossible for users who have been delegated specific tasks to perform those tasks. You should verify that this change won't negatively affect the ability of your organization’s personnel to do their jobs.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeRestorePrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeRestorePrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:194" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="281" ID="{1b5601cc-1320-487e-b983-60235aaf9883}" OriginalSettingID="{591bd8ac-a5b3-41cc-8978-2bce50123a00}" Name="Debug programs" LockdownDate="2011-05-02T01:36:00Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8583-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which user accounts will have the right to attach a debugger to any process or to the kernel, which provides complete access to sensitive and critical operating system components.</ShortDescription>
<FullDescription>This policy setting determines which user accounts will have the right to attach a debugger to any process or to the kernel, which provides complete access to sensitive and critical operating system components. Developers who are debugging their own applications do not need to be assigned this user right; however, developers who are debugging new system components will need it.
Note Microsoft released several security updates in October 2003 that used a version of Update.exe that required the administrator to have the Debug programs user right. Administrators who did not have this user right were unable to install these security updates until they reconfigured their user rights. This is not typical behavior for operating system updates. For more information, see Knowledge Base article 830846: "Windows Product Updates may stop responding or may use most or all the CPU resources."
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators</DefaultValue>
<Vulnerability>The Debug programs user right can be exploited to capture sensitive computer information from system memory, or to access and modify kernel or application structures. Some attack tools exploit this user right to extract hashed passwords and other private security information, or to insert rootkit code. By default, the Debug programs user right is assigned only to administrators, which helps to mitigate the risk from this vulnerability.</Vulnerability>
<Countermeasure>Remove the accounts of all users and groups that do not require the Debug programs user right.</Countermeasure>
<PotentialImpact>If you revoke this user right, no one will be able to debug programs. However, typical circumstances rarely require this capability on production computers. If a problem arises that requires an application to be debugged on a production server, you can move the server to a different OU temporarily and assign the Debug programs user right to a separate Group Policy for that OU.
The service account that is used for the cluster service needs the Debug programs privilege; if it does not have it, Windows Clustering will fail. For additional information about how to configure Windows Clustering in conjunction with computer hardening, see article 891597, How to apply more restrictive security settings on a Windows Server 2003–based cluster server, in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=100746).
Tools that are used to manage processes will be unable to affect processes that are not owned by the person who runs the tools. For example, the Windows Server 2003 Resource Kit tool Kill.exe requires this user right for administrators to terminate processes that they did not start.
Also, some older versions of Update.exe (which is used to install Windows product updates) require the account that applies the update to have this user right. If you install one of the patches that uses this version of Update.exe, the computer could become unresponsive. For more information, see article 830846, Windows Product Updates may stop responding or may use most or all the CPU resources, in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=100747).
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeDebugPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeDebugPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:173" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="282" ID="{6a674d75-0d07-4f37-85f8-113d1122437d}" OriginalSettingID="{9066c223-8261-4c0b-9cfc-6a396532dbbc}" Name="Change the time zone" LockdownDate="2011-10-12T11:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8423-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting determines which users can change the time zone of the computer.</ShortDescription>
<FullDescription>This setting determines which users can change the time zone of the computer. This ability holds no great danger for the computer and may be useful for mobile workers.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>LOCAL SERVICE, Administrators, Users
</DefaultValue>
<Vulnerability>Changing the time zone represents little vulnerability because the system time is not affected. This setting merely enables users to display their preferred time zone while being synchronized with domain controllers in different time zones.</Vulnerability>
<Countermeasure>Countermeasures are not required because system time is not affected by this setting.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeTimeZonePrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeTimeZonePrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="283" ID="{6e71fdb8-46c0-485d-b542-26881d3ea428}" OriginalSettingID="{eba90e79-8551-416f-9258-a48e1d9a60c7}" Name="Increase scheduling priority" LockdownDate="2011-05-22T07:27:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8999-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows users to change the amount of processor time that a process uses.</ShortDescription>
<FullDescription>This policy setting determines whether users can increase the base priority class of a process. (It is not a privileged operation to increase relative priority within a priority class.) This user right is not required by administrative tools that are supplied with the operating system but might be required by software development tools.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators</DefaultValue>
<Vulnerability>A user who is assigned this user right could increase the scheduling priority of a process to Real-Time, which would leave little processing time for all other processes and could lead to a DoS condition.</Vulnerability>
<Countermeasure>Verify that only Administrators have the Increase scheduling priority user right assigned to them.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeIncreaseBasePriorityPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeIncreaseBasePriorityPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:182" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="284" ID="{6abbdad3-1a59-498d-9ae2-e8e5b14a43f5}" OriginalSettingID="{c3a6cfaf-1504-4d55-ace8-1ebc971d9ebc}" Name="Create global objects" LockdownDate="2011-11-09T03:56:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8431-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether users can create global objects that are available to all sessions. Users can still create objects that are specific to their own session if they do not have this user right.</ShortDescription>
<FullDescription>This policy setting determines whether users can create global objects that are available to all sessions. Users can still create objects that are specific to their own session if they do not have this user right.
Users who can create global objects could affect processes that run under other users' sessions. This capability could lead to a variety of problems, such as application failure or data corruption.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators, SERVICE, Local Service, Network Service</DefaultValue>
<Vulnerability>Users who can create global objects could affect Windows services and processes that run under other user or system accounts. This capability could lead to a variety of problems, such as application failure, data corruption and elevation of privilege.</Vulnerability>
<Countermeasure>Restrict the Create global objects user right to members of the local Administrators and Service groups.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeCreateGlobalPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeCreateGlobalPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="285" ID="{e78277dc-9342-4ede-801c-87d659a3a883}" OriginalSettingID="{eaa6e376-dcd2-4094-96ea-a9f404a50d51}" Name="Allow users to connect remotely using Remote Desktop Services" LockdownDate="2011-10-12T11:37:55Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9985-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows you to control if users can connect to a computer using Terminal Services or Remote Desktop.</ShortDescription>
<FullDescription>This policy setting allows you to control if users can connect to a computer using Terminal Services or Remote Desktop.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections</UIPath>
<DefaultValue>Not Configured</DefaultValue>
<Vulnerability>Any account with the Allow log on through Terminal Services user right can log on to the remote console of the computer. If you do not restrict access to legitimate users who need to log on to the console of the computer, unauthorized users could download and execute malicious code to elevate their privileges.</Vulnerability>
<Countermeasure>To protect against this risk configure this setting to disabled.</Countermeasure>
<PotentialImpact>If this setting is enabled legitimate users will be unable to use Terminal Services or Remote Desktop, this could make it more difficult for help desk technicians to troubleshoot and resolve problems remotely. It would also make it impossible to use Terminal Services for hosting shared applications.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine" />
<DataType>String</DataType>
</DiscoveryInfo>
<policy name="TS_DISABLE_CONNECTIONS" class="Machine" displayName="$(string.06e5c8e768674411b9605c9886a01169)" explainText="$(string.a483a2a9ae094975b32a695226d97ac6)" key="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledList xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:item key="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" valueName="fDenyTSConnections">
<admx:value>
<admx:decimal value="0" />
</admx:value>
</admx:item>
</admx:enabledList>
<admx:disabledList xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:item key="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" valueName="fDenyTSConnections">
<admx:value>
<admx:decimal value="1" />
</admx:value>
</admx:item>
</admx:disabledList>
</policy>
<ADMLDefinition>
<string id="06e5c8e768674411b9605c9886a01169">Allow users to connect remotely using Remote Desktop Services</string>
<string id="a483a2a9ae094975b32a695226d97ac6">This policy setting allows you to control if users can connect to a computer using Terminal Services or Remote Desktop.</string>
</ADMLDefinition>
<supportedOn>At least Windows XP Professional or Windows Server 2003 family</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:166" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="286" ID="{12d1857c-2e5e-4cfb-ae3b-2cff254c527b}" OriginalSettingID="{e197f79b-a454-407c-9307-7b3210313e61}" Name="Network access: Let Everyone permissions apply to anonymous users" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8936-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines what additional permissions are assigned for anonymous connections to the computer</ShortDescription>
<FullDescription>This policy setting determines what additional permissions are assigned for anonymous connections to the computer. If you enable this policy setting, anonymous Windows users are allowed to perform certain activities, such as enumerate the names of domain accounts and network shares. An unauthorized user could anonymously list account names and shared resources and use the information to guess passwords or perform social engineering attacks.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>An unauthorized user could anonymously list account names and shared resources and use the information to attempt to guess passwords, perform social engineering attacks, or launch DoS attacks.</Vulnerability>
<Countermeasure>Configure the Network access: Let Everyone permissions apply to anonymous users setting to Disabled. </Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>EveryoneIncludesAnonymous</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\EveryoneIncludesAnonymous" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:90" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="287" ID="{0a271bb9-213f-40c3-bc5c-30a8fdcb490c}" OriginalSettingID="{d2197a4c-19f4-4630-b15a-aaf85c813045}" Name="Deny log on locally" LockdownDate="2011-10-12T11:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9239-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This security setting determines which users are prevented from logging on at the computer.</ShortDescription>
<FullDescription>This security setting determines which users are prevented from logging on at the computer. This policy setting supersedes the Allow log on locally policy setting if an account is subject to both policies.Important:If you apply this security policy to the Everyone group, no one will be able to log on locally.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Guest
</DefaultValue>
<Vulnerability>Any account with the ability to log on locally could be used to log on at the console of the computer. If this user right is not restricted to legitimate users who need to log on to the console of the computer, unauthorized users might download and run malicious software that elevates their privileges.</Vulnerability>
<Countermeasure>Assign the Deny log on locally user right to the built-in Support account. If you have installed optional components such as ASP.NET, you may want to assign this user right to additional accounts that are required by those components.
Note
The Support_388945a0 account enables Help and Support Service interoperability with signed scripts. This account is primarily used to control access to signed scripts that are accessible from within Help and Support Services. Administrators can use this account to delegate the ability for a typical user who does not have administrative access to run signed scripts from links that are embedded within Help and Support Services. These scripts can be programmed to use the Support_388945a0 account credentials instead of the user's credentials to perform specific administrative operations on the local computer that otherwise would not be supported by the typical user's account. When the delegated user clicks on a link in Help and Support Services, the script will run under the security context of the Support_388945a0 account. This account has limited access to the computer and is disabled by default.
</Countermeasure>
<PotentialImpact>If you assign the Deny log on locally user right to additional accounts, you could limit the abilities of users who are assigned to specific roles in your environment. However, this user right should explicitly be assigned to the ASPNET account on computers that run IIS 6.0. You should confirm that delegated activities will not be adversely affected.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeDenyInteractiveLogonRight' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeDenyInteractiveLogonRight" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:177" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="288" ID="{6ec1ab3e-5abc-44b9-997d-101481b01d44}" OriginalSettingID="{8840018d-e63a-4e69-96a8-c06af7e963a8}" Name="Force shutdown from a remote system" LockdownDate="2011-05-02T01:36:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9336-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows users to shut down Windows Vista–based computers from remote locations on the network.</ShortDescription>
<FullDescription>This policy setting allows users to shut down Windows Vista–based computers from remote locations on the network. Anyone who has been assigned this user right can cause a denial of service (DoS) condition, which would make the computer unavailable to service user requests. Therefore, Microsoft recommends that only highly trusted administrators be assigned this user right.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators</DefaultValue>
<Vulnerability>Any user who can shut down a computer could cause a DoS condition to occur. Therefore, this user right should be tightly restricted.</Vulnerability>
<Countermeasure>Restrict the Force shutdown from a remote system user right to members of the Administrators group or other specifically assigned roles that require this capability (such as non-administrative operations center staff).</Countermeasure>
<PotentialImpact>If you remove the Force shutdown from a remote system user right from the Server Operator group you could limit the abilities of users who are assigned to specific administrative roles in your environment. You should confirm that delegated activities will not be adversely affected.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeRemoteShutdownPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeRemoteShutdownPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:180" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="289" ID="{468483f1-f6a9-403a-9ff1-25b301aa927e}" OriginalSettingID="{b77b9700-3212-4d5f-9547-dbe8ffd32574}" Name="Act as part of the operating system" LockdownDate="2011-10-12T11:37:55Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9407-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows a process to assume the identity of any user and thus gain access to the resources that the user is authorized to access.</ShortDescription>
<FullDescription>This policy setting allows a process to assume the identity of any user and thus gain access to the resources that the user is authorized to access.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>No one</DefaultValue>
<Vulnerability>The Act as part of the operating system user right is extremely powerful. Anyone with this user right can take complete control of the computer and erase evidence of their activities.</Vulnerability>
<Countermeasure>Restrict the Act as part of the operating system user right to as few accounts as possible—it should not even be assigned to the Administrators group under typical circumstances. When a service requires this user right, configure the service to log on with the Local System account, which has this privilege inherently. Do not create a separate account and assign this user right to it.</Countermeasure>
<PotentialImpact>There should be little or no impact because the Act as part of the operating system user right is rarely needed by any accounts other than the Local System account.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeTcbPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeTcbPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:162" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="290" ID="{71553705-afe1-4c91-85a9-503547ef79df}" OriginalSettingID="{dd1e688f-295d-4ee6-8f2f-5cdb83c0b4e1}" Name="Create permanent shared objects" LockdownDate="2011-10-12T11:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9254-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows users to create directory objects in the object manager.</ShortDescription>
<FullDescription>This user right is useful to kernel-mode components that extend the object namespace. However, components that run in kernel mode have this user right inherently. Therefore, it is typically not necessary to specifically assign this user right.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>No One</DefaultValue>
<Vulnerability>Users who have the Create permanent shared objects user right could create new shared objects and expose sensitive data to the network.</Vulnerability>
<Countermeasure>Do not assign the Create permanent shared objects user right to any users. Processes that require this user right should use the System account (which already includes this user right) instead of a separate user account.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeCreatePermanentPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeCreatePermanentPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:172" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="291" ID="{04658362-23eb-402c-9fd5-a750eebd4a7b}" OriginalSettingID="{10afbff0-0f2c-41b7-8b66-68bda79b77bd}" Name="Create symbolic links" LockdownDate="2011-05-02T01:36:00Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8460-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which users can create symbolic links.</ShortDescription>
<FullDescription>This policy setting determines which users can create symbolic links. In Windows Vista, existing NTFS file system objects, such as files and folders, can be accessed by referring to a new kind of file system object called a symbolic link. A symbolic link is a pointer (much like a shortcut or .lnk file) to another file system object, which can be a file, folder, shortcut or another symbolic link. The difference between a shortcut and a symbolic link is that a shortcut only works from within the Windows shell. To other programs and applications, shortcuts are just another file, whereas with symbolic links, the concept of a shortcut is implemented as a feature of the NTFS file system.
Symbolic links can potentially expose security vulnerabilities in applications that are not designed to use them. For this reason, the privilege for creating symbolic links should only be assigned to trusted users. By default, only Administrators can create symbolic links.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators</DefaultValue>
<Vulnerability>Users who have the Create Symbolic Links user right could inadvertently or maliciously expose your system to symbolic link attacks. Symbolic link attacks can be used to change the permissions on a file, to corrupt data, to destroy data, or as a Denial of Service attack.</Vulnerability>
<Countermeasure>Do not assign the Create Symbolic Links user right to standard users. Restrict this right to trusted administrators. You can use the fsutil command to establish a symlink file system setting that controls the kind of symlinks that can be created on a computer. For more information about fsutil and symbolic links, type fsutil behavior set symlinkevaluation /? at an elevated command prompt.</Countermeasure>
<PotentialImpact>In most cases there will be no impact because this is the default configuration, however, on Windows Servers with the Hyper-V server role installed this user right should also be granted to the special group "Virtual Machines" otherwise you will not be able to create new virtual machines.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeCreateSymbolicLinkPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeCreateSymbolicLinkPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="292" ID="{e260bd2f-9e47-4a50-991b-515423b705ca}" OriginalSettingID="{52a9b265-75cb-45a0-ac23-3e5d4fa566c2}" Name="Create a pagefile" LockdownDate="2011-05-22T07:27:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9185-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows users to change the size of the pagefile.</ShortDescription>
<FullDescription>This policy setting allows users to change the size of the pagefile. By making the pagefile extremely large or extremely small, an attacker could easily affect the performance of a compromised computer.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators</DefaultValue>
<Vulnerability>Users who can change the page file size could make it extremely small or move the file to a highly fragmented storage volume, which could cause reduced computer performance.</Vulnerability>
<Countermeasure>Restrict the Create a page file user right to members of the Administrators group.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeCreatePagefilePrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeCreatePagefilePrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:170" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="293" ID="{60ac480b-8940-4d98-a327-553ffe0dc3cb}" OriginalSettingID="{49862b02-e96e-4ebc-8cac-129f07b1298e}" Name="Deny log on through Remote Desktop Services" LockdownDate="2011-05-25T12:12:50Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9274-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether users can log on as Terminal Services clients.</ShortDescription>
<FullDescription>This policy setting determines whether users can log on as Terminal Services clients. After the baseline member server is joined to a domain environment, there is no need to use local accounts to access the server from the network. Domain accounts can access the server for administration and end-user processing.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>No One</DefaultValue>
<Vulnerability>Any account with the right to log on through Terminal Services could be used to log on to the remote console of the computer. If this user right is not restricted to legitimate users who need to log on to the console of the computer, unauthorized users might download and run malicious software that elevates their privileges.</Vulnerability>
<Countermeasure>Assign the Deny log on through Terminal Services logon right to the built-in local Administrator account and all service accounts. If you have installed optional components such as ASP.NET, you may want to assign this logon right to additional accounts that are required by those components.</Countermeasure>
<PotentialImpact>If you assign the Deny log on through Terminal Services user right to other groups, you could limit the abilities of users who are assigned to specific administrative roles in your environment. Accounts that have this user right will be unable to connect to the computer through either Terminal Services or Remote Assistance. You should confirm that delegated tasks will not be negatively impacted.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeDenyRemoteInteractiveLogonRight' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeDenyRemoteInteractiveLogonRight" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:178" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="294" ID="{3c0e1a7d-4a77-45f0-86e9-504829d375c5}" OriginalSettingID="{1ce3bf70-68d8-419b-96ef-d293de427cff}" Name="Back up files and directories" LockdownDate="2011-05-02T01:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9389-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows users to circumvent file and directory permissions to back up the system.</ShortDescription>
<FullDescription>This policy setting allows users to circumvent file and directory permissions to back up the system. This user right is enabled only when an application (such as NTBACKUP) attempts to access a file or directory through the NTFS file system backup application programming interface (API). Otherwise, the assigned file and directory permissions apply.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators, Backup Operators</DefaultValue>
<Vulnerability>Users who are able to back up data from a computer could take the backup media to a non-domain computer on which they have administrative privileges and restore the data. They could take ownership of the files and view any unencrypted data that is contained within the backup set.</Vulnerability>
<Countermeasure>Restrict the Back up files and directories user right to members of the IT team who need to be able to back up organizational data as part of their day-to-day job responsibilities. If you are using backup software that runs under specific service accounts, only these accounts (and not the IT staff) should have the Back up files and directories user right.</Countermeasure>
<PotentialImpact>Changes in the membership of the groups that have the Back up files and directories user right could limit the abilities of users who are assigned to specific administrative roles in your environment. You should confirm that authorized backup administrators are still able to perform backup operations.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeBackupPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeBackupPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:167, oval:gov.nist.1:def:234" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="295" ID="{85081419-d966-4da0-99c8-a309788566cf}" OriginalSettingID="{07c9da61-11e4-4a7e-b2ff-e968444f7bc0}" Name="Log on as a service" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9461-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows accounts to start network services or register a process as a service running on the system.</ShortDescription>
<FullDescription>This policy setting allows accounts to launch network services or to register a process as a service running on the system. This user right should be restricted on any computer in a high security environment, but because many applications may require this privilege, it should be carefully evaluated and tested before configuring it in an enterprise environment. On Windows Vista–based computers, no users or groups have this privilege by default.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>NT SERVICE\ALL SERVICES
</DefaultValue>
<Vulnerability>Log on as a service is a powerful user right because it allows accounts to launch network services or services that run continuously on a computer, even when no one is logged on to the console. The risk is reduced by the fact that only users with administrative privileges can install and configure services. An attacker who has already attained that level of access could configure the service to run with the Local System account.</Vulnerability>
<Countermeasure>The default set of security principals that have the Log on as a service user right is restricted to Local System, Local Service, and Network Service, all of which are built-in local accounts. You should minimize the number of other accounts that have this user right.</Countermeasure>
<PotentialImpact>On most computers, this is the default configuration and there will be no negative impact. However, if you have installed optional components such as ASP.NET or IIS, you may need to assign the Log on as a service user right to additional accounts that are required by those components. IIS requires that this user right be explicitly granted to the ASPNET user account. </PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeServiceLogonRight' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeServiceLogonRight" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="296" ID="{f59f14f0-7ab4-46a1-840a-67ba5e41f04f}" OriginalSettingID="{38165ccc-d675-481c-8881-231a5c2032f9}" Name="Lock pages in memory" LockdownDate="2011-10-12T11:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9289-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows a process to keep data in physical memory, which prevents the system from paging the data to virtual memory on disk. </ShortDescription>
<FullDescription>This policy setting allows a process to keep data in physical memory, which prevents the system from paging the data to virtual memory on disk. If this user right is assigned, significant degradation of system performance can occur.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>No one</DefaultValue>
<Vulnerability>Users with the Lock pages in memory user right could assign physical memory to several processes, which could leave little or no RAM for other processes and result in a DoS condition.</Vulnerability>
<Countermeasure>Do not assign the Lock pages in memory user right to any accounts.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeLockMemoryPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeLockMemoryPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:184" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="297" ID="{26a3389d-c92a-43c3-9ddc-e7cfa913f1f2}" OriginalSettingID="{f540aa73-5550-4058-9209-e268908611d5}" Name="Take ownership of files or other objects" LockdownDate="2011-05-15T05:26:31Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9309-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows users to take ownership of files, folders, registry keys, processes, or threads. This user right bypasses any permissions that are in place to protect objects and give ownership to the specified user.</ShortDescription>
<FullDescription>This policy setting allows users to take ownership of files, folders, registry keys, processes, or threads. This user right bypasses any permissions that are in place to protect objects to give ownership to the specified user.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators</DefaultValue>
<Vulnerability>Any users with the Take ownership of files or other objects user right can take control of any object, regardless of the permissions on that object, and then make any changes they wish to that object. Such changes could result in exposure of data, corruption of data, or a DoS condition.</Vulnerability>
<Countermeasure>Ensure that only the local Administrators group has the Take ownership of files or other objects user right.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeTakeOwnershipPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeTakeOwnershipPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:19" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="298" ID="{b608cca7-a88d-4e92-8c56-00c9c07af926}" OriginalSettingID="{361edf21-5cc1-4a97-bef3-2421545e5175}" Name="Profile system performance" LockdownDate="2011-11-09T03:56:56Z" GenerateDCM="true" GenerateSCAP="false" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9419-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows users to use tools to view the performance of different system processes, which could be abused to allow attackers to determine a system's active processes and provide insight into the potential attack surface of the computer.</ShortDescription>
<FullDescription>This policy setting allows users to use tools to view the performance of different system processes, which could be abused to allow attackers to determine a system's active processes and provide insight into the potential attack surface of the computer.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators,NT SERVICE\WdiServiceHost</DefaultValue>
<Vulnerability>The Profile system performance user right poses a moderate vulnerability. Attackers with this user right could monitor a computer's performance to help identify critical processes that they might wish to attack directly. Attackers may also be able to determine what processes are active on the computer so that they could identify countermeasures that they may need to avoid, such as antivirus software or an intrusion detection system.</Vulnerability>
<Countermeasure>Ensure that only the local Administrators group is assigned the Profile system performance user right.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Script" Scope="Machine">
<ScriptDiscoveryInfo>
<mssasc-core:ScriptType>VBScript</mssasc-core:ScriptType>
<mssasc-core:ScriptBody>WScript.Echo ValidateSetting("root\rsop\computer", "RSOP_UserPrivilegeRight", "UserRight='SeSystemProfilePrivilege' and precedence=1", "AccountList", "NT SERVICE\WdiServiceHost,Administrators")
Function ValidateSetting(wmiNamespace, wmiClass, wmiWhere, wmiProperty, baselineValue)
on error resume next
' Get expected values and actual valuse we are testing against
Dim ExpectedValues, ActualValues
ExpectedValues = baselineValue
' Poll WMI
Dim objWMIService, strWQL, objSettings
Set objWMIService = GetObject("winmgmts:\\.\" + wmiNamespace)
strWQL = "Select * from " + wmiClass + " where " + wmiWhere
Set objSettings = objWMIService.ExecQuery(strWQL)
' Set ActualValues for case where no settings are found.
If objSettings.Count = 0 Then
Select Case wmiClass
Case "RSOP_AuditPolicy"
ActualValues = "NO AUDITING"
Case "RSOP_UserPrivilegeRight"
ActualValues = "NO ONE"
Case Else
ActualValues = "Invalid wmiClass parameter: " + wmiClass
End Select
Else
' Set ActualValues with actual settings.
ActualValues = PollWMIForSettings (objSettings, UCase(wmiProperty))
End If
' do our validation
ValidateSetting = ValidateResults(wmiClass, ExpectedValues, ActualValues)
' do error checking, make sure our function return something.
If ValidateSetting = "" Then
ValidateSetting = "ValidateSetting return Nothing or Empty"
If Err.Number <> 0 Then
ValidateSetting = ValidateSetting & ", Error: " & Err.Number
ValidateSetting = ValidateSetting & ", Error (Hex): " & Hex(Err.Number)
ValidateSetting = ValidateSetting & ", Source: " & Err.Source
ValidateSetting = ValidateSetting & ", Description: " & Err.Description
Err.Clear
End If
End If
End Function
'compare two list, isExactMatch=true means two list need exactly macth.
Function CompareTwoListString(expectedListString, actualListString, isExactMatch)
on error resume next
' verify that the actual list is exectly equal to the expected list.
Dim ActualValueList, ExpectedValueList, ActualValue, ExpectedValue, Result
ActualValueList = Split(UCase(actualListString), ",")
ExpectedValueList = Split(UCase(expectedListString), ",")
If isExactMatch = true AND UBound(ExpectedValueList) <> UBound(ActualValueList) Then
CompareTwoListString = false
Exit Function
End If
' Verify all the actual values are in the list of expected values
For Each ActualValue in ActualValueList
' Find if actual value is in list of expected values
Result = false
For Each ExpectedValue in ExpectedValueList
If Trim(ActualValue) = Trim(ExpectedValue) Then
Result = true
Exit For
End If
Next
If Result = false Then
CompareTwoListString = false
Exit Function
End If
Next
'if no need exectly match, when actual value is sub-set of expect value, will return true.
If isExactMatch <> true Then
CompareTwoListString = true
Exit Function
End If
' If we want exactly mathc, so verify all the expected value are in the list of actual value
For Each ExpectedValue in ExpectedValueList
' Find if expected value is in list of actual values
Result = false
For Each ActualValue in ActualValueList
If Trim(ActualValue) = Trim(ExpectedValue) Then
Result = true
Exit For
End If
Next
If Result = false Then
CompareTwoListString = false
Exit Function
End If
Next
' Passsed all tests
CompareTwoListString = true
End Function
' Validate results
Function ValidateResults(wmiClass, ExpectedValues, ActualValues)
on error resume next
Select Case wmiClass
Case "RSOP_AuditPolicy"
If ActualValues = "" Then
If UCase(ExpectedValues) = "NO AUDITING" Then
ValidateResults = ExpectedValues
Else
ValidateResults = "No Auditing"
End If
Exit Function
End If
If CompareTwoListString(ExpectedValues, ActualValues, true) = true Then
ValidateResults = ExpectedValues
Else
ValidateResults = ActualValues
End If
Case "RSOP_UserPrivilegeRight"
' We are always in compliant if no one has the privilege
If Trim(ActualValues) = "" Or UCase(Trim(ActualValues)) = "NO ONE" Then
ValidateResults = ExpectedValues
Exit Function
End If
If CompareTwoListString(ExpectedValues, ActualValues, true) = true Then
ValidateResults = ExpectedValues
Else
ValidateResults = ActualValues
End If
Case Else
' Just return the actual value
ValidateResults = ActualValues
End Select
End Function
' Set ActualValues to a comma deliminated list of values defined by what settings we are polling.
Function PollWMIForSettings(objSettings, wmiProperty)
on error resume next
Dim ActualValues, objSetting, value
ActualValues = ""
' Go through all properties
For Each objSetting in objSettings
For Each value in Split(wmiProperty, ",")
Select Case UCase(Trim(value))
Case "SUCCESS"
If objSetting.Success = True Then
If ActualValues <> "" Then
ActualValues = ActualValues + ","
End If
ActualValues = ActualValues + "SUCCESS"
End If
Case "FAILURE"
If objSetting.Failure = True Then
If ActualValues <> "" Then
ActualValues = ActualValues + ","
End If
ActualValues = ActualValues + "FAILURE"
End If
Case "SETTING"
If ActualValues <> "" Then
ActualValues = ActualValues + ","
End If
ActualValues = ActualValues + objSetting.Setting
Case "ACCOUNTLIST"
If NOT (IsNull(objSetting) Or IsNull(objSetting.AccountList)) Then
For Each strAccount in objSetting.AccountList
If ActualValues <> "" Then
ActualValues = ActualValues + ","
End If
ActualValues = ActualValues + UCase(Right(strAccount, Len(strAccount)))
Next
End If
case Else
ActualValues = ActualValues + "--Unknown property: " + value + " :--"
End Select
Next
Next
PollWMIForSettings = ActualValues
End Function</mssasc-core:ScriptBody>
</ScriptDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeSystemProfilePrivilege" DataType="REG_SZ" />
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="299" ID="{80d8a16f-212f-4ec5-8a57-0769ec3d0d4c}" OriginalSettingID="{5e0f8e3b-f0fe-40be-b155-c4fd56f6c9e1}" Name="Perform volume maintenance tasks" LockdownDate="2011-05-02T01:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8475-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows users to manage the system's volume or disk configuration, which could allow a user to delete a volume and cause data loss as well as a denial-of-service condition.</ShortDescription>
<FullDescription>This policy setting allows users to manage the system's volume or disk configuration, which could allow a user to delete a volume and cause data loss as well as a denial-of-service condition.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators</DefaultValue>
<Vulnerability>A user who is assigned the Perform volume maintenance tasks user right could delete a volume, which could result in the loss of data or a DoS condition.</Vulnerability>
<Countermeasure>Ensure that only the local Administrators group is assigned the Perform volume maintenance tasks user right.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeManageVolumePrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeManageVolumePrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:189" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="300" ID="{887c32a5-df92-4238-b883-a945251768f4}" OriginalSettingID="{b61bd492-74b0-40f3-909d-36b9bf54e94c}" Name="Increase a process working set" LockdownDate="2011-05-22T07:27:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9048-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which user accounts can increase or decrease the size of a process’s working set. The working set of a process is the set of memory pages currently visible to the process in physical random access memory (RAM).</ShortDescription>
<FullDescription>This privilege determines which user accounts can increase or decrease the size of a process’s working set. The working set of a process is the set of memory pages currently visible to the process in physical RAM memory. These pages are resident and available for an application to use without triggering a page fault. The minimum and maximum working set sizes affect the virtual memory paging behavior of a process.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Users</DefaultValue>
<Vulnerability>This right is granted to all users by default. However, increasing the working set size for a process decreases the amount of physical memory available to the rest of the system. It would be possible for malicious code to increase the process working set to a level that could severely degrade system performance and potentially cause a denial of service. </Vulnerability>
<Countermeasure>Certain environments can help mitigate this risk by limiting which users can increase the process working set.</Countermeasure>
<PotentialImpact>Users will be unable to increase the working set for their processes, which could degrade performance.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeIncreaseWorkingSetPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeIncreaseWorkingSetPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="301" ID="{d3820f0b-ba8d-45ab-9c9c-5137a91356a7}" OriginalSettingID="{8dcd558f-d276-493c-86e4-b259adab009b}" Name="Remove computer from docking station" LockdownDate="2011-10-12T11:37:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9326-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows the user of a portable computer to click Eject PC on the Start menu to undock the computer.</ShortDescription>
<FullDescription>This policy setting allows the user of a portable computer to click Eject PC on the Start menu to undock the computer.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators, Users</DefaultValue>
<Vulnerability>Anyone who has the Remove computer from docking station user right can log on and then remove a portable computer from its docking station. If this setting is not defined, it has the same effect as if everyone was granted this right. However, the value of implementing this countermeasure is reduced by the following factors:
• If attackers can restart the computer, they could remove it from the docking station after the BIOS starts but before the operating system starts.
• This setting does not affect servers, because they typically are not installed in docking stations.
• An attacker could steal the computer and the docking station together.
</Vulnerability>
<Countermeasure>Ensure that only the local Administrators group and the user account to which the computer is allocated are assigned the Remove computer from docking station user right.</Countermeasure>
<PotentialImpact>By default, only members of the local Administrator group are granted this right. Other user accounts must be explicitly granted the right as necessary. If your organization's users are not members of the local Administrators groups on their portable computers, they will be unable to remove their own portable computers from their docking stations without shutting them down first. Therefore, you may want to assign the Remove computer from docking station privilege to the local Users group for portable computers.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeUndockPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeUndockPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:192, oval:gov.nist.1:def:236" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="302" ID="{460942f4-ec7f-4eee-8a99-d0cc46ec2a12}" OriginalSettingID="{c25cfa17-7dbb-4699-a9a9-f53962a70de9}" Name="Bypass traverse checking" LockdownDate="2011-10-12T11:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8414-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows users who do not have the special "Traverse Folder" access permission to "pass through" folders when they browse an object path in the NTFS file system or the registry.</ShortDescription>
<FullDescription>This policy setting allows users who do not have the Traverse Folder access permission to pass through folders when they browse an object path in the NTFS file system or the registry. This user right does not allow users to list the contents of a folder.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Everyone, Administrators, Users, Backup Operators, Local Service, Network Service</DefaultValue>
<Vulnerability>The default configuration for the Bypass traverse checking setting is to allow all users, including the Everyone group, to bypass traverse checking. Permissions to files and folders are controlled though appropriate configuration of file system access control lists (ACLs), as the ability to traverse the folder does not provide any read or write permissions to the user. The only scenario in which the default configuration could lead to a mishap would be if the administrator who configures permissions does not understand how this policy setting works. For example, the administrator might expect that users who are unable to access a folder will be unable to access the contents of any child folders. Such a situation is unlikely, and therefore this vulnerability presents little risk.</Vulnerability>
<Countermeasure>Organizations that are extremely concerned about security may want to remove the Everyone group, or perhaps even the Users group, from the list of groups with the Bypass traverse checking user right. Taking explicit control over traversal assignments can be an effective way to limit access to sensitive information. (Also, the Access–based Enumeration feature that was added in Windows Server 2003 with SP1 can be used. If you use access–based enumeration, users cannot see any folder or file to which they do not have access. For more information about this feature, see Access-based Enumeration (http://go.microsoft.com/fwlink/?LinkId=100745).</Countermeasure>
<PotentialImpact>The Windows operating systems, as well as many applications, were designed with the expectation that anyone who can legitimately access the computer will have this user right. Therefore, we recommend that you thoroughly test any changes to assignments of the Bypass traverse checking user right before you make such changes to production systems. In particular, IIS requires this user right to be assigned to the Network Service, Local Service, IIS_WPG, IUSR_<ComputerName>, and IWAM_<ComputerName> accounts. (It must also be assigned to the ASPNET account through its membership in the Users group.) We recommend that you leave this policy setting at its default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeChangeNotifyPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeChangeNotifyPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:168" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="303" ID="{42ca1c76-4099-4347-b219-de35dcf0d889}" OriginalSettingID="{96bc8bd8-d3d6-4f89-8f91-4ea964f2db67}" Name="Create a token object" LockdownDate="2011-10-12T11:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9215-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows a process to create an access token, which may provide elevated rights to access sensitive data.</ShortDescription>
<FullDescription>This policy setting allows a process to create an access token, which may provide elevated rights to access sensitive data.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>No One</DefaultValue>
<Vulnerability>A user account that is given this user right has complete control over the system and can lead to the system being compromised. It is highly recommended that you do not assign any user accounts this right.
The operating system examines a user's access token to determine the level of the user's privileges. Access tokens are built when users log on to the local computer or connect to a remote computer over a network. When you revoke a privilege, the change is immediately recorded, but the change is not reflected in the user's access token until the next time the user logs on or connects. Users with the ability to create or modify tokens can change the level of access for any currently logged on account. They could escalate their own privileges or create a DoS condition.
</Vulnerability>
<Countermeasure>Do not assign the Create a token object user right to any users. Processes that require this user right should use the Local System account, which already includes it, instead of a separate user account that has this user right assigned.</Countermeasure>
<PotentialImpact>None. This is the default configuration.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeCreateTokenPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeCreateTokenPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:171" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="304" ID="{d4ba28a6-fd3a-4ac3-a99c-19e501136098}" OriginalSettingID="{204ff604-1cab-46c8-aa22-01e7d78925e4}" Name="Shut down the system" LockdownDate="2011-10-12T11:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9014-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines which users who are logged on locally can use the Shut Down command to shut down the operating system.</ShortDescription>
<FullDescription>This policy setting determines which users who are logged on locally to the computers in your environment can shut down the operating system with the Shut Down command. Misuse of this user right can result in a denial of service condition.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment</UIPath>
<DefaultValue>Administrators, Backup Operators, Users</DefaultValue>
<Vulnerability>The ability to shut down domain controllers should be limited to a very small number of trusted administrators. Although the Shut down the system user right requires the ability to log on to the server, you should be very careful about which accounts and groups you allow to shut down a domain controller.
When a domain controller is shut down, it is no longer available to process logons, serve Group Policy, and answer Lightweight Directory Access Protocol (LDAP) queries. If you shut down domain controllers that possess Flexible Single–Master Operations (FSMO) roles, you can disable key domain functionality, such as processing logons for new passwords—the Primary Domain Controller (PDC) Emulator role.
</Vulnerability>
<Countermeasure>Ensure that only Administrators and Backup Operators are assigned the Shut down the system user right on member servers, and that only Administrators have it on domain controllers.</Countermeasure>
<PotentialImpact>The impact of removing these default groups from the Shut down the system user right could limit the delegated abilities of assigned roles in your environment. You should confirm that delegated activities will not be adversely affected.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="GeneratedScript (User Rights Assignment)" Scope="Machine">
<WMIDiscoveryInfo>
<mssasc-core:Namespace>root\rsop\computer</mssasc-core:Namespace>
<mssasc-core:Class>RSOP_UserPrivilegeRight</mssasc-core:Class>
<mssasc-core:Property>AccountList</mssasc-core:Property>
<mssasc-core:Where>UserRight='SeShutdownPrivilege' and precedence=1</mssasc-core:Where>
</WMIDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Privilege Rights" Name="SeShutdownPrivilege" DataType="REG_SZ" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:195" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Comment>
</Comment>
</SettingGroup>
<SettingGroup ID="{cb33cbe5-22cd-4ae7-844c-348d318f764c}" Name="Event Logging" OriginalSettingGroupID="{d5a00663-7ec6-49cc-aa32-ed4106bdc79a}">
<mssasc-core:Description>
</mssasc-core:Description>
<mssasc-core:Version Major="1" Minor="0" />
<Author>
</Author>
<Setting Index="305" ID="{7e9c0250-1901-4b7c-8892-cb595774f5b2}" OriginalSettingID="{561441aa-7cd5-4875-81bb-80dc08355b26}" Name="Audit Policy: Policy Change: Authorization Policy Change" LockdownDate="2011-05-02T01:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9633-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The policy setting for this audit category determines whether to audit Authorization Policy changes on computers running Windows Vista or later Windows operating systems.</ShortDescription>
<FullDescription>This subcategory reports changes in authorization policy including permissions (DACL) changes. Events for this subcategory include:
– 4704: A user right was assigned.
– 4705: A user right was removed.
– 4706: A new trust was created to a domain.
– 4707: A trust to a domain was removed.
– 4714: Encrypted data recovery policy was changed.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Policy Change</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9231-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="306" ID="{71c2a926-3e4c-4ff1-bf3e-f8ad9147efa1}" OriginalSettingID="{9f76d6a7-9fd2-49cc-851e-eb5e680cbb63}" Name="Audit Policy: Account Management: Application Group Management" LockdownDate="2011-05-02T01:35:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8822-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting audits Application Group Management events.</ShortDescription>
<FullDescription>This subcategory reports each event of application group management on a computer, such as when an application group is created, changed, or deleted or when a member is added to or removed from an application group. If you enable this Audit policy setting, administrators can track events to detect malicious, accidental, and authorized creation of application group accounts. Events for this subcategory include:
– 4783: A basic application group was created.
– 4784: A basic application group was changed.
– 4785: A member was added to a basic application group.
– 4786: A member was removed from a basic application group.
– 4787: A non-member was added to a basic application group.
– 4788: A non-member was removed from a basic application group.
– 4789: A basic application group was deleted.
– 4790: An LDAP query group was created.
– 4791: A basic application group was changed.
– 4792: An LDAP query group was deleted.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Account Management</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9239-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="307" ID="{1fe39da3-5a53-4748-9315-ac1fc3264495}" OriginalSettingID="{1f5ff83f-8640-48ae-9200-ea70a8f5bc9a}" Name="Audit Policy: Object Access: Detailed File Share" LockdownDate="2011-07-12T11:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9720-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>
</ShortDescription>
<FullDescription>This policy setting allows you to audit attempts to access files and folders on a shared folder. The Detailed File Share setting logs an event every time a file or folder is accessed, whereas the File Share setting only records one event for any connection established between a client and file share. Detailed File Share audit events include detailed information about the permissions or other criteria used to grant or deny access.
If you configure this policy setting, an audit event is generated when an attempt is made to access a file or folder on a share. The administrator can specify whether to audit only successes, only failures, or both successes and failures.
Note: There are no system access control lists (SACLs) for shared folders. If this policy setting is enabled, access to all shared files and folders on the system is audited.
Volume: High on a file server or domain controller because of SYSVOL network access required by Group Policy.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Object Access</UIPath>
<DefaultValue>No Auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9244-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="308" ID="{da9beb22-41fc-4ddc-b25f-5714a26a7868}" OriginalSettingID="{39b1c554-31f2-4119-9139-d2d4f083f9b1}" Name="Audit Policy: Account Logon: Kerberos Service Ticket Operations" LockdownDate="2011-10-12T11:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9148-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The Account Logon audit category generates events for credential validation. </ShortDescription>
<FullDescription>This subcategory reports generated by Kerberos ticket request processes on the domain controller that is authoritative for the domain account. Events for this subcategory include:
– 4769: A Kerberos service ticket was requested.
– 4770: A Kerberos service ticket was renewed.
– 4773: A Kerberos service ticket request failed.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Account Logon</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9240-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="309" ID="{0f91e526-0982-4396-b55c-c30f8e42af96}" OriginalSettingID="{abc8294e-c8cc-4edf-998e-b423d9936c77}" Name="Audit Policy: Detailed Tracking: DPAPI Activity" LockdownDate="2011-05-02T01:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9735-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The Detailed Tracking audit category determines whether to audit detailed tracking information for events such as program activation, process exit, handle duplication, and indirect object access. This setting deals with the DPAPI Activity.</ShortDescription>
<FullDescription>This subcategory reports encrypt or decrypt calls into the data protections application interface (DPAPI). DPAPI is used to protect secret information such as stored password and key information. Events for this subcategory include:
– 4692: Backup of data protection master key was attempted.
– 4693: Recovery of data protection master key was attempted.
– 4694: Protection of auditable protected data was attempted.
– 4695: Unprotection of auditable protected data was attempted.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Detailed Tracking</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE922D-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="310" ID="{36bb6358-988e-4bc1-b9fd-2f45391f49cf}" OriginalSettingID="{070368c6-1f71-47ec-aecc-f999fe465565}" Name="Audit Policy: Detailed Tracking: Process Termination" LockdownDate="2011-05-02T01:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9227-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>Detailed Tracking audit category determines whether to audit detailed tracking information for events such as program activation, process exit, handle duplication, and indirect object access. This setting deals with Process Termination.</ShortDescription>
<FullDescription>This subcategory reports when a process terminates. Events for this subcategory include:
– 4689: A process has exited.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Detailed Tracking</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE922C-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="311" ID="{0fb270b1-ae2b-4106-9d85-45d95edc98bf}" OriginalSettingID="{aad1ad34-9f4f-4c86-b29a-c6710169687c}" Name="Audit Policy: System: Other System Events" LockdownDate="2011-05-02T01:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9586-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting in the System audit category determines whether to audit Other System events on computers that are running Windows Vista or later versions of Windows.</ShortDescription>
<FullDescription>This subcategory reports on other system events. Events for this subcategory include:
– 5024 : The Windows Firewall Service has started successfully.
– 5025 : The Windows Firewall Service has been stopped.
– 5027 : The Windows Firewall Service was unable to retrieve the security policy from the local storage. The service will continue enforcing the current policy.
– 5028 : The Windows Firewall Service was unable to parse the new security policy. The service will continue with currently enforced policy.
– 5029: The Windows Firewall Service failed to initialize the driver. The service will continue to enforce the current policy.
– 5030: The Windows Firewall Service failed to start.
– 5032: Windows Firewall was unable to notify the user that it blocked an application from accepting incoming connections on the network.
– 5033 : The Windows Firewall Driver has started successfully.
– 5034 : The Windows Firewall Driver has been stopped.
– 5035 : The Windows Firewall Driver failed to start.
– 5037 : The Windows Firewall Driver detected critical runtime error. Terminating.
– 5058: Key file operation.
– 5059: Key migration operation.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\System</UIPath>
<DefaultValue>Success and Failure</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9214-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="312" ID="{1c218a4c-9d7e-40ab-8c3a-1d82ec931d15}" OriginalSettingID="{b5b348f9-d7fd-4847-bbb1-0371ea5a3987}" Name="Audit Policy: Object Access: Certification Services" LockdownDate="2011-07-12T11:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9460-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy determines whether to audit the event of a user who attempts to access an object that has a specified system access control list (SACL), effectively enabling auditing to take place. It is targeted to the certification services processes.</ShortDescription>
<FullDescription>This subcategory reports when Certification Services operations are performed. Events for this subcategory include:
– 4868: The certificate manager denied a pending certificate request.
– 4869: Certificate Services received a resubmitted certificate request.
– 4870: Certificate Services revoked a certificate.
– 4871: Certificate Services received a request to publish the certificate revocation list (CRL).
– 4872: Certificate Services published the certificate revocation list (CRL).
– 4873: A certificate request extension changed.
– 4874: One or more certificate request attributes changed.
– 4875: Certificate Services received a request to shut down.
– 4876: Certificate Services backup started.
– 4877: Certificate Services backup completed.
– 4878: Certificate Services restore started.
– 4879: Certificate Services restore completed.
– 4880: Certificate Services started.
– 4881: Certificate Services stopped.
– 4882 : The security permissions for Certificate Services changed.
– 4883: Certificate Services retrieved an archived key.
– 4884: Certificate Services imported a certificate into its database.
– 4885: The audit filter for Certificate Services changed.
– 4886: Certificate Services received a certificate request.
– 4887: Certificate Services approved a certificate request and issued a certificate.
– 4888: Certificate Services denied a certificate request.
– 4889: Certificate Services set the status of a certificate request to pending.
– 4890: The certificate manager settings for Certificate Services changed.
– 4891: A configuration entry changed in Certificate Services.
– 4892: A property of Certificate Services changed.
– 4893: Certificate Services archived a key.
– 4894: Certificate Services imported and archived a key.
– 4895: Certificate Services published the CA certificate to Active Directory Domain Services.
– 4896: One or more rows have been deleted from the certificate database.
– 4897: Role separation enabled:
– 4898: Certificate Services loaded a template.
– 4899: A Certificate Services template was updated.
– 4900: Certificate Services template security was updated.
– 5120: OCSP Responder Service Started.
– 5121: OCSP Responder Service Stopped.
– 5122: A Configuration entry changed in the OCSP Responder Service.
– 5123: A configuration entry changed in the OCSP Responder Service.
– 5124: A security setting was updated on OCSP Responder Service.
– 5125: A request was submitted to OCSP Responder Service.
– 5126: Signing Certificate was automatically updated by the OCSP Responder Service.
– 5127: The OCSP Revocation Provider successfully updated the revocation information.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Object Access</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9221-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="313" ID="{37419dd7-35a5-474d-bbb4-ce55427a8298}" OriginalSettingID="{0e6bf82f-4268-4f02-82a6-64ab3f2adab9}" Name="Audit Policy: DS Access: Directory Service Replication" LockdownDate="2011-05-02T01:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9637-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting for the DS Access audit category enables reports to result when replication between two domain controllers starts and ends.</ShortDescription>
<FullDescription>This subcategory reports when replication between two domain controllers begins and ends. Events for this subcategory include:
– 4932: Synchronization of a replica of an Active Directory naming context has begun.
– 4933: Synchronization of a replica of an Active Directory naming context has ended.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\DS Access</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE923D-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="314" ID="{38d832a9-d3ea-4230-ba72-26af8c02a02a}" OriginalSettingID="{abcedd04-373e-493b-8fc4-610ca4e2c11e}" Name="Audit Policy: Logon-Logoff: Logon" LockdownDate="2011-05-02T01:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9683-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This audit category generates events that record the creation and destruction of logon sessions. This setting targets the Logon settings.</ShortDescription>
<FullDescription>This subcategory reports when a user attempts to log on to the system. These events occur on the accessed computer. For interactive logons, the generation of these events occurs on the computer that is logged on to. If a network logon takes place to access a share, these events generate on the computer that hosts the accessed resource. If you configure this setting to No auditing, it is difficult or impossible to determine which user has accessed or attempted to access organization computers. Events for this subcategory include:
– 4624: An account was successfully logged on.
– 4625: An account failed to log on.
– 4648: A logon was attempted using explicit credentials.
– 4675: SIDs were filtered.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Logon/Logoff</UIPath>
<DefaultValue>Success</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Success and Failure">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9215-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="315" ID="{09f5619f-e1a3-4a6b-aa39-9c8a54a07b5d}" OriginalSettingID="{e54d7bef-4406-4689-813c-ba14b3fd3ef8}" Name="Audit Policy: System: Security State Change" LockdownDate="2011-05-02T01:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9850-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting in the System audit category determines whether to audit Security State changes on computers that are running Windows Vista or later Windows operating systems.</ShortDescription>
<FullDescription>This subcategory reports changes in security state of the system, such as when the security subsystem starts and stops. Events for this subcategory include:
– 4608: Windows is starting up.
– 4609: Windows is shutting down.
– 4616: The system time was changed.
– 4621: Administrator recovered system from CrashOnAuditFail. Users who are not administrators will now be allowed to log on. Some auditable activity might not have been recorded.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\System</UIPath>
<DefaultValue>Success</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Success and Failure">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9210-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="316" ID="{49e0da75-e4ed-4d8b-a98e-5fcd69af95e4}" OriginalSettingID="{aca80b6e-cedf-4dd1-8ecb-ec364e4caa4d}" Name="Audit Policy: Logon-Logoff: Network Policy Server" LockdownDate="2011-10-12T11:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9076-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This audit category generates events that record the creation and destruction of logon sessions. </ShortDescription>
<FullDescription>This subcategory reports events generated by RADIUS (IAS) and Network Access Protection (NAP) user access requests. These requests can be Grant, Deny, Discard, Quarantine, Lock, and Unlock. Auditing this setting will result in a medium or high volume of records on NPS and IAS servers. Events for this subcategory include:
Note All the events in the Network Policy Server subcategory are available only in Windows Vista Service Pack 1 and in Windows Server 2008.
– 6272: Network Policy Server granted access to a user.
– 6273: Network Policy Server denied access to a user.
– 6274: Network Policy Server discarded the request for a user.
– 6275: Network Policy Server discarded the accounting request for a user.
– 6276: Network Policy Server quarantined a user.
– 6277: Network Policy Server granted access to a user but put it on probation because the host did not meet the defined health policy.
– 6278: Network Policy Server granted full access to a user because the host met the defined health policy.
– 6279: Network Policy Server locked the user account due to repeated failed authentication attempts.
– 6280: Network Policy Server unlocked the user account.
– 8191: Network Policy Server unlocked the user account.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Logon/Logoff</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9243-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="317" ID="{e7edf862-c094-4113-8ae7-b89911c06850}" OriginalSettingID="{72b0b48c-f755-44e5-9a80-9f2973e8589a}" Name="Audit Policy: Logon-Logoff: IPsec Extended Mode" LockdownDate="2011-05-02T01:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9661-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This audit category generates events that record the creation and destruction of logon sessions. This setting targets the IPsec Extended Mode settings.</ShortDescription>
<FullDescription>This subcategory reports the results of AuthIP during Extended Mode negotiations. Events for this subcategory include:
– 4978: During Extended Mode negotiation, IPsec received an invalid negotiation packet. If this problem persists, it could indicate a network issue or an attempt to modify or replay this negotiation.
– 4979: IPsec Main Mode and Extended Mode security associations were established.
– 4980: IPsec Main Mode and Extended Mode security associations were established.
– 4981: IPsec Main Mode and Extended Mode security associations were established.
– 4982: IPsec Main Mode and Extended Mode security associations were established.
– 4983: An IPsec Extended Mode negotiation failed. The corresponding Main Mode security association has been deleted.
– 4984: An IPsec Extended Mode negotiation failed. The corresponding Main Mode security association has been deleted.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Logon/Logoff</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE921A-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="318" ID="{d33970c6-6b45-41de-9fa1-c4e62329bbce}" OriginalSettingID="{f3179229-59a3-4c89-8eb2-45cdf42660b1}" Name="Audit Policy: Logon-Logoff: Special Logon" LockdownDate="2011-05-02T01:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9763-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This audit category generates events that record the creation and destruction of logon sessions. This setting targets the special settings defined in the Windows Vista Security Guide.</ShortDescription>
<FullDescription>This subcategory reports when a special logon is used. A special logon is a logon that has administrator-equivalent privileges and can be used to elevate a process to a higher level. Events for this subcategory include:
– 4964 : Special groups have been assigned to a new logon.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Logon/Logoff</UIPath>
<DefaultValue>Success</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Success">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE921B-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="319" ID="{e62dadb5-aaf6-44fc-bb86-b929491ac651}" OriginalSettingID="{b8fc1e7a-57fd-48a0-827e-f466b21663ae}" Name="Audit Policy: System: System Integrity" LockdownDate="2011-05-02T01:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9520-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting in the System audit category determines whether to audit System Integrity changes on computers that are running Windows Vista.</ShortDescription>
<FullDescription>This subcategory reports on violations of integrity of the security subsystem. Events for this subcategory include:
– 4612 : Internal resources allocated for the queuing of audit messages have been exhausted, leading to the loss of some audits.
– 4615 : Invalid use of LPC port.
– 4618 : A monitored security event pattern has occurred.
– 4816 : RPC detected an integrity violation while decrypting an incoming message.
– 5038 : Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error.
– 5056: A cryptographic self test was performed.
– 5057: A cryptographic primitive operation failed.
– 5060: Verification operation failed.
– 5061: Cryptographic operation.
– 5062: A kernel-mode cryptographic self test was performed.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\System</UIPath>
<DefaultValue>Success and Failure</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Success and Failure">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9212-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="320" ID="{db5ecbea-b6cb-4a1c-8757-f4593e9a4bb6}" OriginalSettingID="{312054c9-efe6-4892-8441-77c0bcbfb8a2}" Name="Audit Policy: Account Logon: Kerberos Authentication Service" LockdownDate="2011-06-13T03:16:32Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9258-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The Account Logon audit category generates events for credential validation. </ShortDescription>
<FullDescription>This subcategory reports events generated by the Kerberos Authentication Server. These events occur on the computer that is authoritative for the credentials. Events for this subcategory include:
– 4768: A Kerberos authentication ticket (TGT) was requested.
– 4771: Kerberos pre-authentication failed.
– 4772: A Kerberos authentication ticket request failed.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Account Logon</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9242-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="321" ID="{4f49cb93-d48f-4a74-a1b6-df789d0c147c}" OriginalSettingID="{56d671e2-8ff8-47cd-adeb-82fb86067598}" Name="Audit Policy: Account Management: Security Group Management" LockdownDate="2011-05-02T01:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9692-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting audits Security Group Management events.</ShortDescription>
<FullDescription>This subcategory reports each event of security group management, such as when a security group is created, changed, or deleted or when a member is added to or removed from a security group. If you enable this Audit policy setting, administrators can track events to detect malicious, accidental, and authorized creation of security group accounts. Events for this subcategory include:
– 4727: A security-enabled global group was created.
– 4728: A member was added to a security-enabled global group.
– 4729: A member was removed from a security-enabled global group.
– 4730: A security-enabled global group was deleted.
– 4731: A security-enabled local group was created.
– 4732: A member was added to a security-enabled local group.
– 4733: A member was removed from a security-enabled local group.
– 4734: A security-enabled local group was deleted.
– 4735: A security-enabled local group was changed.
– 4737: A security-enabled global group was changed.
– 4754: A security-enabled universal group was created.
– 4755: A security-enabled universal group was changed.
– 4756: A member was added to a security-enabled universal group.
– 4757: A member was removed from a security-enabled universal group.
– 4758: A security-enabled universal group was deleted.
– 4764: A group’s type was changed.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Account Management</UIPath>
<DefaultValue>Success</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Success and Failure">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9237-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="322" ID="{89d4f42a-8f08-49e2-8566-8903564a4a73}" OriginalSettingID="{504f27d5-2540-48f2-9aa4-ee0eebc84728}" Name="Audit Policy: System: IPsec Driver" LockdownDate="2011-05-02T01:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9925-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting in the System audit category determines whether to audit IPsec Driver events on computers that are running Windows Vista.</ShortDescription>
<FullDescription>This subcategory reports on the activities of the Internet Protocol security (IPsec) driver. Events for this subcategory include:
– 4960: IPsec dropped an inbound packet that failed an integrity check. If this problem persists, it could indicate a network issue or that packets are being modified in transit to this computer. Verify that the packets sent from the remote computer are the same as those received by this computer. This error might also indicate interoperability problems with other IPsec implementations.
– 4961: IPsec dropped an inbound packet that failed a replay check. If this problem persists, it could indicate a replay attack against this computer.
– 4962: IPsec dropped an inbound packet that failed a replay check. The inbound packet had too low a sequence number to ensure it was not a replay.
– 4963: IPsec dropped an inbound clear text packet that should have been secured. This is usually due to the remote computer changing its IPsec policy without informing this computer. This could also be a spoofing attack attempt.
– 4965: IPsec received a packet from a remote computer with an incorrect Security Parameter Index (SPI). This is usually caused by malfunctioning hardware that is corrupting packets. If these errors persist, verify that the packets sent from the remote computer are the same as those received by this computer. This error may also indicate interoperability problems with other IPsec implementations. In that case, if connectivity is not impeded, then these events can be ignored.
– 5478: IPsec Services has started successfully.
– 5479: IPsec Services has been shut down successfully. The shutdown of IPsec Services can put the computer at greater risk of network attack or expose the computer to potential security risks.
– 5480: IPsec Services failed to get the complete list of network interfaces on the computer. This poses a potential security risk because some of the network interfaces may not get the protection provided by the applied IPsec filters. Use the IP Security Monitor snap-in to diagnose the problem.
– 5483: IPsec Services failed to initialize RPC server. IPsec Services could not be started.
– 5484: IPsec Services has experienced a critical failure and has been shut down. The shutdown of IPsec Services can put the computer at greater risk of network attack or expose the computer to potential security risks.
– 5485: IPsec Services failed to process some IPsec filters on a plug-and-play event for network interfaces. This poses a potential security risk because some of the network interfaces may not get the protection provided by the applied IPsec filters. Use the IP Security Monitor snap-in to diagnose the problem.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\System</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Success and Failure">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9213-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="323" ID="{6b9ad7b8-5118-415d-9265-5001b3a56c2a}" OriginalSettingID="{48b4f45e-2950-4a72-a0da-66f87a4f6208}" Name="Audit Policy: Account Logon: Other Account Logon Events" LockdownDate="2011-05-02T01:35:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9808-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting audits logon events other than credential validation and Kerberos Ticket Events.</ShortDescription>
<FullDescription>This subcategory reports the events that occur in response to credentials submitted for a user account logon request that do not relate to credential validation or Kerberos tickets. These events occur on the computer that is authoritative for the credentials. For domain accounts, the domain controller is authoritative, whereas for local accounts, the local computer is authoritative. In domain environments, most of the Account Logon events occur in the Security log of the domain controllers that are authoritative for the domain accounts. However, these events can occur on other computers in the organization when local accounts are used to log on.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Account Logon</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9241-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="324" ID="{e87ca912-7d3b-4065-863f-306ee183334d}" OriginalSettingID="{79a516e0-3fc6-4173-b412-a7532f0c604d}" Name="Audit Policy: Object Access: SAM" LockdownDate="2011-07-12T11:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9856-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The policy setting controls whether to audit users who have accessed the Security Accounts Manager (SAM) object on computers running Windows Vista or later Windows operating systems.</ShortDescription>
<FullDescription>This subcategory reports when SAM objects are accessed. Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Object Access</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9220-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="325" ID="{6a94cbec-a238-4ae4-9beb-f32d393c2d15}" OriginalSettingID="{f0238fe5-80bc-4feb-83a7-3e70bd621d83}" Name="Audit Policy: Object Access: Kernel Object" LockdownDate="2011-07-12T11:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9803-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This settings determines whether to audit the event of a user who attempts to access an object that has a specified system access control list (SACL), effectively enabling auditing to take place. It is targeted to Kernal Object access processes.</ShortDescription>
<FullDescription>This subcategory reports when kernel objects such as processes and mutexes are accessed. Only kernel objects with SACLs cause audit events to be generated, and only when they are accessed in a manner matching their SACL. Typically kernel objects are only given SACLs if the AuditBaseObjects or AuditBaseDirectories auditing options are enabled.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Object Access</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE921F-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="326" ID="{ad3db651-0d72-4f1f-9869-227fdf5eb177}" OriginalSettingID="{a28ddc45-464d-4cee-a675-9a3dfe0c07c7}" Name="Audit Policy: Logon-Logoff: Account Lockout" LockdownDate="2011-05-02T01:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8853-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This audit category generates events that record the creation and destruction of logon sessions. This setting targets the Logon-Logoff Account Lockout setting.</ShortDescription>
<FullDescription>This subcategory reports when a user's account is locked out as a result of too many failed logon attempts. Events for this subcategory include:
– 4625: An account failed to log on.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Logon/Logoff</UIPath>
<DefaultValue>Success</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9217-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="327" ID="{55b55248-b303-4316-afcb-4cb4fba97222}" OriginalSettingID="{4237d39f-ea09-47d6-96bb-91b199d9c384}" Name="Audit Policy: Logon-Logoff: Other Logon/Logoff Events" LockdownDate="2011-05-02T01:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9622-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This audit category generates events that record the creation and destruction of logon sessions.</ShortDescription>
<FullDescription>This subcategory reports other logon/logoff-related events, such as Terminal Services session disconnects and reconnects, using RunAs to run processes under a different account, and locking and unlocking a workstation. Events for this subcategory include:
– 4649: A replay attack was detected.
– 4778: A session was reconnected to a Window Station.
– 4779: A session was disconnected from a Window Station.
– 4800: The workstation was locked.
– 4801: The workstation was unlocked.
– 4802: The screen saver was invoked.
– 4803: The screen saver was dismissed.
– 5378: The requested credentials delegation was disallowed by policy.
– 5632: A request was made to authenticate to a wireless network.
– 5633: A request was made to authenticate to a wired network.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Logon/Logoff</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE921C-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="328" ID="{0d81866d-0bd6-4df0-8c2f-86751536b022}" OriginalSettingID="{b881554b-111f-46a8-9079-b9eeb9ea60f6}" Name="Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" LockdownDate="2011-08-05T07:16:32Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9432-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting allows administrators to enable the more precise auditing capabilities present in Windows Vista. Uses subcategory setting to override audit policy categories.</ShortDescription>
<FullDescription>This policy setting allows administrators to enable the more precise auditing capabilities present in Windows Vista.
The Audit Policy settings available in Windows Server 2003 Active Directory do not yet contain settings for managing the new auditing subcategories. To properly apply the auditing policies prescribed in this baseline, the Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings setting needs to be configured to Enabled.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not defined</DefaultValue>
<Vulnerability>Prior to the introduction of auditing subcategories in Windows Vista, it was difficult to track events at a per-system or per-user level. The larger event categories created too many events and the key information that needed to be audited was difficult to find. </Vulnerability>
<Countermeasure>Enable audit policy subcategories as needed to track specific events. </Countermeasure>
<PotentialImpact>The individual audit policy subcategories that are available in Windows Vista are not exposed in the interface of Group Policy tools. Administrators can deploy a custom audit policy that applies detailed security auditing settings to Windows Vista-based client computers in a Windows Server 2003 domain or in a Windows 2000 domain. If after enabling this setting, you attempt to modify an auditing setting by using Group Policy, the Group Policy auditing setting will be ignored in favor of the custom policy setting. To modify auditing settings by using Group Policy, you must first disable this key.
Important
Be very cautious about audit settings that can generate a large volume of traffic. For example, if you enable either success or failure auditing for all of the Privilege Use subcategories, the high volume of audit events generated can make it difficult to find other types of entries in the Security log. Such a configuration could also have a significant impact on system performance.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Enabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>scenoapplylegacyauditpolicy</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\SCENoApplyLegacyAuditPolicy" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="329" ID="{c11bf343-b498-4209-b0c6-e28de6440be0}" OriginalSettingID="{b5aecffd-079f-4217-bbf0-fb20af1d7a2e}" Name="Audit Policy: Account Management: Distribution Group Management" LockdownDate="2011-05-02T01:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9644-6">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting audits Distribution Group Management events.</ShortDescription>
<FullDescription>This subcategory reports each event of distribution group management, such as when a distribution group is created, changed, or deleted or when a member is added to or removed from a distribution group. If you enable this Audit policy setting, administrators can track events to detect malicious, accidental, and authorized creation of group accounts. Events for this subcategory include:
– 4744: A security-disabled local group was created.
– 4745: A security-disabled local group was changed.
– 4746: A member was added to a security-disabled local group.
– 4747: A member was removed from a security-disabled local group.
– 4748: A security-disabled local group was deleted.
– 4749: A security-disabled global group was created.
– 4750: A security-disabled global group was changed.
– 4751: A member was added to a security-disabled global group.
– 4752: A member was removed from a security-disabled global group.
– 4753: A security-disabled global group was deleted.
– 4759: A security-disabled universal group was created.
– 4760: A security-disabled universal group was changed.
– 4761: A member was added to a security-disabled universal group.
– 4762: A member was removed from a security-disabled universal group.
– 4763: A security-disabled universal group was deleted.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Account Management</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9238-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="330" ID="{bf2194fc-6a41-469f-8952-4ffa8b6b52eb}" OriginalSettingID="{ebd86e7c-c2be-461a-9db9-c4f9fd79e32f}" Name="Audit Policy: Account Logon: Credential Validation" LockdownDate="2011-06-13T03:16:32Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9725-3">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The Account Logon audit category generates events for credential validation. These events occur on the computer that is authoritative for the credentials.</ShortDescription>
<FullDescription>This subcategory reports the results of validation tests on credentials submitted for a user account logon request. These events occur on the computer that is authoritative for the credentials. For domain accounts, the domain controller is authoritative, whereas for local accounts, the local computer is authoritative. In domain environments, most of the Account Logon events occur in the Security log of the domain controllers that are authoritative for the domain accounts. However, these events can occur on other computers in the organization when local accounts are used to log on. Events for this subcategory include:
– 4774: An account was mapped for logon.
– 4775: An account could not be mapped for logon.
– 4776: The domain controller attempted to validate the credentials for an account.
– 4777: The domain controller failed to validate the credentials for an account.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Account Logon</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Success and Failure">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE923F-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="331" ID="{914f78ce-7f5d-4de5-a9a9-a0363fbac31c}" OriginalSettingID="{2ea0de1a-c71d-46c8-8350-a7dd4d447895}" Name="Audit Policy: Account Management: Other Account Management Events" LockdownDate="2011-05-02T01:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9657-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting audits Other Account Management events.</ShortDescription>
<FullDescription>This subcategory reports other account management events. Events for this subcategory include:
– 4782: The password hash an account was accessed.
– 4793: The Password Policy Checking API was called.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Account Management</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Success and Failure">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE923A-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="332" ID="{31ecfc9a-3c80-4d57-923e-6c7001525b08}" OriginalSettingID="{5bd3a1dc-6de8-4021-a1a7-f1cf51f51235}" Name="Audit Policy: System: Security System Extension" LockdownDate="2011-05-02T01:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9863-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting in the System audit category determines whether to audit Security System Extension changes on computers that are running Windows Vista or later Windows operating systems.</ShortDescription>
<FullDescription>This subcategory reports the loading of extension code such as authentication packages by the security subsystem. Events for this subcategory include:
– 4610: An authentication package has been loaded by the Local Security Authority.
– 4611: A trusted logon process has been registered with the Local Security Authority.
– 4614: A notification package has been loaded by the Security Account Manager.
– 4622: A security package has been loaded by the Local Security Authority.
– 4697: A service was installed in the system.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\System</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Success and Failure">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9211-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="333" ID="{5b7b64d4-cee6-499b-b1fe-f645735cdc49}" OriginalSettingID="{5c16519e-7075-4814-8d32-1e05b869b7d3}" Name="Audit Policy: Object Access: Registry" LockdownDate="2011-07-12T11:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9737-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This settings determines whether to audit the event of a user who accesses an object that has a specified system access control list (SACL), effectively enabling auditing to take place. It is targeted to Registry Object access events.</ShortDescription>
<FullDescription>This subcategory reports when registry objects are accessed. Only registry objects with SACLs cause audit events to be generated, and only when they are accessed in a manner matching their SACL. By itself, this policy setting will not cause auditing of any events. It determines whether to audit the event of a user who accesses a registry object that has a specified system access control list (SACL), effectively enabling auditing to take place.
A SACL is comprised of access control entries (ACEs). Each ACE contains three pieces of information:
• The security principal (user, computer, or group) to be audited.
• The specific access type to be audited, called an access mask.
• A flag to indicate whether to audit failed access events, successful access events, or both.
If you configure the Audit object access setting to Success, an audit entry is generated each time that a user successfully accesses an object with a specified SACL. If you configure this policy setting to Failure, an audit entry is generated each time that a user fails in an attempt to access an object with a specified SACL.
Organizations should define only the actions they want enabled when they configure SACLs. For example, you might want to enable the Write and Append Data auditing setting on executable files to track when they are changed or replaced, because computer viruses, worms, and Trojan horses typically target executable files. Similarly, you might want to track when sensitive documents are accessed or changed.
Events for this subcategory include:
– 4657 : A registry value was modified.
– 5039: A registry key was virtualized.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Object Access</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE921E-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="334" ID="{9842896d-04aa-453c-9503-66cde229db61}" OriginalSettingID="{866ba9bb-ea1e-45bc-aa8a-4700d56615f4}" Name="Audit Policy: Privilege Use: Other Privilege Use Events" LockdownDate="2011-05-02T01:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9988-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting applies to Other Privilege Use Events subcategory of events. You can use it to audit users exercising user rights.</ShortDescription>
<FullDescription>This subcategory reports when a user account or service uses a sensitive privilege. A sensitive privilege includes the following user rights: Act as part of the operating system, Back up files and directories, Create a token object, Debug programs, Enable computer and user accounts to be trusted for delegation, Generate security audits, Impersonate a client after authentication, Load and unload device drivers, Manage auditing and security log, Modify firmware environment values, Replace a process-level token, Restore files and directories, and Take ownership of files or other objects. Auditing this subcategory will create a high volume of events. Events for this subcategory include:
– 4672: Special privileges assigned to new logon.
– 4673: A privileged service was called.
– 4674: An operation was attempted on a privileged object.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Privilege Use</UIPath>
<DefaultValue>No Auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE922A-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="335" ID="{8c86ec8b-ea18-4c6e-8c76-412f295967e9}" OriginalSettingID="{c1802c70-87b8-4167-867b-2d93fd66b826}" Name="Audit Policy: Object Access: File Share" LockdownDate="2011-07-12T11:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9376-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting determines whether to audit the event of a user who attempts to access an object that has a specified system access control list (SACL), effectively enabling auditing to take place. This setting is targeted to File Share access operations.</ShortDescription>
<FullDescription>This subcategory reports when a file share is accessed. By itself, this policy setting will not cause auditing of any events. It determines whether to audit the event of a user who accesses a file share object that has a specified system access control list (SACL), effectively enabling auditing to take place.
A SACL is comprised of access control entries (ACEs). Each ACE contains three pieces of information:
• The security principal (user, computer, or group) to be audited.
• The specific access type to be audited, called an access mask.
• A flag to indicate whether to audit failed access events, successful access events, or both.
If you configure the Audit object access setting to Success, an audit entry is generated each time that a user successfully accesses an object with a specified SACL. If you configure this policy setting to Failure, an audit entry is generated each time that a user fails in an attempt to access an object with a specified SACL.
Organizations should define only the actions they want enabled when they configure SACLs. For example, you might want to enable the Write and Append Data auditing setting on executable files to track when they are changed or replaced, because computer viruses, worms, and Trojan horses typically target executable files. Similarly, you might want to track when sensitive documents are accessed or changed.
Events for this subcategory include:
– 5140: A network share object was accessed.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Object Access</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9224-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="336" ID="{a8e68b1c-604e-46ac-909a-7208c6d21772}" OriginalSettingID="{5e887dce-109d-4619-b532-731ad234824a}" Name="Audit Policy: DS Access: Directory Service Changes" LockdownDate="2011-05-02T01:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9734-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting in the DS Access audit category enables reports to result when changes to create, modify, move, or undelete operations are performed on objects in Active Directory Domain Services (AD DS).</ShortDescription>
<FullDescription>This subcategory reports changes to objects in Active Directory Domain Services (AD DS). The types of changes that are reported are create, modify, move, and undelete operations that are performed on an object. DS Change auditing, where appropriate, indicates the old and new values of the changed properties of the objects that were changed. Only objects with SACLs cause audit events to be generated, and only when they are accessed in a manner that matches their SACL. Some objects and properties do not cause audit events to be generated due to settings on the object class in the schema. This subcategory applies only to domain controllers. Events for this subcategory include:
– 5136 : A directory service object was modified.
– 5137 : A directory service object was created.
– 5138 : A directory service object was undeleted.
– 5139 : A directory service object was moved.
Note The following event in the Directory Service Changes subcategory is available only in Windows Vista Service Pack 1 and in Windows Server 2008.
– 5141: A directory service object was deleted.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\DS Access</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE923C-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="337" ID="{8aa78998-b2dd-4aea-9f09-a68bfbb9d32b}" OriginalSettingID="{bd2f2b74-c1cb-4413-a92d-c4dfb73e7279}" Name="Audit Policy: Policy Change: Other Policy Change Events" LockdownDate="2011-05-02T01:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9596-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The policy setting for this audit category determines whether to audit Other Policy Change events on computers running Windows Vista or later Windows operating systems.</ShortDescription>
<FullDescription>This subcategory reports other types of security policy changes such as configuration of the Trusted Platform Module (TPM) or cryptographic providers. Events for this subcategory include:
– 4909: The local policy settings for the TBS were changed.
– 4910: The group policy settings for the TBS were changed.
– 5063: A cryptographic provider operation was attempted.
– 5064: A cryptographic context operation was attempted.
– 5065: A cryptographic context modification was attempted.
– 5066: A cryptographic function operation was attempted.
– 5067: A cryptographic function modification was attempted.
– 5068: A cryptographic function provider operation was attempted.
– 5069: A cryptographic function property operation was attempted.
– 5070: A cryptographic function property modification was attempted.
– 5447: A Windows Filtering Platform filter has been changed.
– 6144: Security policy in the group policy objects has been applied successfully.
– 6145: One or more errors occurred while processing security policy in the group policy objects.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Policy Change</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9234-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="338" ID="{29b1d926-1928-45bb-953a-5033235e064c}" OriginalSettingID="{854a078d-a0aa-43d7-9a32-3489b7d8d7ae}" Name="Audit: Audit the access of global system objects" LockdownDate="2011-05-02T01:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9150-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting creates a default system access control list (SACL) for system objects such as mutexes (mutual exclusive), events, semaphores, and MS-DOS devices, and causes access to these system objects to be audited.</ShortDescription>
<FullDescription>This policy setting creates a default system access control list (SACL) for system objects such as mutexes (mutual exclusive), events, semaphores, and MS-DOS devices, and causes access to these system objects to be audited.
If the Audit: Audit the access of global system objects setting is enabled, a very large number of security events could quickly fill the Security event log.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>A globally visible named object, if incorrectly secured, could be acted upon by malicious software that knows the name of the object. For instance, if a synchronization object such as a mutex had a poorly chosen discretionary access control list (DACL), then malicious software could access that mutex by name and cause the program that created it to malfunction. However, the risk of such an occurrence is very low.</Vulnerability>
<Countermeasure>Enable the Audit: Audit the access of global system objects setting.</Countermeasure>
<PotentialImpact>If you enable the Audit: Audit the access of global system objects setting, a large number of security events could be generated, especially on busy domain controllers and application servers. Such an occurrence could cause servers to respond slowly and force the Security log to record numerous events of little significance. This policy setting can only be enabled or disabled, and there is no way to choose which events are recorded. Even organizations that have the resources to analyze events that are generated by this policy setting would not likely have the source code or a description of what each named object is used for. Therefore, it is unlikely that many organizations could benefit by enabling this policy setting.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>AuditBaseObjects</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\AuditBaseObjects" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:45" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="339" ID="{9b4f5ded-0f09-4e8c-b1ee-0b94ae015201}" OriginalSettingID="{821af41f-7ff7-4dae-a841-c098b7112b0c}" Name="Audit Policy: Policy Change: Audit Policy Change" LockdownDate="2011-05-02T01:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10021-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The Policy Change audit category determines whether to audit every incident of a change to user rights assignment policies, Windows Firewall policies, Trust policies, or changes to the Audit policy itself.</ShortDescription>
<FullDescription>This subcategory reports changes in audit policy including SACL changes. Events for this subcategory include:
– 4715: The audit policy (SACL) on an object was changed.
– 4719: System audit policy was changed.
– 4902: The Per-user audit policy table was created.
– 4904: An attempt was made to register a security event source.
– 4905: An attempt was made to unregister a security event source.
– 4906: The CrashOnAuditFail value has changed.
– 4907: Auditing settings on object were changed.
– 4908: Special Groups Logon table modified.
– 4912: Per User Audit Policy was changed.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Policy Change</UIPath>
<DefaultValue>Success</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Success and Failure">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE922F-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="340" ID="{bda8c721-de8a-4565-9e6c-ec653cc1a362}" OriginalSettingID="{c1aa5f37-73e5-4abf-85f5-601b5a28623c}" Name="Audit Policy: Object Access: File System" LockdownDate="2011-10-31T10:45:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9217-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This settings determines whether to audit the event of a user who attempts to access an object that has a specified system access control list (SACL), effectively enabling auditing to take place. It is targeted to File System object access processes.</ShortDescription>
<FullDescription>This subcategory reports when file system objects are accessed. Only file system objects with SACLs cause audit events to be generated, and only when they are accessed in a manner matching their SACL. By itself, this policy setting will not cause auditing of any events. It determines whether to audit the event of a user who accesses a file system object that has a specified system access control list (SACL), effectively enabling auditing to take place.
A SACL is comprised of access control entries (ACEs). Each ACE contains three pieces of information:
• The security principal (user, computer, or group) to be audited.
• The specific access type to be audited, called an access mask.
• A flag to indicate whether to audit failed access events, successful access events, or both.
If you configure the Audit object access setting to Success, an audit entry is generated each time that a user successfully accesses an object with a specified SACL. If you configure this policy setting to Failure, an audit entry is generated each time that a user fails in an attempt to access an object with a specified SACL.
Organizations should define only the actions they want enabled when they configure SACLs. For example, you might want to enable the Write and Append Data auditing setting on executable files to track when they are changed or replaced, because computer viruses, worms, and Trojan horses typically target executable files. Similarly, you might want to track when sensitive documents are accessed or changed.
Events for this subcategory include:
– 4664: An attempt was made to create a hard link.
– 4985: The state of a transaction has changed.
– 5051: A file was virtualized.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Object Access</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE921D-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="341" ID="{eba1c827-a52f-4859-a825-9030ad7a4676}" OriginalSettingID="{17bbd596-ee57-4506-b4eb-b8914b2d8b34}" Name="Audit Policy: Account Management: User Account Management" LockdownDate="2011-05-02T01:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9542-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting audits Account Management events.</ShortDescription>
<FullDescription>This subcategory reports each event of user account management, such as when a user account is created, changed, or deleted; a user account is renamed, disabled, or enabled; or a password is set or changed. If you enable this Audit policy setting, administrators can track events to detect malicious, accidental, and authorized creation of user accounts. Events for this subcategory include:
– 4720: A user account was created.
– 4722: A user account was enabled.
– 4723: An attempt was made to change an account's password.
– 4724: An attempt was made to reset an account's password.
– 4725: A user account was disabled.
– 4726: A user account was deleted.
– 4738: A user account was changed.
– 4740: A user account was locked out.
– 4765: SID History was added to an account.
– 4766: An attempt to add SID History to an account failed.
– 4767: A user account was unlocked.
– 4780: The ACL was set on accounts which are members of administrators groups.
– 4781: The name of an account was changed:
– 4794: An attempt was made to set the Directory Services Restore Mode.
– 5376: Credential Manager credentials were backed up.
– 5377: Credential Manager credentials were restored from a backup.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Account Management</UIPath>
<DefaultValue>Success</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Success and Failure">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9235-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="342" ID="{451ba901-735a-4ed1-9fe6-7cec1817d16a}" OriginalSettingID="{c6105a0f-00eb-4789-8ccb-06cf25b6add3}" Name="Audit Policy: DS Access: Detailed Directory Service Replication" LockdownDate="2011-06-13T03:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9628-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting in the DS Access audit category enables domain controllers to report detailed information about information that replicates between domain controllers.</ShortDescription>
<FullDescription>This subcategory reports detailed information about the information replicating between domain controllers. These events can be very high in volume. Events for this subcategory include:
– 4928: An Active Directory replica source naming context was established.
– 4929 : An Active Directory replica source naming context was removed.
– 4930 : An Active Directory replica source naming context was modified.
– 4931 : An Active Directory replica destination naming context was modified.
– 4934 : Attributes of an Active Directory object were replicated.
– 4935 : Replication failure begins.
– 4936 : Replication failure ends.
– 4937 : A lingering object was removed from a replica.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\DS Access</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE923E-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="343" ID="{e3367498-746b-444a-ae06-d5c1b7792fa9}" OriginalSettingID="{9c282479-a942-4863-9f47-84d94426eb33}" Name="Audit Policy: Logon-Logoff: IPsec Main Mode" LockdownDate="2011-05-02T01:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8956-5">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This audit category generates events that record the creation and destruction of logon sessions. This setting targets the IPsec Main Mode settings.</ShortDescription>
<FullDescription>This subcategory reports the results of Internet Key Exchange (IKE) protocol and Authenticated Internet Protocol (AuthIP) during Main Mode negotiations. Events for this subcategory include:
– 4646: IKE DoS-prevention mode started.
– 4650: An IPsec Main Mode security association was established. Extended Mode was not enabled. Certificate authentication was not used.
– 4651: An IPsec Main Mode security association was established. Extended Mode was not enabled. A certificate was used for authentication.
– 4652: An IPsec Main Mode negotiation failed.
– 4653: An IPsec Main Mode negotiation failed.
– 4655: An IPsec Main Mode security association ended.
– 4976: During Main Mode negotiation, IPsec received an invalid negotiation packet. If this problem persists, it could indicate a network issue or an attempt to modify or replay this negotiation.
– 5049: An IPsec Security Association was deleted.
– 5453: An IPsec negotiation with a remote computer failed because the IKE and AuthIP IPsec Keying Modules (IKEEXT) service is not started.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Logon/Logoff</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9218-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="344" ID="{5bdc9cfc-9552-48c7-a2e0-7002a2de1808}" OriginalSettingID="{2768f99a-87a1-4be6-bf44-efcfd1412dea}" Name="Audit Policy: Policy Change: Authentication Policy Change" LockdownDate="2011-05-02T01:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9976-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The policy setting for this audit category determines whether to audit Authentication Policy changes on computers running Windows Vista or later Windows operating systems.</ShortDescription>
<FullDescription>This subcategory reports changes in authentication policy. Events for this subcategory include:
– 4706: A new trust was created to a domain.
– 4707: A trust to a domain was removed.
– 4713: Kerberos policy was changed.
– 4716: Trusted domain information was modified.
– 4717: System security access was granted to an account.
– 4718: System security access was removed from an account.
– 4739: Domain Policy was changed.
– 4864: A namespace collision was detected.
– 4865: A trusted forest information entry was added.
– 4866: A trusted forest information entry was removed.
– 4867: A trusted forest information entry was modified.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Policy Change</UIPath>
<DefaultValue>Success</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Success">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9230-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="345" ID="{20d07ce6-0aeb-4c0f-9174-37a83aa961f2}" OriginalSettingID="{4f7ecb8a-7516-42f4-ad65-89596bc987d2}" Name="Audit Policy: Object Access: Handle Manipulation" LockdownDate="2011-07-12T11:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9789-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This settings determines whether to audit the event of a user who attempts to access an object that has a specified system access control list (SACL), effectively enabling auditing to take place. It is targeted to Handle Manipulation on Windows objects.</ShortDescription>
<FullDescription>This subcategory reports when a handle to an object is opened or closed. Only objects with SACLs cause these events to be generated, and only if the attempted handle operation matches the SACL. Handle Manipulation events are only generated for object types where the corresponding Object Access subcategory is enabled, for example File System or Registry. Events for this subcategory include:
– 4656: A handle to an object was requested.
– 4658: The handle to an object was closed.
– 4690: An attempt was made to duplicate a handle to an object.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Object Access</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9223-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="346" ID="{5f461288-fa20-4afb-bbcf-b16678b9b4e0}" OriginalSettingID="{a94d7f10-22ff-48e8-bd82-1dfc5ccb1cb4}" Name="Audit Policy: Account Management: Computer Account Management" LockdownDate="2011-06-13T03:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9498-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting audits Computer Account Management events.</ShortDescription>
<FullDescription>This subcategory reports each event of computer account management, such as when a computer account is created, changed, deleted, renamed, disabled, or enabled. Events for this subcategory include:
– 4741: A computer account was created.
– 4742: A computer account was changed.
– 4743: A computer account was deleted.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Account Management</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Success">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9236-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="347" ID="{cb289093-c8ea-45cb-82f0-5207b1be480d}" OriginalSettingID="{390b33ac-8fa0-4c26-b15c-c2056743857e}" Name="Audit Policy: Policy Change: MPSSVC Rule-Level Policy Change" LockdownDate="2011-05-02T01:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9153-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The policy setting for this audit category determines whether to audit MPSSVC Rule-Level Policy changes on computers running Windows Vista or later Windows operating systems.</ShortDescription>
<FullDescription>This subcategory reports changes in policy rules used by the Microsoft Protection Service (MPSSVC.exe). This service is used by Windows Firewall and by Microsoft OneCare. Events for this subcategory include:
– 4944: The following policy was active when the Windows Firewall started.
– 4945: A rule was listed when the Windows Firewall started.
– 4946: A change has been made to Windows Firewall exception list. A rule was added.
– 4947: A change has been made to Windows Firewall exception list. A rule was modified.
– 4948: A change has been made to Windows Firewall exception list. A rule was deleted.
– 4949: Windows Firewall settings were restored to the default values.
– 4950: A Windows Firewall setting has changed.
– 4951: A rule has been ignored because its major version number was not recognized by Windows Firewall.
– 4952 : Parts of a rule have been ignored because its minor version number was not recognized by Windows Firewall. The other parts of the rule will be enforced.
– 4953: A rule has been ignored by Windows Firewall because it could not parse the rule.
– 4954: Windows Firewall Group Policy settings have changed. The new settings have been applied.
– 4956: Windows Firewall has changed the active profile.
– 4957: Windows Firewall did not apply the following rule:
– 4958: Windows Firewall did not apply the following rule because the rule referred to items not configured on this computer:
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Policy Change</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9232-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="348" ID="{2d6b97d6-7a62-4f49-b857-efe8a8483a4f}" OriginalSettingID="{b76ef57e-563d-4741-a283-865d37250ca8}" Name="Audit Policy: Object Access: Filtering Platform Packet Drop" LockdownDate="2011-07-12T11:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9133-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This settings determines whether to audit the event of a user who attempts to access an object that has a specified system access control list (SACL), effectively enabling auditing to take place. It is targeted to dropped packet events by the Filtering Pl</ShortDescription>
<FullDescription>This subcategory reports when packets are dropped by Windows Filtering Platform (WFP). These events can be very high in volume. Events for this subcategory include:
– 5152: The Windows Filtering Platform blocked a packet.
– 5153: A more restrictive Windows Filtering Platform filter has blocked a packet.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Object Access</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9225-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="349" ID="{3c6a3b59-78e7-422b-9a41-bca745e440f0}" OriginalSettingID="{4aebc02d-1987-41b1-878a-33e558e308be}" Name="Audit Policy: Privilege Use: Non Sensitive Privilege Use" LockdownDate="2011-05-02T01:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9190-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting applies to the Non Sensitive Privilege Use subcategory of events. You can use it to audit users exercising user rights.</ShortDescription>
<FullDescription>This subcategory reports when a user account or service uses a non-sensitive privilege. A non-sensitive privilege includes the following user rights: Access Credential Manager as a trusted caller, Access this computer from the network, Add workstations to domain, Adjust memory quotas for a process, Allow log on locally, Allow log on through Terminal Services, Bypass traverse checking, Change the system time, Create a pagefile, Create global objects, Create permanent shared objects, Create symbolic links, Deny access this computer from the network, Deny log on as a batch job, Deny log on as a service, Deny log on locally, Deny log on through Terminal Services, Force shutdown from a remote system, Increase a process working set, Increase scheduling priority, Lock pages in memory, Log on as a batch job, Log on as a service, Modify an object label, Perform volume maintenance tasks, Profile single process, Profile system performance, Remove computer from docking station, Shut down the system, and Synchronize directory service data. Auditing this subcategory will create a very high volume of events. Events for this subcategory include:
– 4672: Special privileges assigned to new logon.
– 4673: A privileged service was called.
– 4674: An operation was attempted on a privileged object.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Privilege Use</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9229-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="350" ID="{8360778a-69bb-4499-be39-0a588ea4f1ee}" OriginalSettingID="{4b0a5f5f-f8e0-42ea-870e-4b935fde16a5}" Name="Audit Policy: Object Access: Other Object Access Events" LockdownDate="2011-07-12T11:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9455-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This settings determines whether to audit the event of a user who accesses an object that has a specified system access control list (SACL), effectively enabling auditing to take place. It is targeted to Other Object Access events.</ShortDescription>
<FullDescription>This subcategory reports other object access-related events such as Task Scheduler jobs and COM+ objects. Events for this subcategory include:
– 4671: An application attempted to access a blocked ordinal through the TBS.
– 4691: Indirect access to an object was requested.
– 4698: A scheduled task was created.
– 4699 : A scheduled task was deleted.
– 4700 : A scheduled task was enabled.
– 4701: A scheduled task was disabled.
– 4702 : A scheduled task was updated.
– 5888: An object in the COM+ Catalog was modified.
– 5889: An object was deleted from the COM+ Catalog.
– 5890: An object was added to the COM+ Catalog.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Object Access</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9227-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="351" ID="{51594bd7-beec-4d17-9f67-7f537a2697d1}" OriginalSettingID="{846ed96d-48c5-4ea0-a6e3-965e4a000cb4}" Name="Audit Policy: Policy Change: Filtering Platform Policy Change" LockdownDate="2011-05-02T01:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9902-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The policy setting for this audit category determines whether to audit Filtering Platform Policy changes on computers running Windows Vista or later Windows operating systems.</ShortDescription>
<FullDescription>This subcategory reports the addition and removal of objects from WFP, including startup filters. These events can be very high in volume. Events for this subcategory include:
– 4709: IPsec Services was started.
– 4710: IPsec Services was disabled.
– 4711: May contain any one of the following:
• PAStore Engine applied locally cached copy of Active Directory storage IPsec policy on the computer.
• PAStore Engine applied Active Directory storage IPsec policy on the computer.
• PAStore Engine applied local registry storage IPsec policy on the computer.
• PAStore Engine failed to apply locally cached copy of Active Directory storage IPsec policy on the computer.
• PAStore Engine failed to apply Active Directory storage IPsec policy on the computer.
• PAStore Engine failed to apply local registry storage IPsec policy on the computer.
• PAStore Engine failed to apply some rules of the active IPsec policy on the computer.
• PAStore Engine failed to load directory storage IPsec policy on the computer.
• PAStore Engine loaded directory storage IPsec policy on the computer.
• PAStore Engine failed to load local storage IPsec policy on the computer.
• PAStore Engine loaded local storage IPsec policy on the computer.
• PAStore Engine polled for changes to the active IPsec policy and detected no changes.
– 4712: IPsec Services encountered a potentially serious failure.
– 5040: A change has been made to IPsec settings. An Authentication Set was added.
– 5041: A change has been made to IPsec settings. An Authentication Set was modified.
– 5042: A change has been made to IPsec settings. An Authentication Set was deleted.
– 5043: A change has been made to IPsec settings. A Connection Security Rule was added.
– 5044: A change has been made to IPsec settings. A Connection Security Rule was modified.
– 5045: A change has been made to IPsec settings. A Connection Security Rule was deleted.
– 5046: A change has been made to IPsec settings. A Crypto Set was added.
– 5047: A change has been made to IPsec settings. A Crypto Set was modified.
– 5048: A change has been made to IPsec settings. A Crypto Set was deleted.
– 5440: The following callout was present when the Windows Filtering Platform Base Filtering Engine started.
– 5441: The following filter was present when the Windows Filtering Platform Base Filtering Engine started.
– 5442: The following provider was present when the Windows Filtering Platform Base Filtering Engine started.
– 5443: The following provider context was present when the Windows Filtering Platform Base Filtering Engine started.
– 5444 : The following sub-layer was present when the Windows Filtering Platform Base Filtering Engine started.
– 5446: A Windows Filtering Platform callout has been changed.
– 5448: A Windows Filtering Platform provider has been changed.
– 5449: A Windows Filtering Platform provider context has been changed.
– 5450: A Windows Filtering Platform sub-layer has been changed.
– 5456: PAStore Engine applied Active Directory storage IPsec policy on the computer.
– 5457: PAStore Engine failed to apply Active Directory storage IPsec policy on the computer.
– 5458 : PAStore Engine applied locally cached copy of Active Directory storage IPsec policy on the computer.
– 5459: PAStore Engine failed to apply locally cached copy of Active Directory storage IPsec policy on the computer.
– 5460: PAStore Engine applied local registry storage IPsec policy on the computer.
– 5461: PAStore Engine failed to apply local registry storage IPsec policy on the computer.
– 5462: PAStore Engine failed to apply some rules of the active IPsec policy on the computer. Use the IP Security Monitor snap-in to diagnose the problem.
– 5463: PAStore Engine polled for changes to the active IPsec policy and detected no changes.
– 5464: PAStore Engine polled for changes to the active IPsec policy, detected changes, and applied them to IPsec Services.
– 5465: PAStore Engine received a control for forced reloading of IPsec policy and processed the control successfully.
– 5466: PAStore Engine polled for changes to the Active Directory IPsec policy, determined that Active Directory cannot be reached, and will use the cached copy of the Active Directory IPsec policy instead. Any changes made to the Active Directory IPsec policy since the last poll could not be applied.
– 5467: PAStore Engine polled for changes to the Active Directory IPsec policy, determined that Active Directory can be reached, and found no changes to the policy. The cached copy of the Active Directory IPsec policy is no longer being used.
– 5468: PAStore Engine polled for changes to the Active Directory IPsec policy, determined that Active Directory can be reached, found changes to the policy, and applied those changes. The cached copy of the Active Directory IPsec policy is no longer being used.
– 5471: PAStore Engine loaded local storage IPsec policy on the computer.
– 5472: PAStore Engine failed to load local storage IPsec policy on the computer.
– 5473: PAStore Engine loaded directory storage IPsec policy on the computer.
– 5474: PAStore Engine failed to load directory storage IPsec policy on the computer.
– 5477: PAStore Engine failed to add quick mode filter.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Policy Change</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9233-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="352" ID="{9d9e663b-d39a-467a-9efb-ec56805b72d6}" OriginalSettingID="{9fae3ac5-92b8-41f6-817c-2357c3885be9}" Name="Audit Policy: Logon-Logoff: IPsec Quick Mode" LockdownDate="2011-05-02T01:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9632-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This audit category generates events that record the creation and destruction of logon sessions. This setting targets IPsec Quick Mode settings.</ShortDescription>
<FullDescription>This subcategory reports the results of IKE protocol and AuthIP during Quick Mode negotiations.
– 4654: An IPsec Quick Mode negotiation failed. Events for this subcategory include:
– 4977: During Quick Mode negotiation, IPsec received an invalid negotiation packet. If this problem persists, it could indicate a network issue or an attempt to modify or replay this negotiation.
– 5451: An IPsec Quick Mode security association was established.
– 5452: An IPsec Quick Mode security association ended.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Logon/Logoff</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9219-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="353" ID="{57b9f5c0-ecfc-4efa-800c-eb6c972ee318}" OriginalSettingID="{6598ae0c-9227-4f87-b754-f68d2f5820fc}" Name="Audit Policy: Detailed Tracking: Process Creation" LockdownDate="2011-05-02T01:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9562-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The Detailed Tracking audit category determines whether to audit detailed tracking information for events such as program activation, process exit, handle duplication, and indirect object access. This setting deals with Process Creation.</ShortDescription>
<FullDescription>This subcategory reports the creation of a process and the name of the program or user that created it. Events for this subcategory include:
– 4688: A new process has been created.
– 4696: A primary token was assigned to process.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Detailed Tracking</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Success">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE922B-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="354" ID="{406d0b5b-c2ef-452e-ab6c-3cb93da75706}" OriginalSettingID="{08d34924-4c27-4af4-8d2b-ed772f0c992e}" Name="Audit Policy: Object Access: Application Generated" LockdownDate="2011-07-12T11:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9816-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting determines whether to audit the event of a user who accesses an object that has a specified system access control list (SACL), effectively enabling auditing to take place. It targets application generated events.</ShortDescription>
<FullDescription>This subcategory reports when applications attempt to generate audit events by using the Windows auditing application programming interfaces (APIs). Events for this subcategory include:
– 4665: An attempt was made to create an application client context.
– 4666: An application attempted an operation:
– 4667: An application client context was deleted.
– 4668: An application was initialized.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Object Access</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9222-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="355" ID="{4faa8055-18b0-47e4-b3ea-b66ce86568ad}" OriginalSettingID="{df146b9e-754a-4c93-a878-97780a135274}" Name="Audit: Audit the use of Backup and Restore privilege" LockdownDate="2011-05-02T01:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8789-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether to audit the use of all user privileges, including Backup and Restore, when the Audit privilege use setting is in effect.</ShortDescription>
<FullDescription>This policy setting determines whether to audit the use of all user privileges, including Backup and Restore, when the Audit privilege use setting is in effect. If you enable both policies, an audit event will be generated for every file that is backed up or restored.
If the Audit: Audit the use of Backup and Restore privilege setting is enabled, a very large number of security events could quickly fill the Security event log.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>When back up and restore is used it creates a copy of the file system that is identical to the target of the backup. Making regular backups and restore volumes is an important part of a your incident response plan, but a malicious user could use a legitimate backup copy to get access to information or spoof a legitimate network resource to compromise your enterprise. </Vulnerability>
<Countermeasure>Enable the Audit use of Backup and Restore privilege setting. Alternatively, implement automatic log backup by configuring the AutoBackupLogFiles registry key. If you enable this option when the Audit privilege use setting is also enabled, an audit event is generated for every file that is backed up or restored. This information could help you to identify an account that was used to accidentally or maliciously restore data in an unauthorized manner.
For more information about configuring this key, see article 100879, The event log stops logging events before reaching the maximum log size, in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=100879).
</Countermeasure>
<PotentialImpact>If you enable this policy setting, a large number of security events could be generated, which could cause servers to respond slowly and force the Security event log to record numerous events of little significance. If you increase the Security log size to reduce the chances of a system shutdown, an excessively large log file may affect system performance.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Not Defined">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="00" />
<SCAPValue ValueA="00" />
<GPOValue ValueA="00" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="01" />
<SCAPValue ValueA="01" />
<GPOValue ValueA="01" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_BINARY</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>fullprivilegeauditing</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Binary</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\FullPrivilegeAuditing" DataType="REG_BINARY" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:52" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="356" ID="{b2304c80-0de3-4f72-ad5d-9462323c217d}" OriginalSettingID="{87497709-c19c-4769-9ea4-87af6f40db3d}" Name="Audit Policy: Object Access: Filtering Platform Connection" LockdownDate="2011-07-12T11:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9728-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting determines whether to audit the event of a user who attempts to access an object that has a specified system access control list (SACL), effectively enabling auditing to take place. It is targeted to connections to the Filtering Platform.</ShortDescription>
<FullDescription>This subcategory reports when connections are allowed or blocked by WFP. These events can be high in volume. Events for this subcategory include:
– 5031: The Windows Firewall Service blocked an application from accepting incoming connections on the network.
– 5154: The Windows Filtering Platform has permitted an application or service to listen on a port for incoming connections.
– 5155 : The Windows Filtering Platform has blocked an application or service from listening on a port for incoming connections.
– 5156: The Windows Filtering Platform has allowed a connection.
– 5157: The Windows Filtering Platform has blocked a connection.
– 5158: The Windows Filtering Platform has permitted a bind to a local port.
– 5159: The Windows Filtering Platform has blocked a bind to a local port.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Object Access</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9226-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="357" ID="{f31c70aa-dd23-4679-93a2-10ad2ae72174}" OriginalSettingID="{5c9c8613-01a7-4694-8550-778c7c1b5d4b}" Name="Audit Policy: DS Access: Directory Service Access" LockdownDate="2011-05-02T01:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9765-9">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting in the DS Access audit category enables reports to result when Active Directory Domain Services (AD DS) objects are accessed.</ShortDescription>
<FullDescription>This subcategory reports when an AD DS object is accessed. Only objects with SACLs cause audit events to be generated, and only when they are accessed in a manner that matches their SACL. These events are similar to the directory service access events in previous versions of Windows Server. This subcategory applies only to domain controllers. Events for this subcategory include:
– 4662 : An operation was performed on an object.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\DS Access</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE923B-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="358" ID="{c8a945da-c435-49b5-8828-db0fa665be10}" OriginalSettingID="{591401f2-3712-4434-ae22-e8633dcf2ad5}" Name="Audit Policy: Privilege Use: Sensitive Privilege Use" LockdownDate="2011-05-02T01:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9878-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This setting applies to the Sensitive Privilege Use subcategory of events. You can use it to audit users exercising user rights.</ShortDescription>
<FullDescription>This subcategory reports when a user account or service uses a sensitive privilege. A sensitive privilege includes the following user rights: Act as part of the operating system, Back up files and directories, Create a token object, Debug programs, Enable computer and user accounts to be trusted for delegation, Generate security audits, Impersonate a client after authentication, Load and unload device drivers, Manage auditing and security log, Modify firmware environment values, Replace a process-level token, Restore files and directories, and Take ownership of files or other objects. Auditing this subcategory will create a high volume of events. Events for this subcategory include:
– 4672: Special privileges assigned to new logon.
– 4673: A privileged service was called.
– 4674: An operation was attempted on a privileged object.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Privilege Use</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a Denial of Service. If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Success and Failure">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9228-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="359" ID="{7391bbd7-06f8-4277-b3a6-a09dbf6cc2cd}" OriginalSettingID="{9f28bf93-31ae-4a09-b064-a391772fe13d}" Name="Audit Policy: Logon-Logoff: Logoff" LockdownDate="2011-06-13T03:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-8856-7">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This audit category generates events that record the creation and destruction of logon sessions. This setting targets the Logoff event settings.</ShortDescription>
<FullDescription>This subcategory reports when a user logs off from the system. These events occur on the accessed computer. For interactive logons, the generation of these events occurs on the computer that is logged on to. If a network logon takes place to access a share, these events generate on the computer that hosts the accessed resource. If you configure this setting to No auditing, it is difficult or impossible to determine which user has accessed or attempted to access organization computers. Events for this subcategory include:
– 4634: An account was logged off.
– 4647: User initiated logoff.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Logon/Logoff</UIPath>
<DefaultValue>Success</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Success">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE9216-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="360" ID="{780ca8bc-addf-4311-8a8d-879b0678e3ad}" OriginalSettingID="{6f40d10a-7998-417e-8718-1f9a60d291b3}" Name="Audit Policy: Detailed Tracking: RPC Events" LockdownDate="2011-05-02T01:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9492-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The Detailed Tracking audit category determines whether to audit detailed tracking information for events, such as program activation, process exit, handle duplication, and indirect object access. This setting is focused on RPC events.</ShortDescription>
<FullDescription>This subcategory reports remote procedure call (RPC) connection events. Events for this subcategory include:
– 5712: A Remote Procedure Call (RPC) was attempted.
Refer to the Microsoft Knowledgebase article “Description of security events in Windows Vista and in Windows Server 2008” for the most recent information about this setting: http://support.microsoft.com/default.aspx/kb/947226.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Detailed Tracking</UIPath>
<DefaultValue>No auditing</DefaultValue>
<Vulnerability>If audit settings are not configured, it can be difficult or impossible to determine what occurred during a security incident. However, if audit settings are configured so that events are generated for all activities the Security log will be filled with data and hard to use. Also, you can use a large amount of data storage as well as adversely affect overall computer performance if you configure audit settings for a large number of objects.
If failure auditing is used and the Audit: Shut down system immediately if unable to log security audits setting in the Security Options section of Group Policy is enabled, an attacker could generate millions of failure events such as logon failures in order to fill the Security log and force the computer to shut down, creating a denial of service (DoS). If security logs are allowed to be overwritten, an attacker can overwrite part or all of their activity by generating large numbers of events so that the evidence of their intrusion is overwritten.</Vulnerability>
<Countermeasure>Enable Audit policy settings that support the organizational security policy for all the computers in your organization. Identify the components that you need for an audit policy that enables your organization to hold users accountable for their actions while using organizational resources and enables IT departments to detect unauthorized activity efficiently and then track those events in log files.</Countermeasure>
<PotentialImpact>If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="No Auditing">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Success">
<BehaviorDescription />
<DCMValue ValueA="Success" />
<SCAPValue ValueA="Success" />
<GPOValue ValueA="success" />
</Mapping>
<Mapping FriendlyName="Failure">
<BehaviorDescription />
<DCMValue ValueA="Failure" />
<SCAPValue ValueA="Failure" />
<GPOValue ValueA="failure" />
</Mapping>
<Mapping FriendlyName="Success and Failure">
<BehaviorDescription />
<DCMValue ValueA="Success and Failure" />
<SCAPValue ValueA="Success and Failure" />
<GPOValue ValueA="success and failure" />
</Mapping>
<Mapping FriendlyName="No Auditing">
<BehaviorDescription />
<DCMValue ValueA="No Auditing" />
<SCAPValue ValueA="No Auditing" />
<GPOValue ValueA="no auditing" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="AdvancedAuditPolicy" Scope="Machine">
<AdvancedAuditDiscoveryInfo>
<mssasc-core:AdvancedAuditSettingID>{0CCE922E-69AE-11D9-BED3-505054503030}</mssasc-core:AdvancedAuditSettingID>
</AdvancedAuditDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="CSV">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Comment>
</Comment>
</SettingGroup>
<SettingGroup ID="{55090040-22a3-4565-ac1c-3df7b2d40752}" Name="Logging Configuration" OriginalSettingGroupID="{4f12115a-3aff-4ef4-b7ec-3c37c3e65565}">
<mssasc-core:Description>
</mssasc-core:Description>
<mssasc-core:Version Major="1" Minor="0" />
<Author>
</Author>
<Setting Index="361" ID="{d3da926f-5048-4cae-a7ec-d9adfc976284}" OriginalSettingID="{67df32ce-77ba-4def-ab25-61536d146e60}" Name="Maximum Log Size (KB)" LockdownDate="2011-05-02T01:36:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9603-2">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy requires Windows Vista or later versions of Windows, it specifies the maximum size of the log file in kilobytes.</ShortDescription>
<FullDescription>This policy requires Windows Vista or later versions of Windows. This policy setting specifies the maximum size of the log file in kilobytes. If you enable this policy setting, you can configure the maximum log file size to be between 1 megabyte (1024 kilobytes) and 2 terabytes (2147483647 kilobytes) in kilobyte increments. If you disable or do not configure this policy setting, the maximum size of the log file maximum size will be set to the local configuration value. This value can be changed by the local administrator using the log properties dialog and it defaults to 20 megabytes. For backwards compatibility the same setting can also be configured at Computer Configuration\Windows Settings\Security Settings\Event Log, if set at both locations this one will take precedence.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Event Log Service\Application</UIPath>
<DefaultValue>20480 KB</DefaultValue>
<Vulnerability>If events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users</Vulnerability>
<Countermeasure>You should enable sensible log size policies for all computers in your organization so that legitimate users can be held accountable for their actions, unauthorized activity can be detected and tracked, and computer problems can be detected and diagnosed.</Countermeasure>
<PotentialImpact>When event logs fill to capacity, they will stop recording information unless the retention method for each is set so that the computer will overwrite the oldest entries with the most recent ones. To mitigate the risk of loss of recent data, you can configure the retention method so that older events are overwritten as needed.
The consequence of this configuration is that older events will be removed from the logs. Attackers can take advantage of such a configuration, because they can generate a large number of extraneous events to overwrite any evidence of their attack. These risks can be somewhat reduced if you automate the archival and backup of event log data.
Ideally, all specifically monitored events should be sent to a server that uses Microsoft Operations Manager (MOM) or some other automated monitoring tool. Such a configuration is particularly important because an attacker who successfully compromises a server could clear the Security log. If all events are sent to a monitoring server, then you will be able to gather forensic information about the attacker's activities.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine" />
<DataType>String</DataType>
</DiscoveryInfo>
<policy name="Channel_LogMaxSize_1" class="Machine" displayName="$(string.ae6bfb71a5fb4bf4bd316b26e6b229f4)" explainText="$(string.afdf2ee6389b435e885612df228d94d0)" presentation="$(presentation.Channel_LogMaxSize_1)" key="Software\Policies\Microsoft\Windows\EventLog\Application">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:elements xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal id="Channel_LogMaxSize" key="Software\Policies\Microsoft\Windows\EventLog\Application" valueName="MaxSize" minValue="1024" maxValue="2147483647" />
</admx:elements>
</policy>
<ADMLDefinition>
<presentation id="Channel_LogMaxSize_1">
<admx:decimalTextBox refId="Channel_LogMaxSize" defaultValue="1024" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Maximum Log Size (KB)</admx:decimalTextBox>
</presentation>
<string id="ae6bfb71a5fb4bf4bd316b26e6b229f4">Maximum Log Size (KB)</string>
<string id="afdf2ee6389b435e885612df228d94d0">This policy requires Windows Vista or later versions of Windows. This policy setting specifies the maximum size of the log file in kilobytes. If you enable this policy setting, you can configure the maximum log file size to be between 1 megabyte (1024 kilobytes) and 2 terabytes (2147483647 kilobytes) in kilobyte increments. If you disable or do not configure this policy setting, the maximum size of the log file maximum size will be set to the local configuration value. This value can be changed by the local administrator using the log properties dialog and it defaults to 20 megabytes. For backwards compatibility the same setting can also be configured at Computer Configuration\Windows Settings\Security Settings\Event Log, if set at both locations this one will take precedence.</string>
</ADMLDefinition>
<supportedOn>At least Windows Vista</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="362" ID="{4a721ef9-3518-433f-a603-444921aab28e}" OriginalSettingID="{76e64466-6461-4950-95ae-dd69521f5b10}" Name="Retain old events" LockdownDate="2011-10-12T11:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9500-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy requires Windows Vista or later versions of Windows, it specifies the maximum size of the log file in kilobytes.</ShortDescription>
<FullDescription>This policy setting controls Event Log behavior when the log file reaches its maximum size. Old events may or may not be retained according to the “Backup log automatically when full” policy setting.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Event Log Service\Security</UIPath>
<DefaultValue>Not configured</DefaultValue>
<Vulnerability>If new events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users</Vulnerability>
<Countermeasure>Configure this setting to Disabled. </Countermeasure>
<PotentialImpact>When this policy setting is enabled and a log file reaches its maximum size, new events are not written to the log and are lost. When this policy setting is disabled and a log file reaches its maximum size, new events overwrite old events.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows\EventLog\Security</mssasc-core:KeyPath>
<mssasc-core:ValueName>Retention</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<policy name="Channel_Log_Retention_2" class="Machine" displayName="$(string.54a9676053524d8fb975026101fa130c)" explainText="$(string.1f08ff9f4a8a4779b52323ef7fa9a0ba)" key="Software\Policies\Microsoft\Windows\EventLog\Security" valueName="Retention">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:string>1</admx:string>
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:string>0</admx:string>
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="54a9676053524d8fb975026101fa130c">Retain old events</string>
<string id="1f08ff9f4a8a4779b52323ef7fa9a0ba">This policy setting controls Event Log behavior when the log file reaches its maximum size. Old events may or may not be retained according to the “Backup log automatically when full” policy setting.</string>
</ADMLDefinition>
<supportedOn>At least Windows Vista</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="363" ID="{8cbe4d06-bbd5-4fdb-8701-0a922fcb860a}" OriginalSettingID="{e2e11f15-b46c-44f4-829d-5012808ca980}" Name="Retain old events" LockdownDate="2011-10-12T11:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10064-4">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy requires Windows Vista or later versions of Windows, it specifies the maximum size of the log file in kilobytes.</ShortDescription>
<FullDescription>This policy setting controls Event Log behavior when the log file reaches its maximum size. Old events may or may not be retained according to the “Backup log automatically when full” policy setting.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Event Log Service\System</UIPath>
<DefaultValue>Not configured</DefaultValue>
<Vulnerability>If new events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users</Vulnerability>
<Countermeasure>Configure this setting to Disabled. </Countermeasure>
<PotentialImpact>When this policy setting is enabled and a log file reaches its maximum size, new events are not written to the log and are lost. When this policy setting is disabled and a log file reaches its maximum size, new events overwrite old events.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows\EventLog\System</mssasc-core:KeyPath>
<mssasc-core:ValueName>Retention</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<policy name="Channel_Log_Retention_4" class="Machine" displayName="$(string.13a50fbdeadd48dc8a2ed12ed8d632f6)" explainText="$(string.f0a2185a65974911a0dcb6bdb5b1af40)" key="Software\Policies\Microsoft\Windows\EventLog\System" valueName="Retention">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:string>1</admx:string>
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:string>0</admx:string>
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="13a50fbdeadd48dc8a2ed12ed8d632f6">Retain old events</string>
<string id="f0a2185a65974911a0dcb6bdb5b1af40">This policy setting controls Event Log behavior when the log file reaches its maximum size. Old events may or may not be retained according to the “Backup log automatically when full” policy setting.</string>
</ADMLDefinition>
<supportedOn>At least Windows Vista</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="364" ID="{c690159e-9b73-4bab-abbb-4341c2179837}" OriginalSettingID="{9b1bedaf-67d8-4d82-983e-300f0738996a}" Name="Maximum Log Size (KB)" LockdownDate="2011-10-31T10:45:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-00000-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy requires Windows Vista or later versions of Windows, it specifies the maximum size of the log file in kilobytes.</ShortDescription>
<FullDescription>This policy requires Windows Vista or later versions of Windows. This policy setting specifies the maximum size of the log file in kilobytes. If you enable this policy setting, you can configure the maximum log file size to be between 1 megabyte (1024 kilobytes) and 2 terabytes (2147483647 kilobytes) in kilobyte increments. If you disable or do not configure this policy setting, the maximum size of the log file maximum size will be set to the local configuration value. This value can be changed by the local administrator using the log properties dialog and it defaults to 20 megabytes. For backwards compatibility the same setting can also be configured at Computer Configuration\Windows Settings\Security Settings\Event Log, if set at both locations this one will take precedence.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Event Log Service\Security</UIPath>
<DefaultValue>20480 KB</DefaultValue>
<Vulnerability>If you significantly increase the number of objects to audit in your organization, there is a risk that the Security log will reach its capacity and force the computer to shut down if you enabled the Audit: Shut down system immediately if unable to log security audits setting. If such a shutdown occurs, the computer will be unusable until an administrator clears the Security log. To prevent such a shutdown, you can disable the Audit: Shut down system immediately if unable to log security audits setting that is described in Chapter 5, "Security Options," and increase the Security log size. Alternatively, you can configure automatic log rotation as described in the Microsoft Knowledge Base article "The event log stops logging events before reaching the maximum log size" at http://support.microsoft.com/default.aspx?kbid=312571.</Vulnerability>
<Countermeasure>You should enable sensible log size policies for all computers in your organization so that legitimate users can be held accountable for their actions, unauthorized activity can be detected and tracked, and computer problems can be detected and diagnosed.</Countermeasure>
<PotentialImpact>When event logs fill to capacity, they will stop recording information unless the retention method for each is set so that the computer will overwrite the oldest entries with the most recent ones. To mitigate the risk of loss of recent data, you can configure the retention method so that older events are overwritten as needed.
The consequence of this configuration is that older events will be removed from the logs. Attackers can take advantage of such a configuration, because they can generate a large number of extraneous events to overwrite any evidence of their attack. These risks can be somewhat reduced if you automate the archival and backup of event log data.
Ideally, all specifically monitored events should be sent to a server that uses Microsoft Operations Manager (MOM) or some other automated monitoring tool. Such a configuration is particularly important because an attacker who successfully compromises a server could clear the Security log. If all events are sent to a monitoring server, then you will be able to gather forensic information about the attacker's activities.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine" />
<DataType>String</DataType>
</DiscoveryInfo>
<policy name="Channel_LogMaxSize_2" class="Machine" displayName="$(string.39821a6e72f04c8a80155dc7ad2180e7)" explainText="$(string.0df1c968565d4f9eb4f23ab305fb2fb9)" presentation="$(presentation.Channel_LogMaxSize_2)" key="Software\Policies\Microsoft\Windows\EventLog\Security">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:elements xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal id="Channel_LogMaxSize" key="Software\Policies\Microsoft\Windows\EventLog\Security" valueName="MaxSize" minValue="20480" maxValue="2147483647" />
</admx:elements>
</policy>
<ADMLDefinition>
<presentation id="Channel_LogMaxSize_2">
<admx:decimalTextBox refId="Channel_LogMaxSize" defaultValue="20480" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Maximum Log Size (KB)</admx:decimalTextBox>
</presentation>
<string id="39821a6e72f04c8a80155dc7ad2180e7">Maximum Log Size (KB)</string>
<string id="0df1c968565d4f9eb4f23ab305fb2fb9">This policy requires Windows Vista or later versions of Windows. This policy setting specifies the maximum size of the log file in kilobytes. If you enable this policy setting, you can configure the maximum log file size to be between 1 megabyte (1024 kilobytes) and 2 terabytes (2147483647 kilobytes) in kilobyte increments. If you disable or do not configure this policy setting, the maximum size of the log file maximum size will be set to the local configuration value. This value can be changed by the local administrator using the log properties dialog and it defaults to 20 megabytes. For backwards compatibility the same setting can also be configured at Computer Configuration\Windows Settings\Security Settings\Event Log, if set at both locations this one will take precedence.</string>
</ADMLDefinition>
<supportedOn>At least Windows Vista</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="365" ID="{6aada6cc-42d5-4331-9be4-a5c0155495af}" OriginalSettingID="{450b73e6-5bad-4c64-8d1f-abffea2f08d7}" Name="Retain old events" LockdownDate="2011-10-12T11:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10136-0">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy requires Windows Vista or later versions of Windows, it specifies the maximum size of the log file in kilobytes.</ShortDescription>
<FullDescription>This policy setting controls Event Log behavior when the log file reaches its maximum size. Old events may or may not be retained according to the “Backup log automatically when full” policy setting.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Event Log Service\Application</UIPath>
<DefaultValue>Not configured</DefaultValue>
<Vulnerability>If new events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users</Vulnerability>
<Countermeasure>Configure this setting to Disabled. </Countermeasure>
<PotentialImpact>When this policy setting is enabled and a log file reaches its maximum size, new events are not written to the log and are lost. When this policy setting is disabled and a log file reaches its maximum size, new events overwrite old events.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_SZ</mssasc-core:DataType>
<mssasc-core:KeyPath>Software\Policies\Microsoft\Windows\EventLog\Application</mssasc-core:KeyPath>
<mssasc-core:ValueName>Retention</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>String</DataType>
</DiscoveryInfo>
<policy name="Channel_Log_Retention_1" class="Machine" displayName="$(string.041a3064ea1b4e31ac1942d001868eea)" explainText="$(string.c4d53992aeca4839b9d4c377b1d11d18)" key="Software\Policies\Microsoft\Windows\EventLog\Application" valueName="Retention">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:enabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:string>1</admx:string>
</admx:enabledValue>
<admx:disabledValue xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:string>0</admx:string>
</admx:disabledValue>
</policy>
<ADMLDefinition>
<string id="041a3064ea1b4e31ac1942d001868eea">Retain old events</string>
<string id="c4d53992aeca4839b9d4c377b1d11d18">This policy setting controls Event Log behavior when the log file reaches its maximum size. Old events may or may not be retained according to the “Backup log automatically when full” policy setting.</string>
</ADMLDefinition>
<supportedOn>At least Windows Vista</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="366" ID="{1f29245a-401d-476e-b508-7fdb4006f22e}" OriginalSettingID="{25c67f65-0d37-41d5-9e75-72707c97a290}" Name="Audit: Shut down system immediately if unable to log security audits" LockdownDate="2011-05-02T01:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9463-1">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy setting determines whether the system shuts down if it is unable to log Security events. </ShortDescription>
<FullDescription>This policy setting determines whether the system shuts down if it is unable to log Security events. It is a requirement for Trusted Computer System Evaluation Criteria (TCSEC)-C2 and Common Criteria certification to prevent auditable events from occurring if the audit system is unable to log them. Microsoft has chosen to meet this requirement by halting the system and displaying a stop message if the auditing system experiences a failure. When this policy setting is enabled, the system will be shut down if a security audit cannot be logged for any reason.
If the Audit: Shut down system immediately if unable to log security audits setting is enabled, unplanned system failures can occur. Therefore, this policy setting is configured to Not Defined for both of the environments that are discussed in this chapter.
</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Disabled</DefaultValue>
<Vulnerability>If the computer is unable to record events to the Security log, critical evidence or important troubleshooting information may not be available for review after a security incident. Also, an attacker could potentially generate a large volume of Security log events to purposely force a computer shutdown.</Vulnerability>
<Countermeasure>Enable the Shut down system immediately if unable to log security audits setting.</Countermeasure>
<PotentialImpact>If you enable this policy setting, the administrative burden can be significant, especially if you also configure the Retention method for the Security log to Do not overwrite events (clear log manually). This configuration causes a repudiation threat (a backup operator could deny that they backed up or restored data) to become a denial of service (DoS) vulnerability, because a server could be forced to shut down if it is overwhelmed with logon events and other security events that are written to the Security log. Also, because the shutdown is not graceful, it is possible that irreparable damage to the operating system, applications, or data could result. Although the NTFS file system guarantees its integrity when an ungraceful computer shutdown occurs, it cannot guarantee that every data file for every application will still be in a usable form when the computer restarts.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable SelectedFriendlyName="Disabled">
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
<Mapping FriendlyName="Disabled">
<BehaviorDescription />
<DCMValue ValueA="0" />
<SCAPValue ValueA="0" />
<GPOValue ValueA="0" />
</Mapping>
<Mapping FriendlyName="Enabled">
<BehaviorDescription />
<DCMValue ValueA="1" />
<SCAPValue ValueA="1" />
<GPOValue ValueA="1" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>System\CurrentControlSet\Control\Lsa</mssasc-core:KeyPath>
<mssasc-core:ValueName>crashonauditfail</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\System\CurrentControlSet\Control\Lsa\CrashOnAuditFail" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="367" ID="{0bfdacae-8913-4e59-b0da-d1f359b47781}" OriginalSettingID="{19a0c0e2-48ca-4a9f-9493-bd547b86d8ad}" Name="MSS: (WarningLevel) Percentage threshold for the security event log at which the system will generate a warning" LockdownDate="2011-08-05T07:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-9501-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>The entry appears as MSS: (WarningLevel) Percentage threshold for the security event log at which the system will generate a warning in the SCE.</ShortDescription>
<FullDescription>The registry value entry WarningLevel was added to the template file in the HKEY_LOCAL_MACHINE\ SYSTEM\CurrentControlSet\Services\Eventlog\Security\ registry key. The entry appears as MSS: (WarningLevel) Percentage threshold for the security event log at which the system will generate a warning in the SCE.
This setting can generate a security audit in the Security event log when the log reaches a user-defined threshold.
Note If log settings are configured to Overwrite events as needed or Overwrite events older than x days, this event will not be generated.</FullDescription>
<UIPath>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</UIPath>
<DefaultValue>Not Defined</DefaultValue>
<Vulnerability>If the Security log reaches 90 percent of its capacity and the computer has not been configured to overwrite events as needed, more recent events will not be written to the log. If the log reaches its capacity and the computer has been configured to shut down when it can no longer record events to the Security log, the computer will shut down and will no longer be available to provide network services.</Vulnerability>
<Countermeasure>Configure the MSS: (WarningLevel) Percentage threshold for the security event log at which the system will generate a warning entry to a value of 90.
The possible values for this registry entry are:
• 0 to 100. The default configuration is 0 (no warning event is generated).
In the SCE UI, the following options are available:
• 50%
• 60%
• 70%
• 80%
• 90%
• Not Defined
</Countermeasure>
<PotentialImpact>This setting will generate an audit event when the Security log reaches the 90 percent-full threshold unless the log is configured to overwrite events as needed.</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="9999">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>%</Unit>
<ValueMappingTable>
<Mapping FriendlyName="Not Defined">
<BehaviorDescription />
<DCMValue ValueA="Not Defined" />
<SCAPValue ValueA="Not Defined" />
<GPOValue ValueA="Not Defined" />
</Mapping>
<Mapping FriendlyName="Not Configured">
<BehaviorDescription />
<DCMValue ValueA="Not Configured" />
<SCAPValue ValueA="Not Configured" />
<GPOValue ValueA="Not Configured" />
</Mapping>
<Mapping FriendlyName="Not Applicable">
<BehaviorDescription />
<DCMValue ValueA="Not Applicable" />
<SCAPValue ValueA="Not Applicable" />
<GPOValue ValueA="Not Applicable" />
</Mapping>
<Mapping FriendlyName="Not Recommended">
<BehaviorDescription />
<DCMValue ValueA="Not Recommended" />
<SCAPValue ValueA="Not Recommended" />
<GPOValue ValueA="Not Recommended" />
</Mapping>
<Mapping FriendlyName="Recommended">
<BehaviorDescription />
<DCMValue ValueA="Recommended" />
<SCAPValue ValueA="Recommended" />
<GPOValue ValueA="Recommended" />
</Mapping>
</ValueMappingTable>
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine">
<RegistryDiscoveryInfo>
<mssasc-core:Hive>HKEY_LOCAL_MACHINE</mssasc-core:Hive>
<mssasc-core:DataType>REG_DWORD</mssasc-core:DataType>
<mssasc-core:KeyPath>SYSTEM\CurrentControlSet\Services\Eventlog\Security</mssasc-core:KeyPath>
<mssasc-core:ValueName>WarningLevel</mssasc-core:ValueName>
</RegistryDiscoveryInfo>
</SettingDiscoveryInfo>
<DataType>Int64</DataType>
</DiscoveryInfo>
<ExportInfo GPOGenerateFormat="INF">
<Inf SectionName="Registry Values" Name="MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Security\WarningLevel" DataType="REG_DWORD" />
<OVAL>
<Reference source="" ref_id="oval:gov.nist.1:def:127" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Setting Index="368" ID="{311a474a-a1c0-4337-8f52-7f36e048d41b}" OriginalSettingID="{e9877eb1-8034-4347-86c1-d8e45f76e315}" Name="Maximum Log Size (KB)" LockdownDate="2011-05-02T01:36:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true">
<mssasc-core:Version Major="1" Minor="0" />
<Publisher ID="{f36fa61d-22fa-4a50-a532-ca4e83b23c00}">
<DisplayName>Microsoft</DisplayName>
</Publisher>
<PMOwner>Microsoft</PMOwner>
<DevOwner>Microsoft</DevOwner>
<TestOwner>Microsoft</TestOwner>
<ReviewedBy>Microsoft</ReviewedBy>
<ReviewStatus>Complete</ReviewStatus>
<Content>
<ProductInfo>
<ProductRef product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<CCEID-50 ID="CCE-10156-8">
<Description>
</Description>
</CCEID-50>
<ShortDescription>This policy requires Windows Vista or later versions of Windows, it specifies the maximum size of the log file in kilobytes.</ShortDescription>
<FullDescription>This policy requires Windows Vista or later versions of Windows. This policy setting specifies the maximum size of the log file in kilobytes. If you enable this policy setting, you can configure the maximum log file size to be between 1 megabyte (1024 kilobytes) and 2 terabytes (2147483647 kilobytes) in kilobyte increments. If you disable or do not configure this policy setting, the maximum size of the log file maximum size will be set to the local configuration value. This value can be changed by the local administrator using the log properties dialog and it defaults to 20 megabytes. For backwards compatibility the same setting can also be configured at Computer Configuration\Windows Settings\Security Settings\Event Log, if set at both locations this one will take precedence.</FullDescription>
<UIPath>Computer Configuration\Administrative Templates\Windows Components\Event Log Service\System</UIPath>
<DefaultValue>20480 KB</DefaultValue>
<Vulnerability>If events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users</Vulnerability>
<Countermeasure>You should enable sensible log size policies for all computers in your organization so that legitimate users can be held accountable for their actions, unauthorized activity can be detected and tracked, and computer problems can be detected and diagnosed.</Countermeasure>
<PotentialImpact>When event logs fill to capacity, they will stop recording information unless the retention method for each is set so that the computer will overwrite the oldest entries with the most recent ones. To mitigate the risk of loss of recent data, you can configure the retention method so that older events are overwritten as needed.
The consequence of this configuration is that older events will be removed from the logs. Attackers can take advantage of such a configuration, because they can generate a large number of extraneous events to overwrite any evidence of their attack. These risks can be somewhat reduced if you automate the archival and backup of event log data.
Ideally, all specifically monitored events should be sent to a server that uses Microsoft Operations Manager (MOM) or some other automated monitoring tool. Such a configuration is particularly important because an attacker who successfully compromises a server could clear the Security log. If all events are sent to a monitoring server, then you will be able to gather forensic information about the attacker's activities.
</PotentialImpact>
<ManualTestProcedure>
</ManualTestProcedure>
<ValueRange Low="0" High="0">
<Exclude>
<Value>
</Value>
</Exclude>
<Include>
<Value>
</Value>
</Include>
</ValueRange>
</ProductInfo>
<ProductStartedFrom product_ref="{ca347361-ac97-4dfa-a666-eeca698eff9f}" />
<Unit>
</Unit>
<ValueMappingTable />
</Content>
<DiscoveryInfo>
<SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine" />
<DataType>String</DataType>
</DiscoveryInfo>
<policy name="Channel_LogMaxSize_4" class="Machine" displayName="$(string.aca781003ed249418a7d8897e6b50b72)" explainText="$(string.4c933a0626bd440c994dac245c3559fc)" presentation="$(presentation.Channel_LogMaxSize_4)" key="Software\Policies\Microsoft\Windows\EventLog\System">
<admx:supportedOn ref="Unsupported_in_SCM_v2" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" />
<admx:elements xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">
<admx:decimal id="Channel_LogMaxSize" key="Software\Policies\Microsoft\Windows\EventLog\System" valueName="MaxSize" minValue="1024" maxValue="2147483647" />
</admx:elements>
</policy>
<ADMLDefinition>
<presentation id="Channel_LogMaxSize_4">
<admx:decimalTextBox refId="Channel_LogMaxSize" defaultValue="1024" xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions">Maximum Log Size (KB)</admx:decimalTextBox>
</presentation>
<string id="aca781003ed249418a7d8897e6b50b72">Maximum Log Size (KB)</string>
<string id="4c933a0626bd440c994dac245c3559fc">This policy requires Windows Vista or later versions of Windows. This policy setting specifies the maximum size of the log file in kilobytes. If you enable this policy setting, you can configure the maximum log file size to be between 1 megabyte (1024 kilobytes) and 2 terabytes (2147483647 kilobytes) in kilobyte increments. If you disable or do not configure this policy setting, the maximum size of the log file maximum size will be set to the local configuration value. This value can be changed by the local administrator using the log properties dialog and it defaults to 20 megabytes. For backwards compatibility the same setting can also be configured at Computer Configuration\Windows Settings\Security Settings\Event Log, if set at both locations this one will take precedence.</string>
</ADMLDefinition>
<supportedOn>At least Windows Vista</supportedOn>
<ExportInfo GPOGenerateFormat="POL">
<Inf />
<OVAL>
<Reference source="" ref_id="" ref_url="" />
</OVAL>
</ExportInfo>
<Comment>
</Comment>
</Setting>
<Comment>
</Comment>
</SettingGroup>
<Check>
<SettingRef setting_ref="{4d0beb7d-f233-4024-9ee4-4580d68e3ebe}" Severity="Critical" />
<ExistentialRule Name="Network Security: Restrict NTLM: Add remote server exceptions for NTLM authentication" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network Security: Restrict NTLM: Add remote server exceptions for NTLM authentication</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network Security: Restrict NTLM: Add remote server exceptions for NTLM authentication" Operator="Equals" Severity="Critical" id="{35336969-0afb-4d32-947b-fef5d3cc4ee5}">
<Description>This policy setting allows you to create an exception list of remote servers to which clients are allowed to use NTLM authentication if the "Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers" policy setting is configured.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{2cb1f8c6-e95d-4765-baab-37e1f4f9c4a9}" Severity="Critical" />
<ExistentialRule Name="Network security: Do not store LAN Manager hash value on next password change" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Network security: Do not store LAN Manager hash value on next password change</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network security: Do not store LAN Manager hash value on next password change" Operator="Equals" Severity="Critical" id="{c1a359d7-a72b-41ae-95a1-91a2bd525d54}">
<Description>The LM hash is relatively weak and prone to attack compared to the cryptographically stronger Microsoft Windows NT® hash.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{3b89eaba-a593-4ab4-9da6-e62124a4748a}" Severity="Important" />
<ExistentialRule Name="Network Security: Allow PKU2U authentication requests to this computer to use online identities" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network Security: Allow PKU2U authentication requests to this computer to use online identities</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network Security: Allow PKU2U authentication requests to this computer to use online identities" Operator="Equals" Severity="Warning" id="{228b7477-4686-4df1-979c-e828dfabb238}">
<Description>This policy will be turned off by default on domain joined machines. This would disallow the online identities to be able to authenticate to the domain joined machine in Windows 7.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{e7ebae2a-912a-4fb1-a92b-e2b9f346baf8}" Severity="Critical" />
<ExistentialRule Name="Network security: LAN Manager authentication level" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Network security: LAN Manager authentication level</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network security: LAN Manager authentication level" Operator="Equals" Severity="Critical" id="{a8169533-f80b-4791-bd76-2d21c8f33bc4}">
<Description>Configure to the strongest possible authentication level. Windows Server 2003 with Windows Vista or Windows XP Professional–based workstations, configure policy to Send NTLMv2 response only. Refuse LM and NTLM option for the highest security.</Description>
<Value ValueA="5" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{97ec51b5-9da5-4043-940f-f8d8282e9af2}" Severity="Critical" />
<ExistentialRule Name="Microsoft network client: Send unencrypted password to third-party SMB servers" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Microsoft network client: Send unencrypted password to third-party SMB servers</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Microsoft network client: Send unencrypted password to third-party SMB servers" Operator="Equals" Severity="Critical" id="{dd9b5acd-8bdd-4c77-a72c-7d091fdfe1f9}">
<Description>Microsoft recommends that you disable this policy setting unless there is a strong business case to enable it. If this policy setting is enabled, unencrypted passwords will be allowed across the network.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{00cb2759-acdf-40c1-8f0a-0983f8071c34}" Severity="Critical" />
<ExistentialRule Name="Network Security: Restrict NTLM: NTLM authentication in this domain" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network Security: Restrict NTLM: NTLM authentication in this domain</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network Security: Restrict NTLM: NTLM authentication in this domain" Operator="Equals" Severity="Critical" id="{6455be8e-b138-4c52-a5df-8c1d3022eca2}">
<Description>This policy setting allows you to audit NTLM authentication in a domain from this domain controller.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{34e2a485-7cf2-4009-953c-aebc160866ce}" Severity="Critical" />
<ExistentialRule Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) clients" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network security: Minimum session security for NTLM SSP based (including secure RPC) clients</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) clients" Operator="Equals" Severity="Critical" id="{dc3bbd01-1992-45cc-bc6d-c9657c4994c6}">
<Description> The options for this policy setting are:
• Require NTLMv2 session security
• Require 128-bit encryption</Description>
<Value ValueA="537395200" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{1c12b886-5e73-4018-87fa-05c04d78c787}" Severity="Critical" />
<ExistentialRule Name="Network Security: Restrict NTLM: Add server exceptions in this domain" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network Security: Restrict NTLM: Add server exceptions in this domain</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network Security: Restrict NTLM: Add server exceptions in this domain" Operator="Equals" Severity="Critical" id="{012aaed9-2c85-4498-89cc-1fbcb78fcca1}">
<Description>This policy setting allows you to create an exception list of servers in this domain to which clients are allowed to use NTLM pass-through authentication if the "Network Security: Restrict NTLM: Deny NTLM authentication in this domain" is set.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{63b9260b-0551-4ccf-bd90-711d0faef7d5}" Severity="Critical" />
<ExistentialRule Name="Interactive logon: Require Domain Controller authentication to unlock workstation" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Interactive logon: Require Domain Controller authentication to unlock workstation</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Interactive logon: Require Domain Controller authentication to unlock workstation" Operator="Equals" Severity="Critical" id="{3911c359-3c6c-42db-a057-086df2f93052}">
<Description>Microsoft recommends that this policy setting be disabled for laptop users in both environments, because mobile users do not have network access to domain controllers.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{e2d8ec35-9c92-48eb-988c-58b7228ed1a6}" Severity="Important" />
<ExistentialRule Name="Network security: Allow Local System to use computer identity for NTLM" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network security: Allow Local System to use computer identity for NTLM</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network security: Allow Local System to use computer identity for NTLM" Operator="Equals" Severity="Warning" id="{18484e14-aba5-46fe-8719-040cbfbb416b}">
<Description>This policy setting allows Local System services that use Negotiate to use the computer identity when reverting to NTLM authentication.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{d1f88718-583e-4ea8-b22c-972be135b5c7}" Severity="Critical" />
<ExistentialRule Name="Interactive logon: Number of previous logons to cache (in case domain controller is not available)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Interactive logon: Number of previous logons to cache (in case domain controller is not available)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Interactive logon: Number of previous logons to cache (in case domain controller is not available)" Operator="Equals" Severity="Critical" id="{8c6175e8-536c-40c5-aa93-c3f927b74677}">
<Description>This policy setting determines the number of unique users for whom logon information is cached locally.</Description>
<Value ValueA="2" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{bbe3858c-766c-4c4f-a4e2-4923715ed0f1}" Severity="Critical" />
<ExistentialRule Name="Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers" Operator="Equals" Severity="Critical" id="{ea667b47-750b-4b2e-a4bd-34c81eaf942c}">
<Description>This policy setting allows you to deny or audit outgoing NTLM traffic from this Windows 7 or this Windows Server 2008 R2 computer to any Windows remote server.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{66a658b9-9b3c-4d08-a131-2aac9e53b5c5}" Severity="Critical" />
<ExistentialRule Name="Microsoft network server: Server SPN target name validation level " Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Microsoft network server: Server SPN target name validation level </Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Microsoft network server: Server SPN target name validation level " Operator="Equals" Severity="Critical" id="{caa80db8-fe74-4794-9e06-c45d880af667}">
<Description>Enable policy setting, client sessions with the SMB service will be forcibly disconnected when the client’s logon hours expire. Disable policy setting, established client sessions will be maintained after the client’s logon hours expire.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{597039d5-d445-40b3-9e6c-da503f3fabb2}" Severity="Important" />
<ExistentialRule Name="Network security: Allow LocalSystem NULL session fallback" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network security: Allow LocalSystem NULL session fallback</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network security: Allow LocalSystem NULL session fallback" Operator="Equals" Severity="Warning" id="{ee51772c-e9b0-4aee-aeb6-421efed5ca71}">
<Description>Allow NTLM to fall back to NULL session when used with LocalSystem.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{1dd11027-79c4-4100-b533-e995dd664a10}" Severity="Important" />
<ExistentialRule Name="Interactive logon: Require smart card" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Interactive logon: Require smart card</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Interactive logon: Require smart card" Operator="Equals" Severity="Warning" id="{0099a8cf-8b60-4920-8d92-102c941ffa76}">
<Description>Microsoft encourages organizations to migrate to smart cards or other strong authentication technologies. However, you should only enable the Interactive logon: Require smart card setting if smart cards are already deployed.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{245197db-2fbb-426e-86c0-53fb70f633de}" Severity="Critical" />
<ExistentialRule Name="Network access: Let Everyone permissions apply to anonymous users" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Network access: Let Everyone permissions apply to anonymous users</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Let Everyone permissions apply to anonymous users" Operator="Equals" Severity="Critical" id="{eec90afe-20d0-4d87-9e6f-5c1bc837ae0a}">
<Description>Enable setting, anonymous users allowed to enumerate the names of domain accounts and network shares. Unauthorized user could anonymously list account names and shared resources to guess passwords or perform social engineering attacks.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{f36a9b81-5174-4eee-940d-5cc98b66ca18}" Severity="Critical" />
<ExistentialRule Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) servers" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network security: Minimum session security for NTLM SSP based (including secure RPC) servers</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) servers" Operator="Equals" Severity="Critical" id="{d8291bc1-08e3-4657-a090-dc131edcd7de}">
<Description>The options for the setting are the same:
• Require NTLMv2 session security
• Require 128-bit encryption</Description>
<Value ValueA="537395200" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{30afa923-5828-4ad2-85cd-817fd62e00d2}" Severity="Critical" />
<ExistentialRule Name="Network Security: Restrict NTLM: Incoming NTLM traffic" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network Security: Restrict NTLM: Incoming NTLM traffic</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network Security: Restrict NTLM: Incoming NTLM traffic" Operator="Equals" Severity="Critical" id="{55a758ef-201e-4f0a-9d25-acb18ce20b13}">
<Description>This policy setting allows you to deny or allow incoming NTLM traffic.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{0f0e8a78-3087-4c4a-8f5a-c21ce15219f9}" Severity="Critical" />
<ExistentialRule Name="Network Security: Restrict NTLM: NTLM authentication in this domain" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network Security: Restrict NTLM: NTLM authentication in this domain</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network Security: Restrict NTLM: NTLM authentication in this domain" Operator="Equals" Severity="Critical" id="{d6fe3b2f-a783-47c1-8a20-934ac36ddea2}">
<Description>This policy setting allows you to deny or allow NTLM authentication within a domain from this domain controller. This policy does not affect interactive logon to this domain controller.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{05a7cc0d-0a17-4406-9896-c4cc17d0caa0}" Severity="Important" />
<ExistentialRule Name="Interactive logon: Smart card removal behavior" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Interactive logon: Smart card removal behavior</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Interactive logon: Smart card removal behavior" Operator="Equals" Severity="Warning" id="{87380337-c8f2-4238-bffc-6fafea1f2304}">
<Description>When configured to Lock Workstation, this policy setting locks the workstation when the smart card is removed, which allows users to leave the area, take their smart cards with them, and automatically lock their workstations.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{129ea24b-baa4-4de0-a500-d3fb5dedc666}" Severity="Critical" />
<ExistentialRule Name="Network Security: Restrict NTLM: Audit Incoming NTLM Traffic" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network Security: Restrict NTLM: Audit Incoming NTLM Traffic</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network Security: Restrict NTLM: Audit Incoming NTLM Traffic" Operator="Equals" Severity="Critical" id="{725e22de-d566-4e13-9012-583e533d4590}">
<Description>This policy setting allows you to audit incoming NTLM traffic.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{082304a5-6006-41d3-9817-2eadc7e971bb}" Severity="Critical" />
<ExistentialRule Name="Restrictions for Unauthenticated RPC clients" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Restrictions for Unauthenticated RPC clients</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Restrictions for Unauthenticated RPC clients" Operator="Equals" Severity="Critical" id="RpcRestrictRemoteClients">
<Description> A client will be considered an authenticated client if it uses a named pipe to communicate with the server or if it uses RPC Security . • None
• Authenticated.
• Authenticated without exceptions. </Description>
<Value ValueA="Enabled" />
</SettingRule>
<OptionRule Name="RPC Runtime Unauthenticated Client Restriction to Apply" Operator="Equals" Severity="Warning" id="RpcRestrictRemoteClientsList">
<Description>A client will be considered an authenticated client if it uses a named pipe to communicate with the server or if it uses RPC Security . • None
• Authenticated.
• Authenticated without exceptions.</Description>
<Value ValueA="$(string.e6744bcc94c84ce7b9eee9a979b2d36c)" />
</OptionRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{0c1bebbb-ab69-4093-9e04-c237e1f19cf4}" Severity="Important" />
<ExistentialRule Name="RPC Endpoint Mapper Client Authentication" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>RPC Endpoint Mapper Client Authentication</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="RPC Endpoint Mapper Client Authentication" Operator="Equals" Severity="Warning" id="RpcEnableAuthEpResolution">
<Description>By default, RPC clients will not use authentication to communicate with the RPC Server Endpoint Mapper Service when they request the endpoint of a server. </Description>
<Value ValueA="Disabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{55ca8870-6e90-41c6-af69-597997f7d743}" Severity="Critical" />
<ExistentialRule Name="Accounts: Guest account status" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Accounts: Guest account status</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Accounts: Guest account status" Operator="Equals" Severity="Critical" id="{9030f328-a539-4930-be12-eb693106a2c0}">
<Description>The Guest account allows unauthenticated network users to gain access to the system.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{3f02b561-e59c-4b87-aff0-db9f98210ac8}" Severity="Critical" />
<ExistentialRule Name="Network access: Sharing and security model for local accounts" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network access: Sharing and security model for local accounts</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Sharing and security model for local accounts" Operator="Equals" Severity="Critical" id="{53b46e5b-f48e-499b-bbb7-d3c00701f9ec}">
<Description>The Classic option allows precise control over access to resources. The Guest only option allows you to treat all users equally. </Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{12b049a5-9194-4a59-a6bc-3469bcdee08d}" Severity="Critical" />
<ExistentialRule Name="System objects: Strengthen default permissions of internal system objects (e.g. Symbolic Links)" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>System objects: Strengthen default permissions of internal system objects (e.g. Symbolic Links)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="System objects: Strengthen default permissions of internal system objects (e.g. Symbolic Links)" Operator="Equals" Severity="Critical" id="{77b657d9-6810-4b77-86c4-cfce63f0ad3d}">
<Description>Helps secure objects located and shared among processes, it allows users who are not administrators to read shared objects but does not allow them to modify any that they did not create.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{c3a57a34-29ec-475e-8020-607d3a863972}" Severity="Critical" />
<ExistentialRule Name="Accounts: Rename administrator account" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Accounts: Rename administrator account</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Accounts: Rename administrator account" Operator="NotEquals" Severity="Critical" id="{6511f795-8996-4d6a-8dcb-4084ec9398e1}">
<Description>Microsoft recommends that you choose another name for this account, and that you avoid names that denote administrative or elevated access accounts.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{78fdc1b1-209e-4cad-9295-b49b35e3b334}" Severity="Important" />
<ExistentialRule Name="Accounts: Rename guest account" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Accounts: Rename guest account</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Accounts: Rename guest account" Operator="NotEquals" Severity="Warning" id="{a46ae0aa-7ed8-46b5-be14-7ca3c10b0c53}">
<Description>Microsoft also recommends that you rename this account to something that does not indicate its purpose. Even if you disable this account (which is recommended), ensure that you rename it for added security.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{ac369d63-4dfe-4afe-bd3f-6c04c9871c39}" Severity="Critical" />
<ExistentialRule Name="Accounts: Administrator account status" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Accounts: Administrator account status</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Accounts: Administrator account status" Operator="Equals" Severity="Critical" id="{fecb7b4d-49ee-49d7-b304-849f3ef0c618}">
<Description>When a computer is booted into safe mode, the Administrator account is always enabled, regardless of how this setting is configured.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{a7cdd16c-4bfb-44a2-9c5f-7521bf1f640f}" Severity="Optional" />
<ExistentialRule Name="MSS: (NtfsDisable8dot3NameCreation) Enable the computer to stop generating 8.3 style filenames (recommended)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (NtfsDisable8dot3NameCreation) Enable the computer to stop generating 8.3 style filenames (recommended)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (NtfsDisable8dot3NameCreation) Enable the computer to stop generating 8.3 style filenames (recommended)" Operator="Equals" Severity="Informational" id="{132e1b76-6a75-4d53-9c1f-ecead7636975}">
<Description>Windows Server 2003 supports 8.3 file name formats for backward compatibility with16-bit applications. The 8.3 file name convention is a naming format that allows file names up to eight characters long.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{917896fc-f341-4c69-b52e-af2860974dce}" Severity="Critical" />
<ExistentialRule Name="Interactive logon: Message text for users attempting to log on" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Interactive logon: Message text for users attempting to log on</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Interactive logon: Message text for users attempting to log on" Operator="Equals" Severity="Critical" id="{f30ed988-24b1-46cf-a286-f0784cd3363f}">
<Description>This text is often used for legal reasons—for example, to warn users about the ramifications of misusing company information or to warn them that their actions may be audited. </Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{c9b6a248-2674-42ef-984e-ee28f5ae480f}" Severity="Critical" />
<ExistentialRule Name="Interactive logon: Message title for users attempting to log on" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Interactive logon: Message title for users attempting to log on</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Interactive logon: Message title for users attempting to log on" Operator="Equals" Severity="Critical" id="{76c23266-2c4a-4b55-b088-b142a6d517c7}">
<Description>Organizations that do not use this policy setting are more legally vulnerable to trespassers who attack the system.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{ec837347-60b2-4515-8290-fcbbdd02eb50}" Severity="Critical" />
<ExistentialRule Name="Microsoft network server: Disconnect clients when logon hours expire" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Microsoft network server: Disconnect clients when logon hours expire</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Microsoft network server: Disconnect clients when logon hours expire" Operator="Equals" Severity="Critical" id="{31573373-bfd4-4d9b-a96c-b32d94b832a1}">
<Description>Enable policy setting, client sessions with the SMB service will be forcibly disconnected when the client’s logon hours expire. Disable policy setting, established client sessions will be maintained after the client’s logon hours expire.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{db3f7b65-f813-48b3-abc8-f95e104eb7d4}" Severity="Critical" />
<ExistentialRule Name="Interactive logon: Do not display last user name" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Interactive logon: Do not display last user name</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Interactive logon: Do not display last user name" Operator="Equals" Severity="Critical" id="{7a5f0933-ceca-4541-be4c-1a80b5521978}">
<Description>Enable this policy setting to prevent intruders from collecting account names visually from the screens of desktop or laptop computers in your organization.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{4adfec68-fb9d-4616-9e0c-2a7aa1e553d5}" Severity="Critical" />
<ExistentialRule Name="Interactive logon: Message text for users attempting to log on" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Interactive logon: Message text for users attempting to log on</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Interactive logon: Message text for users attempting to log on" Operator="Equals" Severity="Critical" id="{f30ed988-24b1-46cf-a286-f0784cd3363f}">
<Description>This text is often used for legal reasons—for example, to warn users about the ramifications of misusing company information or to warn them that their actions may be audited. </Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{36e3fe86-8b1c-41bc-81bf-14ee389d1dd2}" Severity="Important" />
<ExistentialRule Name="MSS: (ScreenSaverGracePeriod) The time in seconds before the screen saver grace period expires (0 recommended)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (ScreenSaverGracePeriod) The time in seconds before the screen saver grace period expires (0 recommended)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (ScreenSaverGracePeriod) The time in seconds before the screen saver grace period expires (0 recommended)" Operator="Equals" Severity="Warning" id="{d56b4361-5d43-4e78-9fb3-1ce643cf782b}">
<Description>Windows includes a grace period between when the screen saver is launched and when the console is actually locked automatically when screen saver locking is enabled. </Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{ea043c7a-f25a-4827-9e69-7ca3d03e626b}" Severity="Critical" />
<ExistentialRule Name="Microsoft network server: Amount of idle time required before suspending session" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Microsoft network server: Amount of idle time required before suspending session</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Microsoft network server: Amount of idle time required before suspending session" Operator="LessEquals" Severity="Critical" id="{2a0255fb-7da4-4b91-a78b-ab17e648aa2e}">
<Description>Administrators can use this policy setting to control when a computer suspends an inactive SMB session. If client activity resumes, the session is automatically reestablished.</Description>
<Value ValueA="15" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{ca5df750-54ac-4893-8938-32137e469af2}" Severity="Important" />
<ExistentialRule Name="Network security: Force logoff when logon hours expire" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Network security: Force logoff when logon hours expire</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network security: Force logoff when logon hours expire" Operator="Equals" Severity="Warning" id="{8364d3c4-8362-41ee-8e1f-e97903e03da4}">
<Description> If you enable this policy setting, client sessions with the SMB server will be disconnected when the client’s logon hours expire. If you disable this policy setting, established client sessions will be maintained after the client’s logon hours expire</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{64143a46-78e1-4738-803b-726c0b71351e}" Severity="Important" />
<ExistentialRule Name="Interactive logon: Smart card removal behavior" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Interactive logon: Smart card removal behavior</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Interactive logon: Smart card removal behavior" Operator="Equals" Severity="Warning" id="{87380337-c8f2-4238-bffc-6fafea1f2304}">
<Description>When configured to Lock Workstation, this policy setting locks the workstation when the smart card is removed, which allows users to leave the area, take their smart cards with them, and automatically lock their workstations.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{8d0e2f6a-cc6c-42ec-98d9-2a62156d307d}" Severity="Critical" />
<ExistentialRule Name="Interactive logon: Display user information when the session is locked" Operator="GreaterThan" Severity="None" ValueA="0">
<Description>Interactive logon: Display user information when the session is locked</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Interactive logon: Display user information when the session is locked" Operator="Equals" Severity="Critical" id="{74ac92bc-47d1-4635-a7b4-ffbad01599db}">
<Description />
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{d5f8a901-1ba3-4f5f-b8bd-da1cc11c82f3}" Severity="Critical" />
<ExistentialRule Name="Interactive logon: Message title for users attempting to log on" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Interactive logon: Message title for users attempting to log on</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Interactive logon: Message title for users attempting to log on" Operator="Equals" Severity="Critical" id="{76c23266-2c4a-4b55-b088-b142a6d517c7}">
<Description>Organizations that do not use this policy setting are more legally vulnerable to trespassers who attack the system.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{6b510307-672d-4eed-ae0e-6c62ca4a1a12}" Severity="Important" />
<ExistentialRule Name="Restore files and directories" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Restore files and directories</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Restore files and directories" Operator="Equals" Severity="Warning" id="{d240e37d-156e-49d6-9773-c799bae4860c}">
<Description> This user right also determines which users can set valid security principals as object owners; it is similar to the Back up files and directories user right.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{f779bf0f-37cf-4a97-8a8a-1f00c23a2979}" Severity="Important" />
<ExistentialRule Name="Create symbolic links" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Create symbolic links</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Create symbolic links" Operator="Equals" Severity="Warning" id="{8cbb4073-da8a-42c0-8f7d-e67eb0aedfec}">
<Description>In Vista, existing NTFS file system objects, can be accessed by referring to a new kind of file system object called a symbolic link. Symbolic links can potentially expose security vulnerabilities in applications that are not designed to use them.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{c223a5a2-b2e5-4d88-8d5e-0e58ed7f822f}" Severity="Important" />
<ExistentialRule Name="Back up files and directories" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Back up files and directories</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Back up files and directories" Operator="Equals" Severity="Warning" id="{a7c2ce3c-5718-4cc1-9934-e2a0b3a2e276}">
<Description>This user right is enabled only when an application (such as NTBACKUP) attempts to access a file or directory through the NTFS file system backup application programming interface (API). Otherwise, the assigned file and directory permissions apply.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{1caaf822-63ea-4157-9b86-ffa544885307}" Severity="Important" />
<ExistentialRule Name="Take ownership of files or other objects" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Take ownership of files or other objects</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Take ownership of files or other objects" Operator="Equals" Severity="Warning" id="{ef022bf8-de86-4f93-aa35-e4392e45fa1e}">
<Description>This setting is configured to the default value of the Administrators group.</Description>
<Value ValueA="Administrators" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{e6387c64-6cce-4766-aed3-a8e973bebef1}" Severity="Critical" />
<ExistentialRule Name="Bypass traverse checking" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Bypass traverse checking</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Bypass traverse checking" Operator="Equals" Severity="Critical" id="{f257bd70-d858-4364-b7b1-c00b9279bd59}">
<Description>This user right does not allow users to list the contents of a folder, but only allows them to traverse directories.</Description>
<Value ValueA="Users, NETWORK SERVICE, LOCAL SERVICE, Administrators" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{5834a109-0fe4-4bb1-b48a-57697b760864}" Severity="Important" />
<ExistentialRule Name="System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" Operator="Equals" Severity="Warning" id="{bf69e235-d7f3-4e54-9dc3-4bab7ae09c3c}">
<Description>Increases security, most public Web sites that are secured with TLS or SSL do not support these algorithms. Enabled client computers will be unable to connect to Terminal Services on servers not configured likewise.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{1a20f423-f1fa-40e4-9f2a-980c0c928e96}" Severity="Critical" />
<ExistentialRule Name="Microsoft network client: Send unencrypted password to third-party SMB servers" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Microsoft network client: Send unencrypted password to third-party SMB servers</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Microsoft network client: Send unencrypted password to third-party SMB servers" Operator="Equals" Severity="Critical" id="{dd9b5acd-8bdd-4c77-a72c-7d091fdfe1f9}">
<Description>Microsoft recommends that you disable this policy setting unless there is a strong business case to enable it. If this policy setting is enabled, unencrypted passwords will be allowed across the network.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{2c8cc955-6210-469f-a3e7-eac4923307f4}" Severity="Critical" />
<ExistentialRule Name="Microsoft network client: Digitally sign communications (always)" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Microsoft network client: Digitally sign communications (always)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Microsoft network client: Digitally sign communications (always)" Operator="Equals" Severity="Critical" id="{d73dff05-2cba-4e26-9d06-019ff34f2d69}">
<Description>If you enable this policy setting, the Microsoft network client computer cannot communicate with a Microsoft network server unless that server agrees to sign SMB packets. Does not work in mixed environments</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{58638d9b-8c66-4f4c-81be-4ba18ce17b27}" Severity="Critical" />
<ExistentialRule Name="Domain member: Digitally encrypt secure channel data (when possible)" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Domain member: Digitally encrypt secure channel data (when possible)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Domain member: Digitally encrypt secure channel data (when possible)" Operator="Equals" Severity="Critical" id="{348951c5-443a-4eba-9774-2b47a86bee35}">
<Description>Enable this policy setting, the domain member will request encryption of all secure channel traffic. Disable this policy setting, the domain member will be prevented from negotiating secure channel encryption.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{5845ddb2-f798-49f0-a020-202700be3972}" Severity="Critical" />
<ExistentialRule Name="Domain member: Digitally encrypt or sign secure channel data (always)" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Domain member: Digitally encrypt or sign secure channel data (always)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Domain member: Digitally encrypt or sign secure channel data (always)" Operator="Equals" Severity="Critical" id="{ecbe94ef-b32b-4ddb-81be-e096e42731cc}">
<Description>Set to always encrypt or sign secure channel data, it cannot establish a secure channel with a domain controller that is not capable of signing or encrypting all secure channel traffic.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{28a3d4ca-a5c6-48d5-94d9-624b8f1db163}" Severity="Critical" />
<ExistentialRule Name="Domain member: Require strong (Windows 2000 or later) session key" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Domain member: Require strong (Windows 2000 or later) session key</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Domain member: Require strong (Windows 2000 or later) session key" Operator="Equals" Severity="Critical" id="{17cc7240-2e94-4340-a93f-c50378e546fb}">
<Description>To enable this policy setting, all domain controllers in the domain must be able to encrypt secure channel data with a strong key, which means all domain controllers must be running Microsoft Windows 2000 or later. </Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{22ade905-3209-4235-8006-517167adb188}" Severity="Critical" />
<ExistentialRule Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) clients" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network security: Minimum session security for NTLM SSP based (including secure RPC) clients</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) clients" Operator="Equals" Severity="Critical" id="{dc3bbd01-1992-45cc-bc6d-c9657c4994c6}">
<Description> The options for this policy setting are:
• Require NTLMv2 session security
• Require 128-bit encryption</Description>
<Value ValueA="537395200" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{3fbec02a-7a63-4b24-b0a9-442cdf75ef19}" Severity="Critical" />
<ExistentialRule Name="Microsoft network server: Digitally sign communications (always)" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Microsoft network server: Digitally sign communications (always)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Microsoft network server: Digitally sign communications (always)" Operator="Equals" Severity="Critical" id="{98a24d38-9fe8-4280-864d-13c307e13236}">
<Description>Enable this policy setting in a mixed environment to prevent downstream clients from using the workstation as a network server.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{fb9da3eb-fe5b-4c60-b97f-94718ee51363}" Severity="Critical" />
<ExistentialRule Name="Microsoft network client: Digitally sign communications (if server agrees)" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Microsoft network client: Digitally sign communications (if server agrees)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Microsoft network client: Digitally sign communications (if server agrees)" Operator="Equals" Severity="Critical" id="{aab6b4a7-1a3e-4b7f-9896-fa8e3b4d132a}">
<Description>Digital signing in Windows–based networks helps to prevent sessions from being hijacked. Enable this policy setting, the Microsoft network client will use signing only if the server with which it communicates accepts digitally signed communication.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{c2472de5-9781-4495-a0ec-914a64814c78}" Severity="Critical" />
<ExistentialRule Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) servers" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network security: Minimum session security for NTLM SSP based (including secure RPC) servers</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) servers" Operator="Equals" Severity="Critical" id="{d8291bc1-08e3-4657-a090-dc131edcd7de}">
<Description>The options for the setting are the same:
• Require NTLMv2 session security
• Require 128-bit encryption</Description>
<Value ValueA="537395200" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{3688dfbf-8a81-43b1-b5f6-1d450a2ad0a5}" Severity="Important" />
<ExistentialRule Name="System cryptography: Force strong key protection for user keys stored on the computer" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>System cryptography: Force strong key protection for user keys stored on the computer</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="System cryptography: Force strong key protection for user keys stored on the computer" Operator="Equals" Severity="Warning" id="{07a6afa7-55de-4989-a12d-6b3765ff80b5}">
<Description>Setting so that users must provide a password—distinct from their domain password—every time that they use a key, makes it more difficult for an attacker to access locally stored keys.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{98c92a2d-77fb-42b5-836a-bcb6530961d2}" Severity="Critical" />
<ExistentialRule Name="Set client connection encryption level" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Set client connection encryption level</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Set client connection encryption level" Operator="Equals" Severity="Critical" id="TS_ENCRYPTION_POLICY">
<Description>
The encryption level is set to Enabled:High Level to enforce 128-bit encryption for the two environments that are discussed in this guide.
</Description>
<Value ValueA="Enabled" />
</SettingRule>
<OptionRule Name="Encryption Level" Operator="Equals" Severity="Warning" id="TS_ENCRYPTION_LEVEL">
<Description>The encryption level is set to Enabled:High Level to enforce 128-bit encryption for the two environments that are discussed in this guide.</Description>
<Value ValueA="$(string.c7c2c16080314e20b138a74cb1e8b1dd)" />
</OptionRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{f3ac882d-c27b-40a1-abb0-cf6c0eac88da}" Severity="Critical" />
<ExistentialRule Name="Microsoft network server: Digitally sign communications (if client agrees)" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Microsoft network server: Digitally sign communications (if client agrees)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Microsoft network server: Digitally sign communications (if client agrees)" Operator="Equals" Severity="Critical" id="{548a38c2-7762-4e70-88cf-7882cf1c036a}">
<Description>If no signing request comes from the client, a connection will be allowed without a signature if the Microsoft network server: Digitally sign communications (always) setting is not enabled.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{6af41287-d664-4623-8f5d-fef63ef6e8f6}" Severity="Critical" />
<ExistentialRule Name="Domain member: Digitally sign secure channel data (when possible)" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Domain member: Digitally sign secure channel data (when possible)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Domain member: Digitally sign secure channel data (when possible)" Operator="Equals" Severity="Critical" id="{327982cb-5268-40de-9b8d-ebdf18456dde}">
<Description>Digital signatures protect the traffic from being modified by anyone who captures the data as it traverses the network.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{80dc8338-8465-4e26-8f45-46bf141932aa}" Severity="Important" />
<ExistentialRule Name="Network Security: Configure encryption types allowed for Kerberos" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network Security: Configure encryption types allowed for Kerberos</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network Security: Configure encryption types allowed for Kerberos" Operator="Equals" Severity="Warning" id="{58ca8c65-eff9-4dc4-a55d-f111f296a78e}">
<Description>This policy setting allows you to set the encryption types that Kerberos is allowed to use.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{b4b2894f-5c26-4f35-ba9e-e08ad22fc40f}" Severity="Critical" />
<ExistentialRule Name="User Account Control: Behavior of the elevation prompt for standard users" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>User Account Control: Behavior of the elevation prompt for standard users</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="User Account Control: Behavior of the elevation prompt for standard users" Operator="Equals" Severity="Critical" id="{732e0fda-d721-472b-83de-b40246cb7dbd}">
<Description>• Automatically deny elevation requests.
• Prompt for credentials. </Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{54415948-2d82-4269-ab18-d0919318813e}" Severity="Critical" />
<ExistentialRule Name="Require trusted path for credential entry" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Require trusted path for credential entry</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Require trusted path for credential entry" Operator="Equals" Severity="Critical" id="EnableSecureCredentialPrompting">
<Description>This policy setting determines whether users must first press CTRL+ALT+DEL to establish a trusted path before typing account and password information to log on to computers in the environment.</Description>
<Value ValueA="Not Configured" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{60784c55-d964-4ede-bbaf-40334e512ee6}" Severity="Critical" />
<ExistentialRule Name="User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop" Operator="Equals" Severity="Critical" id="{63ba4df8-1cec-49c4-8791-1550bfb387d6}">
<Description>By default this setting is disabled.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{21cfd351-1789-4d1a-bd58-ec3ebdad8185}" Severity="Critical" />
<ExistentialRule Name="Interactive logon: Do not require CTRL+ALT+DEL" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Interactive logon: Do not require CTRL+ALT+DEL</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Interactive logon: Do not require CTRL+ALT+DEL" Operator="Equals" Severity="Critical" id="{e3c42d14-4ae9-4f3e-acc8-e77e97145b0a}">
<Description>When this policy setting is enabled, users are not required to use this key combination to log on to the network. However, this configuration poses a security risk because it provides an opportunity for users to log on with weaker logon credentials.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{be00e277-89c8-46d0-9720-32bbbab2a034}" Severity="Critical" />
<ExistentialRule Name="User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode" Operator="Equals" Severity="Critical" id="{bac7cabd-b08c-4b9f-881f-b8865eaef45f}">
<Description>• No prompt.
• Prompt for consent.
• Prompt for credentials.</Description>
<Value ValueA="3" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{c3f39314-7abe-4116-9aaf-38220b9eb076}" Severity="Critical" />
<ExistentialRule Name="User Account Control: Detect application installations and prompt for elevation" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>User Account Control: Detect application installations and prompt for elevation</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="User Account Control: Detect application installations and prompt for elevation" Operator="Equals" Severity="Critical" id="{b0a9b853-c18a-48f1-9fb6-3b5e9f16661b}">
<Description>• Enabled. Using this value causes Windows Vista, on detection of an installer, to prompt the user for consent or credentials.
• Disabled. Using this value causes application installations to fail silently or in a non-deterministic manner.
</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{f89e96b8-9911-4b7e-88e8-62d8bdbd6bd6}" Severity="Critical" />
<ExistentialRule Name="Do not process the legacy run list" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Do not process the legacy run list</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Do not process the legacy run list" Operator="Equals" Severity="Critical" id="DisableExplorerRunLegacy_2">
<Description>You can enable the Do not process the legacy run list setting to help prevent a malicious user from running a program each time Windows Vista starts, which could compromise data on the computer or cause other harm. </Description>
<Value ValueA="Not Configured" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{1b12d408-25ff-463f-a272-e3e8c8a09ad5}" Severity="Critical" />
<ExistentialRule Name="User Account Control: Only elevate UIAccess applications that are installed in secure locations" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>User Account Control: Only elevate UIAccess applications that are installed in secure locations</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="User Account Control: Only elevate UIAccess applications that are installed in secure locations" Operator="Equals" Severity="Critical" id="{2790f666-9530-49c2-bb13-27728db1ee16}">
<Description>The configuration for the User Account Control: Only elevate UIAccess applications that are installed in secure locations setting is Enabled for both of the environments that are discussed in this guide.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{28394e64-95ae-42dc-9eff-b2396aa16d31}" Severity="Critical" />
<ExistentialRule Name="User Account Control: Only elevate executables that are signed and validated" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>User Account Control: Only elevate executables that are signed and validated</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="User Account Control: Only elevate executables that are signed and validated" Operator="Equals" Severity="Critical" id="{88f18ac8-398f-452d-b9e6-f3741f143be3}">
<Description>• Enabled. Using this value allows only signed executable files to run. This setting blocks unsigned applications from running.
• Disabled. Using this value allows both signed and unsigned executables to run.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{fa10a5ad-8541-40cc-aa30-2e25eb590a4c}" Severity="Critical" />
<ExistentialRule Name="System objects: Strengthen default permissions of internal system objects (e.g. Symbolic Links)" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>System objects: Strengthen default permissions of internal system objects (e.g. Symbolic Links)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="System objects: Strengthen default permissions of internal system objects (e.g. Symbolic Links)" Operator="Equals" Severity="Critical" id="{77b657d9-6810-4b77-86c4-cfce63f0ad3d}">
<Description>Helps secure objects located and shared among processes, it allows users who are not administrators to read shared objects but does not allow them to modify any that they did not create.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{7b69a75a-4f57-4700-9e37-2e46eedc01c1}" Severity="Critical" />
<ExistentialRule Name="User Account Control: Switch to the secure desktop when prompting for elevation" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>User Account Control: Switch to the secure desktop when prompting for elevation</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="User Account Control: Switch to the secure desktop when prompting for elevation" Operator="Equals" Severity="Critical" id="{ccef1ba2-21d4-440f-b160-5e9ca70c4573}">
<Description>• Enabled. Using this value displays the UAC elevation prompt on the secure desktop.
• Disabled. Using this value causes the UAC elevation prompt to display on the user desktop.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{75e59622-79d7-41bd-89b1-58617df2bb71}" Severity="Critical" />
<ExistentialRule Name="User Account Control: Run all administrators in Admin Approval Mode" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>User Account Control: Run all administrators in Admin Approval Mode</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="User Account Control: Run all administrators in Admin Approval Mode" Operator="Equals" Severity="Critical" id="{c38a9ac0-7304-404c-8b22-abf01f521341}">
<Description>• Enabled. Using this value prompts both administrators and standard users when either type of user attempts to perform administrative operations. The prompt style depends on policy.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{d8cb6429-acf3-497a-9243-bf0a1faa6655}" Severity="Critical" />
<ExistentialRule Name="User Account Control: Admin Approval Mode for the Built-in Administrator account" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>User Account Control: Admin Approval Mode for the Built-in Administrator account</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="User Account Control: Admin Approval Mode for the Built-in Administrator account" Operator="Equals" Severity="Critical" id="{183704d8-0339-4c19-a5e8-941291ed2b5f}">
<Description>Disabled by default for new installations and for upgrades where the built-in Administrator is not the only local active administrator on the computer. Disabled built-in Administrator account by default for installations and upgrades on domain-joined computers. Enabled by default for upgrades where the built-in Administrator account is the only active local administrator on the computer.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{6694acde-abc6-48a9-9f71-f3c3e8165062}" Severity="Optional" />
<ExistentialRule Name="Always install with elevated privileges" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Always install with elevated privileges</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Always install with elevated privileges" Operator="Equals" Severity="Informational" id="AlwaysInstallElevated_2">
<Description />
<Value ValueA="Disabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{9d5286b3-4ac5-4114-8f64-1c03f0089d80}" Severity="Critical" />
<ExistentialRule Name="Turn off downloading of print drivers over HTTP" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Turn off downloading of print drivers over HTTP</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Turn off downloading of print drivers over HTTP" Operator="Equals" Severity="Critical" id="DisableWebPnPDownload_2">
<Description>The Turn off downloading of print drivers over HTTP setting is configured to Enabled to prevent print drivers from being downloaded over HTTP.</Description>
<Value ValueA="Enabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{46e26d52-9510-4c6a-8dbc-58cbfe54c857}" Severity="Critical" />
<ExistentialRule Name="Registry policy processing" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Registry policy processing</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Registry policy processing" Operator="Equals" Severity="Critical" id="CSE_Registry">
<Description> If this policy setting is enabled, the following options are available:
• Do not apply during periodic background processing.
• Process even if the Group Policy objects have not changed.</Description>
<Value ValueA="Enabled" />
</SettingRule>
<OptionRule Name="Do not apply during periodic background processing" Operator="Equals" Severity="Informational" id="CSE_NOBACKGROUND10">
<Description> If this policy setting is enabled, the following options are available:
• Do not apply during periodic background processing.
• Process even if the Group Policy objects have not changed.</Description>
<Value ValueA="False" />
</OptionRule>
<OptionRule Name="Process even if the Group Policy objects have not changed" Operator="Equals" Severity="Informational" id="CSE_NOCHANGES10">
<Description> If this policy setting is enabled, the following options are available:
• Do not apply during periodic background processing.
• Process even if the Group Policy objects have not changed.</Description>
<Value ValueA="True" />
</OptionRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{085e1a51-4e69-47a5-8a03-5f073bb6cfe8}" Severity="Critical" />
<ExistentialRule Name="Turn off Data Execution Prevention for Explorer" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Turn off Data Execution Prevention for Explorer</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Turn off Data Execution Prevention for Explorer" Operator="Equals" Severity="Critical" id="NoDataExecutionPrevention">
<Description>Disabling data execution prevention can allow certain legacy plug-in applications to function without terminating Explorer.</Description>
<Value ValueA="Disabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{545a92f8-05f8-4d8b-bb3b-c54071d59621}" Severity="Critical" />
<ExistentialRule Name="Turn off Windows Update device driver searching" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Turn off Windows Update device driver searching</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Turn off Windows Update device driver searching" Operator="Equals" Severity="Critical" id="DriverSearchPlaces_DontSearchWindowsUpdate">
<Description>The types of attacks that can exploit a driver download will typically be mitigated by proper enterprise resource and configuration management. This will also help ensure compatibility and stability across the computers in your environment.</Description>
<Value ValueA="Enabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{d6003991-51df-4527-8cc9-bd0d5609e5f7}" Severity="Critical" />
<ExistentialRule Name="User Account Control: Virtualize file and registry write failures to per-user locations" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>User Account Control: Virtualize file and registry write failures to per-user locations</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="User Account Control: Virtualize file and registry write failures to per-user locations" Operator="Equals" Severity="Critical" id="{c2c4aae7-d0ef-48df-80ea-cb65535a2b7a}">
<Description>• Enabled. Environments that utilize software that is not UAC-compliant should configure this setting to Enabled.
• Disabled. Environments that utilize software that is UAC-compliant should configure this setting to Disabled.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{0ebb1667-2781-4a0d-833f-bf3872543a76}" Severity="Critical" />
<ExistentialRule Name="Do not process the run once list" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Do not process the run once list</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Do not process the run once list" Operator="Equals" Severity="Critical" id="DisableExplorerRunOnceLegacy_2">
<Description>If this policy is enabled, the "Always do this..." checkbox in Autoplay dialog will not be set by default when the dialog is shown. The default setting is to run Autoplay.</Description>
<Value ValueA="Not Configured" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{38b6ff0a-4f1e-4f44-8af8-cc0456695253}" Severity="Optional" />
<ExistentialRule Name="MSS: (AutoReboot) Allow Windows to automatically restart after a system crash (recommended except for highly secure environments)" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>MSS: (AutoReboot) Allow Windows to automatically restart after a system crash (recommended except for highly secure environments)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (AutoReboot) Allow Windows to automatically restart after a system crash (recommended except for highly secure environments)" Operator="Equals" Severity="Informational" id="{7c5e841a-332d-4b82-8b83-d43058527929}">
<Description>Enabled, permits a server to automatically reboot after a fatal crash. It is enabled by default, which is undesirable on highly secure servers. </Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{9630f89d-f55b-4d72-85b2-9cc3739a9dfc}" Severity="Critical" />
<ExistentialRule Name="Accounts: Guest account status" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Accounts: Guest account status</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Accounts: Guest account status" Operator="Equals" Severity="Critical" id="{9030f328-a539-4930-be12-eb693106a2c0}">
<Description>The Guest account allows unauthenticated network users to gain access to the system.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{0681de05-828d-451b-aaf9-1704c2ed8b86}" Severity="Critical" />
<ExistentialRule Name="Network access: Let Everyone permissions apply to anonymous users" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Network access: Let Everyone permissions apply to anonymous users</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Let Everyone permissions apply to anonymous users" Operator="Equals" Severity="Critical" id="{eec90afe-20d0-4d87-9e6f-5c1bc837ae0a}">
<Description>Enable setting, anonymous users allowed to enumerate the names of domain accounts and network shares. Unauthorized user could anonymously list account names and shared resources to guess passwords or perform social engineering attacks.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{05538263-d4d3-40eb-929e-07c7fdfd8260}" Severity="Critical" />
<ExistentialRule Name="Accounts: Rename administrator account" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Accounts: Rename administrator account</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Accounts: Rename administrator account" Operator="NotEquals" Severity="Critical" id="{6511f795-8996-4d6a-8dcb-4084ec9398e1}">
<Description>Microsoft recommends that you choose another name for this account, and that you avoid names that denote administrative or elevated access accounts.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{4aead19f-a276-4b88-990c-a8dfa231dae1}" Severity="Important" />
<ExistentialRule Name="Accounts: Rename guest account" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Accounts: Rename guest account</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Accounts: Rename guest account" Operator="NotEquals" Severity="Warning" id="{a46ae0aa-7ed8-46b5-be14-7ca3c10b0c53}">
<Description>Microsoft also recommends that you rename this account to something that does not indicate its purpose. Even if you disable this account (which is recommended), ensure that you rename it for added security.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{154408ea-0242-45d6-9230-0e0cbadd21d4}" Severity="Critical" />
<ExistentialRule Name="Accounts: Administrator account status" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Accounts: Administrator account status</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Accounts: Administrator account status" Operator="Equals" Severity="Critical" id="{fecb7b4d-49ee-49d7-b304-849f3ef0c618}">
<Description>When a computer is booted into safe mode, the Administrator account is always enabled, regardless of how this setting is configured.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{70ba3854-33f1-4402-b067-2bcadf0d7e66}" Severity="Critical" />
<ExistentialRule Name="Accounts: Limit local account use of blank passwords to console logon only" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Accounts: Limit local account use of blank passwords to console logon only</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Accounts: Limit local account use of blank passwords to console logon only" Operator="Equals" Severity="Critical" id="{a26b1edb-8955-4d86-af6a-134c7f2f5e50}">
<Description> If you enable this policy setting, local accounts that have blank passwords will not be able to log on to the network from remote client computers. Such accounts will only be able to log on at the keyboard of the computer.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{d1cd54c8-2cd6-4123-b0da-e01eac9afde8}" Severity="Critical" />
<ExistentialRule Name="Network security: Do not store LAN Manager hash value on next password change" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Network security: Do not store LAN Manager hash value on next password change</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network security: Do not store LAN Manager hash value on next password change" Operator="Equals" Severity="Critical" id="{c1a359d7-a72b-41ae-95a1-91a2bd525d54}">
<Description>The LM hash is relatively weak and prone to attack compared to the cryptographically stronger Microsoft Windows NT® hash.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{9e417a02-8f2a-4e5f-9962-5a9274616230}" Severity="Critical" />
<ExistentialRule Name="Microsoft network client: Send unencrypted password to third-party SMB servers" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Microsoft network client: Send unencrypted password to third-party SMB servers</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Microsoft network client: Send unencrypted password to third-party SMB servers" Operator="Equals" Severity="Critical" id="{dd9b5acd-8bdd-4c77-a72c-7d091fdfe1f9}">
<Description>Microsoft recommends that you disable this policy setting unless there is a strong business case to enable it. If this policy setting is enabled, unencrypted passwords will be allowed across the network.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{dcfdbeca-9a86-4676-8137-0f0829f0a2f7}" Severity="Critical" />
<ExistentialRule Name="Require a Password When a Computer Wakes (Plugged In)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Require a Password When a Computer Wakes (Plugged In)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Require a Password When a Computer Wakes (Plugged In)" Operator="Equals" Severity="Critical" id="ACPromptForPasswordOnResume_2">
<Description>Specifies whether or not the user is prompted for a password when the system resumes from sleep. </Description>
<Value ValueA="Enabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{c65edca7-226d-4e48-a78f-c9b2f8cc7058}" Severity="Critical" />
<ExistentialRule Name="Interactive logon: Prompt user to change password before expiration" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Interactive logon: Prompt user to change password before expiration</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Interactive logon: Prompt user to change password before expiration" Operator="Equals" Severity="Critical" id="{e363e291-d149-43c1-bb11-22eef13c7933}">
<Description>Microsoft recommends that you configure this policy setting to 14 days to sufficiently warn users when their passwords will expire.</Description>
<Value ValueA="14" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{013e644e-eb3a-4a43-b35b-3a003882e176}" Severity="Critical" />
<ExistentialRule Name="Require a Password When a Computer Wakes (On Battery)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Require a Password When a Computer Wakes (On Battery)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Require a Password When a Computer Wakes (On Battery)" Operator="Equals" Severity="Critical" id="DCPromptForPasswordOnResume_2">
<Description>Specifies whether or not the user is prompted for a password when the system resumes from sleep. </Description>
<Value ValueA="Enabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{d1c4d69f-f20e-4e51-a4bb-4df603d826bf}" Severity="Critical" />
<ExistentialRule Name="Do not allow passwords to be saved" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Do not allow passwords to be saved</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Do not allow passwords to be saved" Operator="Equals" Severity="Critical" id="TS_CLIENT_DISABLE_PASSWORD_SAVING_2">
<Description> If you enable this policy setting, the password saving checkbox is disabled for Terminal Services clients and users will not be able to save passwords.</Description>
<Value ValueA="Enabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{999f78ef-2e2e-41b5-9284-ede0123c6d85}" Severity="Critical" />
<ExistentialRule Name="Domain member: Maximum machine account password age" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Domain member: Maximum machine account password age</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Domain member: Maximum machine account password age" Operator="Equals" Severity="Critical" id="{8912a696-54aa-40be-953f-f7e2d26875c2}">
<Description>By default, domain members automatically change their domain passwords every 30 days. </Description>
<Value ValueA="30" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{f77f0e76-2de7-4bdc-b549-1539f366c603}" Severity="Critical" />
<ExistentialRule Name="Always prompt for password upon connection" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Always prompt for password upon connection</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Always prompt for password upon connection" Operator="Equals" Severity="Critical" id="TS_PASSWORD">
<Description>Enforce a password prompt for log on to Terminal Services, even if already provided the password in the Remote Desktop Connection client. By default, Terminal Services allows automatic log on if password was entered Remote Desktop Connection client.</Description>
<Value ValueA="Enabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{f33945b7-f22e-4133-91e2-6ac3b34370ec}" Severity="Critical" />
<ExistentialRule Name="Domain member: Disable machine account password changes" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Domain member: Disable machine account password changes</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Domain member: Disable machine account password changes" Operator="Equals" Severity="Critical" id="{379eacc8-3fff-457a-bc1c-6d722428402d}">
<Description> If you enable this policy setting, the domain member will be prevented from changing its computer account </Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{605bc6fb-834b-40f0-90ff-ae131080fe70}" Severity="Critical" />
<ExistentialRule Name="Network access: Do not allow storage of passwords and credentials for network authentication" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network access: Do not allow storage of passwords and credentials for network authentication</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Do not allow storage of passwords and credentials for network authentication" Operator="Equals" Severity="Critical" id="{93c57666-29fd-4a8f-87dd-88c3700c092b}">
<Description>The Network access: Do not allow storage of passwords and credentials for network authentication setting is configured to Enabled for the two environments that are discussed in this guide.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{ee2775b4-c93e-4c5f-9fc2-bfbeff323fe9}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Domain: Firewall state" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Windows Firewall: Domain: Firewall state</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Domain: Firewall state" Operator="Equals" Severity="Critical" id="{84874c8d-e5f0-477b-af0b-9d9f4ef4bd57}">
<Description>This setting controls the Windows Firewall state and can be used to turn the Windows Firewall on or off.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{0d62d8f2-6ee2-4bb5-bdb3-570ac2fd7185}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Private: Display a notification" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Windows Firewall: Private: Display a notification</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Private: Display a notification" Operator="Equals" Severity="Critical" id="{c3fdcfec-61ab-49e0-aef5-0696e491934e}">
<Description>The recommended Windows Firewall with Advanced Security configuration for the EC environment includes firewall rules that allow for Remote Desktop communications to occur. This GPO is recommended to be set to Yes</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{97711f97-8b54-4a4c-b635-71b943d2d853}" Severity="Important" />
<ExistentialRule Name="MSS: (TcpMaxDataRetransmissions) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (TcpMaxDataRetransmissions) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (TcpMaxDataRetransmissions) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)" Operator="Equals" Severity="Warning" id="{632b59db-5c43-4b91-bb46-fe77047543cc}">
<Description>This setting controls the number of times that TCP retransmits an individual data segment (non-connect segment) before the connection is aborted. The retransmission time-out is doubled with each successive retransmission on a connection. </Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{23f9a43b-a364-4b30-9ccb-5aef1d033433}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Public: Display a notification" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Windows Firewall: Public: Display a notification</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Public: Display a notification" Operator="Equals" Severity="Critical" id="{7fdc956d-3302-4fc7-b85d-5cf09589ca57}">
<Description>Can used both mistakenly and maliciously to allow programs and ports to be opened in the Windows Firewall.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{2e371982-9233-40c0-83ab-291434fab365}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Private: Apply local firewall rules" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Windows Firewall: Private: Apply local firewall rules</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Private: Apply local firewall rules" Operator="Equals" Severity="Critical" id="{2eaa62e2-c341-43ed-8be6-92cfd9b87709}">
<Description>The recommended Windows Firewall with Advanced Security configuration for the EC environment includes firewall rules that allow for Remote Desktop communications to occur. This GPO is recommended to be set to Yes</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{204580f7-4e41-4efb-9874-e84a0f122cb4}" Severity="Important" />
<ExistentialRule Name="MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)" Operator="Equals" Severity="Warning" id="{6ae49043-193a-4fc6-a9fc-8cbb1bae33e4}">
<Description>IP source routing is a mechanism that allows the sender to determine the IP route that a datagram should take through the network. </Description>
<Value ValueA="2" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{c138280d-0c23-4b35-a6fc-87c47fda667e}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Private: Apply local connection security rules" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Windows Firewall: Private: Apply local connection security rules</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Private: Apply local connection security rules" Operator="Equals" Severity="Critical" id="{3f986510-705c-4cf0-9960-46749dae4306}">
<Description>The recommended Windows Firewall with Advanced Security configuration for the EC environment includes firewall rules that allow for Remote Desktop communications to occur. This GPO is recommended to be set to Yes</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{3db1f779-3892-4d8d-a7d8-9c98f0ca1ffb}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Private: Firewall state" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Windows Firewall: Private: Firewall state</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Private: Firewall state" Operator="Equals" Severity="Critical" id="{ebfa47ec-45b5-4bf6-acf1-593fa1282987}">
<Description>Local administrators of computers in the EC environment can configure local firewall rules to permit additional communications to a computer. Defined rules may be found in Windows Firewall section of the Group Policy Object Editor Inbound Rules link.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{f26658af-ce03-4505-8263-1a598ebfe27c}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Public: Inbound connections" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Windows Firewall: Public: Inbound connections</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Public: Inbound connections" Operator="Equals" Severity="Critical" id="Public_Inbound_Connections">
<Description>The default behavior is to block connections unless there are firewall rules to allow the connection. </Description>
<Value ValueA="Enabled" />
</SettingRule>
<OptionRule Name="Inbound Connections" Operator="Equals" Severity="Warning" id="DefaultInboundActions">
<Description>The default behavior is to block connections unless there are firewall rules to allow the connection. </Description>
<Value ValueA="$(string.ac1a7471dc154e72b11333ca4d0ba7fd)" />
</OptionRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{ee7799ac-d3c4-4061-bc72-701fa8963916}" Severity="Important" />
<ExistentialRule Name="MSS: (TcpMaxDataRetransmissions IPv6) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (TcpMaxDataRetransmissions IPv6) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (TcpMaxDataRetransmissions IPv6) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)" Operator="Equals" Severity="Warning" id="{793bba7d-070e-4bc5-b9d8-16fdaf7f9f72}">
<Description>This setting controls the number of times that TCP retransmits an individual data segment (non-connect segment) before the connection is aborted. The retransmission time-out is doubled with each successive retransmission on a connection. </Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{d4b34b26-3436-4ca9-9883-9df57f1192a7}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Private: Outbound connections" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Windows Firewall: Private: Outbound connections</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Private: Outbound connections" Operator="Equals" Severity="Critical" id="{c8cbfca5-2578-42a5-bfb8-189ab4bf1b9f}">
<Description>Set to Allow or Block outbound connections. Default is Allow.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{e58f7b1a-f57f-46ab-a8d2-1a1eb7095a4a}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Public: Allow unicast response" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Windows Firewall: Public: Allow unicast response</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Public: Allow unicast response" Operator="Equals" Severity="Critical" id="{31f94d5a-bc3e-4cdb-b6a2-ca18996736df}">
<Description>Potential vulnerability to DoS attacks and machine profile probing</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{80feb8df-d6d2-4bb2-9900-05ab7470aca8}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Public: Apply local firewall rules" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Windows Firewall: Public: Apply local firewall rules</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Public: Apply local firewall rules" Operator="Equals" Severity="Critical" id="{a3157489-be2b-48cc-b9d8-7c8df6f29282}">
<Description>If you configure this setting to No, administrators can still create firewall rules, but the rules will not be applied. </Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{b9b9852d-d5dd-4818-90c5-030a9fa1ae1a}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Public: Firewall state" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Windows Firewall: Public: Firewall state</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Public: Firewall state" Operator="Equals" Severity="Critical" id="{cbf6858c-0f7f-4419-9370-1ab531163b98}">
<Description>Select On (recommended) to have Windows Firewall with Advanced Security use the settings for this profile to filter network traffic</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{a6fa9373-0401-4ce7-aa44-3649c9b5b21b}" Severity="Optional" />
<ExistentialRule Name="MSS: (PerformRouterDiscovery) Allow IRDP to detect and configure Default Gateway addresses (could lead to DoS)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (PerformRouterDiscovery) Allow IRDP to detect and configure Default Gateway addresses (could lead to DoS)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (PerformRouterDiscovery) Allow IRDP to detect and configure Default Gateway addresses (could lead to DoS)" Operator="Equals" Severity="Informational" id="{ef89ea15-99c2-49a9-894e-3e978eaa36a3}">
<Description>This setting is used to enable or disable the Internet Router Discovery Protocol (IRDP), which allows the system to detect and configure default gateway addresses automatically as described in RFC 1256 on a per-interface basis</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{e527bd6d-fa91-474d-9b8f-45b623024bd8}" Severity="Optional" />
<ExistentialRule Name="MSS: (NoDefaultExempt) Configure IPSec exemptions for various types of network traffic." Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (NoDefaultExempt) Configure IPSec exemptions for various types of network traffic.</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (NoDefaultExempt) Configure IPSec exemptions for various types of network traffic." Operator="Equals" Severity="Informational" id="{7d74a5a3-06cd-4c3a-827e-9ed32422063b}">
<Description>The default exemptions to IPsec policy filters are documented in the online help for the specific operating system and it possible for Internet Key Exchange (IKE) and the Kerberos authentication protocol to function. See the Knowledge Base article 811832</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{19e95a46-d240-4df0-8b1e-70d2014fbec1}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Domain: Allow unicast response" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Windows Firewall: Domain: Allow unicast response</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Domain: Allow unicast response" Operator="Equals" Severity="Critical" id="{9c92d568-918c-4b2f-ad71-4e3c55538488}">
<Description>Enable sends multicast or broadcast messages to other computers Firewall waits three seconds for unicast responses then blocks responses. Disable computer sends a multicast or broadcast message to other computers Firewall blocks unicast responses.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{7449ec76-fe13-40d7-9336-6087547ff5ba}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Domain: Apply local connection security rules" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Windows Firewall: Domain: Apply local connection security rules</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Domain: Apply local connection security rules" Operator="Equals" Severity="Critical" id="{a107c4a0-ad8f-4b54-a702-c8f4d26ecf90}">
<Description>If you configure this setting to No, administrators can still create firewall rules, but the rules will not be applied. This setting is available only when configuring the policy through Group Policy.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{31fc7cb9-90a1-4095-a254-14a8dd75ee26}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Domain: Apply local firewall rules" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Windows Firewall: Domain: Apply local firewall rules</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Domain: Apply local firewall rules" Operator="Equals" Severity="Critical" id="{1c0a2120-059f-44b3-96f2-7ec692ac210d}">
<Description>If you configure this setting to No, administrators can still create firewall rules, but the rules will not be applied. This setting is available only when configuring the policy through Group Policy.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{50bc83e9-55b7-49cc-87ec-d4faa56c69a8}" Severity="Optional" />
<ExistentialRule Name="MSS: (Hidden) Hide Computer From the Browse List (not recommended except for highly secure environments)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (Hidden) Hide Computer From the Browse List (not recommended except for highly secure environments)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (Hidden) Hide Computer From the Browse List (not recommended except for highly secure environments)" Operator="Equals" Severity="Informational" id="{98f444af-789f-4654-a9c0-9217c6162189}">
<Description>Hide the computer from the Browse list, which means that the computer will stop announcing itself to other computers on the same network. An attacker who knows the name of a computer can more easily gather additional information .</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{9ed01778-21e7-4b1e-b88e-6939d117f08a}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Private: Allow unicast response" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Windows Firewall: Private: Allow unicast response</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Private: Allow unicast response" Operator="Equals" Severity="Critical" id="{22b0c796-6e24-452f-a04c-187a2722f304}">
<Description>The recommended Windows Firewall with Advanced Security configuration for the EC environment includes firewall rules that allow for Remote Desktop communications to occur. Microsoft recommends to configure this policy setting to No.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{b6329fe9-70d3-4c68-9bf5-98f602ed36b2}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Domain: Inbound connections" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Windows Firewall: Domain: Inbound connections</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Domain: Inbound connections" Operator="Equals" Severity="Critical" id="Domain_Inbound_Connections">
<Description>The default behavior is to block connections unless there are firewall rules to allow the connection. </Description>
<Value ValueA="Enabled" />
</SettingRule>
<OptionRule Name="Inbound Connections" Operator="Equals" Severity="Critical" id="DefaultInboundActions">
<Description>The default behavior is to block connections unless there are firewall rules to allow the connection. </Description>
<Value ValueA="$(string.3dc8e9cfabac4a4d9dc4e289fdf262da)" />
</OptionRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{8bb50fdf-497a-407e-8b90-2355b7fba2c1}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Domain: Display a notification" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Windows Firewall: Domain: Display a notification</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Domain: Display a notification" Operator="Equals" Severity="Critical" id="{6380cace-ea1b-4d18-b537-4445a4cdb4c2}">
<Description>If Apply local firewall rules setting is configured to No, Microsoft recommends also configuring the Display a notification setting to No. </Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{f8f37b46-5b7e-48d9-92a4-408f28c7b30e}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Public: Apply local connection security rules" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Windows Firewall: Public: Apply local connection security rules</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Public: Apply local connection security rules" Operator="Equals" Severity="Critical" id="{67468f4c-b656-427e-9042-b708a6cef491}">
<Description>If enabled this setting allows local administrators to override group policy.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{91bb8506-e5c5-4221-a58f-e836f736208f}" Severity="Optional" />
<ExistentialRule Name="MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes" Operator="Equals" Severity="Informational" id="{55d8c1e1-06c9-4ec0-a026-fbb0842d1bac}">
<Description>Internet Control Message Protocol (ICMP) redirects cause the stack to plumb host routes. These routes override the Open Shortest Path First (OSPF)–generated routes.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{194ff3d9-ba8a-481f-b8b9-002760e1276c}" Severity="Optional" />
<ExistentialRule Name="MSS: (KeepAliveTime) How often keep-alive packets are sent in milliseconds" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (KeepAliveTime) How often keep-alive packets are sent in milliseconds</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (KeepAliveTime) How often keep-alive packets are sent in milliseconds" Operator="LessEquals" Severity="Informational" id="{96dc4051-65a7-4618-976f-3096afbb8448}">
<Description>This value controls how often TCP attempts to verify that an idle connection is still intact by sending a keep-alive packet. If the remote computer is still reachable, it acknowledges the keep-alive packet. </Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{ad6d56d7-4087-4287-aa24-23e6f0ab2eeb}" Severity="Important" />
<ExistentialRule Name="MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)" Operator="Equals" Severity="Warning" id="{3e7a5baf-3362-4550-acb2-7eb0cc5bb2f7}">
<Description>IP source routing is a mechanism that allows the sender to determine the IP route that a datagram should take through the network. </Description>
<Value ValueA="2" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{eb2729bd-189e-4e49-8f12-f72cd675ff82}" Severity="Optional" />
<ExistentialRule Name="MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers" Operator="Equals" Severity="Informational" id="{4ecfa16e-0710-4823-bf61-1826d299beb1}">
<Description>NetBIOS over TCP/IP is a network protocol that among other things provides a way to easily resolve NetBIOS names that are registered on Windows–based systems to the IP addresses that are configured on those systems. </Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{e86c5885-b74c-4438-bae6-d655b5d6c002}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Private: Inbound connections" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Windows Firewall: Private: Inbound connections</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Private: Inbound connections" Operator="Equals" Severity="Critical" id="Private_Inbound_Connections">
<Description>Microsoft recommends only changing the profile to Private for a trusted network.</Description>
<Value ValueA="Enabled" />
</SettingRule>
<OptionRule Name="Inbound Connections" Operator="Equals" Severity="Warning" id="DefaultInboundActions">
<Description>Microsoft recommends only changing the profile to Private for a trusted network.</Description>
<Value ValueA="$(string.43bcf2ef7f9e4f21a3222e0b58894de8)" />
</OptionRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{19fcb177-e639-4400-9683-9918461cdd31}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Public: Outbound connections" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Windows Firewall: Public: Outbound connections</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Public: Outbound connections" Operator="Equals" Severity="Critical" id="{906da049-baa7-4e21-a2a7-b72a405e6f2d}">
<Description>Set to Allow or Block outbound connections. Default is Allow.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{c3fa4e56-78ce-4ed7-96de-e4565196cebf}" Severity="Critical" />
<ExistentialRule Name="Windows Firewall: Domain: Outbound connections" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Windows Firewall: Domain: Outbound connections</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Windows Firewall: Domain: Outbound connections" Operator="Equals" Severity="Critical" id="{61fd4f85-980b-4105-ba46-2a11ed050eaa}">
<Description>Outbound connections set to Block and then deploy the firewall policy by using a GPO, computers that receive the GPO settings cannot receive subsequent Group Policy updates unless you create and deploy an outbound rule that enables Group Policy to work. </Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{c60773c7-68a6-4461-b569-1a3a71b74ce9}" Severity="Critical" />
<ExistentialRule Name="Manage auditing and security log" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Manage auditing and security log</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Manage auditing and security log" Operator="Equals" Severity="Critical" id="{3f8bdf0e-40ed-44cd-83d9-5dfdfb580bdf}">
<Description>Because this capability represents a relatively small threat, the Manage auditing and security log setting enforces the default value of the Administrators group </Description>
<Value ValueA="Administrators" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{c0a0e44c-bb20-47ff-ab30-bdbe6a73ca2d}" Severity="Important" />
<ExistentialRule Name="Allow log on through Remote Desktop Services" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Allow log on through Remote Desktop Services</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Allow log on through Remote Desktop Services" Operator="Equals" Severity="Warning" id="{a2854958-7e0c-428e-93a6-5271c536576d}">
<Description>Remote Assistance as part of its help desk strategy, create a group and assign it this user right through Group Policy. Do not use Remote Assistance, assign this user right only to the Administrators group or use the restricted groups feature. </Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{e92b4d3c-832b-4381-9fcf-34d9e9124720}" Severity="Optional" />
<ExistentialRule Name="Allow users to connect remotely using Remote Desktop Services" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Allow users to connect remotely using Remote Desktop Services</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Allow users to connect remotely using Remote Desktop Services" Operator="Equals" Severity="Informational" id="TS_DISABLE_CONNECTIONS">
<Description>Creates a potential breach of authentication. Use with caution.</Description>
<Value ValueA="Not Configured" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{5393d3c1-df1c-4edb-b4a7-502fd56d3fb2}" Severity="Critical" />
<ExistentialRule Name="Allow Remote Shell Access" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Allow Remote Shell Access</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Allow Remote Shell Access" Operator="Equals" Severity="Critical" id="AllowRemoteShellAccess">
<Description>Configures access to remote shells.</Description>
<Value ValueA="Enabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{b994a95d-8cfc-4eb9-beef-135cb64fbfce}" Severity="Optional" />
<ExistentialRule Name="Deny log on through Remote Desktop Services" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Deny log on through Remote Desktop Services</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Deny log on through Remote Desktop Services" Operator="Equals" Severity="Informational" id="{0731f637-f0ae-4700-8391-ab43a86ce705}">
<Description>After the baseline member server is joined to a domain environment, there is no need to use local accounts to access the server from the network. Domain accounts can access the server for administration and end-user processing.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{aa7a0ab6-45c2-4e18-aaa3-ab523ca477ff}" Severity="Critical" />
<ExistentialRule Name="Domain member: Require strong (Windows 2000 or later) session key" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Domain member: Require strong (Windows 2000 or later) session key</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Domain member: Require strong (Windows 2000 or later) session key" Operator="Equals" Severity="Critical" id="{17cc7240-2e94-4340-a93f-c50378e546fb}">
<Description>To enable this policy setting, all domain controllers in the domain must be able to encrypt secure channel data with a strong key, which means all domain controllers must be running Microsoft Windows 2000 or later. </Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{a36ea21c-cf4f-45f5-bd89-f0cb226af50d}" Severity="Important" />
<ExistentialRule Name="System cryptography: Force strong key protection for user keys stored on the computer" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>System cryptography: Force strong key protection for user keys stored on the computer</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="System cryptography: Force strong key protection for user keys stored on the computer" Operator="Equals" Severity="Warning" id="{07a6afa7-55de-4989-a12d-6b3765ff80b5}">
<Description>Setting so that users must provide a password—distinct from their domain password—every time that they use a key, makes it more difficult for an attacker to access locally stored keys.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{e3d255b0-001b-4207-8120-f52f76e2181f}" Severity="Critical" />
<ExistentialRule Name="Network Security: Restrict NTLM: Add remote server exceptions for NTLM authentication" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network Security: Restrict NTLM: Add remote server exceptions for NTLM authentication</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network Security: Restrict NTLM: Add remote server exceptions for NTLM authentication" Operator="Equals" Severity="Critical" id="{35336969-0afb-4d32-947b-fef5d3cc4ee5}">
<Description>This policy setting allows you to create an exception list of remote servers to which clients are allowed to use NTLM authentication if the "Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers" policy setting is configured.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{73e61ff1-beea-4870-a7b3-71e48a59b29c}" Severity="Important" />
<ExistentialRule Name="MSS: (TcpMaxDataRetransmissions) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (TcpMaxDataRetransmissions) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (TcpMaxDataRetransmissions) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)" Operator="Equals" Severity="Warning" id="{632b59db-5c43-4b91-bb46-fe77047543cc}">
<Description>This setting controls the number of times that TCP retransmits an individual data segment (non-connect segment) before the connection is aborted. The retransmission time-out is doubled with each successive retransmission on a connection. </Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{da93aa84-62b1-4e95-af91-a0bc5b32d22a}" Severity="Critical" />
<ExistentialRule Name="Network security: Do not store LAN Manager hash value on next password change" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Network security: Do not store LAN Manager hash value on next password change</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network security: Do not store LAN Manager hash value on next password change" Operator="Equals" Severity="Critical" id="{c1a359d7-a72b-41ae-95a1-91a2bd525d54}">
<Description>The LM hash is relatively weak and prone to attack compared to the cryptographically stronger Microsoft Windows NT® hash.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{2f56ef7d-0613-47f4-ab88-060b0a534a52}" Severity="Important" />
<ExistentialRule Name="Network Security: Allow PKU2U authentication requests to this computer to use online identities" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network Security: Allow PKU2U authentication requests to this computer to use online identities</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network Security: Allow PKU2U authentication requests to this computer to use online identities" Operator="Equals" Severity="Warning" id="{228b7477-4686-4df1-979c-e828dfabb238}">
<Description>This policy will be turned off by default on domain joined machines. This would disallow the online identities to be able to authenticate to the domain joined machine in Windows 7.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{f5e35cb8-8c62-41c8-9953-ee1052ccb877}" Severity="Critical" />
<ExistentialRule Name="Network security: LAN Manager authentication level" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Network security: LAN Manager authentication level</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network security: LAN Manager authentication level" Operator="Equals" Severity="Critical" id="{a8169533-f80b-4791-bd76-2d21c8f33bc4}">
<Description>Configure to the strongest possible authentication level. Windows Server 2003 with Windows Vista or Windows XP Professional–based workstations, configure policy to Send NTLMv2 response only. Refuse LM and NTLM option for the highest security.</Description>
<Value ValueA="5" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{b2131895-e20b-4442-9c5e-c7b70e1b2794}" Severity="Important" />
<ExistentialRule Name="MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)" Operator="Equals" Severity="Warning" id="{6ae49043-193a-4fc6-a9fc-8cbb1bae33e4}">
<Description>IP source routing is a mechanism that allows the sender to determine the IP route that a datagram should take through the network. </Description>
<Value ValueA="2" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{7867b62c-7e11-4f8b-a452-fb2d0d4dd1b8}" Severity="Important" />
<ExistentialRule Name="MSS: (TcpMaxDataRetransmissions IPv6) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (TcpMaxDataRetransmissions IPv6) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (TcpMaxDataRetransmissions IPv6) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)" Operator="Equals" Severity="Warning" id="{793bba7d-070e-4bc5-b9d8-16fdaf7f9f72}">
<Description>This setting controls the number of times that TCP retransmits an individual data segment (non-connect segment) before the connection is aborted. The retransmission time-out is doubled with each successive retransmission on a connection. </Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{309aee2a-d7e8-4813-8ed6-89bf1fc7c8fb}" Severity="Optional" />
<ExistentialRule Name="MSS: (PerformRouterDiscovery) Allow IRDP to detect and configure Default Gateway addresses (could lead to DoS)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (PerformRouterDiscovery) Allow IRDP to detect and configure Default Gateway addresses (could lead to DoS)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (PerformRouterDiscovery) Allow IRDP to detect and configure Default Gateway addresses (could lead to DoS)" Operator="Equals" Severity="Informational" id="{ef89ea15-99c2-49a9-894e-3e978eaa36a3}">
<Description>This setting is used to enable or disable the Internet Router Discovery Protocol (IRDP), which allows the system to detect and configure default gateway addresses automatically as described in RFC 1256 on a per-interface basis</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{712d0c6e-7783-4341-a63b-4f3d011237ef}" Severity="Critical" />
<ExistentialRule Name="Microsoft network client: Send unencrypted password to third-party SMB servers" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Microsoft network client: Send unencrypted password to third-party SMB servers</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Microsoft network client: Send unencrypted password to third-party SMB servers" Operator="Equals" Severity="Critical" id="{dd9b5acd-8bdd-4c77-a72c-7d091fdfe1f9}">
<Description>Microsoft recommends that you disable this policy setting unless there is a strong business case to enable it. If this policy setting is enabled, unencrypted passwords will be allowed across the network.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{6ddfe646-fbff-4401-b44e-1ff7565457b9}" Severity="Optional" />
<ExistentialRule Name="MSS: (NoDefaultExempt) Configure IPSec exemptions for various types of network traffic." Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (NoDefaultExempt) Configure IPSec exemptions for various types of network traffic.</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (NoDefaultExempt) Configure IPSec exemptions for various types of network traffic." Operator="Equals" Severity="Informational" id="{7d74a5a3-06cd-4c3a-827e-9ed32422063b}">
<Description>The default exemptions to IPsec policy filters are documented in the online help for the specific operating system and it possible for Internet Key Exchange (IKE) and the Kerberos authentication protocol to function. See the Knowledge Base article 811832</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{c4f93ad9-c4cc-46a9-82c7-2fc9e9f94340}" Severity="Critical" />
<ExistentialRule Name="Network Security: Restrict NTLM: NTLM authentication in this domain" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network Security: Restrict NTLM: NTLM authentication in this domain</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network Security: Restrict NTLM: NTLM authentication in this domain" Operator="Equals" Severity="Critical" id="{6455be8e-b138-4c52-a5df-8c1d3022eca2}">
<Description>This policy setting allows you to audit NTLM authentication in a domain from this domain controller.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{b63916c3-146d-4ad3-aa3a-35404b0a5ace}" Severity="Critical" />
<ExistentialRule Name="Network access: Do not allow anonymous enumeration of SAM accounts" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Network access: Do not allow anonymous enumeration of SAM accounts</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Do not allow anonymous enumeration of SAM accounts" Operator="Equals" Severity="Critical" id="{7999a80a-6876-4d0f-a62e-39f0e328c1ff}">
<Description>If you enable this policy setting, users with anonymous connections cannot enumerate domain account user names on the workstations in your environment. This policy setting also allows additional restrictions on anonymous connections.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{47f57ddd-49c2-49ee-af8b-c20ea20ca1f7}" Severity="Critical" />
<ExistentialRule Name="Microsoft network client: Digitally sign communications (always)" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Microsoft network client: Digitally sign communications (always)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Microsoft network client: Digitally sign communications (always)" Operator="Equals" Severity="Critical" id="{d73dff05-2cba-4e26-9d06-019ff34f2d69}">
<Description>If you enable this policy setting, the Microsoft network client computer cannot communicate with a Microsoft network server unless that server agrees to sign SMB packets. Does not work in mixed environments</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{f18bcc17-1664-4b85-9538-39ae9c8c0e62}" Severity="Critical" />
<ExistentialRule Name="Domain member: Digitally encrypt secure channel data (when possible)" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Domain member: Digitally encrypt secure channel data (when possible)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Domain member: Digitally encrypt secure channel data (when possible)" Operator="Equals" Severity="Critical" id="{348951c5-443a-4eba-9774-2b47a86bee35}">
<Description>Enable this policy setting, the domain member will request encryption of all secure channel traffic. Disable this policy setting, the domain member will be prevented from negotiating secure channel encryption.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{8b3b77ec-ee5d-420d-bd6d-7393154e5edb}" Severity="Critical" />
<ExistentialRule Name="Domain member: Digitally encrypt or sign secure channel data (always)" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Domain member: Digitally encrypt or sign secure channel data (always)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Domain member: Digitally encrypt or sign secure channel data (always)" Operator="Equals" Severity="Critical" id="{ecbe94ef-b32b-4ddb-81be-e096e42731cc}">
<Description>Set to always encrypt or sign secure channel data, it cannot establish a secure channel with a domain controller that is not capable of signing or encrypting all secure channel traffic.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{13cd9999-b480-411f-ac83-e8da24d907e9}" Severity="Critical" />
<ExistentialRule Name="Domain member: Require strong (Windows 2000 or later) session key" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Domain member: Require strong (Windows 2000 or later) session key</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Domain member: Require strong (Windows 2000 or later) session key" Operator="Equals" Severity="Critical" id="{17cc7240-2e94-4340-a93f-c50378e546fb}">
<Description>To enable this policy setting, all domain controllers in the domain must be able to encrypt secure channel data with a strong key, which means all domain controllers must be running Microsoft Windows 2000 or later. </Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{422c9a4a-e8cb-49ce-ba4c-673187357703}" Severity="Critical" />
<ExistentialRule Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) clients" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network security: Minimum session security for NTLM SSP based (including secure RPC) clients</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) clients" Operator="Equals" Severity="Critical" id="{dc3bbd01-1992-45cc-bc6d-c9657c4994c6}">
<Description> The options for this policy setting are:
• Require NTLMv2 session security
• Require 128-bit encryption</Description>
<Value ValueA="537395200" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{e379af24-45be-4a32-bd3d-5991cf9d4ada}" Severity="Critical" />
<ExistentialRule Name="Network access: Sharing and security model for local accounts" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network access: Sharing and security model for local accounts</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Sharing and security model for local accounts" Operator="Equals" Severity="Critical" id="{53b46e5b-f48e-499b-bbb7-d3c00701f9ec}">
<Description>The Classic option allows precise control over access to resources. The Guest only option allows you to treat all users equally. </Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{c6373a1c-e5d6-4e55-aa4e-b17017aed0a3}" Severity="Critical" />
<ExistentialRule Name="Network Security: Restrict NTLM: Add server exceptions in this domain" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network Security: Restrict NTLM: Add server exceptions in this domain</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network Security: Restrict NTLM: Add server exceptions in this domain" Operator="Equals" Severity="Critical" id="{012aaed9-2c85-4498-89cc-1fbcb78fcca1}">
<Description>This policy setting allows you to create an exception list of servers in this domain to which clients are allowed to use NTLM pass-through authentication if the "Network Security: Restrict NTLM: Deny NTLM authentication in this domain" is set.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{63b25c87-2f6e-4c0b-b544-365a617572d0}" Severity="Important" />
<ExistentialRule Name="Network access: Named Pipes that can be accessed anonymously" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network access: Named Pipes that can be accessed anonymously</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Named Pipes that can be accessed anonymously" Operator="Equals" Severity="Warning" id="{af5136b5-ad33-4f59-b8af-1b10815c8619}">
<Description>Rule set to Not Defined or netlogon, lsarpc, samr, browser</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{d285a7a0-4548-4270-b4b1-3e551a6048fc}" Severity="Critical" />
<ExistentialRule Name="Interactive logon: Require Domain Controller authentication to unlock workstation" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Interactive logon: Require Domain Controller authentication to unlock workstation</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Interactive logon: Require Domain Controller authentication to unlock workstation" Operator="Equals" Severity="Critical" id="{3911c359-3c6c-42db-a057-086df2f93052}">
<Description>Microsoft recommends that this policy setting be disabled for laptop users in both environments, because mobile users do not have network access to domain controllers.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{5238d7fe-6006-4482-8aa5-23875627eece}" Severity="Important" />
<ExistentialRule Name="Network security: Allow Local System to use computer identity for NTLM" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network security: Allow Local System to use computer identity for NTLM</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network security: Allow Local System to use computer identity for NTLM" Operator="Equals" Severity="Warning" id="{18484e14-aba5-46fe-8719-040cbfbb416b}">
<Description>This policy setting allows Local System services that use Negotiate to use the computer identity when reverting to NTLM authentication.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{a9d5b56b-3174-4227-8004-e817118d7442}" Severity="Critical" />
<ExistentialRule Name="Interactive logon: Number of previous logons to cache (in case domain controller is not available)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Interactive logon: Number of previous logons to cache (in case domain controller is not available)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Interactive logon: Number of previous logons to cache (in case domain controller is not available)" Operator="Equals" Severity="Critical" id="{8c6175e8-536c-40c5-aa93-c3f927b74677}">
<Description>This policy setting determines the number of unique users for whom logon information is cached locally.</Description>
<Value ValueA="2" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{9ab95317-895a-4e6e-a2ee-d063eb3fa587}" Severity="Critical" />
<ExistentialRule Name="Microsoft network server: Digitally sign communications (always)" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Microsoft network server: Digitally sign communications (always)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Microsoft network server: Digitally sign communications (always)" Operator="Equals" Severity="Critical" id="{98a24d38-9fe8-4280-864d-13c307e13236}">
<Description>Enable this policy setting in a mixed environment to prevent downstream clients from using the workstation as a network server.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{60effdd2-b86e-469a-b456-ef77b6223157}" Severity="Optional" />
<ExistentialRule Name="MSS: (Hidden) Hide Computer From the Browse List (not recommended except for highly secure environments)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (Hidden) Hide Computer From the Browse List (not recommended except for highly secure environments)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (Hidden) Hide Computer From the Browse List (not recommended except for highly secure environments)" Operator="Equals" Severity="Informational" id="{98f444af-789f-4654-a9c0-9217c6162189}">
<Description>Hide the computer from the Browse list, which means that the computer will stop announcing itself to other computers on the same network. An attacker who knows the name of a computer can more easily gather additional information .</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{da041203-cfc1-44ed-ad6a-c505d620c35d}" Severity="Critical" />
<ExistentialRule Name="Microsoft network client: Digitally sign communications (if server agrees)" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Microsoft network client: Digitally sign communications (if server agrees)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Microsoft network client: Digitally sign communications (if server agrees)" Operator="Equals" Severity="Critical" id="{aab6b4a7-1a3e-4b7f-9896-fa8e3b4d132a}">
<Description>Digital signing in Windows–based networks helps to prevent sessions from being hijacked. Enable this policy setting, the Microsoft network client will use signing only if the server with which it communicates accepts digitally signed communication.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{fe3742e8-779a-4f52-80d5-c556f80c8c35}" Severity="Critical" />
<ExistentialRule Name="Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers" Operator="Equals" Severity="Critical" id="{ea667b47-750b-4b2e-a4bd-34c81eaf942c}">
<Description>This policy setting allows you to deny or audit outgoing NTLM traffic from this Windows 7 or this Windows Server 2008 R2 computer to any Windows remote server.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{6d7f98ad-c893-4a7f-b930-1366364f8388}" Severity="Critical" />
<ExistentialRule Name="Microsoft network server: Server SPN target name validation level " Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Microsoft network server: Server SPN target name validation level </Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Microsoft network server: Server SPN target name validation level " Operator="Equals" Severity="Critical" id="{caa80db8-fe74-4794-9e06-c45d880af667}">
<Description>Enable policy setting, client sessions with the SMB service will be forcibly disconnected when the client’s logon hours expire. Disable policy setting, established client sessions will be maintained after the client’s logon hours expire.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{dbeb6cdd-12ce-4c09-8ed7-50e83d8efec8}" Severity="Important" />
<ExistentialRule Name="Network security: Allow LocalSystem NULL session fallback" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network security: Allow LocalSystem NULL session fallback</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network security: Allow LocalSystem NULL session fallback" Operator="Equals" Severity="Warning" id="{ee51772c-e9b0-4aee-aeb6-421efed5ca71}">
<Description>Allow NTLM to fall back to NULL session when used with LocalSystem.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{0c2f431a-9641-4342-89e6-da8735a689c2}" Severity="Optional" />
<ExistentialRule Name="Allow users to connect remotely using Remote Desktop Services" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Allow users to connect remotely using Remote Desktop Services</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Allow users to connect remotely using Remote Desktop Services" Operator="Equals" Severity="Informational" id="TS_DISABLE_CONNECTIONS">
<Description>Creates a potential breach of authentication. Use with caution.</Description>
<Value ValueA="Not Configured" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{698413e7-00fd-459c-8fef-1a843679751f}" Severity="Important" />
<ExistentialRule Name="Network access: Restrict anonymous access to Named Pipes and Shares" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network access: Restrict anonymous access to Named Pipes and Shares</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Restrict anonymous access to Named Pipes and Shares" Operator="Equals" Severity="Warning" id="{875c50ad-165b-471d-84a4-ad65093e5671}">
<Description>Null sessions are a weakness that can be exploited through shares (including the default shares) on computers in your environment.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{b9a7f6be-bcf1-40d1-8624-fbb82988fd7e}" Severity="Critical" />
<ExistentialRule Name="Network access: Let Everyone permissions apply to anonymous users" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Network access: Let Everyone permissions apply to anonymous users</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Let Everyone permissions apply to anonymous users" Operator="Equals" Severity="Critical" id="{eec90afe-20d0-4d87-9e6f-5c1bc837ae0a}">
<Description>Enable setting, anonymous users allowed to enumerate the names of domain accounts and network shares. Unauthorized user could anonymously list account names and shared resources to guess passwords or perform social engineering attacks.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{44ed2d85-622a-4818-bc2b-f662f1110895}" Severity="Critical" />
<ExistentialRule Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) servers" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network security: Minimum session security for NTLM SSP based (including secure RPC) servers</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) servers" Operator="Equals" Severity="Critical" id="{d8291bc1-08e3-4657-a090-dc131edcd7de}">
<Description>The options for the setting are the same:
• Require NTLMv2 session security
• Require 128-bit encryption</Description>
<Value ValueA="537395200" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{1e8b628d-efd5-4db9-a40d-549dde9fd0f3}" Severity="Optional" />
<ExistentialRule Name="MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes" Operator="Equals" Severity="Informational" id="{55d8c1e1-06c9-4ec0-a026-fbb0842d1bac}">
<Description>Internet Control Message Protocol (ICMP) redirects cause the stack to plumb host routes. These routes override the Open Shortest Path First (OSPF)–generated routes.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{0994b843-ee52-4cf0-8b3d-496c85b0bc3c}" Severity="Critical" />
<ExistentialRule Name="Network Security: Restrict NTLM: Incoming NTLM traffic" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network Security: Restrict NTLM: Incoming NTLM traffic</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network Security: Restrict NTLM: Incoming NTLM traffic" Operator="Equals" Severity="Critical" id="{55a758ef-201e-4f0a-9d25-acb18ce20b13}">
<Description>This policy setting allows you to deny or allow incoming NTLM traffic.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{852d2467-045b-49ef-9d0c-a421477830c7}" Severity="Optional" />
<ExistentialRule Name="MSS: (KeepAliveTime) How often keep-alive packets are sent in milliseconds" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (KeepAliveTime) How often keep-alive packets are sent in milliseconds</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (KeepAliveTime) How often keep-alive packets are sent in milliseconds" Operator="LessEquals" Severity="Informational" id="{96dc4051-65a7-4618-976f-3096afbb8448}">
<Description>This value controls how often TCP attempts to verify that an idle connection is still intact by sending a keep-alive packet. If the remote computer is still reachable, it acknowledges the keep-alive packet. </Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{66759ffc-15e5-4a70-90ff-f9c347e76516}" Severity="Important" />
<ExistentialRule Name="Network access: Shares that can be accessed anonymously" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network access: Shares that can be accessed anonymously</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Shares that can be accessed anonymously" Operator="Equals" Severity="Warning" id="{27cd7a84-00e3-4a99-847d-6b3d574fd3f1}">
<Description>The Network access: Shares that can be accessed anonymously setting is configured to Not Defined for the EC environment. However, ensure that this setting is configured to None for the SSLF environment.</Description>
<Value ValueA="" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{5850e810-a38a-44ca-baee-5466141360eb}" Severity="Critical" />
<ExistentialRule Name="Network Security: Restrict NTLM: NTLM authentication in this domain" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network Security: Restrict NTLM: NTLM authentication in this domain</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network Security: Restrict NTLM: NTLM authentication in this domain" Operator="Equals" Severity="Critical" id="{d6fe3b2f-a783-47c1-8a20-934ac36ddea2}">
<Description>This policy setting allows you to deny or allow NTLM authentication within a domain from this domain controller. This policy does not affect interactive logon to this domain controller.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{12be7e2c-242d-4b65-b48d-19732c753cb5}" Severity="Critical" />
<ExistentialRule Name="Network security: LDAP client signing requirements" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network security: LDAP client signing requirements</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network security: LDAP client signing requirements" Operator="Equals" Severity="Critical" id="{dceba9b6-66c1-4ddc-82c0-454f16964d78}">
<Description>Because unsigned network traffic is susceptible to man-in-the-middle attacks, an attacker could cause an LDAP server to make decisions that are based on false queries from the LDAP client.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{0fc438da-9248-4f6b-9850-6d87df1e23bc}" Severity="Critical" />
<ExistentialRule Name="Network access: Allow anonymous SID/Name translation" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Network access: Allow anonymous SID/Name translation</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Allow anonymous SID/Name translation" Operator="Equals" Severity="Critical" id="{568bc756-549f-494c-aad0-9568e4f0aa46}">
<Description>Disable this policy setting to prevent unauthenticated users from obtaining user names that are associated with their respective SIDs</Description>
<Value ValueA="False" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{09a43a14-05fe-4857-a63d-fb577d6d8152}" Severity="Critical" />
<ExistentialRule Name="Set client connection encryption level" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Set client connection encryption level</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Set client connection encryption level" Operator="Equals" Severity="Critical" id="TS_ENCRYPTION_POLICY">
<Description>
The encryption level is set to Enabled:High Level to enforce 128-bit encryption for the two environments that are discussed in this guide.
</Description>
<Value ValueA="Enabled" />
</SettingRule>
<OptionRule Name="Encryption Level" Operator="Equals" Severity="Warning" id="TS_ENCRYPTION_LEVEL">
<Description>The encryption level is set to Enabled:High Level to enforce 128-bit encryption for the two environments that are discussed in this guide.</Description>
<Value ValueA="$(string.c7c2c16080314e20b138a74cb1e8b1dd)" />
</OptionRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{cc756843-7c32-4d11-8e35-a84ce3a1ae59}" Severity="Critical" />
<ExistentialRule Name="Microsoft network server: Digitally sign communications (if client agrees)" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Microsoft network server: Digitally sign communications (if client agrees)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Microsoft network server: Digitally sign communications (if client agrees)" Operator="Equals" Severity="Critical" id="{548a38c2-7762-4e70-88cf-7882cf1c036a}">
<Description>If no signing request comes from the client, a connection will be allowed without a signature if the Microsoft network server: Digitally sign communications (always) setting is not enabled.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{d8f7d3e9-c767-4d9e-8f2b-b38c44780bf2}" Severity="Important" />
<ExistentialRule Name="MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)" Operator="Equals" Severity="Warning" id="{3e7a5baf-3362-4550-acb2-7eb0cc5bb2f7}">
<Description>IP source routing is a mechanism that allows the sender to determine the IP route that a datagram should take through the network. </Description>
<Value ValueA="2" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{00a154a4-682f-4e15-a548-eb63ce62e039}" Severity="Critical" />
<ExistentialRule Name="Network Security: Restrict NTLM: Audit Incoming NTLM Traffic" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network Security: Restrict NTLM: Audit Incoming NTLM Traffic</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network Security: Restrict NTLM: Audit Incoming NTLM Traffic" Operator="Equals" Severity="Critical" id="{725e22de-d566-4e13-9012-583e533d4590}">
<Description>This policy setting allows you to audit incoming NTLM traffic.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{2c26183e-a136-4f39-b229-5a2f868104ab}" Severity="Optional" />
<ExistentialRule Name="MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers" Operator="Equals" Severity="Informational" id="{4ecfa16e-0710-4823-bf61-1826d299beb1}">
<Description>NetBIOS over TCP/IP is a network protocol that among other things provides a way to easily resolve NetBIOS names that are registered on Windows–based systems to the IP addresses that are configured on those systems. </Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{4414146f-11e4-4afc-bbfa-314e2795c05d}" Severity="Critical" />
<ExistentialRule Name="Restrictions for Unauthenticated RPC clients" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Restrictions for Unauthenticated RPC clients</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Restrictions for Unauthenticated RPC clients" Operator="Equals" Severity="Critical" id="RpcRestrictRemoteClients">
<Description> A client will be considered an authenticated client if it uses a named pipe to communicate with the server or if it uses RPC Security . • None
• Authenticated.
• Authenticated without exceptions. </Description>
<Value ValueA="Enabled" />
</SettingRule>
<OptionRule Name="RPC Runtime Unauthenticated Client Restriction to Apply" Operator="Equals" Severity="Warning" id="RpcRestrictRemoteClientsList">
<Description>A client will be considered an authenticated client if it uses a named pipe to communicate with the server or if it uses RPC Security . • None
• Authenticated.
• Authenticated without exceptions.</Description>
<Value ValueA="$(string.e6744bcc94c84ce7b9eee9a979b2d36c)" />
</OptionRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{e3ef6df9-606f-448a-bdda-983541e66709}" Severity="Critical" />
<ExistentialRule Name="Domain member: Digitally sign secure channel data (when possible)" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Domain member: Digitally sign secure channel data (when possible)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Domain member: Digitally sign secure channel data (when possible)" Operator="Equals" Severity="Critical" id="{327982cb-5268-40de-9b8d-ebdf18456dde}">
<Description>Digital signatures protect the traffic from being modified by anyone who captures the data as it traverses the network.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{df35bbb2-b762-4a25-a841-5d64ed7268a3}" Severity="Important" />
<ExistentialRule Name="Network access: Remotely accessible registry paths and sub-paths" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network access: Remotely accessible registry paths and sub-paths</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Remotely accessible registry paths and sub-paths" Operator="Equals" Severity="Warning" id="{790e6cd4-8b28-4952-b95d-3250a88754cb}">
<Description>See the applicable (Vista, Win2K3, or XP) security guide for the detailed description of this rule.</Description>
<Value ValueA="System\CurrentControlSet\Control\Print\Printers
System\CurrentControlSet\Services\Eventlog
Software\Microsoft\OLAP Server
Software\Microsoft\Windows NT\CurrentVersion\Print
Software\Microsoft\Windows NT\CurrentVersion\Windows
System\CurrentControlSet\Control\ContentIndex
System\CurrentControlSet\Control\Terminal Server
System\CurrentControlSet\Control\Terminal Server\UserConfig
System\CurrentControlSet\Control\Terminal Server\DefaultUserConfiguration
Software\Microsoft\Windows NT\CurrentVersion\Perflib
System\CurrentControlSet\Services\SysmonLog
" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{ca8523ec-b32d-4cb0-bac4-9dfa139c0928}" Severity="Important" />
<ExistentialRule Name="RPC Endpoint Mapper Client Authentication" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>RPC Endpoint Mapper Client Authentication</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="RPC Endpoint Mapper Client Authentication" Operator="Equals" Severity="Warning" id="RpcEnableAuthEpResolution">
<Description>By default, RPC clients will not use authentication to communicate with the RPC Server Endpoint Mapper Service when they request the endpoint of a server. </Description>
<Value ValueA="Disabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{f0ff568e-3ac8-4b30-8ce1-64886c761bcc}" Severity="Critical" />
<ExistentialRule Name="Network access: Do not allow anonymous enumeration of SAM accounts and shares" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Network access: Do not allow anonymous enumeration of SAM accounts and shares</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Do not allow anonymous enumeration of SAM accounts and shares" Operator="Equals" Severity="Critical" id="{e0d0bb2c-1e9e-4fec-990f-61d8e111155f}">
<Description>If you enable this policy setting, anonymous users will not be able to enumerate domain account user names and network share names on the workstations in your environment.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{90264ed6-4875-4baa-829a-c07f99e0981d}" Severity="Important" />
<ExistentialRule Name="Network access: Remotely accessible registry paths" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network access: Remotely accessible registry paths</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Remotely accessible registry paths" Operator="Equals" Severity="Warning" id="{2305ec27-4c51-4a76-a3a4-ef36a14186ff}">
<Description>System\CurrentControlSet\Control\ProductOptions
• System\CurrentControlSet\Control\Server Applications
• Software\Microsoft\Windows NT\CurrentVersion</Description>
<Value ValueA="System\CurrentControlSet\Control\ProductOptions
System\CurrentControlSet\Control\Server Applications
Software\Microsoft\Windows NT\CurrentVersion
" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{20b8331f-728f-4cd3-bc19-08edd4ba2076}" Severity="Important" />
<ExistentialRule Name="Network Security: Configure encryption types allowed for Kerberos" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network Security: Configure encryption types allowed for Kerberos</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network Security: Configure encryption types allowed for Kerberos" Operator="Equals" Severity="Warning" id="{58ca8c65-eff9-4dc4-a55d-f111f296a78e}">
<Description>This policy setting allows you to set the encryption types that Kerberos is allowed to use.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{b305aabb-a23d-4cab-8ed2-24d913595b24}" Severity="Optional" />
<ExistentialRule Name="DCOM: Machine Launch Restrictions in Security Descriptor Definition Language (SDDL) syntax" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>DCOM: Machine Launch Restrictions in Security Descriptor Definition Language (SDDL) syntax</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="DCOM: Machine Launch Restrictions in Security Descriptor Definition Language (SDDL) syntax" Operator="Equals" Severity="Informational" id="{2b1108fa-9c24-4873-8810-2ac3b98ff53d}">
<Description>This setting is used to control the attack surface of the computer for DCOM applications.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{1dee17e2-5c53-458f-9f20-a7c0e3cdb052}" Severity="Optional" />
<ExistentialRule Name="System settings: Optional subsystems" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>System settings: Optional subsystems</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="System settings: Optional subsystems" Operator="Equals" Severity="Informational" id="{6dac56a1-c99c-4292-99e4-8bdae5269609}">
<Description>The default value for this policy setting in Windows Server 2003 is POSIX. To disable the POSIX subsystem, the System settings: Optional subsystems setting is configured to None.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{995c4b02-75a4-49ca-ba15-ed2000b6c878}" Severity="Optional" />
<ExistentialRule Name="MSS: (AutoAdminLogon) Enable Automatic Logon (not recommended)" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>MSS: (AutoAdminLogon) Enable Automatic Logon (not recommended)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (AutoAdminLogon) Enable Automatic Logon (not recommended)" Operator="Equals" Severity="Informational" id="{c883c1c8-866f-46c5-8675-2bbe6309b782}">
<Description> If you configure a computer for automatic logon, anyone who can physically gain access to the computer can also gain access to everything that is on the computer, including any network or networks to which the computer is connected.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{e0622d43-d847-4810-aa7a-11907a6f1790}" Severity="Critical" />
<ExistentialRule Name="Turn off Search Companion content file updates" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Turn off Search Companion content file updates</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Turn off Search Companion content file updates" Operator="Equals" Severity="Critical" id="SearchCompanion_DisableFileUpdates">
<Description>If you configure this policy setting to Enabled, you prevent Search Companion from downloading content updates during searches.</Description>
<Value ValueA="Enabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{bcc1b6a1-4c4b-41d8-bdff-4671077603c6}" Severity="Critical" />
<ExistentialRule Name="Interactive logon: Do not require CTRL+ALT+DEL" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Interactive logon: Do not require CTRL+ALT+DEL</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Interactive logon: Do not require CTRL+ALT+DEL" Operator="Equals" Severity="Critical" id="{e3c42d14-4ae9-4f3e-acc8-e77e97145b0a}">
<Description>When this policy setting is enabled, users are not required to use this key combination to log on to the network. However, this configuration poses a security risk because it provides an opportunity for users to log on with weaker logon credentials.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{7beff6b6-edff-4265-a24a-0f320306ecff}" Severity="Critical" />
<ExistentialRule Name="Network access: Do not allow anonymous enumeration of SAM accounts" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Network access: Do not allow anonymous enumeration of SAM accounts</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Do not allow anonymous enumeration of SAM accounts" Operator="Equals" Severity="Critical" id="{7999a80a-6876-4d0f-a62e-39f0e328c1ff}">
<Description>If you enable this policy setting, users with anonymous connections cannot enumerate domain account user names on the workstations in your environment. This policy setting also allows additional restrictions on anonymous connections.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{9143427d-93b2-46c0-a13e-934d1ff98dfc}" Severity="Critical" />
<ExistentialRule Name="Solicited Remote Assistance" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Solicited Remote Assistance</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Solicited Remote Assistance" Operator="Equals" Severity="Critical" id="RA_Solicit">
<Description>If the Solicited Remote Assistance setting is enabled, the following options are available:
• Allow helpers to remotely control the computer
• Allow helpers to only view the computer</Description>
<Value ValueA="Disabled" />
</SettingRule>
<OptionRule Name="Maximum ticket time (units)" Operator="Equals" Severity="Informational" id="RA_Solicit_ExpireUnits_List">
<Description>If the Solicited Remote Assistance setting is enabled, the following options are available:
• Allow helpers to remotely control the computer
• Allow helpers to only view the computer</Description>
<Value ValueA="" />
</OptionRule>
<OptionRule Name="Maximum ticket time (value)" Operator="Equals" Severity="Informational" id="RA_Solicit_ExpireValue_Edt">
<Description>If the Solicited Remote Assistance setting is enabled, the following options are available:
• Allow helpers to remotely control the computer
• Allow helpers to only view the computer</Description>
<Value ValueA="" />
</OptionRule>
<OptionRule Name="Method for sending e-mail invitations" Operator="Equals" Severity="Informational" id="RA_Solicit_Mailto_List">
<Description>If the Solicited Remote Assistance setting is enabled, the following options are available:
• Allow helpers to remotely control the computer
• Allow helpers to only view the computer</Description>
<Value ValueA="" />
</OptionRule>
<OptionRule Name="Permit remote control of this computer" Operator="Equals" Severity="Informational" id="RA_Solicit_Control_List">
<Description>If the Solicited Remote Assistance setting is enabled, the following options are available:
• Allow helpers to remotely control the computer
• Allow helpers to only view the computer</Description>
<Value ValueA="" />
</OptionRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{06192296-c01c-41c2-9ec3-400fd5a13d65}" Severity="Critical" />
<ExistentialRule Name="Turn off the Windows Messenger Customer Experience Improvement Program" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Turn off the Windows Messenger Customer Experience Improvement Program</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Turn off the Windows Messenger Customer Experience Improvement Program" Operator="Equals" Severity="Critical" id="WinMSG_NoInstrumentation_2">
<Description>Enable this policy setting to ensure that Windows Messenger does not collect usage information. Large enterprise environments may not want to have information collected from managed client computers. </Description>
<Value ValueA="Enabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{df75109b-b7a3-4f31-ba0e-898c30b1d56d}" Severity="Critical" />
<ExistentialRule Name="Reschedule Automatic Updates scheduled installations" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Reschedule Automatic Updates scheduled installations</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Reschedule Automatic Updates scheduled installations" Operator="Equals" Severity="Critical" id="RescheduleWaitTime_Title">
<Description>Enabled, a previously scheduled installation will begin after a specified number of minutes when you next start the computer. Disabled or Not configured, previously scheduled installations will occur during the next regularly scheduled installation time.</Description>
<Value ValueA="Enabled" />
</SettingRule>
<OptionRule Name="startup (minutes)" Operator="Equals" Severity="Informational" id="RescheduleWaitTime_Minutes2">
<Description>Enabled, a previously scheduled installation will begin after a specified number of minutes when you next start the computer. Disabled or Not configured, previously scheduled installations will occur during the next regularly scheduled installation time.</Description>
<Value ValueA="1" />
</OptionRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{7bd05027-314d-46be-82b8-a8fecad3b4c5}" Severity="Critical" />
<ExistentialRule Name="Network access: Sharing and security model for local accounts" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network access: Sharing and security model for local accounts</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Sharing and security model for local accounts" Operator="Equals" Severity="Critical" id="{53b46e5b-f48e-499b-bbb7-d3c00701f9ec}">
<Description>The Classic option allows precise control over access to resources. The Guest only option allows you to treat all users equally. </Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{62941427-df06-4408-ad1c-b4969efdb67f}" Severity="Critical" />
<ExistentialRule Name="No auto-restart with logged on users for scheduled automatic updates installations" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>No auto-restart with logged on users for scheduled automatic updates installations</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="No auto-restart with logged on users for scheduled automatic updates installations" Operator="Equals" Severity="Critical" id="NoAutoRebootWithLoggedOnUsers_Title">
<Description>Enabled, wait for a logged-on user to restart it to complete a scheduled installation. No auto-restart for scheduled Automatic Updates installations setting is configured to Disabled or Not configured, notifies user automatically restart in 5 min . </Description>
<Value ValueA="Disabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{c18eaed6-7058-449e-82de-bd53aa5de63d}" Severity="Important" />
<ExistentialRule Name="Network access: Named Pipes that can be accessed anonymously" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network access: Named Pipes that can be accessed anonymously</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Named Pipes that can be accessed anonymously" Operator="Equals" Severity="Warning" id="{af5136b5-ad33-4f59-b8af-1b10815c8619}">
<Description>Rule set to Not Defined or netlogon, lsarpc, samr, browser</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{a7683d68-8eb4-429a-878c-3153f61291cc}" Severity="Critical" />
<ExistentialRule Name="Configure Automatic Updates" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Configure Automatic Updates</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Configure Automatic Updates" Operator="Equals" Severity="Critical" id="AutoUpdateCfg">
<Description>Enabled, the OS recognizes a network connection available and searchs Windows Update or designated intranet site for updates that apply (additonal settings required). Disabled you will need to download and manually install available updates. </Description>
<Value ValueA="Enabled" />
</SettingRule>
<OptionRule Name="Configure automatic updating" Operator="Equals" Severity="Warning" id="AutoUpdateMode">
<Description>Enabled, the OS recognizes a network connection available and searchs Windows Update or designated intranet site for updates that apply (additonal settings required). Disabled you will need to download and manually install available updates.</Description>
<Value ValueA="$(string.55e92f3de0df4cd8a681eb1690b115ab)" />
</OptionRule>
<OptionRule Name="Scheduled install day" Operator="Equals" Severity="Warning" id="AutoUpdateSchDay">
<Description>Enabled, the OS recognizes a network connection available and searchs Windows Update or designated intranet site for updates that apply (additonal settings required). Disabled you will need to download and manually install available updates.</Description>
<Value ValueA="$(string.509b93b359e4419b9bf14dff6451c845)" />
</OptionRule>
<OptionRule Name="Scheduled install time" Operator="Equals" Severity="Warning" id="AutoUpdateSchTime">
<Description>Enabled, the OS recognizes a network connection available and searchs Windows Update or designated intranet site for updates that apply (additonal settings required). Disabled you will need to download and manually install available updates.</Description>
<Value ValueA="$(string.12fa4f86528e41c085492cbac96da3b3)" />
</OptionRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{dd0bbd63-cb83-4771-83e4-4c8bfb6dd31c}" Severity="Critical" />
<ExistentialRule Name="Enumerate administrator accounts on elevation" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Enumerate administrator accounts on elevation</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Enumerate administrator accounts on elevation" Operator="Equals" Severity="Critical" id="EnumerateAdministrators">
<Description>Enable this policy, users will always be required to type in a user name and password to elevate. Disable this policy, all local administrator accounts on the computer will be displayed so the user can choose one and enter the correct password.</Description>
<Value ValueA="Disabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{ca7b8d48-4e41-4e71-9a20-230da5c6ba0c}" Severity="Critical" />
<ExistentialRule Name="Do not allow drive redirection" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Do not allow drive redirection</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Do not allow drive redirection" Operator="Equals" Severity="Critical" id="TS_CLIENT_DRIVE_M">
<Description>If local drives are shared they are left vulnerable to intruders who want to exploit the data that is stored on them. </Description>
<Value ValueA="Enabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{2233fc3e-260f-449e-9e19-6f6f326e10c8}" Severity="Optional" />
<ExistentialRule Name="Devices: Restrict floppy access to locally logged-on user only" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Devices: Restrict floppy access to locally logged-on user only</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Devices: Restrict floppy access to locally logged-on user only" Operator="Equals" Severity="Informational" id="{7815c733-26c6-41ff-acf4-90a6c567081a}">
<Description>If you enable this policy setting, only the interactively logged-on user is allowed to access removable floppy media. If this policy setting is enabled and no one is logged on interactively, the floppy media is accessible over the network.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{106dd3a8-c846-4e8f-86aa-5c81d84e1483}" Severity="Important" />
<ExistentialRule Name="Shutdown: Allow system to be shut down without having to log on" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Shutdown: Allow system to be shut down without having to log on</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Shutdown: Allow system to be shut down without having to log on" Operator="Equals" Severity="Warning" id="{74cf05e1-552e-4f83-8bbb-7cbd5c4cb771}">
<Description>If this policy setting is enabled, the shutdown command is available on the Windows logon screen. Microsoft recommends that you disable this policy setting to restrict the ability to shut down the computer to users with credentials on the system.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{d56842e4-3659-4777-97c1-f9bbe47477df}" Severity="Important" />
<ExistentialRule Name="Prevent the computer from joining a homegroup" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Prevent the computer from joining a homegroup</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Prevent the computer from joining a homegroup" Operator="Equals" Severity="Warning" id="DisableHomeGroup">
<Description>By default, users can add their computer to a homegroup on a home network.
If you enable this policy setting, a user on this computer will not be able to add this computer to a homegroup. This setting does not affect other network sharing features.
If you disable or do not configure this policy setting, a user can add this computer to a homegroup. However, data on a domain-joined computer is not shared with the homegroup.</Description>
<Value ValueA="Not Configured" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{bad20a53-2c9b-4e1c-8a27-4c73f8adbb36}" Severity="Critical" />
<ExistentialRule Name="Shutdown: Clear virtual memory pagefile" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Shutdown: Clear virtual memory pagefile</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Shutdown: Clear virtual memory pagefile" Operator="Equals" Severity="Critical" id="{8c2c4890-d409-4ee5-a98e-32e95477a897}">
<Description> When this policy setting is enabled, the system pagefile is cleared each time that the system shuts down properly. It will take longer to shut down and restart the computer, and will be especially noticeable on computers with large paging files.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{f0164392-334b-46cb-9b1a-e4fd2d378c56}" Severity="Optional" />
<ExistentialRule Name="MSS: (AutoShareWks) Enable Administrative Shares (recommended except for highly secure environments)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (AutoShareWks) Enable Administrative Shares (recommended except for highly secure environments)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (AutoShareWks) Enable Administrative Shares (recommended except for highly secure environments)" Operator="Equals" Severity="Informational" id="{d6887e02-ae62-4c75-91e8-219320a15df5}">
<Description>You can add this registry value to the template file in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RasMan\Parameters\ subkey.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{48fab6d9-60e1-4fe5-8c3f-7b2b728cbe2f}" Severity="Critical" />
<ExistentialRule Name="Turn off printing over HTTP" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Turn off printing over HTTP</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Turn off printing over HTTP" Operator="Equals" Severity="Critical" id="DisableHTTPPrinting_2">
<Description>Information that is transmitted over HTTP through this capability is not protected and can be intercepted by malicious users. For this reason, it is not often used in enterprise environments. </Description>
<Value ValueA="Enabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{4b5df42d-5abb-4b3e-b1a6-63a54ae46e64}" Severity="Optional" />
<ExistentialRule Name="Always install with elevated privileges" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Always install with elevated privileges</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Always install with elevated privileges" Operator="Equals" Severity="Informational" id="AlwaysInstallElevated_2">
<Description />
<Value ValueA="Disabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{5f372990-4414-4c40-b8fb-98dc76bc675c}" Severity="Important" />
<ExistentialRule Name="System objects: Require case insensitivity for non-Windows subsystems" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>System objects: Require case insensitivity for non-Windows subsystems</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="System objects: Require case insensitivity for non-Windows subsystems" Operator="Equals" Severity="Warning" id="{179183d8-cf50-4da2-abba-3a9fb481246a}">
<Description>Because Windows is case insensitive, failure to enforce this policy setting makes it possible for a user of the POSIX subsystem to create a file with the same name as another file by using mixed case to label it.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{93cbd17d-76b9-4cb1-82d7-f43cff1bf7da}" Severity="Important" />
<ExistentialRule Name="Devices: Allowed to format and eject removable media" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Devices: Allowed to format and eject removable media</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Devices: Allowed to format and eject removable media" Operator="Equals" Severity="Warning" id="{5c4134d3-07cb-4f19-8531-e7d8b58b5f24}">
<Description>You can use this policy setting to prevent unauthorized users from removing data on one computer to access it on another computer on which they have local administrator privileges.</Description>
<Value ValueA="2" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{5dce86f2-da6a-4d99-ac8d-fd05b5c863ca}" Severity="Optional" />
<ExistentialRule Name="DCOM: Machine Access Restrictions in Security Descriptor Definition Language (SDDL) syntax" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>DCOM: Machine Access Restrictions in Security Descriptor Definition Language (SDDL) syntax</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="DCOM: Machine Access Restrictions in Security Descriptor Definition Language (SDDL) syntax" Operator="Equals" Severity="Informational" id="{dc5c42d6-d756-453d-9d85-1c4306dec139}">
<Description>This setting is used to control the attack surface of the computer for DCOM applications. </Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{95577ba0-26db-4064-9b27-8ef3ed080108}" Severity="Critical" />
<ExistentialRule Name="Turn off downloading of print drivers over HTTP" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Turn off downloading of print drivers over HTTP</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Turn off downloading of print drivers over HTTP" Operator="Equals" Severity="Critical" id="DisableWebPnPDownload_2">
<Description>The Turn off downloading of print drivers over HTTP setting is configured to Enabled to prevent print drivers from being downloaded over HTTP.</Description>
<Value ValueA="Enabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{2f11dbfa-2b0f-4b4a-b0eb-19ff44136ed6}" Severity="Important" />
<ExistentialRule Name="Network access: Restrict anonymous access to Named Pipes and Shares" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network access: Restrict anonymous access to Named Pipes and Shares</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Restrict anonymous access to Named Pipes and Shares" Operator="Equals" Severity="Warning" id="{875c50ad-165b-471d-84a4-ad65093e5671}">
<Description>Null sessions are a weakness that can be exploited through shares (including the default shares) on computers in your environment.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{8cbb0aca-e8ea-4417-8a07-7d2293844996}" Severity="Critical" />
<ExistentialRule Name="Turn off the "Publish to Web" task for files and folders" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Turn off the "Publish to Web" task for files and folders</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Turn off the "Publish to Web" task for files and folders" Operator="Equals" Severity="Critical" id="ShellRemovePublishToWeb_2">
<Description>This Setting prevents the exposure of secured content to an unauthenticated Web client computer</Description>
<Value ValueA="Enabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{4a0d9ef7-a7a5-4e6d-a531-3004d37ac748}" Severity="Important" />
<ExistentialRule Name="MSS: (SafeDllSearchMode) Enable Safe DLL search mode (recommended)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (SafeDllSearchMode) Enable Safe DLL search mode (recommended)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (SafeDllSearchMode) Enable Safe DLL search mode (recommended)" Operator="Equals" Severity="Warning" id="{c6cd5bac-c6b1-4de9-90dd-21635603f60d}">
<Description>The DLL search order can be configured to in one of two ways: system path first, and then search the current working folder.Search current working folder first, and then search the folders specified in the system path.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{2bfe6f4b-aee1-47ae-b09e-0e9ecf963804}" Severity="Critical" />
<ExistentialRule Name="Do not adjust default option to 'Install Updates and Shut Down' in Shut Down Windows Dialog box" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Do not adjust default option to 'Install Updates and Shut Down' in Shut Down Windows Dialog box</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Do not adjust default option to 'Install Updates and Shut Down' in Shut Down Windows Dialog box" Operator="Equals" Severity="Critical" id="AUNoUasDefaultPolicy_Mach">
<Description>If you disable this policy setting, the Install Updates and Shut Down option will display in the Shut Down Windows dialog box if updates are available when the user selects the Shut Down option in the Start menu.</Description>
<Value ValueA="Disabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{b95c63bb-db24-4986-a958-b79fb9fb387f}" Severity="Important" />
<ExistentialRule Name="Network access: Shares that can be accessed anonymously" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network access: Shares that can be accessed anonymously</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Shares that can be accessed anonymously" Operator="Equals" Severity="Warning" id="{27cd7a84-00e3-4a99-847d-6b3d574fd3f1}">
<Description>The Network access: Shares that can be accessed anonymously setting is configured to Not Defined for the EC environment. However, ensure that this setting is configured to None for the SSLF environment.</Description>
<Value ValueA="" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{fc9b9d91-7a18-4238-a20c-1bdca54fd6ad}" Severity="Critical" />
<ExistentialRule Name="Turn off Windows Update device driver searching" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Turn off Windows Update device driver searching</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Turn off Windows Update device driver searching" Operator="Equals" Severity="Critical" id="DriverSearchPlaces_DontSearchWindowsUpdate">
<Description>The types of attacks that can exploit a driver download will typically be mitigated by proper enterprise resource and configuration management. This will also help ensure compatibility and stability across the computers in your environment.</Description>
<Value ValueA="Enabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{a4c51a0e-bcb9-4cb1-88fa-a65e42687eb9}" Severity="Important" />
<ExistentialRule Name="Recovery console: Allow floppy copy and access to all drives and all folders" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Recovery console: Allow floppy copy and access to all drives and all folders</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Recovery console: Allow floppy copy and access to all drives and all folders" Operator="Equals" Severity="Warning" id="{5b9c09e6-edf7-41ba-8046-013a2712356e}">
<Description>set the following recovery console environment variables:
• AllowWildCards.
• AllowAllPaths.
• AllowRemovableMedia.
• NoCopyPrompt. </Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{89e0c392-8039-4a0c-824b-445fc668b123}" Severity="Critical" />
<ExistentialRule Name="Allow Remote Shell Access" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Allow Remote Shell Access</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Allow Remote Shell Access" Operator="Equals" Severity="Critical" id="AllowRemoteShellAccess">
<Description>Configures access to remote shells.</Description>
<Value ValueA="Enabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{da991e9c-7f16-4f15-ae08-de862d02f061}" Severity="Critical" />
<ExistentialRule Name="Do not display 'Install Updates and Shut Down' option in Shut Down Windows dialog box" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Do not display 'Install Updates and Shut Down' option in Shut Down Windows dialog box</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Do not display 'Install Updates and Shut Down' option in Shut Down Windows dialog box" Operator="Equals" Severity="Critical" id="AUDontShowUasPolicy">
<Description>If you disable this policy setting, the Install Updates and Shut Down option will display in the Shut Down Windows dialog box if updates are available when the user selects the Shut Down option in the Start menu.</Description>
<Value ValueA="Disabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{0302bf62-c593-4921-a0ce-8f65012ea8bc}" Severity="Critical" />
<ExistentialRule Name="Turn off Autoplay" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Turn off Autoplay</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Turn off Autoplay" Operator="Equals" Severity="Critical" id="Autorun">
<Description>You can enable the Turn off Autoplay setting to disable the Autoplay feature. Autoplay is disabled by default on some removable drive types, such as floppy disk and network drives, but not on CD-ROM drives.</Description>
<Value ValueA="Enabled" />
</SettingRule>
<OptionRule Name="Turn off Autoplay on" Operator="Equals" Severity="Informational" id="Autorun_Box">
<Description>You can enable the Turn off Autoplay setting to disable the Autoplay feature. Autoplay is disabled by default on some removable drive types, such as floppy disk and network drives, but not on CD-ROM drives.</Description>
<Value ValueA="$(string.d97da86453d5448fbe2cbc4ff0b031cc)" />
</OptionRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{2e85f56e-6fb1-4b46-a0e5-4457834dbf81}" Severity="Critical" />
<ExistentialRule Name="Network access: Allow anonymous SID/Name translation" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Network access: Allow anonymous SID/Name translation</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Allow anonymous SID/Name translation" Operator="Equals" Severity="Critical" id="{568bc756-549f-494c-aad0-9568e4f0aa46}">
<Description>Disable this policy setting to prevent unauthenticated users from obtaining user names that are associated with their respective SIDs</Description>
<Value ValueA="False" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{6d2333d9-7ed1-4b8a-a438-472c326e31b9}" Severity="Critical" />
<ExistentialRule Name="Offer Remote Assistance" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Offer Remote Assistance</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Offer Remote Assistance" Operator="Equals" Severity="Critical" id="RA_Unsolicit">
<Description>• Allow helpers to only view the computer
• Allow helpers to remotely control the computer
When you configure this policy setting, you can also specify a list of users or user groups known as "helpers" who may offer remote assistance.</Description>
<Value ValueA="Disabled" />
</SettingRule>
<OptionRule Name="Permit remote control of this computer" Operator="Equals" Severity="Informational" id="RA_Unsolicit_Control_List">
<Description>• Allow helpers to only view the computer
• Allow helpers to remotely control the computer
When you configure this policy setting, you can also specify a list of users or user groups known as "helpers" who may offer remote assistance.</Description>
<Value ValueA="" />
</OptionRule>
<ListOptionRule Name="Helpers" Operator="Equals" Severity="Informational" id="RA_Unsolicit_DACL_Edit">
<Description>• Allow helpers to only view the computer
• Allow helpers to remotely control the computer
When you configure this policy setting, you can also specify a list of users or user groups known as "helpers" who may offer remote assistance.</Description>
<Value ValueA="" />
</ListOptionRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{7636eb85-a48a-4d53-bde7-78ef0f9ab377}" Severity="Critical" />
<ExistentialRule Name="Recovery console: Allow automatic administrative logon" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Recovery console: Allow automatic administrative logon</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Recovery console: Allow automatic administrative logon" Operator="Equals" Severity="Critical" id="{a8e33b43-6a05-41d0-b089-90d6ddf58e72}">
<Description>Microsoft recommends that you disable this policy setting, which will require administrators to enter a password to access the recovery console.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{93993ea8-cf22-4784-a39e-4337190e71ec}" Severity="Important" />
<ExistentialRule Name="System settings: Use Certificate Rules on Windows Executables for Software Restriction Policies" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>System settings: Use Certificate Rules on Windows Executables for Software Restriction Policies</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="System settings: Use Certificate Rules on Windows Executables for Software Restriction Policies" Operator="Equals" Severity="Warning" id="{335a7e16-246b-4441-9376-de939fc83ff6}">
<Description>It enables or disables certificate rules. Creates certificate rule that will allow or disallow the execution of Authenticode®-signed software, based on the digital certificate that is associated with the software. </Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{49302c49-5309-4506-b042-c99447402034}" Severity="Optional" />
<ExistentialRule Name="Devices: Restrict CD-ROM access to locally logged-on user only" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Devices: Restrict CD-ROM access to locally logged-on user only</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Devices: Restrict CD-ROM access to locally logged-on user only" Operator="Equals" Severity="Informational" id="{10b67eb1-9a83-44b2-a601-6923a4c4d997}">
<Description>If you enable this policy setting, only the interactively logged-on user is allowed to access removable CD-ROM media. When this policy setting is enabled and no one is logged on interactively, the CD-ROM is accessible over the network.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{f201f6ca-cafa-455d-bc30-62354cad5714}" Severity="Critical" />
<ExistentialRule Name="Specify intranet Microsoft update service location" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Specify intranet Microsoft update service location</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Specify intranet Microsoft update service location" Operator="Equals" Severity="Critical" id="CorpWuURL">
<Description>This policy setting allows you to specify an intranet server to host updates from the Microsoft Update Web site. </Description>
<Value ValueA="Not Configured" />
</SettingRule>
<OptionRule Name="Set the intranet statistics server" Operator="Equals" Severity="Informational" id="CorpWUStatusURL_Name">
<Description>This policy setting allows you to specify an intranet server to host updates from the Microsoft Update Web site.</Description>
<Value ValueA="" />
</OptionRule>
<OptionRule Name="Set the intranet update service for detecting updates" Operator="Equals" Severity="Informational" id="CorpWUURL_Name">
<Description>This policy setting allows you to specify an intranet server to host updates from the Microsoft Update Web site.</Description>
<Value ValueA="" />
</OptionRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{dd6bf205-5777-4c03-89fb-7a825a2955ab}" Severity="Critical" />
<ExistentialRule Name="Turn off Internet download for Web publishing and online ordering wizards" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Turn off Internet download for Web publishing and online ordering wizards</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Turn off Internet download for Web publishing and online ordering wizards" Operator="Equals" Severity="Critical" id="ShellPreventWPWDownload_2">
<Description> If this policy setting is enabled, Windows is prevented from downloading providers; only the service providers cached in the local registry will display. Enabled to minimize the attack surface of client computers.</Description>
<Value ValueA="Enabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{e0c28680-3712-4177-914c-d0ce0efa226b}" Severity="Important" />
<ExistentialRule Name="Network access: Remotely accessible registry paths and sub-paths" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network access: Remotely accessible registry paths and sub-paths</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Remotely accessible registry paths and sub-paths" Operator="Equals" Severity="Warning" id="{790e6cd4-8b28-4952-b95d-3250a88754cb}">
<Description>See the applicable (Vista, Win2K3, or XP) security guide for the detailed description of this rule.</Description>
<Value ValueA="System\CurrentControlSet\Control\Print\Printers
System\CurrentControlSet\Services\Eventlog
Software\Microsoft\OLAP Server
Software\Microsoft\Windows NT\CurrentVersion\Print
Software\Microsoft\Windows NT\CurrentVersion\Windows
System\CurrentControlSet\Control\ContentIndex
System\CurrentControlSet\Control\Terminal Server
System\CurrentControlSet\Control\Terminal Server\UserConfig
System\CurrentControlSet\Control\Terminal Server\DefaultUserConfiguration
Software\Microsoft\Windows NT\CurrentVersion\Perflib
System\CurrentControlSet\Services\SysmonLog
" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{fc736f51-ff9d-48ed-8d0c-c510112b7589}" Severity="Critical" />
<ExistentialRule Name="Network access: Do not allow anonymous enumeration of SAM accounts and shares" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Network access: Do not allow anonymous enumeration of SAM accounts and shares</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Do not allow anonymous enumeration of SAM accounts and shares" Operator="Equals" Severity="Critical" id="{e0d0bb2c-1e9e-4fec-990f-61d8e111155f}">
<Description>If you enable this policy setting, anonymous users will not be able to enumerate domain account user names and network share names on the workstations in your environment.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{e17e8f70-2ed6-4cd9-98f5-a402eb36a774}" Severity="Optional" />
<ExistentialRule Name="Devices: Allow undock without having to Log on" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Devices: Allow undock without having to Log on</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Devices: Allow undock without having to Log on" Operator="Equals" Severity="Informational" id="{e1148c56-88ab-44ba-9024-b239d430687a}">
<Description>Enable to eliminate a Log on requirement and allow use of an external hardware eject button to undock the computer. Disabled, a user must log on and have been assigned the Remove computer from docking station user right to undock the computer.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{10130ac4-30f6-40f0-b85e-c078a7ccbcf9}" Severity="Optional" />
<ExistentialRule Name="MSS: (NtfsDisable8dot3NameCreation) Enable the computer to stop generating 8.3 style filenames (recommended)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (NtfsDisable8dot3NameCreation) Enable the computer to stop generating 8.3 style filenames (recommended)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (NtfsDisable8dot3NameCreation) Enable the computer to stop generating 8.3 style filenames (recommended)" Operator="Equals" Severity="Informational" id="{132e1b76-6a75-4d53-9c1f-ecead7636975}">
<Description>Windows Server 2003 supports 8.3 file name formats for backward compatibility with16-bit applications. The 8.3 file name convention is a naming format that allows file names up to eight characters long.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{5c7a5f8a-467c-407a-a240-385c40907929}" Severity="Important" />
<ExistentialRule Name="Network access: Remotely accessible registry paths" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Network access: Remotely accessible registry paths</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Remotely accessible registry paths" Operator="Equals" Severity="Warning" id="{2305ec27-4c51-4a76-a3a4-ef36a14186ff}">
<Description>System\CurrentControlSet\Control\ProductOptions
• System\CurrentControlSet\Control\Server Applications
• Software\Microsoft\Windows NT\CurrentVersion</Description>
<Value ValueA="System\CurrentControlSet\Control\ProductOptions
System\CurrentControlSet\Control\Server Applications
Software\Microsoft\Windows NT\CurrentVersion
" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{68bf7f2a-0937-4d22-a966-730c358209e4}" Severity="Critical" />
<ExistentialRule Name="Deny log on as a service" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Deny log on as a service</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Deny log on as a service" Operator="Equals" Severity="Critical" id="{1dd6a7b5-60ba-4240-aa0f-a788379d7966}">
<Description>By default, there are no accounts denied logon as a service.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{1a4f18a5-e3d9-4d4c-bebf-32351b0d6d67}" Severity="Important" />
<ExistentialRule Name="Load and unload device drivers" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Load and unload device drivers</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Load and unload device drivers" Operator="Equals" Severity="Warning" id="{6bd32577-3f1f-4a00-8c12-f794e5308a25}">
<Description>An attacker could potentially use this capability to install malicious code that appears to be a device driver. </Description>
<Value ValueA="Administrators" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{54e4bdd4-cb65-4ab3-a011-07ce073873c8}" Severity="Important" />
<ExistentialRule Name="Log on as a batch job" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Log on as a batch job</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Log on as a batch job" Operator="Equals" Severity="Warning" id="{c9fc3945-ccbf-4aea-ae69-12943649294d}">
<Description>Because the task scheduler is often used for administrative purposes, it may be needed in the EC environment. Its use should be restricted in the SSLF environment to prevent misuse of system resources .</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{0183e5be-9bb3-41a0-b7d6-45611f6b1aa1}" Severity="Important" />
<ExistentialRule Name="Impersonate a client after authentication" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Impersonate a client after authentication</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Impersonate a client after authentication" Operator="Equals" Severity="Warning" id="{c09dd67f-e925-4b5b-8754-52281526c6e1}">
<Description>An attacker with the Impersonate a client after authentication user right could create a service, trick a client to make them connect to the service, and then impersonate that client to elevate the attacker's level of access to that of the client.</Description>
<Value ValueA="Administrators, SERVICE, Local Service, Network Service" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{8bf58466-78a7-4a7d-a15d-55393ef8f619}" Severity="Important" />
<ExistentialRule Name="Change the system time" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Change the system time</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Change the system time" Operator="Equals" Severity="Warning" id="{71fa117a-5955-431a-bb14-a7f90fad91b6}">
<Description>Users who are assigned this user right can affect the appearance of event logs. When a computer’s time setting is changed, logged events reflect the new time, not the actual time that the events occurred.</Description>
<Value ValueA="LOCAL SERVICE, Administrators" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{39d24ad9-3577-4274-b91a-6a966afe7bce}" Severity="Important" />
<ExistentialRule Name="Replace a process level token" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Replace a process level token</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Replace a process level token" Operator="Equals" Severity="Warning" id="{2638ae8a-c185-4da7-a1b2-14e7faf0ae06}">
<Description>The Replace a process level token setting is configured to the default values of Local Service and Network Service </Description>
<Value ValueA="Local Service, Network Service" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{8306d62f-72db-4bee-93e2-bc55ea5c5d40}" Severity="Critical" />
<ExistentialRule Name="Generate security audits" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Generate security audits</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Generate security audits" Operator="Equals" Severity="Critical" id="{915b0922-0701-4e85-b902-f587a893ab55}">
<Description>An attacker could use this capability to create a large number of audited events, which would make it more difficult for a system administrator to locate any illicit activity.</Description>
<Value ValueA="Local Service, Network Service" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{3d083179-8db5-47b4-bdd0-d630bdb0e96c}" Severity="Important" />
<ExistentialRule Name="Adjust memory quotas for a process" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Adjust memory quotas for a process</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Adjust memory quotas for a process" Operator="Equals" Severity="Warning" id="{d7c36b22-29a3-4ac5-b2aa-e2e6ea8b6b9c}">
<Description>The ability to adjust memory quotas is useful for system tuning, but it can be abused. In the wrong hands, it could be used to launch a denial of service (DoS) attack.</Description>
<Value ValueA="Administrators, Local Service, Network Service" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{b2e98fde-ef4d-4b49-adee-8299ce77910b}" Severity="Important" />
<ExistentialRule Name="Access Credential Manager as a trusted caller" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Access Credential Manager as a trusted caller</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Access Credential Manager as a trusted caller" Operator="Equals" Severity="Warning" id="{202d847c-05a9-4955-be71-5a88aaabb813}">
<Description>This security setting is used by Credential Manager during Backup and Restore.</Description>
<Value ValueA="No One" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{6a793d6e-87fa-4546-be71-aec4c74e2674}" Severity="Important" />
<ExistentialRule Name="Profile single process" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Profile single process</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Profile single process" Operator="Equals" Severity="Warning" id="{a6d81eb1-93be-4d0f-8515-15af239e2aab}">
<Description>Restricting the Profile single process user right prevents intruders from gaining additional information that could be used to mount an attack on the system.
</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{0bbbb061-2b02-448e-8b5c-7db64bacdb16}" Severity="Critical" />
<ExistentialRule Name="Manage auditing and security log" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Manage auditing and security log</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Manage auditing and security log" Operator="Equals" Severity="Critical" id="{3f8bdf0e-40ed-44cd-83d9-5dfdfb580bdf}">
<Description>Because this capability represents a relatively small threat, the Manage auditing and security log setting enforces the default value of the Administrators group </Description>
<Value ValueA="Administrators" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{65a028c4-e391-45b5-87ca-27bfd1b78c03}" Severity="Critical" />
<ExistentialRule Name="Deny access to this computer from the network" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Deny access to this computer from the network</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Deny access to this computer from the network" Operator="Equals" Severity="Critical" id="{85128f72-9be2-4295-890b-656457887c5e}">
<Description>In an SSLF environment, there should be no need for remote users to access data on a computer. Instead, file sharing should be accomplished through the use of network servers.</Description>
<Value ValueA="Guests" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{7d8fa5d5-b0e9-479c-9807-4d095b1fd44b}" Severity="Critical" />
<ExistentialRule Name="Access this computer from the network" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Access this computer from the network</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Access this computer from the network" Operator="Equals" Severity="Critical" id="{82ea0153-85ed-4fe7-be71-b2dd9988a832}">
<Description>Required by various network protocols that include Server Message Block (SMB)–based protocols, NetBIOS, Common Internet File System (CIFS), and Component Object Model Plus (COM+).</Description>
<Value ValueA="Users, Administrators" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{1649e4fa-0cc0-4ef1-81e7-498c6a58bb79}" Severity="Important" />
<ExistentialRule Name="Allow log on through Remote Desktop Services" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Allow log on through Remote Desktop Services</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Allow log on through Remote Desktop Services" Operator="Equals" Severity="Warning" id="{a2854958-7e0c-428e-93a6-5271c536576d}">
<Description>Remote Assistance as part of its help desk strategy, create a group and assign it this user right through Group Policy. Do not use Remote Assistance, assign this user right only to the Administrators group or use the restricted groups feature. </Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{58789aea-c3a7-40c2-bbce-a486b411813a}" Severity="Critical" />
<ExistentialRule Name="Allow log on locally" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Allow log on locally</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Allow log on locally" Operator="Equals" Severity="Critical" id="{df99171b-37e7-41e1-a4b9-609dca306986}">
<Description>Although this account is disabled by default, Microsoft recommends that you enable this setting through Group Policy. However, this user right should generally be restricted to the Administrators and Users groups.</Description>
<Value ValueA="Administrators, Users" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{33292c81-06d4-4a1f-b2c2-eeedd154bccc}" Severity="Critical" />
<ExistentialRule Name="Deny log on as a batch job" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Deny log on as a batch job</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Deny log on as a batch job" Operator="Equals" Severity="Critical" id="{3e1eb11f-1617-4570-9f01-7ab8496032b3}">
<Description>The Deny log on as a batch job user right overrides the Log on as a batch job user right, which could be used to allow accounts to schedule jobs that consume excessive system resources. </Description>
<Value ValueA="Guests" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{f13a5f62-361c-4c17-bc71-74decdb11119}" Severity="Critical" />
<ExistentialRule Name="Enable computer and user accounts to be trusted for delegation" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Enable computer and user accounts to be trusted for delegation</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Enable computer and user accounts to be trusted for delegation" Operator="Equals" Severity="Critical" id="{bebb9f08-a88b-439d-a1b4-c652803a024c}">
<Description>Abuse of this privilege could allow unauthorized users to impersonate other users on the network.</Description>
<Value ValueA="No One" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{2be27f71-30e4-41fe-8fe9-a243a1ce6d25}" Severity="Important" />
<ExistentialRule Name="Modify firmware environment values" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Modify firmware environment values</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Modify firmware environment values" Operator="Equals" Severity="Warning" id="{7516d549-a030-4df6-86df-5cd744847960}">
<Description>Modification of these values and could lead to a hardware failure that would result in a denial of service condition. Because this capability represents a relatively small threat, this setting enforces the default value of the Administrators group</Description>
<Value ValueA="Administrators" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{30a68dcc-7f6b-4d71-a668-611a6c873c2e}" Severity="Important" />
<ExistentialRule Name="Modify an object label" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Modify an object label</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Modify an object label" Operator="Equals" Severity="Warning" id="{af4533c1-b637-4778-b84e-56b930d0755a}">
<Description>This privilege determines which user accounts can modify the integrity label of objects, such as files, registry keys, or processes owned by other users.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{6e05588d-1e43-4607-bad8-6ab4a0c433c8}" Severity="Important" />
<ExistentialRule Name="Devices: Prevent users from installing printer drivers" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Devices: Prevent users from installing printer drivers</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Devices: Prevent users from installing printer drivers" Operator="Equals" Severity="Warning" id="{96c54bd0-dddd-4787-abc8-e6f2ab74eae0}">
<Description>It is feasible for a attacker to disguise a Trojan horse program as a printer driver. The program may appear to users as if they must use it to print, but such a program could unleash malicious code on your computer network. T</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{0cd825b9-23c9-4c5a-830f-51a13a3b7dd4}" Severity="Important" />
<ExistentialRule Name="Restore files and directories" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Restore files and directories</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Restore files and directories" Operator="Equals" Severity="Warning" id="{d240e37d-156e-49d6-9773-c799bae4860c}">
<Description> This user right also determines which users can set valid security principals as object owners; it is similar to the Back up files and directories user right.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{1b5601cc-1320-487e-b983-60235aaf9883}" Severity="Critical" />
<ExistentialRule Name="Debug programs" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Debug programs</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Debug programs" Operator="Equals" Severity="Critical" id="{eeba2492-9034-4dbc-a942-a5082c0b55dc}">
<Description>This policy setting determines which user accounts will have the right to attach a debugger to any process or to the kernel, which provides complete access to sensitive and critical operating system components. </Description>
<Value ValueA="Administrators" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{6a674d75-0d07-4f37-85f8-113d1122437d}" Severity="Important" />
<ExistentialRule Name="Change the time zone" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Change the time zone</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Change the time zone" Operator="Equals" Severity="Warning" id="{355e7be7-b549-4ed8-93af-90bf4d1e645c}">
<Description>This ability holds no great danger for the computer and may be useful for mobile workers.</Description>
<Value ValueA="LOCAL SERVICE, Administrators, Users" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{6e71fdb8-46c0-485d-b542-26881d3ea428}" Severity="Important" />
<ExistentialRule Name="Increase scheduling priority" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Increase scheduling priority</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Increase scheduling priority" Operator="Equals" Severity="Warning" id="{4ff88c5b-1242-4b57-847b-7b1e201e6481}">
<Description>An attacker could use this capability to increase the priority of a process to real-time and create a denial of service condition for a computer.</Description>
<Value ValueA="Administrators" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{6abbdad3-1a59-498d-9ae2-e8e5b14a43f5}" Severity="Important" />
<ExistentialRule Name="Create global objects" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Create global objects</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Create global objects" Operator="Equals" Severity="Warning" id="{90faa840-1f4f-4fdb-a5c5-6babc1508451}">
<Description>Users who can create global objects could affect processes that run under other users' sessions. This capability could lead to a variety of problems, such as application failure or data corruption.</Description>
<Value ValueA="Administrators, SERVICE, LOCAL SERVICE, NETWORK SERVICE" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{e78277dc-9342-4ede-801c-87d659a3a883}" Severity="Optional" />
<ExistentialRule Name="Allow users to connect remotely using Remote Desktop Services" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Allow users to connect remotely using Remote Desktop Services</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Allow users to connect remotely using Remote Desktop Services" Operator="Equals" Severity="Informational" id="TS_DISABLE_CONNECTIONS">
<Description>Creates a potential breach of authentication. Use with caution.</Description>
<Value ValueA="Not Configured" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{12d1857c-2e5e-4cfb-ae3b-2cff254c527b}" Severity="Critical" />
<ExistentialRule Name="Network access: Let Everyone permissions apply to anonymous users" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Network access: Let Everyone permissions apply to anonymous users</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Network access: Let Everyone permissions apply to anonymous users" Operator="Equals" Severity="Critical" id="{eec90afe-20d0-4d87-9e6f-5c1bc837ae0a}">
<Description>Enable setting, anonymous users allowed to enumerate the names of domain accounts and network shares. Unauthorized user could anonymously list account names and shared resources to guess passwords or perform social engineering attacks.</Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{0a271bb9-213f-40c3-bc5c-30a8fdcb490c}" Severity="Critical" />
<ExistentialRule Name="Deny log on locally" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Deny log on locally</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Deny log on locally" Operator="Equals" Severity="Critical" id="{4f19a525-e8fa-4270-af82-17ab74ebf0a8}">
<Description>This policy setting determines whether users can log on directly at the computer's keyboard.</Description>
<Value ValueA="Guests" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{6ec1ab3e-5abc-44b9-997d-101481b01d44}" Severity="Critical" />
<ExistentialRule Name="Force shutdown from a remote system" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Force shutdown from a remote system</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Force shutdown from a remote system" Operator="Equals" Severity="Critical" id="{94225969-3839-4cc0-84dd-97782e1287d2}">
<Description>Anyone who has been assigned this user right can cause a denial of service (DoS) condition, which would make the computer unavailable to service user requests. </Description>
<Value ValueA="Administrators" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{468483f1-f6a9-403a-9ff1-25b301aa927e}" Severity="Critical" />
<ExistentialRule Name="Act as part of the operating system" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Act as part of the operating system</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Act as part of the operating system" Operator="Equals" Severity="Critical" id="{70f992cf-7901-48aa-8069-3767273ea6ca}">
<Description>Can allow the injection of malicious code. Use with caution.</Description>
<Value ValueA="No One" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{71553705-afe1-4c91-85a9-503547ef79df}" Severity="Important" />
<ExistentialRule Name="Create permanent shared objects" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Create permanent shared objects</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Create permanent shared objects" Operator="Equals" Severity="Warning" id="{015f3131-5d13-4397-b006-99096bc29371}">
<Description>This user right is useful to kernel-mode components that extend the object namespace. However, components that run in kernel mode have this user right inherently, Therefore, it is typically not necessary to specifically assign this user right.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{04658362-23eb-402c-9fd5-a750eebd4a7b}" Severity="Important" />
<ExistentialRule Name="Create symbolic links" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Create symbolic links</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Create symbolic links" Operator="Equals" Severity="Warning" id="{8cbb4073-da8a-42c0-8f7d-e67eb0aedfec}">
<Description>In Vista, existing NTFS file system objects, can be accessed by referring to a new kind of file system object called a symbolic link. Symbolic links can potentially expose security vulnerabilities in applications that are not designed to use them.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{e260bd2f-9e47-4a50-991b-515423b705ca}" Severity="Critical" />
<ExistentialRule Name="Create a pagefile" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Create a pagefile</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Create a pagefile" Operator="Equals" Severity="Critical" id="{0bca4150-4e11-4246-966c-4ff1f15eabc2}">
<Description>By making the pagefile extremely large or extremely small, an attacker could easily affect the performance of a compromised computer.</Description>
<Value ValueA="Administrators" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{60ac480b-8940-4d98-a327-553ffe0dc3cb}" Severity="Optional" />
<ExistentialRule Name="Deny log on through Remote Desktop Services" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Deny log on through Remote Desktop Services</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Deny log on through Remote Desktop Services" Operator="Equals" Severity="Informational" id="{0731f637-f0ae-4700-8391-ab43a86ce705}">
<Description>After the baseline member server is joined to a domain environment, there is no need to use local accounts to access the server from the network. Domain accounts can access the server for administration and end-user processing.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{3c0e1a7d-4a77-45f0-86e9-504829d375c5}" Severity="Important" />
<ExistentialRule Name="Back up files and directories" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Back up files and directories</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Back up files and directories" Operator="Equals" Severity="Warning" id="{a7c2ce3c-5718-4cc1-9934-e2a0b3a2e276}">
<Description>This user right is enabled only when an application (such as NTBACKUP) attempts to access a file or directory through the NTFS file system backup application programming interface (API). Otherwise, the assigned file and directory permissions apply.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{85081419-d966-4da0-99c8-a309788566cf}" Severity="Critical" />
<ExistentialRule Name="Log on as a service" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Log on as a service</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Log on as a service" Operator="Equals" Severity="Critical" id="{1cd82150-d98e-4170-8b8a-83e949efb499}">
<Description>On Windows Vista–based computers, no users or groups have this privilege by default. This setting should be carefully configured since many applications use services to operate.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{f59f14f0-7ab4-46a1-840a-67ba5e41f04f}" Severity="Important" />
<ExistentialRule Name="Lock pages in memory" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Lock pages in memory</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Lock pages in memory" Operator="Equals" Severity="Warning" id="{065252d6-079d-4d19-879d-fa397e495aa4}">
<Description>If this user right is assigned, significant degradation of system performance can occur.</Description>
<Value ValueA="No One" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{26a3389d-c92a-43c3-9ddc-e7cfa913f1f2}" Severity="Important" />
<ExistentialRule Name="Take ownership of files or other objects" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Take ownership of files or other objects</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Take ownership of files or other objects" Operator="Equals" Severity="Warning" id="{ef022bf8-de86-4f93-aa35-e4392e45fa1e}">
<Description>This setting is configured to the default value of the Administrators group.</Description>
<Value ValueA="Administrators" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{b608cca7-a88d-4e92-8c56-00c9c07af926}" Severity="Important" />
<ExistentialRule Name="Profile system performance" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Profile system performance</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Profile system performance" Operator="Equals" Severity="Warning" id="{e1fb7f61-adac-4737-b6ca-0b6aec44145f}">
<Description>The Profile system performance setting enforces the default of the Administrators group for both of the environments that are discussed in this guide.</Description>
<Value ValueA="NT SERVICE\WdiServiceHost,Administrators" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{80d8a16f-212f-4ec5-8a57-0769ec3d0d4c}" Severity="Critical" />
<ExistentialRule Name="Perform Volume Maintenance Tasks" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Perform Volume Maintenance Tasks</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Perform Volume Maintenance Tasks" Operator="Equals" Severity="Critical" id="{fcf7710e-3ca6-445d-9113-d1d4a08389c3}">
<Description>The Perform volume maintenance tasks setting enforces the default value of the Administrators group for both of the environments that are discussed in this guide.
</Description>
<Value ValueA="Administrators" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{887c32a5-df92-4238-b883-a945251768f4}" Severity="Important" />
<ExistentialRule Name="Increase a process working set" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Increase a process working set</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Increase a process working set" Operator="Equals" Severity="Warning" id="{6cba1e15-9746-45ac-9c8f-5670671c9669}">
<Description>It would be possible for malicious code to increase the process working set to a level that could severely degrade system performance and potentially cause a denial of service. </Description>
<Value ValueA="Administrators, Local Service" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{d3820f0b-ba8d-45ab-9c9c-5137a91356a7}" Severity="Optional" />
<ExistentialRule Name="Remove computer from docking station" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Remove computer from docking station</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Remove computer from docking station" Operator="Equals" Severity="Informational" id="{13962cc1-a15a-49a6-9881-ce052b57b508}">
<Description>The Remove computer from docking station setting is configured to the Administrators and Users groups for both of the environments discussed in this guide.</Description>
<Value ValueA="Administrators, Users" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{460942f4-ec7f-4eee-8a99-d0cc46ec2a12}" Severity="Critical" />
<ExistentialRule Name="Bypass traverse checking" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Bypass traverse checking</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Bypass traverse checking" Operator="Equals" Severity="Critical" id="{f257bd70-d858-4364-b7b1-c00b9279bd59}">
<Description>This user right does not allow users to list the contents of a folder, but only allows them to traverse directories.</Description>
<Value ValueA="Users, NETWORK SERVICE, LOCAL SERVICE, Administrators" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{42ca1c76-4099-4347-b219-de35dcf0d889}" Severity="Important" />
<ExistentialRule Name="Create a token object" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Create a token object</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Create a token object" Operator="Equals" Severity="Warning" id="{4ef1cd24-6435-47cd-8563-b2780e74fa28}">
<Description>In environments in which security is a high priority, this user right should not be assigned to any users. Any processes that require this capability should use the Local System account, which is assigned this user right by default.</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{d4ba28a6-fd3a-4ac3-a99c-19e501136098}" Severity="Important" />
<ExistentialRule Name="Shut down the system" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Shut down the system</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Shut down the system" Operator="Equals" Severity="Warning" id="{f247176e-59c7-48b0-87c6-66b2465d787b}">
<Description>Misuse of this user right can result in a denial of service condition. The Shut down the system setting is configured to the Administrators and Users groups.</Description>
<Value ValueA="Administrators, Users" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{7e9c0250-1901-4b7c-8892-cb595774f5b2}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Policy Change: Authorization Policy Change" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Audit Policy: Policy Change: Authorization Policy Change</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Policy Change: Authorization Policy Change" Operator="Equals" Severity="Critical" id="{7154cb57-7754-4bc7-a9f5-537c40c2676e}">
<Description>The recommended settings would let you see any account privileges that an attacker attempts to elevate—for example, by adding the Debug programs privilege or the Back up files and directories privilege.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{71c2a926-3e4c-4ff1-bf3e-f8ad9147efa1}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Account Management: Application Group Management" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Account Management: Application Group Management</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Account Management: Application Group Management" Operator="Equals" Severity="Critical" id="{2de8537a-6ca1-4c8a-a333-67b319d3dd32}">
<Description> If you enable this Audit policy setting, administrators can track events to detect malicious, accidental, and authorized creation of user and group accounts.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{1fe39da3-5a53-4748-9315-ac1fc3264495}" Severity="Critical" />
<ExistentialRule Name="Advanced Audit Policy: Object Access: Audit Detailed File Share" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Advanced Audit Policy: Object Access: Audit Detailed File Share</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Advanced Audit Policy: Object Access: Audit Detailed File Share" Operator="Equals" Severity="Critical" id="{23e9ba4c-089c-470e-b4fb-2079ab9a5c7f}">
<Description />
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{da9beb22-41fc-4ddc-b25f-5714a26a7868}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Account Logon: Kerberos Service Ticket Operations" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Account Logon: Kerberos Service Ticket Operations</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Account Logon: Kerberos Service Ticket Operations" Operator="Equals" Severity="Critical" id="{870db88c-2a97-4ffc-8eec-384769b66892}">
<Description>The Account Logon audit category generates events for credential validation.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{0f91e526-0982-4396-b55c-c30f8e42af96}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Detailed Tracking: DPAPI Activity" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Detailed Tracking: DPAPI Activity</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Detailed Tracking: DPAPI Activity" Operator="Equals" Severity="Critical" id="{cc5fd9a1-a01b-4ce1-acc0-78326df19684}">
<Description> Enabling Audit process tracking will generate a large number of events, so it is typically set to No Auditing. Setting can provide a benefit during an incident response.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{36bb6358-988e-4bc1-b9fd-2f45391f49cf}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Detailed Tracking: Process Termination" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Detailed Tracking: Process Termination</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Detailed Tracking: Process Termination" Operator="Equals" Severity="Critical" id="{58887805-cbc9-45f6-8763-983d834d0f9f}">
<Description> Enabling Audit process tracking will generate a large number of events, so it is typically set to No Auditing. Setting can provide a benefit during an incident response.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{0fb270b1-ae2b-4106-9d85-45d95edc98bf}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: System: Other System Events" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: System: Other System Events</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: System: Other System Events" Operator="Equals" Severity="Critical" id="{b6eb40c5-ab6e-4a84-9889-673b520cf1c7}">
<Description>System events include starting or shutting down computers in your environment, full event logs, or other security-related events that affect the entire system. This one looks at the Other System Events category of events.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{1c218a4c-9d7e-40ab-8c3a-1d82ec931d15}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Object Access: Certification Services" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Object Access: Certification Services</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Object Access: Certification Services" Operator="Equals" Severity="Critical" id="{ceb584ec-5985-437b-8e74-9f6f4c10bd2c}">
<Description />
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{37419dd7-35a5-474d-bbb4-ce55427a8298}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: DS Access: Directory Service Replication" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: DS Access: Directory Service Replication</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: DS Access: Directory Service Replication" Operator="Equals" Severity="Critical" id="{9f5c7741-f0cc-4744-88e2-3e92f26f1d4e}">
<Description>For this reason, the DS Access audit category and all related subcategories are configured to No Auditing for both environments. See the appropriate windows security guide for more information.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{38d832a9-d3ea-4230-ba72-26af8c02a02a}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Logon-Logoff: Logon" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Logon-Logoff: Logon</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Logon-Logoff: Logon" Operator="Equals" Severity="Critical" id="{c7511b1b-9972-42ef-8915-ccfc913f9187}">
<Description>For interactive logons, events occur on logged on to machine. Network logon to access a share, events generated on machine that hosts the accessed resource. Set to No auditing, it is difficult determine which user has accessed organization computers.</Description>
<Value ValueA="Success and Failure" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{09f5619f-e1a3-4a6b-aa39-9c8a54a07b5d}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: System: Security State Change" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: System: Security State Change</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: System: Security State Change" Operator="Equals" Severity="Critical" id="{bdfac2dc-9f1c-49c1-936e-18a70cff56b2}">
<Description>Either Success and or Failure</Description>
<Value ValueA="Success and Failure" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{49e0da75-e4ed-4d8b-a98e-5fcd69af95e4}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Logon-Logoff: Network Policy Server" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Logon-Logoff: Network Policy Server</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Logon-Logoff: Network Policy Server" Operator="Equals" Severity="Critical" id="{46c35bad-360b-4f91-8021-0788d045fbba}">
<Description>This audit category generates events that record the creation and destruction of logon sessions.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{e7edf862-c094-4113-8ae7-b89911c06850}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Logon-Logoff: IPsec Extended Mode" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Logon-Logoff: IPsec Extended Mode</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Logon-Logoff: IPsec Extended Mode" Operator="Equals" Severity="Critical" id="{195f1ded-7970-45aa-ac11-77afc3d15349}">
<Description>For interactive logons, events occur on logged on to machine. Network logon to access a share, events generated on machine that hosts the accessed resource. Set to No auditing, it is difficult determine which user has accessed organization computers.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{d33970c6-6b45-41de-9fa1-c4e62329bbce}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Logon-Logoff: Special Logon" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Logon-Logoff: Special Logon</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Logon-Logoff: Special Logon" Operator="Equals" Severity="Critical" id="{1ed703b4-cf65-437d-b29a-96b6b7cd38bf}">
<Description>For interactive logons, events occur on logged on to machine. Network logon to access a share, events generated on machine that hosts the accessed resource. Set to No auditing, it is difficult determine which user has accessed organization computers.</Description>
<Value ValueA="Success" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{e62dadb5-aaf6-44fc-bb86-b929491ac651}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: System: System Integrity" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: System: System Integrity</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: System: System Integrity" Operator="Equals" Severity="Critical" id="{ef5ad95b-d34d-48f9-bea9-ee679651a6ad}">
<Description>System events include starting or shutting down computers in your environment, full event logs, or other security-related events that affect the entire system. This policy looks at System Integrity settings.</Description>
<Value ValueA="Success and Failure" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{db5ecbea-b6cb-4a1c-8757-f4593e9a4bb6}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Account Logon: Kerberos Authentication Service" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Account Logon: Kerberos Authentication Service</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Account Logon: Kerberos Authentication Service" Operator="Equals" Severity="Critical" id="{57becd16-b86e-4848-8aca-9095b34cef41}">
<Description>The Account Logon audit category generates events for credential validation.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{4f49cb93-d48f-4a74-a1b6-df789d0c147c}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Account Management: Security Group Management" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Account Management: Security Group Management</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Account Management: Security Group Management" Operator="Equals" Severity="Critical" id="{655c9086-1b1d-4099-a8ef-d70f368026a1}">
<Description>If you enable this Audit policy setting, administrators can track events to detect malicious, accidental, and authorized creation of user and group accounts in the Security Group Management subcategory.</Description>
<Value ValueA="Success and Failure" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{89d4f42a-8f08-49e2-8566-8903564a4a73}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: System: IPsec Driver" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: System: IPsec Driver</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: System: IPsec Driver" Operator="Equals" Severity="Critical" id="{faa163fe-6577-45f5-bc1c-86d5222df064}">
<Description>System events include starting or shutting down computers in your environment, full event logs, or other security-related events that affect the entire system. This one looks at the IPsec Driver</Description>
<Value ValueA="Success and Failure" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{6b9ad7b8-5118-415d-9265-5001b3a56c2a}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Account Logon: Other Account Logon Events" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Account Logon: Other Account Logon Events</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Account Logon: Other Account Logon Events" Operator="Equals" Severity="Critical" id="{cb7e716d-0b2b-4fbe-abc9-4c9756d1ee7a}">
<Description>Set to No Auditing for no auditing. </Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{e87ca912-7d3b-4065-863f-306ee183334d}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Object Access: SAM" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Object Access: SAM</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Object Access: SAM" Operator="Equals" Severity="Critical" id="{41aed31a-6b83-42ed-bc28-e4b37a266a10}">
<Description />
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{6a94cbec-a238-4ae4-9beb-f32d393c2d15}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Object Access: Kernel Object" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Object Access: Kernel Object</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Object Access: Kernel Object" Operator="Equals" Severity="Critical" id="{586da9b8-787b-4492-87a2-c0e6777a378f}">
<Description />
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{ad3db651-0d72-4f1f-9869-227fdf5eb177}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Logon-Logoff: Account Lockout" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Logon-Logoff: Account Lockout</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Logon-Logoff: Account Lockout" Operator="Equals" Severity="Critical" id="{b3c35695-d7e6-4dbc-9f4b-bd375680ab49}">
<Description>For interactive logons, events occur on logged on to machine. Network logon to access a share, events generated on machine that hosts the accessed resource. Set to No auditing, it is difficult determine which user has accessed organization computers.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{55b55248-b303-4316-afcb-4cb4fba97222}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Logon-Logoff: Other Logon/Logoff Events" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Logon-Logoff: Other Logon/Logoff Events</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Logon-Logoff: Other Logon/Logoff Events" Operator="Equals" Severity="Critical" id="{c8770924-e928-46d2-80e8-d5556dc57016}">
<Description>For interactive logons, the generation of these events occurs on the computer that is logged on to. If a network logon takes place to access a share, these events generate on the computer that hosts the accessed resource.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{0d81866d-0bd6-4df0-8c2f-86751536b022}" Severity="Critical" />
<ExistentialRule Name="Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" Operator="GreaterThan" Severity="Critical" ValueA="0">
<Description>Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" Operator="Equals" Severity="Critical" id="{846d59fd-abf3-4fe4-9d0d-f8a81f36d4e3}">
<Description>The Audit Policy settings available in Windows Server 2003 Active Directory do not yet contain settings for managing the new auditing subcategories. This allows those subcategories to be managed.</Description>
<Value ValueA="1" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{c11bf343-b498-4209-b0c6-e28de6440be0}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Account Management: Distribution Group Management" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Account Management: Distribution Group Management</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Account Management: Distribution Group Management" Operator="Equals" Severity="Critical" id="{2d807489-eabd-438b-b631-e43d2ccd3394}">
<Description>If you enable this Audit policy setting, administrators can track events to detect malicious, accidental, and authorized creation of user and group accounts in the Distribution Group Management subcategory.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{bf2194fc-6a41-469f-8952-4ffa8b6b52eb}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Account Logon: Credential Validation" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Account Logon: Credential Validation</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Account Logon: Credential Validation" Operator="Equals" Severity="Critical" id="{8583a2ff-1255-4833-9aa6-24132adaee80}">
<Description>For domain accounts, the domain controller is authoritative, whereas for local accounts, the local computer is authoritative. However, these events can occur on other computers in the organization when local accounts are used to log on.</Description>
<Value ValueA="Success and Failure" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{914f78ce-7f5d-4de5-a9a9-a0363fbac31c}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Account Management: Other Account Management Events" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Account Management: Other Account Management Events</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Account Management: Other Account Management Events" Operator="Equals" Severity="Critical" id="{1d2c3858-a0bc-4b7d-9eaa-0df5feea4cae}">
<Description>If you enable this Audit policy setting, administrators can track events to detect malicious, accidental, and authorized creation of user and group accounts in the Other Management Events subcategory.</Description>
<Value ValueA="Success and Failure" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{31ecfc9a-3c80-4d57-923e-6c7001525b08}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: System: Security System Extension" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: System: Security System Extension</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: System: Security System Extension" Operator="Equals" Severity="Critical" id="{f34929d7-6a6a-4603-a0e2-e3ac0b5557cb}">
<Description>System events include starting or shutting down computers in your environment, full event logs, or other security-related events that affect the entire system. This setting monitors for security system extension.</Description>
<Value ValueA="Success and Failure" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{5b7b64d4-cee6-499b-b1fe-f645735cdc49}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Object Access: Registry" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Object Access: Registry</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Object Access: Registry" Operator="Equals" Severity="Critical" id="{e812bde9-b47f-4b44-95b5-02651d66d65a}">
<Description>See the appropriate windows security guide for definition of SACL. Success, an audit entry is generated successfully accesses an object with a specified SACL. Failure, an audit entry is generated fails access an object with a specified SACL.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{9842896d-04aa-453c-9503-66cde229db61}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Privilege Use: Other Privilege Use Events" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Privilege Use: Other Privilege Use Events</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Privilege Use: Other Privilege Use Events" Operator="Equals" Severity="Critical" id="{9461f7af-40e3-43e6-83b9-2135fa4edbcd}">
<Description>This setting applies to Other Privilege Use Events subcategory of events. You can use it to audit users exercising user rights.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{8c86ec8b-ea18-4c6e-8c76-412f295967e9}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Object Access: File Share" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Object Access: File Share</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Object Access: File Share" Operator="Equals" Severity="Critical" id="{64f21b25-d5f9-4757-b4d3-782cce864765}">
<Description />
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{a8e68b1c-604e-46ac-909a-7208c6d21772}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: DS Access: Directory Service Changes" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: DS Access: Directory Service Changes</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: DS Access: Directory Service Changes" Operator="Equals" Severity="Critical" id="{2155d59d-9b71-4622-b717-9b2132680d32}">
<Description>For this reason, the DS Access audit category and all related subcategories are configured to No Auditing for both environments discussed. See the appropriate windows security guide for more information.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{8aa78998-b2dd-4aea-9f09-a68bfbb9d32b}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Policy Change: Other Policy Change Events" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Audit Policy: Policy Change: Other Policy Change Events</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Policy Change: Other Policy Change Events" Operator="Equals" Severity="Critical" id="{69bab5c2-ae39-4a87-ba8a-3b5849e733f1}">
<Description> If you enable this Audit policy setting, administrators can track events to detect malicious, accidental, and authorized creation of user and group accounts.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{29b1d926-1928-45bb-953a-5033235e064c}" Severity="Critical" />
<ExistentialRule Name="Audit: Audit the access of global system objects" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit: Audit the access of global system objects</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit: Audit the access of global system objects" Operator="Equals" Severity="Critical" id="{65573518-6faa-4d0b-abd0-d74f76948472}">
<Description>Audit: Audit the access of global system objects</Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{9b4f5ded-0f09-4e8c-b1ee-0b94ae015201}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Policy Change: Audit Policy Change" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Audit Policy: Policy Change: Audit Policy Change</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Policy Change: Audit Policy Change" Operator="Equals" Severity="Critical" id="{90fcc646-74a6-4075-9e2f-82c3c0e78bed}">
<Description>The recommended settings would let you see any account privileges that an attacker attempts to elevate—for example, by adding the Debug programs privilege or the Back up files and directories privilege.</Description>
<Value ValueA="Success and Failure" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{bda8c721-de8a-4565-9e6c-ec653cc1a362}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Object Access: File System" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Object Access: File System</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Object Access: File System" Operator="Equals" Severity="Critical" id="{669a6cac-099c-40c0-a868-633341528f6d}">
<Description />
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{eba1c827-a52f-4859-a825-9030ad7a4676}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Account Management: User Account Management" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Account Management: User Account Management</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Account Management: User Account Management" Operator="Equals" Severity="Critical" id="{5ef932dd-d326-4a24-914f-b090f58db753}">
<Description>If you enable this Audit policy setting, administrators can track events to detect malicious, accidental, and authorized creation of user and group accounts for the User Account Management subcategory.</Description>
<Value ValueA="Success and Failure" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{451ba901-735a-4ed1-9fe6-7cec1817d16a}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: DS Access: Detailed Directory Service Replication" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: DS Access: Detailed Directory Service Replication</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: DS Access: Detailed Directory Service Replication" Operator="Equals" Severity="Critical" id="{bc65f51b-2e09-4d18-b6e2-6a10cc2825ed}">
<Description>For this reason, the DS Access audit category and all related subcategories are configured to No Auditing for both environments. See the appropriate windows security guide for more information.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{e3367498-746b-444a-ae06-d5c1b7792fa9}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Logon-Logoff: IPsec Main Mode" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Logon-Logoff: IPsec Main Mode</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Logon-Logoff: IPsec Main Mode" Operator="Equals" Severity="Critical" id="{14e56b09-e7cd-4b8a-98dc-0cb071556bb3}">
<Description>For interactive logons, events occur on logged on to machine. Network logon to access a share, events generated on machine that hosts the accessed resource. Set to No auditing, it is difficult determine which user has accessed organization computers.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{5bdc9cfc-9552-48c7-a2e0-7002a2de1808}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Policy Change: Authentication Policy Change" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Audit Policy: Policy Change: Authentication Policy Change</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Policy Change: Authentication Policy Change" Operator="Equals" Severity="Critical" id="{bdc9580b-8fd6-4f66-85d9-74a4e7e3f1f9}">
<Description>Rule looks for Success or Failure</Description>
<Value ValueA="Success" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{20d07ce6-0aeb-4c0f-9174-37a83aa961f2}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Object Access: Handle Manipulation" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Object Access: Handle Manipulation</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Object Access: Handle Manipulation" Operator="Equals" Severity="Critical" id="{2863d620-9040-4078-aa09-4304140e7887}">
<Description />
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{5f461288-fa20-4afb-bbcf-b16678b9b4e0}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Account Management: Computer Account Management" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Account Management: Computer Account Management</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Account Management: Computer Account Management" Operator="Equals" Severity="Critical" id="{b79fc695-4b13-490f-a3bd-c67549098cb6}">
<Description> If you enable this Audit policy setting, administrators can track events to detect malicious, accidental, and authorized creation of user and group accounts.</Description>
<Value ValueA="Success" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{cb289093-c8ea-45cb-82f0-5207b1be480d}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Policy Change: MPSSVC Rule-Level Policy Change" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Audit Policy: Policy Change: MPSSVC Rule-Level Policy Change</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Policy Change: MPSSVC Rule-Level Policy Change" Operator="Equals" Severity="Critical" id="{b0a5e199-7609-4468-89ba-501b9bce41c9}">
<Description>The recommended settings would let you see any account privileges that an attacker attempts to elevate—for example, by adding the Debug programs privilege or the Back up files and directories privilege.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{2d6b97d6-7a62-4f49-b857-efe8a8483a4f}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Object Access: Filtering Platform Packet Drop" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Object Access: Filtering Platform Packet Drop</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Object Access: Filtering Platform Packet Drop" Operator="Equals" Severity="Critical" id="{e7a3f2b0-d710-4df6-af2a-944c8d3764de}">
<Description />
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{3c6a3b59-78e7-422b-9a41-bca745e440f0}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Privilege Use: Non Sensitive Privilege Use" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Privilege Use: Non Sensitive Privilege Use</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Privilege Use: Non Sensitive Privilege Use" Operator="Equals" Severity="Critical" id="{fb018357-5c57-4900-af95-fd3fb8e395e3}">
<Description>Success, an audit entry is generated each time that a user right is exercised successfully. Failure, an audit entry is generated each time that a user right is exercised unsuccessfully. This setting can generate a very large number of event records.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{8360778a-69bb-4499-be39-0a588ea4f1ee}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Object Access: Other Object Access Events" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Object Access: Other Object Access Events</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Object Access: Other Object Access Events" Operator="Equals" Severity="Critical" id="{ae06de0b-8e6b-476a-b34f-18f22edb6720}">
<Description />
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{51594bd7-beec-4d17-9f67-7f537a2697d1}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Policy Change: Filtering Platform Policy Change" Operator="GreaterThan" Severity="Warning" ValueA="0">
<Description>Audit Policy: Policy Change: Filtering Platform Policy Change</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Policy Change: Filtering Platform Policy Change" Operator="Equals" Severity="Critical" id="{b95e58f1-62a3-4868-98f1-7ad97e5b0d55}">
<Description>The recommended settings would let you see any account privileges that an attacker attempts to elevate—for example, by adding the Debug programs privilege or the Back up files and directories privilege.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{9d9e663b-d39a-467a-9efb-ec56805b72d6}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Logon-Logoff: IPsec Quick Mode" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Logon-Logoff: IPsec Quick Mode</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Logon-Logoff: IPsec Quick Mode" Operator="Equals" Severity="Critical" id="{c93bb5a9-aabe-4196-9b58-502f7c55e95b}">
<Description>For interactive logons, events occur on logged on to machine. Network logon to access a share, events generated on machine that hosts the accessed resource. Set to No auditing, it is difficult determine which user has accessed organization computers.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{57b9f5c0-ecfc-4efa-800c-eb6c972ee318}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Detailed Tracking: Process Creation" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Detailed Tracking: Process Creation</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Detailed Tracking: Process Creation" Operator="Equals" Severity="Critical" id="{c4ff7a84-cd3b-4879-bf1e-e245a18daff8}">
<Description> Enabling Audit process tracking will generate a large number of events, so it is typically set to No Auditing. Setting can provide a benefit during an incident response.</Description>
<Value ValueA="Success" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{406d0b5b-c2ef-452e-ab6c-3cb93da75706}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Object Access: Application Generated" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Object Access: Application Generated</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Object Access: Application Generated" Operator="Equals" Severity="Critical" id="{1d24c5bd-ff69-4485-ac83-7c9d38c632ab}">
<Description />
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{4faa8055-18b0-47e4-b3ea-b66ce86568ad}" Severity="Critical" />
<ExistentialRule Name="Audit: Audit the use of Backup and Restore privilege" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit: Audit the use of Backup and Restore privilege</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit: Audit the use of Backup and Restore privilege" Operator="Equals" Severity="Critical" id="{50313558-c8f4-489c-be3d-b3dd98090060}">
<Description>Enable both policies, audit event generated for file that is backed up or restored. If the Audit: Audit the use of Backup and Restore privilege setting is enabled, a very large number of security events could quickly fill the Security event log. </Description>
<Value ValueA="Not Defined" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{b2304c80-0de3-4f72-ad5d-9462323c217d}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Object Access: Filtering Platform Connection" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Object Access: Filtering Platform Connection</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Object Access: Filtering Platform Connection" Operator="Equals" Severity="Critical" id="{88219aa9-f6b1-471e-9a70-a78ffec9186c}">
<Description />
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{f31c70aa-dd23-4679-93a2-10ad2ae72174}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: DS Access: Directory Service Access" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: DS Access: Directory Service Access</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: DS Access: Directory Service Access" Operator="Equals" Severity="Critical" id="{c5e3918a-c9f8-425e-912d-6f18c10b6001}">
<Description>For this reason, the DS Access audit category and all related subcategories are configured to No Auditing for both environments. See the appropriate windows security guide for more information.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{c8a945da-c435-49b5-8828-db0fa665be10}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Privilege Use: Sensitive Privilege Use" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Privilege Use: Sensitive Privilege Use</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Privilege Use: Sensitive Privilege Use" Operator="Equals" Severity="Critical" id="{6f1d8062-bc12-4f3f-89fa-bdb228ceb8b2}">
<Description>Success, an audit entry is generated each time that a user right is exercised successfully. Failure, an audit entry is generated each time that a user right is exercised unsuccessfully. This setting can generate a very large number of event records.</Description>
<Value ValueA="Success and Failure" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{7391bbd7-06f8-4277-b3a6-a09dbf6cc2cd}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Logon-Logoff: Logoff" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Logon-Logoff: Logoff</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Logon-Logoff: Logoff" Operator="Equals" Severity="Critical" id="{be2080be-dd72-4059-ba13-10d6f98bbcb1}">
<Description>For interactive logons, events occur on logged on to machine. Network logon to access a share, events generated on machine that hosts the accessed resource. Set to No auditing, it is difficult determine which user has accessed organization computers.</Description>
<Value ValueA="Success" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{780ca8bc-addf-4311-8a8d-879b0678e3ad}" Severity="Critical" />
<ExistentialRule Name="Audit Policy: Detailed Tracking: RPC Events" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit Policy: Detailed Tracking: RPC Events</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit Policy: Detailed Tracking: RPC Events" Operator="Equals" Severity="Critical" id="{2a2cc6ec-5580-456f-be06-22884b8b7cd9}">
<Description> Enabling Audit process tracking will generate a large number of events, so it is typically set to No Auditing. Setting can provide a benefit during an incident response.</Description>
<Value ValueA="No Auditing" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{d3da926f-5048-4cae-a7ec-d9adfc976284}" Severity="Critical" />
<ExistentialRule Name="Maximum Log Size (KB)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Maximum Log Size (KB)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Maximum Log Size (KB)" Operator="Equals" Severity="Critical" id="Channel_LogMaxSize_1">
<Description>By default, the maximum log size is 20480 KB.</Description>
<Value ValueA="Enabled" />
</SettingRule>
<OptionRule Name="Maximum Log Size (KB)" Operator="Equals" Severity="Informational" id="Channel_LogMaxSize">
<Description>By default, the maximum log size is 20480 KB.</Description>
<Value ValueA="32768" />
</OptionRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{4a721ef9-3518-433f-a603-444921aab28e}" Severity="Critical" />
<ExistentialRule Name="Retain old events" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Retain old events</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Retain old events" Operator="Equals" Severity="Critical" id="Channel_Log_Retention_2">
<Description>By default, new events overwrite the oldest ones.</Description>
<Value ValueA="Disabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{8cbe4d06-bbd5-4fdb-8701-0a922fcb860a}" Severity="Critical" />
<ExistentialRule Name="Retain old events" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Retain old events</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Retain old events" Operator="Equals" Severity="Critical" id="Channel_Log_Retention_4">
<Description>By default, new events overwrite the oldest ones.</Description>
<Value ValueA="Disabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{c690159e-9b73-4bab-abbb-4341c2179837}" Severity="Critical" />
<ExistentialRule Name="Maximum Log Size (KB)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Maximum Log Size (KB)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Maximum Log Size (KB)" Operator="Equals" Severity="Critical" id="Channel_LogMaxSize_2">
<Description>By default, the maximum log size is 20480 KB.</Description>
<Value ValueA="Enabled" />
</SettingRule>
<OptionRule Name="Maximum Log Size (KB)" Operator="Equals" Severity="Informational" id="Channel_LogMaxSize">
<Description>By default, the maximum log size is 20480 KB.</Description>
<Value ValueA="81920" />
</OptionRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{6aada6cc-42d5-4331-9be4-a5c0155495af}" Severity="Critical" />
<ExistentialRule Name="Retain old events" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Retain old events</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Retain old events" Operator="Equals" Severity="Critical" id="Channel_Log_Retention_1">
<Description>By default, new events overwrite the oldest ones.</Description>
<Value ValueA="Disabled" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{1f29245a-401d-476e-b508-7fdb4006f22e}" Severity="Critical" />
<ExistentialRule Name="Audit: Shut down system immediately if unable to log security audits" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Audit: Shut down system immediately if unable to log security audits</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Audit: Shut down system immediately if unable to log security audits" Operator="Equals" Severity="Critical" id="{28ed8855-2c5b-4123-9152-dd0a2f2cd261}">
<Description>This is a Trusted Computer System Evaluation Criteria (TCSEC)-C2 and Common Criteria certification to prevent auditable events from occurring if the audit system is unable to log them. </Description>
<Value ValueA="0" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{0bfdacae-8913-4e59-b0da-d1f359b47781}" Severity="Important" />
<ExistentialRule Name="MSS: (WarningLevel) Percentage threshold for the security event log at which the system will generate a warning" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>MSS: (WarningLevel) Percentage threshold for the security event log at which the system will generate a warning</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="MSS: (WarningLevel) Percentage threshold for the security event log at which the system will generate a warning" Operator="Equals" Severity="Warning" id="{aca8b5de-4500-401a-a756-fdca58038e05}">
<Description>This setting can generate a security audit in the Security event log when the log reaches a user-defined threshold. This setting is configured to Not Defined for the EC environment and to 90 for the SSLF environment.</Description>
<Value ValueA="90" />
</SettingRule>
</ValidationRules>
</Check>
<Check>
<SettingRef setting_ref="{311a474a-a1c0-4337-8f52-7f36e048d41b}" Severity="Critical" />
<ExistentialRule Name="Maximum Log Size (KB)" Operator="GreaterThan" Severity="Informational" ValueA="0">
<Description>Maximum Log Size (KB)</Description>
</ExistentialRule>
<ValidationRules>
<SettingRule Name="Maximum Log Size (KB)" Operator="Equals" Severity="Critical" id="Channel_LogMaxSize_4">
<Description>By default, the maximum log size is 20480 KB.</Description>
<Value ValueA="Enabled" />
</SettingRule>
<OptionRule Name="Maximum Log Size (KB)" Operator="Equals" Severity="Informational" id="Channel_LogMaxSize">
<Description>By default, the maximum log size is 20480 KB.</Description>
<Value ValueA="32768" />
</OptionRule>
</ValidationRules>
</Check>
<Comment>
</Comment>
</Baseline>
<Product ID="{ca347361-ac97-4dfa-a666-eeca698eff9f}" DisplayName="Windows 7 SP1">
<OperatingSystemInfo MajorVersion="6" MinorVersion="1" BuildVersion="7601" />
<ProductFamilyRef productfamily_ref="{5cea53d1-8a08-4804-8886-1ddea5899aea}" />
<CPE>
<CPE-Dictionary>Windows 7 SP1-CPE-Dictionary.xml</CPE-Dictionary>
<CPE-Oval>Windows 7 SP1-CPE-Oval.xml</CPE-Oval>
</CPE>
</Product>
<ProductFamily ID="{5cea53d1-8a08-4804-8886-1ddea5899aea}" DisplayName="Windows Family">
<Description>The Microsoft Windows product family includes Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, and later versions of the Microsoft Windows operating system.</Description>
</ProductFamily>
</SCMPackage>
Home