Tests/Sample.XML
|
<?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="{01906054-cd2d-4eb4-ac99-619ee5c9f728}" Name="Azure OS Baseline V6" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Description> The steps to create this baseline, #1, Take CIS WS2008 R2 SP1 baseline in SCM format, input into SCM #2, duplicate and create this baseline #3, compare it against CIS WS2008 R2 SP1 baseline from Devendra and customize the baseline #4, made decision to change audit policy setting rule validation logic, use GreaterEquals to support StrongerEquals evaluation, for examples, Success is stronger than No Audit and Success+Failure is stronger than Success only. #5, add account lockout settings #6, add cipher suite order ---------- V4 update ---------- #7, add WER setting as report #8, add "Require user authentication for remote connections by using Network Level Authentication" per Nessus scan #9, make audit policy consistent per review -------------------- V5 update 2015-10-20 -------------------- #10 Add subset processing for selected user rights. Change operation from Equals to LessOrEqual implying that values are the allowed set, not exact set CCE-10849-8 - Adjust memory quotas for a process - Add IIS APPPOOL\DefaultAppPool CCE-10274-9 - Generate security audits - Add IIS APPPOOL\DefaultAppPool CCE-9946-5 - Impersonate a client after authentication -------------------- V6 update 2015-11-04 -------------------- #11 Change RuleName in Checks for CCE-10391-1 so that it exactly matches the RuleName in the Settings/Discovery section. Otherwise can lead to unreported rule results. -------------------- V7 update 2016-22-03 -------------------- #12 Updates 1. Updated Category Names 2. Removed duplicate rules 3. Moved Rules to correct category 4. Added new baseline Rules </mssasc-core:Description> <mssasc-core:Version Major="1" Minor="2" /> <Mode Mode="Edit" /> <VersionControl> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <OriginalBaselineID>{9ff96717-0c7f-4ed0-a7a0-22bdd9c7a75b}</OriginalBaselineID> <RevisionNumber>6</RevisionNumber> <OriginalRevisionNumber>2</OriginalRevisionNumber> </VersionControl> <SettingGroup ID="{7a228c6f-3bd1-4888-9a0e-0d978361d332}" Name="Least Functionality" OriginalSettingGroupID="{887c1df6-2d22-437b-ae24-7fae9dc74e05}"> <mssasc-core:Description> </mssasc-core:Description> <mssasc-core:Version Major="1" Minor="0" /> <Author> </Author> <Setting Index="5" ID="{236aa795-e020-4b72-8d40-9502567f8561}" OriginalSettingID="{c8c43367-6343-4ae7-9387-c4f24303b90d}" Name="Shutdown: Clear virtual memory pagefile" LockdownDate="2011-05-19T05:55:44Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11049-4"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="6" ID="{fe995933-3583-43ab-8932-168850b077a0}" OriginalSettingID="{c836e4ce-c2f0-410c-bbf2-2550e8d24ba8}" Name="MSS: (SafeDllSearchMode) Enable Safe DLL search mode (recommended)" LockdownDate="2011-08-02T06:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10772-2"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="7" ID="{7b14fd19-eadf-42da-960a-e02c5a49cfb5}" OriginalSettingID="{c57013e7-e530-4cbd-951f-2c07f2a91b73}" Name="Always install with elevated privileges" LockdownDate="2011-10-27T09:45:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-12401-6"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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="9" ID="{a40ce73c-ee67-4b10-afcc-70e2c9fb784f}" OriginalSettingID="{2d5369da-937a-4f8c-be9e-3acd79b70585}" Name="Turn off Autoplay" LockdownDate="2011-10-09T10:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11126-0"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" refId="Autorun_Box" defaultItem="0">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="10" ID="{13d86ad6-83cc-4092-9e58-50a54d1aecce}" OriginalSettingID="{1b4d4248-73f1-4950-be5c-8c2fd6d47002}" Name="Recovery console: Allow automatic administrative logon" LockdownDate="2011-04-28T12:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10370-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="12" ID="{162f9d7c-7d0d-4e46-9a18-43d165b07e85}" OriginalSettingID="{7ab41c58-8c4a-4781-9cdd-a6dc5c40fc66}" Name="System objects: Require case insensitivity for non-Windows subsystems" LockdownDate="2011-08-02T06:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10986-8"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="13" ID="{581f0698-c134-4949-a648-267e5e61c5c8}" OriginalSettingID="{e44bb6b6-6bf3-417b-a329-cb9604cde378}" Name="Recovery console: Allow floppy copy and access to all drives and all folders" LockdownDate="2011-05-19T05:55:44Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10643-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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>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="14" ID="{e0e9ab4c-e39c-4251-9ecc-1e8b88749eab}" OriginalSettingID="{8ae83b84-b0fd-4b08-85a5-ff3f897a2db2}" Name="Interactive logon: Do not require CTRL+ALT+DEL" LockdownDate="2011-10-09T10:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10810-0"> <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>Disabled</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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="15" ID="{124534b0-17b7-4944-9922-bbf6a5cc1569}" OriginalSettingID="{6e47e304-7197-4791-b16d-9a6ad3306ad4}" Name="System settings: Use Certificate Rules on Windows Executables for Software Restriction Policies" LockdownDate="2011-08-02T06:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10900-9"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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\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="18" ID="{85029100-6fe5-4f31-a457-7f20b99c5b48}" OriginalSettingID="{b1d27dc2-b5e3-4dc5-9d3b-d634e7a25353}" Name="MSS: (AutoAdminLogon) Enable Automatic Logon (not recommended)" LockdownDate="2011-08-02T06:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10745-8"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="19" ID="{8f58e594-a4ba-43e8-bd78-5b03bc06297c}" OriginalSettingID="{3849d4a1-188c-43d8-ad75-c73a82a8e0fe}" Name="Shutdown: Allow system to be shut down without having to log on" LockdownDate="2011-06-10T12:30:40Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10419-0"> <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>Disabled</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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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>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="213" ID="{25c149ae-0822-4f8c-885b-6d6a9a03963b}" OriginalSettingID="{2448f308-6d86-4bbd-a39f-b7503385fdd7}" Name="Always prompt for password upon connection" LockdownDate="2014-02-09T10:27:24Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11299-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">fPromptForPassword</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <policy xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" name="TS_PASSWORD" class="Machine" displayName="$(string.51930728a8784371a32ee43aaf30c46a)" explainText="$(string.a36b67959aab41b2b5b091c1a15ccaeb)" key="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" valueName="fPromptForPassword"> <admx:supportedOn xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="oval:com.secure-elements.oval:def:6599" ref_url="" /> </OVAL> </ExportInfo> <Comment>Added Setting xtan: the original Azure Excel sheet suggested using the default which is Not Configured. We should enable this rule ro reduce attack surface.</Comment> </Setting> <Setting Index="218" ID="{7ac8fbc8-eecc-4e14-b68c-498df8dcf697}" OriginalSettingID="{d5d37567-6f6c-4b86-a13a-d10b708432dc}" Name="Devices: Allow undock without having to log on" LockdownDate="2014-02-11T12:17:25Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10883-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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" 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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">undockwithoutlogon</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" 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>Added Setting </Comment> </Setting> <Setting Index="219" ID="{abf4270e-5b23-4602-aaa4-fe02ef0cb0b0}" OriginalSettingID="{c95a7fc1-5250-4494-9b94-3f3301b8ae7f}" Name="MSS: (NtfsDisable8dot3NameCreation) Enable the computer to stop generating 8.3 style filenames" LockdownDate="2014-02-13T02:19:43Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10781-3"> <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>There's no known vulnerability associated with this feature at the time of this writing, however directory enumeration performance is improved if you disable short name generation on an NTFS file system (NTFS) partition.</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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" 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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">System\CurrentControlSet\Control\FileSystem</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">NtfsDisable8dot3NameCreation</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" 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> Added Setting xtan: the original Azure Excel suggestted "Enabled" without recommendation. Based on the vulnerability, suggest Not Defined </Comment> </Setting> <Setting Index="220" ID="{3db85b27-a930-4714-b0bd-be050b063580}" OriginalSettingID="{6c495e42-ef02-44ec-a811-f640f0942daf}" Name="Registry policy processing" LockdownDate="2014-02-13T02:51:27Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-12754-8"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine" /> <DataType>String</DataType> </DiscoveryInfo> <policy xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" 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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <presentation id="CSE_Registry"> <admx:checkBox xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" refId="CSE_NOBACKGROUND10">Do not apply during periodic background processing</admx:checkBox> <admx:checkBox xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" refId="CSE_NOCHANGES10">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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment>Added Setting </Comment> </Setting> <Setting Index="226" ID="{f56ab036-9c85-4fe6-96f9-9d4d328bfc88}" OriginalSettingID="{98b3f31f-6710-418d-a037-34b19be8dfa7}" Name="Turn off Search Companion content file updates" LockdownDate="2014-02-13T05:23:00Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10889-4"> <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>Not configured</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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">Software\Policies\Microsoft\SearchCompanion</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">DisableContentFileUpdates</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <policy xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" name="SearchCompanion_DisableFileUpdates" class="Machine" displayName="$(string.2ea9500ccb464b20b7c8fa1316f1cd54)" explainText="$(string.c051df5586ad42b28b39afc74e88b80f)" key="Software\Policies\Microsoft\SearchCompanion" valueName="DisableContentFileUpdates"> <admx:supportedOn xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment>Added Setting </Comment> </Setting> <Setting Index="227" ID="{ce2e90b0-2305-4169-8fa1-eadd8942570d}" OriginalSettingID="{b89a9c6d-4c77-401f-8e1a-375f1d16c1c0}" Name="Turn off the "Publish to Web" task for files and folders" LockdownDate="2014-02-13T05:23:55Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11587-3"> <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>Not configured</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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">Software\Microsoft\Windows\CurrentVersion\Policies\Explorer</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">NoPublishingWizard</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <policy xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" name="ShellRemovePublishToWeb_2" class="Machine" displayName="$(string.eb31306d57014d8dbf9b4a5d86ce670f)" explainText="$(string.a387acce9f314f7c94b7223bc729bf36)" key="Software\Microsoft\Windows\CurrentVersion\Policies\Explorer" valueName="NoPublishingWizard"> <admx:supportedOn xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment>Added Setting </Comment> </Setting> <Setting Index="228" ID="{2999c1ca-bed4-4b51-8ea5-8bf025fccf92}" OriginalSettingID="{436c848f-826f-4f57-b1f0-ca3237156979}" Name="Turn off the Windows Messenger Customer Experience Improvement Program" LockdownDate="2014-02-13T05:24:41Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11958-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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">Software\Policies\Microsoft\Messenger\Client</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">CEIP</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <policy xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" name="WinMSG_NoInstrumentation_2" class="Machine" displayName="$(string.30f6dcb287924251b92118dc2b2591ae)" explainText="$(string.1e78fc6d132341a8b193f7358e83295e)" key="Software\Policies\Microsoft\Messenger\Client" valueName="CEIP"> <admx:supportedOn xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment>Added Setting </Comment> </Setting> <Comment> </Comment> </SettingGroup> <SettingGroup ID="{b05cd43b-ec35-4afc-acea-d57f6a69e4f2}" Name="Session Configuration" OriginalSettingGroupID="{c6572522-1826-4828-b648-df3c7f83316d}"> <mssasc-core:Description> </mssasc-core:Description> <mssasc-core:Version Major="1" Minor="0" /> <Author> </Author> <Setting Index="20" ID="{79b4e067-440a-497d-9a87-95188942a003}" OriginalSettingID="{68c3ff44-f8a7-4059-81d7-56749f60665b}" Name="Microsoft network server: Disconnect clients when logon hours expire" LockdownDate="2011-08-02T06:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10983-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="21" ID="{8b7f3756-397b-49b6-b639-1023af377d3b}" 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-19T05:25:35Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10019-8"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="23" ID="{c007b836-5214-4b0b-b5fb-9a9b58b80f42}" OriginalSettingID="{4ec1a4fa-eccf-4dab-81aa-3e0a7c8f9983}" Name="Microsoft network server: Amount of idle time required before suspending session" LockdownDate="2011-04-28T12:36:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10362-2"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="24" ID="{b4264b5a-d5eb-4534-b514-3884840cc19f}" OriginalSettingID="{6b285a31-21ae-4b0c-813c-a8cc812c694d}" Name="Interactive logon: Do not display last user name" LockdownDate="2011-04-28T12:36:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10788-8"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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> <Comment> </Comment> </SettingGroup> <SettingGroup ID="{82cb83f4-d7ff-4f21-8e27-6a994f896df5}" Name="Encryption Configuration" OriginalSettingGroupID="{20d07c22-bc19-40e1-95ee-a909879d2fd7}"> <mssasc-core:Description> </mssasc-core:Description> <mssasc-core:Version Major="1" Minor="0" /> <Author> </Author> <Setting Index="28" ID="{7556ff3b-976d-4105-97a6-558465627ffc}" OriginalSettingID="{7ab7ae06-f9bd-4252-a282-8fd3a06a73df}" Name="Domain member: Digitally sign secure channel data (when possible)" LockdownDate="2011-06-18T01:57:00Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10009-9"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="30" ID="{94622cee-0b73-4007-a029-cd68273adecb}" OriginalSettingID="{aa6c8875-0777-4685-9f37-193e9f16af51}" Name="System cryptography: Force strong key protection for user keys stored on the computer" LockdownDate="2011-08-19T06:13:47Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11035-3"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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>Per Devendra, use windows default</Comment> </Setting> <Setting Index="31" ID="{a471355b-7f15-41db-b339-b384d0020cfd}" OriginalSettingID="{04b278da-3245-43ec-9d5a-a5a68805027b}" Name="Domain member: Digitally encrypt or sign secure channel data (always)" LockdownDate="2011-04-28T12:36:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10871-2"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="33" ID="{10a56b26-ac55-4ac8-9db7-2cca216d496b}" OriginalSettingID="{b106bcb1-2b74-4287-8587-6cd92d337be8}" Name="Domain member: Digitally encrypt secure channel data (when possible)" LockdownDate="2011-04-28T12:36:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10875-3"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="34" ID="{014038f2-2d49-4cb0-88b3-ae58b2140c6a}" OriginalSettingID="{b1b4a762-3114-438b-92cf-90f021714790}" Name="Microsoft network client: Send unencrypted password to third-party SMB servers" LockdownDate="2011-04-28T12:36:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10838-1"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="36" ID="{4d5107c4-50ce-4625-bb8a-4589ff35b5a7}" OriginalSettingID="{c6c11e09-fbc2-408d-af70-3b47f2d2d1b8}" Name="System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" LockdownDate="2011-05-19T05:55:44Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10789-6"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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\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>xtan: I have seen large failed for this rule based on the recent report. Devendra indicated this is false positive in our service team engagement for down level client compatibility. I am OK to leave it Disabled if exception exists.</Comment> </Setting> <Setting Index="37" ID="{b97df99f-e32c-49c2-bed9-0213fa84e34b}" OriginalSettingID="{577a19bc-6d69-45f1-9806-b413d522b05a}" Name="Domain member: Require strong (Windows 2000 or later) session key" LockdownDate="2011-08-02T06:16:32Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10541-1"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="38" ID="{b7acd6e0-04b1-431e-b7fd-a673562ce721}" OriginalSettingID="{aadb8b38-715d-470b-b67c-b2158ac6c9f7}" Name="Set client connection encryption level" LockdownDate="2011-10-09T10:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11677-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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" refId="TS_ENCRYPTION_LEVEL" defaultItem="1">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="39" ID="{c060464b-ce68-4df9-bff1-58d0fc1c7cea}" OriginalSettingID="{2d7b01a8-4a78-478c-bb69-320e592e5d58}" Name="SSL Cipher Suite Order" LockdownDate="2014-05-13T01:06:48Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11076-7"> <Description> </Description> </CCEID-50> <ShortDescription>SSL Cipher Suite Order</ShortDescription> <FullDescription>Determines the cipher suites used by the Secure Socket Layer (SSL). If this setting is enabled, SSL cipher suites will be prioritized in the order specified. If this setting is disabled or not configured, the factory default cipher suite order will be used. SSL2, SSL3, TLS 1.0 and TLS 1.1 cipher suites: TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_RC4_128_SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P521 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P521 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P384 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P521 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P256 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P521 TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_RC4_128_MD5 SSL_CK_RC4_128_WITH_MD5 SSL_CK_DES_192_EDE3_CBC_WITH_MD5 TLS_RSA_WITH_NULL_SHA TLS_RSA_WITH_NULL_MD5 TLS 1.2 SHA256 and SHA384 cipher suites: TLS_RSA_WITH_AES_128_CBC_SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P521 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P384 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P521 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P521 TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 TLS_RSA_WITH_NULL_SHA256 TLS 1.2 ECC GCM cipher suites: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P384 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P521 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P521 How to modify this setting: 1. Open a blank notepad document. 2. Copy and paste the list of available suites into it. 3. Arrange the suites in the correct order; remove any suites you don't want to use. 4. Place a comma at the end of every suite name except the last. Make sure there are NO embedded spaces. 5. Remove all the line breaks so that the cipher suite names are on a single, long line. 6. Copy the cipher-suite line to the clipboard, then paste it into the edit box. The maximum length is 1023 characters. </FullDescription> <UIPath>Computer Configuration\Administrative Templates\Network\SSL Configuration Settings</UIPath> <DefaultValue> </DefaultValue> <Vulnerability> </Vulnerability> <Countermeasure> </Countermeasure> <PotentialImpact> </PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="0"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine" /> <DataType>String</DataType> </DiscoveryInfo> <policy xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" name="SSLCipherSuiteOrder" class="Machine" displayName="$(string.8bf019626c8c4db3b69429d811aa3311)" explainText="$(string.93aa3003e41243fc965bf46125f68970)" presentation="$(presentation.SSLCipherSuiteOrder)" key="SOFTWARE\Policies\Microsoft\Cryptography\Configuration\SSL\00010002"> <admx:supportedOn xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <admx:elements xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions"> <admx:text id="Pol_SSLCipherSuiteOrder" key="SOFTWARE\Policies\Microsoft\Cryptography\Configuration\SSL\00010002" valueName="Functions" /> </admx:elements> </policy> <ADMLDefinition xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <presentation id="SSLCipherSuiteOrder"> <admx:textBox xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" refId="Pol_SSLCipherSuiteOrder"> <admx:label>SSL Cipher Suites</admx:label> <admx:defaultValue>TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_RC4_128_SHA,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P384,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P384,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P256,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P384,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P384,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P256,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P384,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P384,TLS_DHE_DSS_WITH_AES_128_CBC_SHA256,TLS_DHE_DSS_WITH_AES_128_CBC_SHA,TLS_DHE_DSS_WITH_AES_256_CBC_SHA256,TLS_DHE_DSS_WITH_AES_256_CBC_SHA,TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_RC4_128_MD5,SSL_CK_RC4_128_WITH_MD5,SSL_CK_DES_192_EDE3_CBC_WITH_MD5,TLS_RSA_WITH_NULL_SHA256,TLS_RSA_WITH_NULL_SHA</admx:defaultValue> </admx:textBox> </presentation> <string id="8bf019626c8c4db3b69429d811aa3311">SSL Cipher Suite Order</string> <string id="93aa3003e41243fc965bf46125f68970">Determines the cipher suites used by the Secure Socket Layer (SSL). If this setting is enabled, SSL cipher suites will be prioritized in the order specified. If this setting is disabled or not configured, the factory default cipher suite order will be used. SSL2, SSL3, TLS 1.0 and TLS 1.1 cipher suites: TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_RC4_128_SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P521 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P521 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P384 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P521 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P256 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P521 TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_RC4_128_MD5 SSL_CK_RC4_128_WITH_MD5 SSL_CK_DES_192_EDE3_CBC_WITH_MD5 TLS_RSA_WITH_NULL_SHA TLS_RSA_WITH_NULL_MD5 TLS 1.2 SHA256 and SHA384 cipher suites: TLS_RSA_WITH_AES_128_CBC_SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P521 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P384 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P521 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P521 TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 TLS_RSA_WITH_NULL_SHA256 TLS 1.2 ECC GCM cipher suites: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P384 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P521 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P521 How to modify this setting: 1. Open a blank notepad document. 2. Copy and paste the list of available suites into it. 3. Arrange the suites in the correct order; remove any suites you don't want to use. 4. Place a comma at the end of every suite name except the last. Make sure there are NO embedded spaces. 5. Remove all the line breaks so that the cipher suite names are on a single, long line. 6. Copy the cipher-suite line to the clipboard, then paste it into the edit box. The maximum length is 1023 characters. </string> </ADMLDefinition> <supportedOn>Unspecified</supportedOn> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment>Added Setting, per recent TWC cipher suite order recommendation</Comment> </Setting> <Comment> </Comment> </SettingGroup> <SettingGroup ID="{4c01fe73-699d-4d92-877e-9dddfd8aab97}" Name="Password" OriginalSettingGroupID="{12cc5c96-00dc-4ea7-906e-f8d9deea281f}"> <mssasc-core:Description> </mssasc-core:Description> <mssasc-core:Version Major="1" Minor="0" /> <Author> </Author> <Setting Index="44" ID="{b1c37fde-5315-4563-9b08-3bbb1ac55233}" OriginalSettingID="{74870acb-ad3d-4bec-a067-1b1895ce2621}" Name="Interactive logon: Prompt user to change password before expiration" LockdownDate="2011-08-02T06:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10930-6"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="46" ID="{f5e55156-eb42-421e-a8f4-faa939998db9}" OriginalSettingID="{e3ac5993-d420-4039-abd9-1867cd3dfddf}" Name="Network access: Do not allow storage of passwords and credentials for network authentication" LockdownDate="2011-08-02T06:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10292-1"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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>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>change to disable per devendra excel (which is default)</Comment> </Setting> <Setting Index="47" ID="{6782d755-bfb1-482c-b720-e8e4d03d3800}" OriginalSettingID="{051cdac6-2234-4eb7-85eb-db391c469557}" Name="Accounts: Limit local account use of blank passwords to console logon only" LockdownDate="2011-10-28T09:59:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-9992-9"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="49" ID="{610fb9bb-0d5e-4388-a265-866afeff6660}" OriginalSettingID="{b44fadd3-f7c2-45dc-98dd-5e9ba179d89d}" Name="Domain member: Disable machine account password changes" LockdownDate="2011-08-02T06:16:32Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10775-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="50" ID="{8e2a40ed-2bf7-42ec-8c40-b6d712496fd7}" OriginalSettingID="{5ae8ac79-c4f6-4b24-9906-12326755c58b}" Name="Domain member: Maximum machine account password age" LockdownDate="2011-08-02T06:16:32Z" GenerateDCM="true" GenerateSCAP="false" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10903-3"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="214" ID="{f37ec02b-1925-4cc5-997c-c72912af268c}" OriginalSettingID="{970b184b-62b1-46d1-9262-195dec171cd9}" Name="Do not allow passwords to be saved" LockdownDate="2014-02-11T12:21:46Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11905-7"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">DisablePasswordSaving</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <policy xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" 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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="oval:com.secure-elements.oval:def:6596" ref_url="" /> </OVAL> </ExportInfo> <Comment>Added Setting </Comment> </Setting> <Setting Index="215" ID="{a1d0e16e-e734-4790-b8ca-204b20d5b89c}" OriginalSettingID="{dbf79787-0b0c-4687-acc0-c626247c487f}" Name="Enforce password history" LockdownDate="2014-02-09T01:39:26Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10809-2"> <Description> </Description> </CCEID-50> <ShortDescription>This policy setting determines the number of renewed, unique passwords that have to be associated with a user account before you can reuse an old password. </ShortDescription> <FullDescription> This policy setting determines the number of renewed, unique passwords that have to be associated with a user account before you can reuse an old password. The value for this policy setting must be between 0 and 24 passwords. The default value for Windows Vista is 0 passwords, but the default setting in a domain is 24 passwords. To maintain the effectiveness of this policy setting, use the Minimum password age setting to prevent users from repeatedly changing their password. </FullDescription> <UIPath>Computer Configuration\Windows Settings\Security Settings\Account Policies\Password Policy</UIPath> <DefaultValue>24 passwords remembered</DefaultValue> <Vulnerability> The longer a user uses the same password, the greater the chance that an attacker can determine the password through brute force attacks. Also, any accounts that may have been compromised will remain exploitable for as long as the password is left unchanged. If password changes are required but password reuse is not prevented, or if users continually reuse a small number of passwords, the effectiveness of a good password policy is greatly reduced. If you specify a low number for this policy setting, users will be able to use the same small number of passwords repeatedly. If you do not also configure the Minimum password age setting, users might repeatedly change their passwords until they can reuse their original password. </Vulnerability> <Countermeasure> Configure the Enforce password history setting to 24, the maximum setting, to help minimize the number of vulnerabilities that are caused by password reuse. For this setting to be effective in your organization, do not allow passwords to be changed immediately when you configure the Minimum password age setting. The Enforce password history value should be set at a level that combines a reasonable maximum password age with a reasonable password change interval requirement for all users in your organization. </Countermeasure> <PotentialImpact>The major impact of this configuration is that users must create a new password every time they are required to change their old one. If users are required to change their passwords to new unique values, there is an increased risk of users who write their passwords somewhere so that they do not forget them. Another risk is that users may create passwords that change incrementally (for example, password01, password02, and so on) to facilitate memorization but make them easier to guess. Also, an excessively low value for the Minimum password age setting will likely increase administrative overhead, because users who forget their passwords might ask the help desk to reset them frequently.</PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="9999"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <Mapping FriendlyName="Not Defined"> <BehaviorDescription /> <DCMValue ValueA="Not Defined" /> <SCAPValue ValueA="Not Defined" /> <GPOValue ValueA="Not Defined" /> </Mapping> <Mapping FriendlyName="Not Configured"> <BehaviorDescription /> <DCMValue ValueA="Not Configured" /> <SCAPValue ValueA="Not Configured" /> <GPOValue ValueA="Not Configured" /> </Mapping> <Mapping FriendlyName="Not Applicable"> <BehaviorDescription /> <DCMValue ValueA="Not Applicable" /> <SCAPValue ValueA="Not Applicable" /> <GPOValue ValueA="Not Applicable" /> </Mapping> <Mapping FriendlyName="Not Recommended"> <BehaviorDescription /> <DCMValue ValueA="Not 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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="WMI" Scope="Machine"> <WMIDiscoveryInfo> <mssasc-core:Namespace xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">root\rsop\computer</mssasc-core:Namespace> <mssasc-core:Class xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">RSOP_SecuritySettingNumeric</mssasc-core:Class> <mssasc-core:Property xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">Setting</mssasc-core:Property> <mssasc-core:Where xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">KeyName='PasswordHistorySize' And precedence=1</mssasc-core:Where> </WMIDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="INF"> <Inf SectionName="System Access" Name="PasswordHistorySize" DataType="REG_DWORD" /> <OVAL> <Reference source="" ref_id="oval:gov.nist.1:def:16" ref_url="" /> </OVAL> </ExportInfo> <Comment> Added Setting, there is a problem here, we can't define operation, it should >=. This is also domain setting using RSPO WMI interface. ASM uses secedit. </Comment> </Setting> <Setting Index="216" ID="{d3c1e430-62b3-4e94-8aff-84db4abc82e6}" OriginalSettingID="{71bd810f-5c3d-4836-b3c6-289fdf24e1d2}" Name="Store passwords using reversible encryption" LockdownDate="2014-02-13T03:56:22Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10905-8"> <Description> </Description> </CCEID-50> <ShortDescription>This policy setting determines whether the operating system stores passwords in a way that uses reversible encryption, which provides support for application protocols that require knowledge of the user's password for authentication purposes.</ShortDescription> <FullDescription>This policy setting determines whether the operating system stores passwords in a way that uses reversible encryption, which provides support for application protocols that require knowledge of the user's password for authentication purposes. Passwords that are stored with reversible encryption are essentially the same as plaintext versions of the passwords.</FullDescription> <UIPath>Computer Configuration\Windows Settings\Security Settings\Account Policies\Password Policy</UIPath> <DefaultValue>Disabled</DefaultValue> <Vulnerability>Enabling this policy setting allows the operating system to store passwords in a weaker format that is much more susceptible to compromise and weakens your system security.</Vulnerability> <Countermeasure>Disable the Store password using reversible encryption for all users in the domain setting. </Countermeasure> <PotentialImpact>If your organization uses either the CHAP authentication protocol through remote access or IAS services or Digest Authentication in IIS, you must configure this policy setting to Enabled. This setting is extremely dangerous to apply through Group Policy on a user-by-user basis, because it requires the appropriate user account object to be opened in Active Directory Users and Computers.</PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="0"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" 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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="WMI" Scope="Machine"> <WMIDiscoveryInfo> <mssasc-core:Namespace xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">root\rsop\computer</mssasc-core:Namespace> <mssasc-core:Class xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">RSOP_SecuritySettingBoolean</mssasc-core:Class> <mssasc-core:Property xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">Setting</mssasc-core:Property> <mssasc-core:Where xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">KeyName = 'ClearTextPassword' And precedence=1</mssasc-core:Where> </WMIDiscoveryInfo> </SettingDiscoveryInfo> <DataType>String</DataType> </DiscoveryInfo> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="INF"> <Inf SectionName="System Access" Name="ClearTextPassword" DataType="WMI_Boolean" /> <OVAL> <Reference source="" ref_id="oval:gov.nist.1:def:22" ref_url="" /> </OVAL> </ExportInfo> <Comment> Added Setting, there is a problem here, we can't define operation, it should >=. This is also domain setting using RSPO WMI interface. ASM uses secedit. </Comment> </Setting> <Setting Index="217" ID="{61b3f0bd-4106-464f-9ffb-39255ff9cd58}" OriginalSettingID="{6a2f27c3-0b27-46ff-a33b-28d1117f70b0}" Name="Minimum password age" LockdownDate="2014-02-22T02:21:31Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10760-7"> <Description> </Description> </CCEID-50> <ShortDescription>This policy setting determines the number of days that you must use a password before you can change it. </ShortDescription> <FullDescription>This policy setting determines the number of days that you must use a password before you can change it. The range of values for this policy setting is between 1 and 999 days. (You may also set the value to 0 to allow immediate password changes.) The default value for this setting is 0 days.</FullDescription> <UIPath>Computer Configuration\Windows Settings\Security Settings\Account Policies\Password Policy</UIPath> <DefaultValue>0 days</DefaultValue> <Vulnerability>Users may have favorite passwords that they like to use because they are easy to remember and they believe that their password choice is secure from compromise. Unfortunately, passwords are compromised and if an attacker is targeting a specific individual user account, with foreknowledge of data about that user, reuse of old passwords can cause a security breach. To address password reuse a combination of security settings is required. Using this policy setting with the Enforce password history setting prevents the easy reuse of old passwords. For example, if you configure the Enforce password history setting to ensure that users cannot reuse any of their last 12 passwords, they could change their password 13 times in a few minutes and reuse the password they started with, unless you also configure the Minimum password age setting to a number that is greater than 0. You must configure this policy setting to a number that is greater than 0 for the Enforce password history setting to be effective.</Vulnerability> <Countermeasure>Configure the Minimum password age setting to a value of at least 2 days. Users should know about this limitation and contact the help desk if they need to change their password during that 2-day period. If you configure the number of days to 0, immediate password changes would be allowed, which we do not recommend. When configuring this setting you should also configure the Maximum password age to a value that makes sense in combination with this one.</Countermeasure> <PotentialImpact>If an administrator sets a password for a user but wants that user to change the password when the user first logs on, the administrator must select the User must change password at next logon check box, or the user will not be able to change the password until the next day.</PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="9999"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <Mapping FriendlyName="Not Defined"> <BehaviorDescription /> <DCMValue ValueA="Not Defined" /> <SCAPValue ValueA="Not Defined" /> <GPOValue ValueA="Not Defined" /> </Mapping> <Mapping FriendlyName="Not Configured"> <BehaviorDescription /> <DCMValue ValueA="Not Configured" /> <SCAPValue ValueA="Not Configured" /> <GPOValue ValueA="Not Configured" /> </Mapping> <Mapping FriendlyName="Not Applicable"> <BehaviorDescription /> <DCMValue ValueA="Not Applicable" /> <SCAPValue ValueA="Not Applicable" /> <GPOValue ValueA="Not Applicable" /> </Mapping> <Mapping FriendlyName="Not Recommended"> <BehaviorDescription /> <DCMValue ValueA="Not 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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="WMI" Scope="Machine"> <WMIDiscoveryInfo> <mssasc-core:Namespace xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">root\rsop\computer</mssasc-core:Namespace> <mssasc-core:Class xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">RSOP_SecuritySettingNumeric</mssasc-core:Class> <mssasc-core:Property xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">Setting</mssasc-core:Property> <mssasc-core:Where xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">KeyName = 'MinimumPasswordAge' And precedence=1</mssasc-core:Where> </WMIDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="INF"> <Inf SectionName="System Access" Name="MinimumPasswordAge" DataType="REG_DWORD" /> <OVAL> <Reference source="" ref_id="oval:gov.nist.1:def:18" ref_url="" /> </OVAL> </ExportInfo> <Comment> Added Setting, xtan: equals rule operator is questionable, it may invoke some noise, let's see </Comment> </Setting> <Setting Index="221" ID="{b97ea12f-9ee5-4abe-9928-98fa9f8b9b4d}" OriginalSettingID="{c6638249-48c9-4a21-9b97-d008323fccbf}" Name="Minimum password length" LockdownDate="2014-02-22T03:22:14Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10372-1"> <Description> </Description> </CCEID-50> <ShortDescription>This policy setting determines the least number of characters that make up a password for a user account.</ShortDescription> <FullDescription> This policy setting determines the least number of characters that make up a password for a user account. There are many different theories about how to determine the best password length for an organization, but perhaps "pass phrase" is a better term than "password." In Microsoft Windows 2000 or later, pass phrases can be quite long and can include spaces. Therefore, a phrase such as "I want to drink a $5 milkshake" is a valid pass phrase; it is a considerably stronger password than an 8 or 10 character string of random numbers and letters, and yet is easier to remember. Users must be educated about the proper selection and maintenance of passwords, especially with regard to password length. In enterprise environments, the ideal value for the Minimum password length setting is 14 characters, however you should adjust this value to meet your organization's business requirements. </FullDescription> <UIPath>Computer Configuration\Windows Settings\Security Settings\Account Policies\Password Policy</UIPath> <DefaultValue>0 characters</DefaultValue> <Vulnerability>Types of password attacks include dictionary attacks (which attempt to use common words and phrases) and brute force attacks (which try every possible combination of characters). Also, attackers sometimes try to obtain the account database so they can use tools to discover the accounts and passwords.</Vulnerability> <Countermeasure> Configure the Minimum password length setting to a value of 14 or more. If the number of characters is set to 0, no password will be required. In most environments, we recommend an 14-character password because it is long enough to provide adequate security but not too difficult for users to easily remember. This configuration provides adequate defense against a brute force attack. Using the Passwords must meet complexity requirements setting in addition to the Minimum password length setting helps reduce the possibility of a dictionary attack. </Countermeasure> <PotentialImpact> Requirements for extremely long passwords can actually decrease the security of an organization, because users might leave the information in an insecure location or lose it. If very long passwords are required, mistyped passwords could cause account lockouts and increase the volume of help desk calls. If your organization has issues with forgotten passwords due to password length requirements, consider teaching your users about pass phrases, which are often easier to remember and, due to the larger number of character combinations, much harder to discover. Note Older versions of Windows such as Windows 98 and Windows NT® 4.0 do not support passwords that are longer than 14 characters. Computers that run these older operating systems are unable to authenticate with computers or domains that use accounts that require long passwords. </PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="9999"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <Mapping FriendlyName="Not Defined"> <BehaviorDescription /> <DCMValue ValueA="Not Defined" /> <SCAPValue ValueA="Not Defined" /> <GPOValue ValueA="Not Defined" /> </Mapping> <Mapping FriendlyName="Not Configured"> <BehaviorDescription /> <DCMValue ValueA="Not Configured" /> <SCAPValue ValueA="Not Configured" /> <GPOValue ValueA="Not Configured" /> </Mapping> <Mapping FriendlyName="Not Applicable"> <BehaviorDescription /> <DCMValue ValueA="Not Applicable" /> <SCAPValue ValueA="Not Applicable" /> <GPOValue ValueA="Not Applicable" /> </Mapping> <Mapping FriendlyName="Not Recommended"> <BehaviorDescription /> <DCMValue ValueA="Not 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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="WMI" Scope="Machine"> <WMIDiscoveryInfo> <mssasc-core:Namespace xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">root\rsop\computer</mssasc-core:Namespace> <mssasc-core:Class xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">RSOP_SecuritySettingNumeric</mssasc-core:Class> <mssasc-core:Property xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">Setting</mssasc-core:Property> <mssasc-core:Where xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">KeyName = 'MinimumPasswordLength' And precedence=1</mssasc-core:Where> </WMIDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="INF"> <Inf SectionName="System Access" Name="MinimumPasswordLength" DataType="REG_DWORD" /> <OVAL> <Reference source="" ref_id="oval:gov.nist.1:def:19" ref_url="" /> </OVAL> </ExportInfo> <Comment> Added Setting, there is a problem here, we can't define operation, it should >=. This is also domain setting using RSPO WMI interface. ASM uses secedit. </Comment> </Setting> <Setting Index="222" ID="{6f6a3805-b798-4d65-a61c-89f07554e7e3}" OriginalSettingID="{417af2b2-2dc5-40f3-bfba-d157eaa6b523}" Name="Password must meet complexity requirements" LockdownDate="2014-02-22T03:48:26Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10901-7"> <Description> </Description> </CCEID-50> <ShortDescription>This policy setting checks all new password to ensure that they meet basic requirements for strong password.</ShortDescription> <FullDescription> This policy setting checks all new passwords to ensure that they meet basic requirements for strong passwords. When this policy is enabled, passwords must meet the following minimum requirements: - Not contain the user's account name or parts of the user's full name that exceed two consecutive characters - Be at least six characters in length - Contain characters from three of the following four categories: - English uppercase characters (A through Z) - English lowercase characters (a through z) - Base 10 digits (0 through 9) - Non-alphabetic characters (for example, !, $, #, %) - A catch-all category of any Unicode character that does not fall under the previous four categories. This fifth category can be regionally specific. Each additional character in a password increases its complexity exponentially. For instance, a seven-character, all lower-case alphabetic password would have 267 (approximately 8 x 109 or 8 billion) possible combinations. At 1,000,000 attempts per second (a capability of many password-cracking utilities), it would only take 133 minutes to crack. A seven-character alphabetic password with case sensitivity has 527 combinations. A seven-character case-sensitive alphanumeric password without punctuation has 627 combinations. An eight-character password has 268 (or 2 x 1011) possible combinations. Although this might seem to be a large number, at 1,000,000 attempts per second it would take only 59 hours to try all possible passwords. Remember, these times will significantly increase for passwords that use ALT characters and other special keyboard characters such as "!" or "@". Proper use of the password settings can help make it difficult to mount a brute force attack. </FullDescription> <UIPath>Computer Configuration\Windows Settings\Security Settings\Account Policies\Password Policy</UIPath> <DefaultValue>Disabled</DefaultValue> <Vulnerability>Passwords that contain only alphanumeric characters are extremely easy to discover with several publicly available tools.</Vulnerability> <Countermeasure> Configure the Passwords must meet complexity requirements setting to Enabled and advise users to use a variety of characters in their passwords. When combined with a Minimum password length of 8, this policy setting ensures that the number of different possibilities for a single password is so great that it will be difficult (but not impossible) for a brute force attack to succeed. (If the Minimum password length setting is increased, the average amount of time necessary for a successful attack also increases.) </Countermeasure> <PotentialImpact> If the default password complexity configuration is retained, additional help desk calls for locked-out accounts could occur because users might not be accustomed to passwords that contain non-alphabetic characters. However, all users should be able to comply with the complexity requirement with minimal difficulty. If your organization has more stringent security requirements, you can create a custom version of the Passfilt.dll file that allows the use of arbitrarily complex password strength rules. For example, a custom password filter might require the use of non-upper row characters. (Upper row characters are those that require you to hold down the SHIFT key and press any of the digits between 1 and 0.) A custom password filter might also perform a dictionary check to verify that the proposed password does not contain common dictionary words or fragments. Also, the use of ALT key character combinations can greatly enhance the complexity of a password. However, such stringent password requirements can result in unhappy users and an extremely busy help desk. Alternatively, your organization could consider a requirement for all administrator passwords to use ALT characters in the 0128–0159 range. (ALT characters outside of this range can represent standard alphanumeric characters that would not add additional complexity to the password.) </PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="0"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" 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="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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="WMI" Scope="Machine"> <WMIDiscoveryInfo> <mssasc-core:Namespace xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">root\rsop\computer</mssasc-core:Namespace> <mssasc-core:Class xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">RSOP_SecuritySettingBoolean</mssasc-core:Class> <mssasc-core:Property xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">Setting</mssasc-core:Property> <mssasc-core:Where xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">KeyName = 'PasswordComplexity' And precedence=1</mssasc-core:Where> </WMIDiscoveryInfo> </SettingDiscoveryInfo> <DataType>String</DataType> </DiscoveryInfo> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="INF"> <Inf SectionName="System Access" Name="PasswordComplexity" DataType="WMI_Boolean" /> <OVAL> <Reference source="" ref_id="oval:gov.nist.1:def:21" ref_url="" /> </OVAL> </ExportInfo> <Comment> Added Setting, there is a problem here, we can't define operation, it should >=. This is also domain setting using RSPO WMI interface. ASM uses secedit. </Comment> </Setting> <Setting Index="229" ID="{df07738d-5931-419d-8235-6f5e7c593126}" OriginalSettingID="{a4ebb3e9-373c-45b6-aa4a-7873852ce583}" Name="Maximum password age" LockdownDate="2014-03-09T09:13:41Z" GenerateDCM="true" GenerateSCAP="false" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10562-7"> <Description> </Description> </CCEID-50> <ShortDescription>This policy setting defines how long a user can use their password before it expires.</ShortDescription> <FullDescription> This policy setting defines how long a user can use their password before it expires. Values for this policy setting range from 0 to 999 days. If you set the value to 0, the password will never expire. The default value for this policy setting is 42 days. Because attackers can crack passwords, the more frequently you change the password the less opportunity an attacker has to use a cracked password. However, the lower this value is set, the higher the potential for an increase in calls to help desk support due to users having to change their password or forgetting which password is current. </FullDescription> <UIPath>Computer Configuration\Windows Settings\Security Settings\Account Policies\Password Policy</UIPath> <DefaultValue>42 days</DefaultValue> <Vulnerability>The longer a password exists the higher the likelihood that it will be compromised by a brute force attack, by an attacker gaining general knowledge about the user, or by the user sharing the password. Configuring the Maximum password age setting to 0 so that users are never required to change their passwords is a major security risk because that allows a compromised password to be used by the malicious user for as long as the valid user is authorized access.</Vulnerability> <Countermeasure>Configure the Maximum password age setting to a value that is suitable for your organization’s business requirements. When configuring this setting you should also configure the Minimum password age to a value that makes sense in combination with this one.</Countermeasure> <PotentialImpact>If the Maximum password age setting is too low, users are required to change their passwords very often. Such a configuration can reduce security in the organization, because users might write their passwords in an insecure location or lose them. If the value for this policy setting is too high, the level of security within an organization is reduced because it allows potential attackers more time in which to discover user passwords or to use compromised accounts.</PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="9999"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <Mapping FriendlyName="Not Defined"> <BehaviorDescription /> <DCMValue ValueA="Not Defined" /> <SCAPValue ValueA="Not Defined" /> <GPOValue ValueA="Not Defined" /> </Mapping> <Mapping FriendlyName="Not Configured"> <BehaviorDescription /> <DCMValue ValueA="Not Configured" /> <SCAPValue ValueA="Not Configured" /> <GPOValue ValueA="Not Configured" /> </Mapping> <Mapping FriendlyName="Not Applicable"> <BehaviorDescription /> <DCMValue ValueA="Not Applicable" /> <SCAPValue ValueA="Not Applicable" /> <GPOValue ValueA="Not Applicable" /> </Mapping> <Mapping FriendlyName="Not Recommended"> <BehaviorDescription /> <DCMValue ValueA="Not 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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Script" Scope="Machine"> <ScriptDiscoveryInfo> <mssasc-core:ScriptType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">VBScript</mssasc-core:ScriptType> <mssasc-core:ScriptBody xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core"> Option Explicit WScript.Echo CheckRange("root\rsop\computer", "RSOP_SecuritySettingNumeric", "Setting", "KeyName='MaximumPasswordAge' And precedence=1", "{BaselineValue}") Function CheckRange(wmiNamespace, wmiClass, wmiProperty, wmiWhere, 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(wmiNamespace, wmiClass, wmiProperty, wmiWhere) '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(wmiNamespace, wmiClass, wmiProperty, wmiWhere) On Error Resume Next Err.Clear ' Get WMI data Dim objWMIService, strWQL, objSettings, objInstance Set objWMIService = GetObject("winmgmts:\\.\" + wmiNamespace) strWQL = "Select " + wmiProperty +" from " + wmiClass + " where " + wmiWhere Set objSettings = objWMIService.ExecQuery(strWQL) For Each objInstance in objSettings GetCurrentValue = objInstance.Setting Exit For Next ' 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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="INF"> <Inf SectionName="System Access" Name="MaximumPasswordAge" DataType="REG_DWORD" /> </ExportInfo> <Comment> Added Setting xtan: per the original Azure Excel sheet </Comment> </Setting> <Comment> </Comment> </SettingGroup> <SettingGroup ID="{556478e1-5663-4973-bde8-3a0be75e2eb4}" Name="Network Protection" OriginalSettingGroupID="{03bcd8af-665b-4502-b205-0b5beaa5a995}"> <mssasc-core:Description> </mssasc-core:Description> <mssasc-core:Version Major="1" Minor="0" /> <Author> </Author> <Setting Index="52" ID="{d5af2ea2-c4ad-49d8-af55-b0a6c1bde041}" OriginalSettingID="{e95c4963-098c-4bd8-bc1a-2980c12b506c}" Name="Windows Firewall: Private: Inbound connections" LockdownDate="2011-08-02T06:16:34Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10857-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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" refId="DefaultInboundActions" noSort="true" defaultItem="0">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="53" ID="{5270f303-206a-45df-b7a4-1d98e0ba3b0e}" OriginalSettingID="{21e5ee29-51b2-4719-b979-af03e47a128e}" Name="MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)" LockdownDate="2011-05-19T05:25:35Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10732-6"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="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>xtan: per original excel sheet, not defined </Comment> </Setting> <Setting Index="54" ID="{d0401a2f-a8b9-486d-8aed-204deb32ef39}" OriginalSettingID="{691c581a-3b42-408b-abbe-f0bea9de3156}" Name="Windows Firewall: Private: Outbound connections" LockdownDate="2011-08-02T06:16:34Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10123-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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="55" ID="{245d1612-ea25-42e9-97c8-02ea2a8b059c}" OriginalSettingID="{3fe3c052-d096-4bc2-8d03-7ddb03f3b1f6}" Name="Windows Firewall: Private: Allow unicast response" LockdownDate="2011-08-02T06:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10127-9"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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>per devendra's excel, use default</Comment> </Setting> <Setting Index="56" ID="{0ad79564-2846-45e3-9d1b-c95768004097}" OriginalSettingID="{75208064-559a-4412-8ca6-5da2d0e10cfd}" Name="Windows Firewall: Public: Outbound connections" LockdownDate="2011-04-28T12:36:07Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10481-0"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="57" ID="{36a80eb5-d25e-464e-ab5e-a70e2c96b305}" OriginalSettingID="{21d226de-3201-414e-a16a-b626b6d0cc26}" Name="MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)" LockdownDate="2011-05-19T05:25:35Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10888-6"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="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>xtan: per the original Azure Excel sheet, Not Defined</Comment> </Setting> <Setting Index="58" ID="{7ab49e87-2ab9-4f7b-b1d2-7be32e06d958}" OriginalSettingID="{1582b4ec-79f8-46f1-a4d6-901dd6e7d3ce}" Name="Windows Firewall: Public: Inbound connections" LockdownDate="2011-08-02T06:16:34Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10171-7"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" refId="DefaultInboundActions" noSort="true" defaultItem="0">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="59" ID="{1b5f0e1b-aa17-4dab-9c97-ac788ae5af2c}" OriginalSettingID="{968787a1-6a19-4c96-82dd-ca531f84666d}" Name="Windows Firewall: Public: Apply local firewall rules" LockdownDate="2011-04-28T12:36:07Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10188-1"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="60" ID="{9b95cd26-50b9-456f-8e98-5723f5a2c0d4}" OriginalSettingID="{62c711b9-cd72-4fd2-8596-bb90387278da}" Name="Windows Firewall: Domain: Outbound connections" LockdownDate="2011-04-28T12:36:07Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10113-9"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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> <Setting Index="61" ID="{0507a6c8-0219-40f6-86be-d6f948e32e47}" OriginalSettingID="{0a80cfc2-0dcd-4566-b4be-6d8224961f83}" Name="Windows Firewall: Domain: Apply local firewall rules" LockdownDate="2011-04-28T12:36:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10798-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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="62" ID="{6442ff6f-d388-42c2-a804-26a00036b127}" OriginalSettingID="{0091ec7e-714b-4bb3-9a36-a73412c6c1f9}" Name="Windows Firewall: Private: Display a notification" LockdownDate="2011-08-02T06:16:34Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10631-0"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="63" ID="{33c89fd1-1cd4-461c-8008-17e2efc277fe}" OriginalSettingID="{f5513338-0fa1-484e-83fb-9a5bd3954d44}" Name="Windows Firewall: Private: Apply local connection security rules" LockdownDate="2011-08-02T06:16:34Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10921-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="64" ID="{1c2e1a4b-2980-42f5-bc39-1d2f79a4971c}" OriginalSettingID="{856f9866-0378-4952-a164-4d524770bb2a}" Name="Windows Firewall: Public: Firewall state" LockdownDate="2011-04-28T12:36:07Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11050-2"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="65" ID="{351866dd-ce4d-4f13-8e17-f72d2381aeda}" OriginalSettingID="{902a957b-c9b3-4302-883a-394555087509}" Name="Windows Firewall: Public: Display a notification" LockdownDate="2011-05-06T11:35:38Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11120-3"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable SelectedFriendlyName="Yes"> <Mapping FriendlyName="Not Defined"> <BehaviorDescription /> <DCMValue ValueA="Not Defined" /> <SCAPValue ValueA="Not Defined" /> <GPOValue ValueA="Not Defined" /> </Mapping> <Mapping FriendlyName="Not Configured"> <BehaviorDescription /> <DCMValue ValueA="Not Configured" /> <SCAPValue ValueA="Not Configured" /> <GPOValue ValueA="Not Configured" /> </Mapping> <Mapping FriendlyName="Not Applicable"> <BehaviorDescription /> <DCMValue ValueA="Not Applicable" /> <SCAPValue ValueA="Not Applicable" /> <GPOValue ValueA="Not Applicable" /> </Mapping> <Mapping FriendlyName="Not Recommended"> <BehaviorDescription /> <DCMValue ValueA="Not 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="66" ID="{e1d6ad24-8993-4879-9121-d58c3777c7a5}" OriginalSettingID="{533bf252-df1b-4b5a-9320-8da18b19bcd2}" Name="Windows Firewall: Private: Apply local firewall rules" LockdownDate="2011-08-02T06:16:34Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10131-1"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="67" ID="{11a69901-de1c-4599-96de-e323e7017e0c}" OriginalSettingID="{96596e24-66e0-4347-961c-c52d6a410804}" Name="Windows Firewall: Domain: Inbound connections" LockdownDate="2011-04-28T12:36:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10997-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" refId="DefaultInboundActions" noSort="true" defaultItem="0">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="68" ID="{ec3aaedb-8cb5-45c9-82ec-e50a18d9f734}" OriginalSettingID="{01cfd956-48cc-4ad6-94ff-b8f7ca488a91}" Name="Windows Firewall: Public: Allow unicast response" LockdownDate="2011-10-29T10:08:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10873-8"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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>xtan: The original Azure baseline Excel sheet suggested using windows default which is YES. This increase the attack surface for malitious payload in broadcast. It indicates the current VM setting is Not Defined. I think it is safe to make Not Defined as recommendation from MS or CIS which is No</Comment> </Setting> <Setting Index="69" ID="{b04263ca-fc10-4d89-aaa1-cb388ea13dea}" OriginalSettingID="{849952c3-4163-4e4d-9320-138c4af87134}" Name="Windows Firewall: Public: Apply local connection security rules" LockdownDate="2011-04-28T12:36:07Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10529-6"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable SelectedFriendlyName="Yes"> <Mapping FriendlyName="Not Defined"> <BehaviorDescription /> <DCMValue ValueA="Not Defined" /> <SCAPValue ValueA="Not Defined" /> <GPOValue ValueA="Not Defined" /> </Mapping> <Mapping FriendlyName="Not Configured"> <BehaviorDescription /> <DCMValue ValueA="Not Configured" /> <SCAPValue ValueA="Not Configured" /> <GPOValue ValueA="Not Configured" /> </Mapping> <Mapping FriendlyName="Not Applicable"> <BehaviorDescription /> <DCMValue ValueA="Not Applicable" /> <SCAPValue ValueA="Not Applicable" /> <GPOValue ValueA="Not Applicable" /> </Mapping> <Mapping FriendlyName="Not Recommended"> <BehaviorDescription /> <DCMValue ValueA="Not 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="70" ID="{eb9e605c-74bd-433d-bd48-a20b616b243d}" OriginalSettingID="{d493f92b-2fe2-4489-a4e6-03fd2e3710cd}" Name="Windows Firewall: Private: Firewall state" LockdownDate="2011-08-02T06:16:34Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11103-9"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="71" ID="{2b627347-5932-4a63-9458-3c3be03012cd}" OriginalSettingID="{db12a482-5822-44ba-b35d-e944d3ddd528}" Name="Windows Firewall: Domain: Apply local connection security rules" LockdownDate="2011-04-28T12:36:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11036-1"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="144" ID="{f819013e-bb1d-4b2f-a412-605d023d03af}" OriginalSettingID="{0f319931-aa36-4313-9320-86311c0fa623}" Name="Network access: Restrict anonymous access to Named Pipes and Shares" LockdownDate="2011-10-09T10:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10940-5"> <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>Not Defined</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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="145" ID="{1ff9acbd-9502-449e-8190-abe5600525f1}" OriginalSettingID="{107f578e-ad55-4bf9-b108-a6477bb35892}" Name="Network access: Allow anonymous SID/Name translation" LockdownDate="2011-05-29T11:12:36Z" GenerateDCM="false" GenerateSCAP="false" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10024-8"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="147" ID="{b149d65d-ab8e-4978-aa97-098e23f8141e}" OriginalSettingID="{502cd61a-fec9-42f0-a096-1ac097bbdf73}" Name="Microsoft network server: Digitally sign communications (always)" LockdownDate="2011-08-02T06:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10992-6"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="148" ID="{0b0f3e44-3c02-49f9-8dc9-b928c67ceaeb}" OriginalSettingID="{c4f13e60-0fae-4766-bba1-00b4c33d54b7}" Name="Network access: Do not allow anonymous enumeration of SAM accounts" LockdownDate="2011-08-02T06:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10027-1"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="149" ID="{be75df5a-acf5-4dcc-846f-b59887b9d7ed}" OriginalSettingID="{e197f79b-a454-407c-9307-7b3210313e61}" Name="Network access: Let Everyone permissions apply to anonymous users" LockdownDate="2011-08-02T06:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10297-0"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="154" ID="{842b8a87-dfd5-4fb5-afac-5ce6535cde3e}" OriginalSettingID="{fbfb6cc4-d294-4884-bc3d-7f74deeb6462}" Name="Network access: Do not allow anonymous enumeration of SAM accounts and shares" LockdownDate="2011-04-28T12:36:03Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10557-7"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="156" ID="{ac1cb4ab-0043-434e-ac04-6113670e316b}" OriginalSettingID="{6e48c65a-e5dd-4d64-a6e9-dfd86742f91e}" Name="Network security: LDAP client signing requirements" LockdownDate="2011-04-28T12:36:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10614-6"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="157" ID="{0239af2e-7bef-4f73-ba18-1c879e8f5607}" OriginalSettingID="{ed734c3b-b27f-4515-9154-9f6f414e6564}" Name="Microsoft network client: Digitally sign communications (always)" LockdownDate="2011-04-28T12:36:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10970-2"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="159" ID="{c8539e2a-518c-439d-9fbe-52e47f4d7605}" OriginalSettingID="{1c96e719-94c8-4333-9165-6efb6a9c6210}" Name="Microsoft network server: Digitally sign communications (if client agrees)" LockdownDate="2011-08-02T06:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10978-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="161" ID="{1d73fbc4-ddc3-46e2-b89d-1683fd35be82}" OriginalSettingID="{9c88cdfc-58ad-4666-9e8a-d84099d42fdd}" Name="Network access: Remotely accessible registry paths and sub-paths" LockdownDate="2011-10-09T10:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10935-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="163" ID="{18a13c8c-6e88-4fe8-8a59-76ce952283c1}" OriginalSettingID="{817b2f4e-1f03-4bcc-927b-816ddd4777f9}" Name="Microsoft network client: Digitally sign communications (if server agrees)" LockdownDate="2011-04-28T12:36:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10974-4"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="164" ID="{ac06599d-73de-4e84-a7f9-b6ad81d13276}" OriginalSettingID="{ab05b768-9c4c-4ff7-a22b-45af430607a8}" Name="Network access: Remotely accessible registry paths" LockdownDate="2011-10-09T10:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10949-6"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="165" ID="{029d0857-80ca-44f5-a4b6-f739f0221aa9}" OriginalSettingID="{7c6c01fd-5c0d-4398-9de0-0a8855c4cd95}" Name="Network access: Sharing and security model for local accounts" LockdownDate="2011-10-09T10:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10825-8"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="223" ID="{e5b84241-75e1-4578-8b76-9c070095a456}" OriginalSettingID="{aa73099d-1954-4488-b76f-72cab4588003}" Name="Turn off downloading of print drivers over HTTP" LockdownDate="2014-02-13T05:20:04Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11563-4"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">Software\Policies\Microsoft\Windows NT\Printers</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">DisableWebPnPDownload</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <policy xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" name="DisableWebPnPDownload_2" class="Machine" displayName="$(string.31584d1f053247a4993492ace70829e2)" explainText="$(string.cfff593b61dd4e4d9227e6f9b58d0f9c)" key="Software\Policies\Microsoft\Windows NT\Printers" valueName="DisableWebPnPDownload"> <admx:supportedOn xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment>Added Setting </Comment> </Setting> <Setting Index="224" ID="{ad5e8cf0-e1ac-4667-b101-21bf0de845bb}" OriginalSettingID="{666f7df6-e8c1-4703-8cd1-3a367d445a8a}" Name="Turn off Internet download for Web publishing and online ordering wizards" LockdownDate="2014-02-13T05:21:18Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11136-9"> <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>Not configured</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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">Software\Microsoft\Windows\CurrentVersion\Policies\Explorer</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">NoWebServices</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <policy xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" name="ShellPreventWPWDownload_2" class="Machine" displayName="$(string.4077a05f702045f499d368102d29a583)" explainText="$(string.f2eef154b3a14b189acfc04548e3ca6a)" key="Software\Microsoft\Windows\CurrentVersion\Policies\Explorer" valueName="NoWebServices"> <admx:supportedOn xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment>Added Setting </Comment> </Setting> <Setting Index="225" ID="{0e750f63-94f3-4ee5-8956-191af9aefd4d}" OriginalSettingID="{ff93353b-e178-4aa5-bfb1-883c2e2b4af8}" Name="Turn off printing over HTTP" LockdownDate="2014-02-13T05:22:09Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11360-5"> <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>Not configured</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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">Software\Policies\Microsoft\Windows NT\Printers</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">DisableHTTPPrinting</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <policy xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" name="DisableHTTPPrinting_2" class="Machine" displayName="$(string.54706246121747c3a3f5a44c10e0189f)" explainText="$(string.1745de3ac5b54a1db1c08fd9affccc22)" key="Software\Policies\Microsoft\Windows NT\Printers" valueName="DisableHTTPPrinting"> <admx:supportedOn xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment>Added Setting </Comment> </Setting> <Comment> </Comment> </SettingGroup> <SettingGroup ID="{e8cc2b98-8d21-4797-8e98-cc28f3a6257b}" Name="Audit Policy" OriginalSettingGroupID="{bac1bfd8-e703-4e47-8712-0a451a256e88}"> <mssasc-core:Description> </mssasc-core:Description> <mssasc-core:Version Major="1" Minor="0" /> <Author> </Author> <Setting Index="72" ID="{2010d729-2830-4578-aa5c-e9bc99f44f66}" OriginalSettingID="{b5aecffd-079f-4217-bbf0-fb20af1d7a2e}" Name="Audit Policy: Account Management: Distribution Group Management" LockdownDate="2011-04-28T12:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10201-2"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="73" ID="{6387c003-9ed7-4207-98b5-4596732345f6}" OriginalSettingID="{2ea0de1a-c71d-46c8-8350-a7dd4d447895}" Name="Audit Policy: Account Management: Other Account Management Events" LockdownDate="2011-04-28T12:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11001-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="74" ID="{831fc482-1d5e-4918-87c8-b7adb1728591}" OriginalSettingID="{9f76d6a7-9fd2-49cc-851e-eb5e680cbb63}" Name="Audit Policy: Account Management: Application Group Management" LockdownDate="2011-04-28T12:35:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10746-6"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="75" ID="{31817c74-55a8-473c-965d-5b8748c5b0de}" OriginalSettingID="{e54d7bef-4406-4689-813c-ba14b3fd3ef8}" Name="Audit Policy: System: Security State Change" LockdownDate="2011-04-28T12:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11007-2"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="76" ID="{864fd407-4b0f-474d-9a2a-940668525875}" OriginalSettingID="{312054c9-efe6-4892-8441-77c0bcbfb8a2}" Name="Audit Policy: Account Logon: Kerberos Authentication Service" LockdownDate="2011-06-09T02:16:32Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11079-1"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="77" ID="{3bb15d3e-d350-4ccc-893a-a2f582427254}" OriginalSettingID="{72b0b48c-f755-44e5-9a80-9f2973e8589a}" Name="Audit Policy: Logon-Logoff: IPsec Extended Mode" LockdownDate="2011-04-28T12:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10961-1"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="78" ID="{a45dc25d-4adb-4da6-ad67-3ba82c3d110b}" OriginalSettingID="{5c16519e-7075-4814-8d32-1e05b869b7d3}" Name="Audit Policy: Object Access: Registry" LockdownDate="2011-07-09T10:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10224-4"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="79" ID="{9b5cef05-0c38-4137-a951-1ec03812703c}" OriginalSettingID="{c1aa5f37-73e5-4abf-85f5-601b5a28623c}" Name="Audit Policy: Object Access: File System" LockdownDate="2011-10-27T09:45:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10263-2"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="80" ID="{752b5794-5a8c-44ae-b048-2f0c65a1e30f}" OriginalSettingID="{2768f99a-87a1-4be6-bf44-efcfd1412dea}" Name="Audit Policy: Policy Change: Authentication Policy Change" LockdownDate="2011-04-28T12:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11160-9"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="81" ID="{1deb0360-7dbb-411b-970f-b4c0d3695cee}" OriginalSettingID="{4237d39f-ea09-47d6-96bb-91b199d9c384}" Name="Audit Policy: Logon-Logoff: Other Logon/Logoff Events" LockdownDate="2011-04-28T12:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10869-6"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="82" ID="{5a73f721-6f43-4bb0-bc02-32c01efd2439}" OriginalSettingID="{bd2f2b74-c1cb-4413-a92d-c4dfb73e7279}" Name="Audit Policy: Policy Change: Other Policy Change Events" LockdownDate="2011-04-28T12:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10680-7"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="83" ID="{29ebd2b0-b6bf-49b8-93d6-36017b2a1d83}" OriginalSettingID="{c6105a0f-00eb-4789-8ccb-06cf25b6add3}" Name="Audit Policy: DS Access: Detailed Directory Service Replication" LockdownDate="2011-06-09T02:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11056-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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="84" ID="{32e2c032-1461-489f-9566-3288cc3a468f}" OriginalSettingID="{6598ae0c-9227-4f87-b754-f68d2f5820fc}" Name="Audit Policy: Detailed Tracking: Process Creation" LockdownDate="2011-04-28T12:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10514-8"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="85" ID="{ff52c0bb-aea1-498f-94fe-fbb33375bb61}" OriginalSettingID="{b8fc1e7a-57fd-48a0-827e-f466b21663ae}" Name="Audit Policy: System: System Integrity" LockdownDate="2011-04-28T12:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11034-6"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="86" ID="{c2c411ee-2744-46b9-bf81-1713f8e56e25}" OriginalSettingID="{9c282479-a942-4863-9f47-84d94426eb33}" Name="Audit Policy: Logon-Logoff: IPsec Main Mode" LockdownDate="2011-04-28T12:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10948-8"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="87" ID="{bac5ad93-64c2-422a-a7b8-5c9da6174397}" OriginalSettingID="{abcedd04-373e-493b-8fc4-610ca4e2c11e}" Name="Audit Policy: Logon-Logoff: Logon" LockdownDate="2011-04-28T12:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11107-0"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="88" ID="{5ebe0373-a273-4c2c-ad2f-4d42409598bc}" OriginalSettingID="{4f7ecb8a-7516-42f4-ad65-89596bc987d2}" Name="Audit Policy: Object Access: Handle Manipulation" LockdownDate="2011-07-09T10:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10902-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="89" ID="{6f2ea732-6efe-4c42-9086-f30a6363a0f3}" OriginalSettingID="{6f40d10a-7998-417e-8718-1f9a60d291b3}" Name="Audit Policy: Detailed Tracking: RPC Events" LockdownDate="2011-04-28T12:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11025-4"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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> <Setting Index="90" ID="{76f567b9-07c9-4aef-8a58-4c41db0327ce}" OriginalSettingID="{561441aa-7cd5-4875-81bb-80dc08355b26}" Name="Audit Policy: Policy Change: Authorization Policy Change" LockdownDate="2011-04-28T12:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10790-4"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="91" ID="{d13987f3-a86c-43e9-a934-6d2583b06201}" OriginalSettingID="{4b0a5f5f-f8e0-42ea-870e-4b935fde16a5}" Name="Audit Policy: Object Access: Other Object Access Events" LockdownDate="2011-07-09T10:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11170-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 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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="92" ID="{b721fbbe-86df-4baf-9ea4-2c7554d1e042}" OriginalSettingID="{b5b348f9-d7fd-4847-bbb1-0371ea5a3987}" Name="Audit Policy: Object Access: Certification Services" LockdownDate="2011-07-09T10:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10216-0"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="93" ID="{4fd2a029-547e-490d-8c37-9fc1ea7d9cf9}" OriginalSettingID="{aca80b6e-cedf-4dd1-8ecb-ec364e4caa4d}" Name="Audit Policy: Logon-Logoff: Network Policy Server" LockdownDate="2011-10-09T10:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10847-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 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>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 (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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="94" ID="{30147e6d-0078-4086-ba10-0ad9b3990e08}" OriginalSettingID="{abc8294e-c8cc-4edf-998e-b423d9936c77}" Name="Audit Policy: Detailed Tracking: DPAPI Activity" LockdownDate="2011-04-28T12:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10761-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="95" ID="{1a2564bc-8cf4-40e1-9a43-733a753629e7}" OriginalSettingID="{f3179229-59a3-4c89-8eb2-45cdf42660b1}" Name="Audit Policy: Logon-Logoff: Special Logon" LockdownDate="2011-04-28T12:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10737-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="96" ID="{16e6b535-93b8-44d6-ac52-4edd98f80260}" OriginalSettingID="{f0238fe5-80bc-4feb-83a7-3e70bd621d83}" Name="Audit Policy: Object Access: Kernel Object" LockdownDate="2011-07-09T10:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10220-2"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="97" ID="{6550cbe2-10e6-442d-87c2-97b7ec891ad3}" 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-02T06:16:32Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10112-1"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="98" ID="{2b1ced96-3a71-46e1-8cb1-f50f612357a5}" OriginalSettingID="{79a516e0-3fc6-4173-b412-a7532f0c604d}" Name="Audit Policy: Object Access: SAM" LockdownDate="2011-07-09T10:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10491-9"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="99" ID="{82e7501d-04fd-433c-bb42-f6d53907fce1}" OriginalSettingID="{17bbd596-ee57-4506-b4eb-b8914b2d8b34}" Name="Audit Policy: Account Management: User Account Management" LockdownDate="2011-04-28T12:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10203-8"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="100" ID="{e167d977-870f-4ef4-b146-af0f0fa1bb43}" OriginalSettingID="{5bd3a1dc-6de8-4021-a1a7-f1cf51f51235}" Name="Audit Policy: System: Security System Extension" LockdownDate="2011-04-28T12:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11029-6"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="101" ID="{8baffdc0-9a5c-4376-a54a-c403c9eb5f4e}" OriginalSettingID="{39b1c554-31f2-4119-9139-d2d4f083f9b1}" Name="Audit Policy: Account Logon: Kerberos Service Ticket Operations" LockdownDate="2011-10-09T10:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10196-4"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="102" ID="{1be1f452-745f-4b80-bb41-243eb322da22}" OriginalSettingID="{b76ef57e-563d-4741-a283-865d37250ca8}" Name="Audit Policy: Object Access: Filtering Platform Packet Drop" LockdownDate="2011-07-09T10:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11148-4"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="103" ID="{8e63e8b4-74ee-4a03-bde1-2fd4fb31a90f}" OriginalSettingID="{866ba9bb-ea1e-45bc-aa8a-4700d56615f4}" Name="Audit Policy: Privilege Use: Other Privilege Use Events" LockdownDate="2011-04-28T12:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10593-2"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="104" ID="{49bfcc2d-29ea-4b7b-9957-c7cad20e8643}" OriginalSettingID="{08d34924-4c27-4af4-8d2b-ed772f0c992e}" Name="Audit Policy: Object Access: Application Generated" LockdownDate="2011-07-09T10:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11111-2"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="105" ID="{83584dcf-369d-4175-a8a2-d830838482eb}" OriginalSettingID="{591401f2-3712-4434-ae22-e8633dcf2ad5}" Name="Audit Policy: Privilege Use: Sensitive Privilege Use" LockdownDate="2011-04-28T12:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11003-1"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="106" ID="{f999aa39-ba73-48a7-9492-5f50a31f04f5}" OriginalSettingID="{0e6bf82f-4268-4f02-82a6-64ab3f2adab9}" Name="Audit Policy: DS Access: Directory Service Replication" LockdownDate="2011-04-28T12:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10206-1"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="107" ID="{d483785a-4e9b-4b42-8ce5-fda2cd396324}" OriginalSettingID="{846ed96d-48c5-4ea0-a6e3-965e4a000cb4}" Name="Audit Policy: Policy Change: Filtering Platform Policy Change" LockdownDate="2011-04-28T12:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10526-2"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="108" ID="{27311858-1d89-4cc3-b374-0a4bb1e370b2}" OriginalSettingID="{821af41f-7ff7-4dae-a841-c098b7112b0c}" Name="Audit Policy: Policy Change: Audit Policy Change" LockdownDate="2011-04-28T12:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10385-3"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="109" ID="{5494b66f-2664-4c73-873f-600330559866}" OriginalSettingID="{5e887dce-109d-4619-b532-731ad234824a}" Name="Audit Policy: DS Access: Directory Service Changes" LockdownDate="2011-04-28T12:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10800-1"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="110" ID="{e9f25f6e-e27e-4d24-9bdd-7fff0613609d}" OriginalSettingID="{c1802c70-87b8-4167-867b-2d93fd66b826}" Name="Audit Policy: Object Access: File Share" LockdownDate="2011-07-09T10:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11021-3"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="111" ID="{fb56d7a0-d1f6-457a-8d6b-7c8008807d86}" OriginalSettingID="{1f5ff83f-8640-48ae-9200-ea70a8f5bc9a}" Name="Audit Policy: Object Access: Detailed File Share" LockdownDate="2011-07-09T10:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10391-1"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="112" ID="{ffeffad3-0568-45d2-a51b-5976fffdd201}" OriginalSettingID="{a94d7f10-22ff-48e8-bd82-1dfc5ccb1cb4}" Name="Audit Policy: Account Management: Computer Account Management" LockdownDate="2011-06-09T02:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10860-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="113" ID="{d842cfc6-45f7-4220-b637-f2a3d62f18bc}" OriginalSettingID="{9f28bf93-31ae-4a09-b064-a391772fe13d}" Name="Audit Policy: Logon-Logoff: Logoff" LockdownDate="2011-06-09T02:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11102-1"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="114" ID="{c4c4d35d-6e34-4565-99fd-10dc89be3d9f}" OriginalSettingID="{56d671e2-8ff8-47cd-adeb-82fb86067598}" Name="Audit Policy: Account Management: Security Group Management" LockdownDate="2011-04-28T12:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10741-7"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="115" ID="{836dc8c5-6844-432f-a1d6-5bcb43043a66}" OriginalSettingID="{aad1ad34-9f4f-4c86-b29a-c6710169687c}" Name="Audit Policy: System: Other System Events" LockdownDate="2011-04-28T12:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10879-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="116" ID="{45c5dc4f-f872-4c11-94bc-d88964148db1}" OriginalSettingID="{070368c6-1f71-47ec-aecc-f999fe465565}" Name="Audit Policy: Detailed Tracking: Process Termination" LockdownDate="2011-04-28T12:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11038-7"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="117" ID="{a543572f-2f65-421c-97bf-f0710d0787fe}" OriginalSettingID="{48b4f45e-2950-4a72-a0da-66f87a4f6208}" Name="Audit Policy: Account Logon: Other Account Logon Events" LockdownDate="2011-04-28T12:35:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10445-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="118" ID="{a867bdd2-5fa3-4f96-9838-ef4522450b51}" OriginalSettingID="{4aebc02d-1987-41b1-878a-33e558e308be}" Name="Audit Policy: Privilege Use: Non Sensitive Privilege Use" LockdownDate="2011-04-28T12:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11173-2"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="119" ID="{c234429b-7d46-437c-b3ae-f6bfaf70c567}" OriginalSettingID="{9fae3ac5-92b8-41f6-817c-2357c3885be9}" Name="Audit Policy: Logon-Logoff: IPsec Quick Mode" LockdownDate="2011-04-28T12:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10706-0"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="120" ID="{175aa1cf-26f8-4d24-a39d-f241f55e1c22}" OriginalSettingID="{504f27d5-2540-48f2-9aa4-ee0eebc84728}" Name="Audit Policy: System: IPsec Driver" LockdownDate="2011-04-28T12:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10390-3"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="121" ID="{9497d4f9-d805-459b-9531-d053ce704891}" OriginalSettingID="{87497709-c19c-4769-9ea4-87af6f40db3d}" Name="Audit Policy: Object Access: Filtering Platform Connection" LockdownDate="2011-07-09T10:48:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10285-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. 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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="122" ID="{8d9ccb64-cca3-4f66-9d90-2fa0873f62d4}" OriginalSettingID="{ebd86e7c-c2be-461a-9db9-c4f9fd79e32f}" Name="Audit Policy: Account Logon: Credential Validation" LockdownDate="2011-06-09T02:16:32Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10192-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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="123" ID="{4098e6f2-4e6f-405d-bbfe-fcf0ea22b835}" OriginalSettingID="{390b33ac-8fa0-4c26-b15c-c2056743857e}" Name="Audit Policy: Policy Change: MPSSVC Rule-Level Policy Change" LockdownDate="2011-04-28T12:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10530-4"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="124" ID="{31541f5d-3c65-48e3-b50b-23793cc9a5c0}" OriginalSettingID="{5c9c8613-01a7-4694-8550-778c7c1b5d4b}" Name="Audit Policy: DS Access: Directory Service Access" LockdownDate="2011-04-28T12:35:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10668-2"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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> <Comment> </Comment> </SettingGroup> <SettingGroup ID="{2578e84f-7e9a-4f47-abac-5f441ed024f2}" Name="Logging Configuration" OriginalSettingGroupID="{f90ec2e7-74c3-45a6-b08b-b486e09cee02}"> <mssasc-core:Description> </mssasc-core:Description> <mssasc-core:Version Major="1" Minor="0" /> <Author> </Author> <Setting Index="125" ID="{14fa680f-80c2-4046-95b8-e66630e86cd9}" OriginalSettingID="{67df32ce-77ba-4def-ab25-61536d146e60}" Name="Maximum Application Log Size (KB)" LockdownDate="2012-02-27T04:28:10Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11143-5"> <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>15168 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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" refId="Channel_LogMaxSize" defaultValue="1024">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>Has to be reviewed with Devendra and Kurt</Comment> </Setting> <Setting Index="126" ID="{51a9d10d-f947-4101-a3b7-686df36aa4df}" OriginalSettingID="{450b73e6-5bad-4c64-8d1f-abffea2f08d7}" Name="Retain old Application events" LockdownDate="2011-10-09T10:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10918-1"> <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>Disabled</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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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="127" ID="{954fc693-9491-4d0e-b76e-624e3ce0096f}" 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-02T06:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11011-4"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="128" ID="{600f3971-db99-4491-8ffb-6dacb64f7ff4}" OriginalSettingID="{e2e11f15-b46c-44f4-829d-5012808ca980}" Name="Retain old System events" LockdownDate="2011-10-09T10:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11055-1"> <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>Disabled</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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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="129" ID="{b25d9b50-7b04-411d-b4be-dce09389821b}" OriginalSettingID="{9b1bedaf-67d8-4d82-983e-300f0738996a}" Name="Maximum Security Log Size (KB)" LockdownDate="2012-02-27T04:23:05Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11033-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\Security</UIPath> <DefaultValue>102400 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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" refId="Channel_LogMaxSize" defaultValue="20480">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>Has to be reviewed with Devendra and Kurt</Comment> </Setting> <Setting Index="130" ID="{81ed1680-2a32-479f-9deb-9f19b6655a4f}" OriginalSettingID="{e9877eb1-8034-4347-86c1-d8e45f76e315}" Name="Maximum System Log Size (KB)" LockdownDate="2012-02-27T04:22:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11174-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\System</UIPath> <DefaultValue>15168 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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" refId="Channel_LogMaxSize" defaultValue="1024">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>Has to be reviewed with Devendra and Kurt</Comment> </Setting> <Setting Index="131" ID="{1e31b25c-6e25-4816-aaa7-6fb2173bbeca}" OriginalSettingID="{25c67f65-0d37-41d5-9e75-72707c97a290}" Name="Audit: Shut down system immediately if unable to log security audits" LockdownDate="2011-04-28T12:35:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10742-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="132" ID="{c110c874-a0db-4c24-90b9-58ea0e38a02c}" OriginalSettingID="{76e64466-6461-4950-95ae-dd69521f5b10}" Name="Retain old Security events" LockdownDate="2011-10-09T10:37:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10663-3"> <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>Disabled</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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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 xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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> <Comment> </Comment> </SettingGroup> <SettingGroup ID="{f182b2f1-6ba4-44e3-b9f8-e934e1acda91}" Name="Authentication" OriginalSettingGroupID="{d88c754c-8dd0-41e3-a00e-17722b7bcf75}"> <mssasc-core:Description> </mssasc-core:Description> <mssasc-core:Version Major="1" Minor="0" /> <Author> </Author> <Setting Index="133" ID="{87b67dfd-0050-46be-b059-7a5bc27450d6}" OriginalSettingID="{9969a7db-5fd1-4713-9a26-9862c15359e9}" Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) clients" LockdownDate="2011-10-09T10:37:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10035-4"> <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>No minimum</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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="135" ID="{dd870988-2b4c-4893-8121-8107e23ce62a}" OriginalSettingID="{794f9728-56e1-4e5e-b697-7079757f4ac3}" Name="Network security: Do not store LAN Manager hash value on next password change" LockdownDate="2011-10-09T10:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10830-8"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="136" ID="{0dbf2d2a-8241-4651-ba0e-fa44f21c205a}" OriginalSettingID="{402dc351-392a-4816-a26a-65a7bcc94087}" Name="Interactive logon: Smart card removal behavior" LockdownDate="2011-10-29T10:03:41Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10573-4"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="137" ID="{37a7c6aa-cec8-48e8-8696-ad205278c119}" OriginalSettingID="{17463ab9-ffc1-40ab-8b09-e8054ba4504c}" Name="Network security: Minimum session security for NTLM SSP based (including secure RPC) servers" LockdownDate="2011-10-09T10:37:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10040-4"> <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>No minimum</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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="139" ID="{8ea9ed06-2613-4007-b957-bc45ef84c196}" 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-11T04:26:30Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10926-4"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="140" ID="{c131f351-2c48-4368-87be-c6d02782f531}" OriginalSettingID="{096b92bd-142b-4c28-985f-f3ba1322265f}" Name="Interactive logon: Require Domain Controller authentication to unlock workstation" LockdownDate="2011-04-28T12:36:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10705-2"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="141" ID="{a0b0d923-27e7-4a27-9eb2-f5816e408983}" OriginalSettingID="{ec468e43-6141-4bfe-970f-ca02d37d0ca7}" Name="Network security: LAN Manager authentication level" LockdownDate="2011-10-09T10:37:58Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10984-3"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="197" ID="{d87bc7fb-eb43-4485-8611-38a6846627c8}" OriginalSettingID="{9e5ba301-4a84-4069-a398-7de2932b1e8f}" Name="Accounts: Guest account status" LockdownDate="2011-08-18T09:48:30Z" GenerateDCM="false" GenerateSCAP="false" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-9989-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="234" ID="{9879927b-0fed-44e0-bef6-b356c96c23b2}" OriginalSettingID="{f2996b93-b513-49bf-a16d-a4cd99132ec2}" Name="Require user authentication for remote connections by using Network Level Authentication" LockdownDate="2014-08-29T11:01:17Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10338-2"> <Description> </Description> </CCEID-50> <ShortDescription>Require user authentication for remote connections by using Network Level Authentication</ShortDescription> <FullDescription>This policy setting allows you to specify whether to require user authentication for remote connections to the RD Session Host server by using Network Level Authentication. This policy setting enhances security by requiring that user authentication occur earlier in the remote connection process. If you enable this policy setting, only client computers that support Network Level Authentication can connect to the RD Session Host server. To determine whether a client computer supports Network Level Authentication, start Remote Desktop Connection on the client computer, click the icon in the upper-left corner of the Remote Desktop Connection dialog box, and then click About. In the About Remote Desktop Connection dialog box, look for the phrase "Network Level Authentication supported." If you disable or do not configure this policy setting, Network Level Authentication is not required for user authentication before allowing remote connections to the RD Session Host server. You can specify that Network Level Authentication be required for user authentication by using Remote Desktop Session Host Configuration tool or the Remote tab in System Properties. Important: Disabling or not configuring this policy setting provides less security because user authentication will occur later in the remote connection process. </FullDescription> <UIPath>Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security</UIPath> <DefaultValue> </DefaultValue> <Vulnerability> </Vulnerability> <Countermeasure> </Countermeasure> <PotentialImpact> </PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="0"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">UserAuthentication</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <policy xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" name="TS_USER_AUTHENTICATION_POLICY" class="Machine" displayName="$(string.99ef3f9b019b44f58922109f90dac919)" explainText="$(string.f7b5f902f4794e40944b722fece91b7f)" key="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" valueName="UserAuthentication"> <admx:supportedOn xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <string id="99ef3f9b019b44f58922109f90dac919">Require user authentication for remote connections by using Network Level Authentication</string> <string id="f7b5f902f4794e40944b722fece91b7f">This policy setting allows you to specify whether to require user authentication for remote connections to the RD Session Host server by using Network Level Authentication. This policy setting enhances security by requiring that user authentication occur earlier in the remote connection process. If you enable this policy setting, only client computers that support Network Level Authentication can connect to the RD Session Host server. To determine whether a client computer supports Network Level Authentication, start Remote Desktop Connection on the client computer, click the icon in the upper-left corner of the Remote Desktop Connection dialog box, and then click About. In the About Remote Desktop Connection dialog box, look for the phrase "Network Level Authentication supported." If you disable or do not configure this policy setting, Network Level Authentication is not required for user authentication before allowing remote connections to the RD Session Host server. You can specify that Network Level Authentication be required for user authentication by using Remote Desktop Session Host Configuration tool or the Remote tab in System Properties. Important: Disabling or not configuring this policy setting provides less security because user authentication will occur later in the remote connection process. </string> </ADMLDefinition> <supportedOn>Unspecified</supportedOn> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment>Added Setting Per Nessus scan finding, TFS ID(s) 1429354 and 1429309, Nessus Plugin ID 58453 and 18405 Turn on monitoring and start learning which services can't support it before large deployment.</Comment> </Setting> <Comment> </Comment> </SettingGroup> <SettingGroup ID="{6b02e89d-8cb7-4f32-9d21-3fd49d39b895}" Name="Least Privilege" OriginalSettingGroupID="{ab9587df-1abd-49c5-b808-9436ffb756fd}"> <mssasc-core:Description> </mssasc-core:Description> <mssasc-core:Version Major="1" Minor="0" /> <Author> </Author> <Setting Index="171" ID="{22e26ced-34e2-42ce-ba97-4e7d967c33bb}" OriginalSettingID="{b61bd492-74b0-40f3-909d-36b9bf54e94c}" Name="Increase a process working set" LockdownDate="2011-05-19T06:27:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10548-6"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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>xtan: the original Azure Excel sheet suggestted the default which is Users, that seems weak. The recent reports showed this part of the setting is not consistent at all. Needs team discussion.</Comment> </Setting> <Setting Index="172" ID="{35830c81-b6b8-4b14-9907-3761b7e139ab}" OriginalSettingID="{591bd8ac-a5b3-41cc-8978-2bce50123a00}" Name="Debug programs" LockdownDate="2011-04-28T12:36:00Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10915-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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="174" ID="{d7ec0317-708c-4274-809f-224fe2f06d45}" OriginalSettingID="{d2197a4c-19f4-4630-b15a-aaf85c813045}" Name="Deny log on locally" LockdownDate="2011-10-09T10:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10750-8"> <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>Guests</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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="175" ID="{a67b797e-c129-4a25-ba26-cf34e33a558f}" OriginalSettingID="{eba90e79-8551-416f-9258-a48e1d9a60c7}" Name="Increase scheduling priority" LockdownDate="2011-05-19T06:27:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-9961-4"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="176" ID="{b3c78a52-a565-4d52-9944-52b07cc2455f}" OriginalSettingID="{485ea1c9-091c-434b-b8e0-c9d8cbfde052}" Name="Enable computer and user accounts to be trusted for delegation" LockdownDate="2011-10-09T10:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10618-7"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="177" ID="{a17804d8-98a5-4300-98dd-1ff45c32e442}" OriginalSettingID="{6630b24b-754a-49a5-9750-188ae53c13b9}" Name="Manage auditing and security log" LockdownDate="2011-04-28T12:36:02Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10726-8"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="178" ID="{ba25b6e3-16fc-46a9-a5b2-18e71080c4b2}" OriginalSettingID="{204ff604-1cab-46c8-aa22-01e7d78925e4}" Name="Shut down the system" LockdownDate="2012-02-27T04:11:43Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10439-8"> <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</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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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> <Setting Index="179" ID="{745eceb6-02c1-421c-a901-19bb8f7e58e5}" OriginalSettingID="{4e63307f-262d-4242-8210-c7753d029bef}" Name="Load and unload device drivers" LockdownDate="2011-04-28T12:36:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10202-0"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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>CIS is not defined</Comment> </Setting> <Setting Index="180" ID="{b727fae4-1c3d-4df4-b3a9-af2f56594b97}" OriginalSettingID="{38165ccc-d675-481c-8881-231a5c2032f9}" Name="Lock pages in memory" LockdownDate="2011-10-09T10:37:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10955-3"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="181" ID="{df236122-5bec-4d70-9779-01af4e3fab2c}" OriginalSettingID="{23a1c3b4-4d38-4153-854a-e315ad699d9b}" Name="Allow log on locally" LockdownDate="2012-02-27T04:00:22Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10853-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>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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="182" ID="{ee2f7f2a-7c63-4738-84f6-80adca85d2b1}" OriginalSettingID="{3ebdc510-830f-4520-9bce-2fe8f4f88b3f}" Name="Generate security audits" LockdownDate="2011-04-28T12:36:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10274-9"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="183" ID="{ba4498d2-9c57-437a-987d-e23715f89aba}" OriginalSettingID="{4b696c3e-dd2c-4d5e-bb0a-d7190de2c322}" Name="Adjust memory quotas for a process" LockdownDate="2011-05-19T05:59:59Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10849-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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="184" ID="{3846e648-ac41-4a1a-8eee-fd5b5f32307d}" OriginalSettingID="{b9af2cf2-1528-469c-b7e8-3787c4513479}" Name="Deny access to this computer from the network" LockdownDate="2011-10-09T10:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10733-4"> <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>guests</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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="185" ID="{a6847356-7858-4a2f-88c9-1bd2e51d9b3b}" OriginalSettingID="{a9411a96-e13f-4b37-ab31-b84a06d63460}" Name="Devices: Prevent users from installing printer drivers" LockdownDate="2011-06-10T11:39:05Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-9999-4"> <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>Enabled</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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="186" ID="{a32e24bf-093e-47ca-be50-54863b467b46}" OriginalSettingID="{8dcd558f-d276-493c-86e4-b259adab009b}" Name="Remove computer from docking station" LockdownDate="2012-02-27T04:10:10Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10969-4"> <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</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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="187" ID="{4466f092-301f-4c80-8933-ab479ccadfbb}" OriginalSettingID="{78c974e6-940e-4fec-8697-73d0ed54943c}" Name="Allow log on through Remote Desktop Services" LockdownDate="2011-05-11T04:27:14Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10858-9"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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='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="188" ID="{257c4081-0278-4785-a6a6-8c44653cfdb7}" OriginalSettingID="{8797b752-5346-436e-8502-cd5031cc77d5}" Name="Deny log on as a batch job" LockdownDate="2011-10-09T10:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10596-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="189" ID="{da248703-5c1d-4c9f-8294-3b86b2222425}" OriginalSettingID="{f540aa73-5550-4058-9209-e268908611d5}" Name="Take ownership of files or other objects" LockdownDate="2011-05-11T04:26:31Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10954-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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="190" ID="{42c34fe5-f793-4ceb-91c8-1a614fe2acd1}" OriginalSettingID="{87691f9f-e18e-42c3-ac3c-621c7b30bdda}" Name="Impersonate a client after authentication" LockdownDate="2011-05-28T04:17:45Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-9946-5"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="191" ID="{b74c8d46-e23c-47b3-9f5a-1f37890b905f}" OriginalSettingID="{c3a6cfaf-1504-4d55-ace8-1ebc971d9ebc}" Name="Create global objects" LockdownDate="2011-11-05T09:56:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10792-0"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="192" ID="{5830a178-7a84-48f1-8bba-df5535aaee50}" OriginalSettingID="{48cf8aee-1c72-4c3e-9f2a-c6dfe8990219}" Name="Access this computer from the network" LockdownDate="2011-10-09T10:37:55Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10086-7"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="193" ID="{a6cfe6c4-2949-4e30-a2d7-335baf9c9721}" OriginalSettingID="{52a9b265-75cb-45a0-ac23-3e5d4fa566c2}" Name="Create a pagefile" LockdownDate="2011-05-19T06:27:57Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-9937-4"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="194" ID="{f588029b-66bd-40d8-bd0a-29a579aadc30}" OriginalSettingID="{c25cfa17-7dbb-4699-a9a9-f53962a70de9}" Name="Bypass traverse checking" LockdownDate="2011-10-09T10:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10369-7"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="195" ID="{c69f490d-63ba-4475-b3fc-27083773f07f}" OriginalSettingID="{b77b9700-3212-4d5f-9547-dbe8ffd32574}" Name="Act as part of the operating system" LockdownDate="2011-10-09T10:37:55Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10232-7"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="212" ID="{fcbb701f-88ab-4618-be42-55d2be230218}" OriginalSettingID="{8840018d-e63a-4e69-96a8-c06af7e963a8}" Name="Force shutdown from a remote system" LockdownDate="2011-04-28T12:36:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10785-4"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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>Added setting</Comment> </Setting> <Comment> </Comment> </SettingGroup> <SettingGroup ID="{b7a399cb-5ea8-4a09-b8a3-ccc5f947616e}" Name="System Integrity" OriginalSettingGroupID="{f3d4cdca-6bbb-485d-af2b-bf412be213b9}"> <mssasc-core:Description> </mssasc-core:Description> <mssasc-core:Version Major="1" Minor="0" /> <Author> </Author> <Setting Index="43" ID="{3cfdfcda-1c9f-4a63-8761-6efbaaff1cf4}" OriginalSettingID="{1b54fa32-2784-46e5-87cc-252478f7b322}" Name="Enforce user logon restrictions" LockdownDate="2014-02-22T01:01:25Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-00001-29873"> <Description> </Description> </CCEID-50> <ShortDescription>Determines whether the Kerberos Key Distribution Center (KDC) validates every request for a session ticket against the user rights policy of the target computer.</ShortDescription> <FullDescription>Kerberos policy settings determine Kerberos-related attributes of domain user accounts, such as the Maximum lifetime for user ticket and Enforce user logon restrictions settings. However, these policy settings are not used for stand-alone client computers because they do not participate in a domain.</FullDescription> <UIPath>Computer Configuration\Windows Settings\Security Settings\Account Policies\Kerberos Policy</UIPath> <DefaultValue>Enabled</DefaultValue> <Vulnerability>If you disable this policy setting, users could receive session tickets for services that they no longer have the right to use because the right was removed after they logged on.</Vulnerability> <Countermeasure>Configure the Enforce user logon restrictions 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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" 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="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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="WMI" Scope="Machine"> <WMIDiscoveryInfo> <mssasc-core:Namespace xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">root\rsop\computer</mssasc-core:Namespace> <mssasc-core:Class xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">RSOP_SecuritySettingBoolean</mssasc-core:Class> <mssasc-core:Property xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">Setting</mssasc-core:Property> <mssasc-core:Where xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">KeyName='TicketValidateClient' and precedence=1</mssasc-core:Where> </WMIDiscoveryInfo> </SettingDiscoveryInfo> <DataType>String</DataType> </DiscoveryInfo> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="INF"> <Inf SectionName="Kerberos Policy" Name="TicketValidateClient" DataType="WMI_Boolean" /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment>per Devendra sheet, use system default</Comment> </Setting> <Setting Index="198" ID="{055bbc50-4de1-4e78-80fd-321a607174ee}" OriginalSettingID="{7ff3401a-70b6-40fa-bb33-73024f591b93}" Name="User Account Control: Detect application installations and prompt for elevation" LockdownDate="2011-08-02T06:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10794-6"> <Description> </Description> </CCEID-50> <ShortDescription>This policy setting controls the behavior of application installation detection for the computer.</ShortDescription> <FullDescription>This policy setting controls the behavior of application installation detection for the computer. The options are: • 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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="199" ID="{86bf6fd4-7fe8-4c18-a74f-817a28f86d6b}" OriginalSettingID="{0d380cb0-a162-4dbb-b54b-d41a2a7f9036}" Name="User Account Control: Only elevate UIAccess applications that are installed in secure locations" LockdownDate="2011-08-02T06:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10570-0"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="200" ID="{28313a00-0b64-49c0-a199-7301c8887941}" OriginalSettingID="{92b9d876-9d87-460c-82ea-9e8bd94c21ad}" Name="System objects: Strengthen default permissions of internal system objects (e.g. Symbolic Links)" LockdownDate="2011-08-02T06:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11010-6"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="202" ID="{a0e9a455-1625-4a8a-831f-9f0bcf5614cf}" OriginalSettingID="{444439f0-8c54-4a1f-9e91-03533d9a69fb}" Name="User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop" LockdownDate="2011-04-28T12:36:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10534-6"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="203" ID="{4eb8bad7-0e87-483c-905f-f0cae5323360}" OriginalSettingID="{f50c62f4-6c34-466b-b495-54c834820a24}" Name="User Account Control: Virtualize file and registry write failures to per-user locations" LockdownDate="2011-04-28T12:36:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10865-4"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="204" ID="{f688e052-605c-48b5-9600-9ed46a34fe14}" OriginalSettingID="{d3ebc555-daf1-451f-88a1-61b1b5ac71b5}" Name="User Account Control: Only elevate executables that are signed and validated" LockdownDate="2011-08-02T06:16:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10922-3"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="206" ID="{a3596a1f-1ecb-4800-8750-6b2088657bc4}" OriginalSettingID="{5a0c69d4-3f9a-4c0c-afe9-89a70342a2f7}" Name="User Account Control: Behavior of the elevation prompt for standard users" LockdownDate="2011-10-21T12:48:30Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10807-6"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable SelectedFriendlyName="Prompt for credentials"> <Mapping FriendlyName="Not Defined"> <BehaviorDescription /> <DCMValue ValueA="Not Defined" /> <SCAPValue ValueA="Not Defined" /> <GPOValue ValueA="Not Defined" /> </Mapping> <Mapping FriendlyName="Not Configured"> <BehaviorDescription /> <DCMValue ValueA="Not Configured" /> <SCAPValue ValueA="Not Configured" /> <GPOValue ValueA="Not Configured" /> </Mapping> <Mapping FriendlyName="Not Applicable"> <BehaviorDescription /> <DCMValue ValueA="Not Applicable" /> <SCAPValue ValueA="Not Applicable" /> <GPOValue ValueA="Not Applicable" /> </Mapping> <Mapping FriendlyName="Not Recommended"> <BehaviorDescription /> <DCMValue ValueA="Not 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="207" ID="{b2825c9d-9d7b-4dd7-b4e2-22a9d6d2999a}" OriginalSettingID="{5fbabdf6-6786-46f6-b959-596af69f2650}" Name="User Account Control: Admin Approval Mode for the Built-in Administrator account" LockdownDate="2011-04-28T12:36:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11028-8"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="208" ID="{1ee1c8ec-d5bd-4f15-b9ed-31c95bed7f28}" OriginalSettingID="{ef509260-bd3a-450b-807d-16b454851c6f}" Name="User Account Control: Run all administrators in Admin Approval Mode" LockdownDate="2011-04-28T12:36:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10684-9"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="209" ID="{a37311b1-65b5-435c-9122-32137c99168f}" OriginalSettingID="{a43ef40c-3543-4204-a431-0f01df930b63}" Name="User Account Control: Switch to the secure desktop when prompting for elevation" LockdownDate="2011-04-28T12:36:06Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10109-7"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <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="210" ID="{9777622a-3415-4141-b3c3-6b739db9c40c}" OriginalSettingID="{48974513-39ec-472c-9ee8-5cb8abf3cb64}" Name="User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode" LockdownDate="2011-10-21T12:48:30Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11023-9"> <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. </PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="0"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable SelectedFriendlyName="Prompt for consent for non-Windows binaries"> <Mapping FriendlyName="Not Defined"> <BehaviorDescription /> <DCMValue ValueA="Not Defined" /> <SCAPValue ValueA="Not Defined" /> <GPOValue ValueA="Not Defined" /> </Mapping> <Mapping FriendlyName="Not Configured"> <BehaviorDescription /> <DCMValue ValueA="Not Configured" /> <SCAPValue ValueA="Not Configured" /> <GPOValue ValueA="Not Configured" /> </Mapping> <Mapping FriendlyName="Not Applicable"> <BehaviorDescription /> <DCMValue ValueA="Not Applicable" /> <SCAPValue ValueA="Not Applicable" /> <GPOValue ValueA="Not Applicable" /> </Mapping> <Mapping FriendlyName="Not Recommended"> <BehaviorDescription /> <DCMValue ValueA="Not 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="Elevate without prompting"> <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> <Mapping FriendlyName="prompt for consent on the secure desktop"> <BehaviorDescription /> <DCMValue ValueA="2" /> <SCAPValue ValueA="2" /> <GPOValue ValueA="2" /> </Mapping> <Mapping FriendlyName="Prompt for credentials"> <BehaviorDescription /> <DCMValue ValueA="3" /> <SCAPValue ValueA="3" /> <GPOValue ValueA="3" /> </Mapping> <Mapping FriendlyName="Prompt for consent"> <BehaviorDescription /> <DCMValue ValueA="4" /> <SCAPValue ValueA="4" /> <GPOValue ValueA="4" /> </Mapping> <Mapping FriendlyName="Prompt for consent for non-Windows binaries"> <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>Software\Microsoft\Windows\CurrentVersion\Policies\System</mssasc-core:KeyPath> <mssasc-core:ValueName>ConsentPromptBehaviorAdmin</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <ExportInfo GPOGenerateFormat="INF"> <Inf SectionName="Registry Values" Name="MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\ConsentPromptBehaviorAdmin" DataType="REG_DWORD" /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment> </Comment> </Setting> <Setting Index="211" ID="{8ee4bb8c-ad79-48ec-99ae-98a2c54c6105}" OriginalSettingID="{c0e16984-8027-4753-af37-e7ed6f8d5aa9}" Name="Require trusted path for credential entry" LockdownDate="2014-03-08T05:30:33Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-12070-9"> <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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">EnableSecureCredentialPrompting</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <policy xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" name="EnableSecureCredentialPrompting" class="Machine" displayName="$(string.3cdad371738b4d0abc2aabfe0a9f69b2)" explainText="$(string.e7a4d9807ee9434a854f7b024d019ed7)" key="SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI" valueName="EnableSecureCredentialPrompting"> <admx:supportedOn xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment> Added Setting xtan: the original Azure excel sheet suggested using default but the default is Not configured. I recommend to enabled it. This may invoke large # of failure. </Comment> </Setting> <Comment> </Comment> </SettingGroup> <SettingGroup ID="{cc6c07fb-b4fe-4cfa-9d45-a351659f76ca}" Name="Account Lockout" OriginalSettingGroupID="{c48005de-0fa6-481b-ac6f-93dc5d708cec}"> <mssasc-core:Description>This setting group includes all Account Lockout Settings</mssasc-core:Description> <mssasc-core:Version Major="0" Minor="0" /> <Author> </Author> <Setting Index="230" ID="{b2a24f45-fab7-4aab-8dc7-ea4321a14784}" OriginalSettingID="{6ced94d3-42e8-4e42-b352-8a19f18c6aa0}" Name="Reset account lockout counter after" LockdownDate="2014-05-13T12:57:01Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11059-3"> <Description> </Description> </CCEID-50> <ShortDescription>This policy setting determines the length of time before the Account lockout threshold resets to zero. </ShortDescription> <FullDescription>This policy setting determines the length of time before the Account lockout threshold resets to zero. The default value for this policy setting is Not Defined. If the Account lockout threshold is defined, this reset time must be less than or equal to the value for the Account lockout duration setting. If you leave this policy setting at its default value or configure the value to an interval that is too long, your environment could be vulnerable to a DoS attack. An attacker could maliciously perform a number of failed logon attempts on all users in the organization, which will lock out their accounts. If no policy were determined to reset the account lockout, it would be a manual task for administrators. Conversely, if a reasonable time value is configured for this policy setting, users would be locked out for a set period until all of the accounts are unlocked automatically.</FullDescription> <UIPath>Computer Configuration\Windows Settings\Security Settings\Account Policies\Account Lockout Policy</UIPath> <DefaultValue>0</DefaultValue> <Vulnerability>Users can accidentally lock themselves out of their accounts if they mistype their password multiple times. To reduce the chance of such accidental lockouts, the Reset account lockout counter after setting determines the number of minutes that must elapse before the counter that tracks failed logon attempts and triggers lockouts is reset to 0.</Vulnerability> <Countermeasure>Configure the Reset account lockout counter after setting to 15 minutes.</Countermeasure> <PotentialImpact>If you do not configure this policy setting or if the value is configured to an interval that is too long, a DoS attack could occur. An attacker could maliciously attempt to log on to each user's account numerous times and lock out their accounts as described in the preceding paragraphs. If you do not configure the Reset account lockout counter after setting, administrators would have to manually unlock all accounts. If you configure this policy setting to a reasonable value the users would be locked out for some period, after which their accounts would unlock automatically. Be sure that you notify users of the values used for this policy setting so that they will wait for the lockout timer to expire before they call the help desk about their inability to log on.</PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="99999"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <Mapping FriendlyName="Not Defined"> <BehaviorDescription /> <DCMValue ValueA="Not Defined" /> <SCAPValue ValueA="Not Defined" /> <GPOValue ValueA="Not Defined" /> </Mapping> <Mapping FriendlyName="Not Configured"> <BehaviorDescription /> <DCMValue ValueA="Not Configured" /> <SCAPValue ValueA="Not Configured" /> <GPOValue ValueA="Not Configured" /> </Mapping> <Mapping FriendlyName="Not Applicable"> <BehaviorDescription /> <DCMValue ValueA="Not Applicable" /> <SCAPValue ValueA="Not Applicable" /> <GPOValue ValueA="Not Applicable" /> </Mapping> <Mapping FriendlyName="Not Recommended"> <BehaviorDescription /> <DCMValue ValueA="Not 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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="WMI" Scope="Machine"> <WMIDiscoveryInfo> <mssasc-core:Namespace xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">root\rsop\computer</mssasc-core:Namespace> <mssasc-core:Class xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">RSOP_SecuritySettingNumeric</mssasc-core:Class> <mssasc-core:Property xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">Setting</mssasc-core:Property> <mssasc-core:Where xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">KeyName='ResetLockoutCount' And precedence=1</mssasc-core:Where> </WMIDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="INF"> <Inf SectionName="System Access" Name="ResetLockoutCount" DataType="REG_DWORD" /> <OVAL> <Reference source="" ref_id="oval:gov.nist.1:def:26" ref_url="" /> </OVAL> </ExportInfo> <Comment>Added Setting, per SOC audit finding, add this into OS baselines, use MS domain baseline recommendation.</Comment> </Setting> <Setting Index="231" ID="{ed1a9aa2-5058-40fb-93d2-2e305be45afd}" OriginalSettingID="{289faee7-ee79-4b99-a024-2f7dd956d6f0}" Name="Account lockout threshold" LockdownDate="2014-05-13T12:57:18Z" GenerateDCM="true" GenerateSCAP="false" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-11046-0"> <Description> </Description> </CCEID-50> <ShortDescription>This policy setting determines the number of failed logon attempts before a lockout occurs.</ShortDescription> <FullDescription>This policy setting determines the number of failed logon attempts before a lock occurs. Authorized users can lock themselves out of an account by mistyping their password or by remembering it incorrectly, or by changing their password on one computer while logged on to another computer. The computer with the incorrect password will continuously try to authenticate the user, and because the password it uses to authenticate is incorrect, a lock occurs. To avoid accidental lockout of authorized users, set the account lockout threshold to a high number. The default value for this policy setting is 0 invalid logon attempts, which disables the account lockout feature. Because it is possible for an attacker to use this lockout state as a denial of service (DoS) by triggering a lockout on a large number of accounts, your organization should determine whether to use this policy setting based on identified threats and the risks you want to mitigate. There are two options to consider for this policy setting. - Configure the value for Account lockout threshold to 0 to ensure that accounts will not be locked out. This setting value will prevent a DoS attack that attempts to lock out accounts in your organization. It will also reduce help desk calls, because users will not be able to lock themselves out of their accounts accidentally. However, this setting value will not prevent a brute force attack. The following defenses should also be considered: - A password policy that forces all users to have complex passwords made up of 8 or more characters. - A robust auditing mechanism, which will alert administrators when a series of account lockouts occurs in the environment. For example, the auditing solution should monitor for security event 539, which is a logon failure. This event identifies that there was a lock on the account at the time of the logon attempt. The second option is: - Configure the value for Account lockout threshold to a value that provides users with the ability to mistype their password several times, but locks out the account if a brute force password attack occurs. This configuration will prevent accidental account lockouts and reduce help desk calls, but will not prevent a DoS attack.</FullDescription> <UIPath>Computer Configuration\Windows Settings\Security Settings\Account Policies\Account Lockout Policy</UIPath> <DefaultValue>0 invalid logon attempts</DefaultValue> <Vulnerability>Password attacks can use automated methods to try millions of password combinations for any user account. The effectiveness of such attacks can be almost eliminated if you limit the number of failed logons that can be performed. However, a DoS attack could be performed on a domain that has an account lockout threshold configured. An attacker could programmatically attempt a series of password attacks against all users in the organization. If the number of attempts is greater than the account lockout threshold, the attacker might be able to lock out every account.</Vulnerability> <Countermeasure>Because vulnerabilities can exist when this value is configured as well as when it is not configured, two distinct countermeasures are defined. Any organization should weigh the choice between the two based on their identified threats and the risks that they want to mitigate. The two countermeasure options are: - Configure the Account Lockout Threshold setting to 0. This configuration ensures that accounts will not be locked out, and will prevent a DoS attack that intentionally attempts to lock out accounts. This configuration also helps reduce help desk calls because users cannot accidentally lock themselves out of their accounts. Because it will not prevent a brute force attack, this configuration should only be chosen if both of the following criteria are explicitly met: - The password policy requires all users to have complex passwords of 8 or more characters. - A robust audit mechanism is in place to alert administrators when a series of failed logons occur in the environment. - Configure the Account Lockout Threshold setting to a sufficiently high value to provide users with the ability to accidentally mistype their password several times before the account is locked, but ensure that a brute force password attack will still lock the account.</Countermeasure> <PotentialImpact>If this policy setting is enabled, a locked-out account will not be usable until it is reset by an administrator or until the account lockout duration expires. This setting will likely generate a number of additional help desk calls. In fact, locked accounts cause the greatest number of calls to the help desk in many organizations. If you enforce this setting an attacker could cause a denial of service condition by deliberately generating failed logons for multiple user, therefore you should also configure the Account Lockout Duration to a relatively low value such as 15 minutes. If you configure the Account Lockout Threshold to 0, there is a possibility that an attacker's attempt to discover passwords with a brute force password attack might go undetected if a robust audit mechanism is not in place.</PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="9999"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <Mapping FriendlyName="Not Defined"> <BehaviorDescription /> <DCMValue ValueA="Not Defined" /> <SCAPValue ValueA="Not Defined" /> <GPOValue ValueA="Not Defined" /> </Mapping> <Mapping FriendlyName="Not Configured"> <BehaviorDescription /> <DCMValue ValueA="Not Configured" /> <SCAPValue ValueA="Not Configured" /> <GPOValue ValueA="Not Configured" /> </Mapping> <Mapping FriendlyName="Not Applicable"> <BehaviorDescription /> <DCMValue ValueA="Not Applicable" /> <SCAPValue ValueA="Not Applicable" /> <GPOValue ValueA="Not Applicable" /> </Mapping> <Mapping FriendlyName="Not Recommended"> <BehaviorDescription /> <DCMValue ValueA="Not 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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Script" Scope="Machine"> <ScriptDiscoveryInfo> <mssasc-core:ScriptType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">VBScript</mssasc-core:ScriptType> <mssasc-core:ScriptBody xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">Option Explicit WScript.Echo CheckRange("root\rsop\computer", "RSOP_SecuritySettingNumeric", "Setting", "KeyName='LockoutBadCount' And precedence=1", "{BaselineValue}") Function CheckRange(wmiNamespace, wmiClass, wmiProperty, wmiWhere, 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(wmiNamespace, wmiClass, wmiProperty, wmiWhere) '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(wmiNamespace, wmiClass, wmiProperty, wmiWhere) On Error Resume Next Err.Clear ' Get WMI data Dim objWMIService, strWQL, objSettings, objInstance Set objWMIService = GetObject("winmgmts:\\.\" + wmiNamespace) strWQL = "Select " + wmiProperty +" from " + wmiClass + " where " + wmiWhere Set objSettings = objWMIService.ExecQuery(strWQL) For Each objInstance in objSettings GetCurrentValue = objInstance.Setting Exit For Next ' 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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="INF"> <Inf SectionName="System Access" Name="LockoutBadCount" DataType="REG_DWORD" /> </ExportInfo> <Comment>Added Setting, per SOC audit finding, add this into OS baselines, use MS domain baseline recommendation.</Comment> </Setting> <Setting Index="232" ID="{7079d671-dace-4f56-8652-e3a9448f371c}" OriginalSettingID="{c055add0-22a5-4d9a-90e9-8e0c6a0a3eae}" Name="Account lockout duration" LockdownDate="2014-05-13T12:57:35Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10399-4"> <Description> </Description> </CCEID-50> <ShortDescription>This policy setting determines the length of time that must pass before a locked account is unlocked and a user can try to log on again. </ShortDescription> <FullDescription>This policy setting determines the length of time that must pass before a locked account is unlocked and a user can try to log on again. The setting does this by specifying the number of minutes a locked out account will remain unavailable. If the value for this policy setting is configured to 0, locked out accounts will remain locked out until an administrator manually unlocks them. Although it might seem like a good idea to configure the value for this policy setting to a high value, such a configuration will likely increase the number of calls that the help desk receives to unlock accounts locked by mistake. Users should be aware of the length of time a lock remains in place, so that they realize they only need to call the help desk if they have an extremely urgent need to regain access to their computer. </FullDescription> <UIPath>Computer Configuration\Windows Settings\Security Settings\Account Policies\Account Lockout Policy</UIPath> <DefaultValue>Not defined</DefaultValue> <Vulnerability>A denial of service (DoS) condition can be created if an attacker abuses the Account lockout threshold and repeatedly attempts to log on with a specific account. Once you configure the Account lockout threshold setting, the account will be locked out after the specified number of failed attempts. If you configure the Account lockout duration setting to 0, then the account will remain locked out until an administrator unlocks it manually.</Vulnerability> <Countermeasure>Configure the Account lockout duration setting to an appropriate value for your environment. To specify that the account will remain locked until an administrator manually unlocks it, configure the value to 0. When the Account lockout duration setting is configured to a non-zero value, automated attempts to guess account passwords must wait for this interval before they resume attempts against a specific account. Using this setting in combination with the Account lockout threshold setting makes automated password guessing attempts more difficult.</Countermeasure> <PotentialImpact>Although it may seem like a good idea to configure this policy setting to never automatically unlock an account, such a configuration can increase the number of requests that your organization's help desk receives to unlock accounts that were locked by mistake.</PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="99999"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <Mapping FriendlyName="Not Defined"> <BehaviorDescription /> <DCMValue ValueA="Not Defined" /> <SCAPValue ValueA="Not Defined" /> <GPOValue ValueA="Not Defined" /> </Mapping> <Mapping FriendlyName="Not Configured"> <BehaviorDescription /> <DCMValue ValueA="Not Configured" /> <SCAPValue ValueA="Not Configured" /> <GPOValue ValueA="Not Configured" /> </Mapping> <Mapping FriendlyName="Not Applicable"> <BehaviorDescription /> <DCMValue ValueA="Not Applicable" /> <SCAPValue ValueA="Not Applicable" /> <GPOValue ValueA="Not Applicable" /> </Mapping> <Mapping FriendlyName="Not Recommended"> <BehaviorDescription /> <DCMValue ValueA="Not 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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="WMI" Scope="Machine"> <WMIDiscoveryInfo> <mssasc-core:Namespace xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">root\rsop\computer</mssasc-core:Namespace> <mssasc-core:Class xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">RSOP_SecuritySettingNumeric</mssasc-core:Class> <mssasc-core:Property xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">Setting</mssasc-core:Property> <mssasc-core:Where xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">KeyName='LockoutDuration' And precedence=1</mssasc-core:Where> </WMIDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="INF"> <Inf SectionName="System Access" Name="LockoutDuration" DataType="REG_DWORD" /> <OVAL> <Reference source="" ref_id="oval:gov.nist.1:def:23" ref_url="" /> </OVAL> </ExportInfo> <Comment>Added Setting, per SOC audit finding, add this into OS baselines, use MS domain baseline recommendation.</Comment> </Setting> <Comment> </Comment> </SettingGroup> <SettingGroup ID="{7903f2c2-e56e-4eff-8250-ddc467113ecc}" Name="Attack Surface Reduction" OriginalSettingGroupID="{59764c34-7ff9-46c0-8ec3-85844e1cd329}"> <mssasc-core:Description> </mssasc-core:Description> <mssasc-core:Version Major="1" Minor="0" /> <Author> </Author> <Setting Index="236" ID="{825abafe-20d8-4520-af63-6bfa1adf8d3b}" OriginalSettingID="{e91cc40b-fd08-4004-b361-cc6f59ddee47}" Name="Enable Windows Error Reporting (Policy Check)" LockdownDate="2014-08-29T02:01:10Z" GenerateDCM="false" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="AZID-00001-a"> <Description> </Description> </CCEID-50> <ShortDescription>Enable Windows Error Reporting (Policy Check)</ShortDescription> <FullDescription>This policy setting turns on Windows Error Reporting, so that reports are collected or sent to either Microsoft or internal servers within your organization when software unexpectedly stops working or fails. </FullDescription> <UIPath>User Configuration\Administrative Templates\Windows Components\Windows Error Reporting</UIPath> <DefaultValue>Not Configured </DefaultValue> <Vulnerability>-- </Vulnerability> <Countermeasure>You can enable Windows Error Reporting by setting the following registry entry: "HKLM\SOFTWARE\Policies\Microsoft\Windows\Windows Error Reporting", REG_DWORD, Disabled==0 </Countermeasure> <PotentialImpact>-- </PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="0"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">SOFTWARE\Policies\Microsoft\Windows\Windows Error Reporting</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">Disabled</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <!--TO DO: Check if policy section is needed <policy xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" name="WerDisable_1" class="User" displayName="$(string.WerDisable)" explainText="$(string.WerDisabledExp)" key="SOFTWARE\Policies\Microsoft\Windows\Windows Error Reporting" valueName="Disabled"> <admx:supportedOn xmlns:admx="http://schemas.microsoft.com/GroupPolicy/2008/03/PolicyDefinitions" ref="Unsupported_in_SCM_v2" /> <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>--> <!--TO DO: Check if ADMLDefinition section is needed <ADMLDefinition xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <string id="WerDisable">Enable Windows Error Reporting</string> <string id="WerDisabledExp"> </string> </ADMLDefinition> --> <supportedOn>Unspecified</supportedOn> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment> updated setting </Comment> </Setting> <Setting Index="237" ID="{3a0fdd4a-e4c3-4788-9240-fd86f6df2225}" OriginalSettingID="{408649be-42a6-420f-b5f5-4e1008a0585e}" Name="Enable Windows Error Reporting (Registry Check)" LockdownDate="2014-08-29T02:01:10Z" GenerateDCM="false" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="AZID-00001-b"> <Description> </Description> </CCEID-50> <ShortDescription>Enable Windows Error Reporting (Registry Check)</ShortDescription> <FullDescription>This policy setting turns on Windows Error Reporting, so that reports are collected or sent to either Microsoft or internal servers within your organization when software unexpectedly stops working or fails. </FullDescription> <UIPath>User Configuration\Administrative Templates\Windows Components\Windows Error Reporting</UIPath> <!--TO DO: Verify if default value is used anywhere in teh code--> <DefaultValue>Not Configured </DefaultValue> <Vulnerability>-- </Vulnerability> <Countermeasure>You can enable Windows Error Reporting by setting the following registry entries: "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting", REG_DWORD, Disabled==0 </Countermeasure> <PotentialImpact>-- </PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="0"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">SOFTWARE\Microsoft\Windows\Windows Error Reporting</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">Disabled</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment> updated setting </Comment> </Setting> <Setting Index="238" ID="{d8081a87-a751-4fe3-bb1f-5dc27f0a6d9f}" OriginalSettingID="{227bbf31-1cbc-4418-bee2-8af345d3841a}" Name="Ensure Azure Watson is configured correctly (Registry Check:ForceQueue)" LockdownDate="2014-08-29T02:01:10Z" GenerateDCM="false" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="AZID-00002-a"> <Description> </Description> </CCEID-50> <ShortDescription>Configure Azure Watson Correctly (Registry Check:ForceQueue)</ShortDescription> <FullDescription>This policy setting checks if Azure Watson is configured correctly for your service. It checks for the following registry entry: "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting", REG_DWORD, ForceQueue==2 </FullDescription> <UIPath>HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting</UIPath> <DefaultValue>Not Configured </DefaultValue> <Vulnerability>-- </Vulnerability> <Countermeasure>You can enable Azure Watson by setting the following registry entry: "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting", REG_DWORD, ForceQueue==2 </Countermeasure> <PotentialImpact>-- </PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="0"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">SOFTWARE\Microsoft\Windows\Windows Error Reporting</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">ForceQueue</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment> </Comment> </Setting> <Setting Index="239" ID="{6798451d-438b-498d-8d7c-1249802b1530}" OriginalSettingID="{57118829-dad3-4043-a505-14830b985c7d}" Name="Ensure Azure Watson is configured correctly (Registry Check:DefaultConsent)" LockdownDate="2014-08-29T02:01:10Z" GenerateDCM="false" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="AZID-00002-b"> <Description> </Description> </CCEID-50> <ShortDescription>Configure Azure Watson Correctly (Registry Check:DefaultConsent)</ShortDescription> <FullDescription>This policy setting checks if Azure Watson is configured correctly for your service. It checks for the following registry:"HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\Consent", REG_DWORD, DefaultConsent==1 </FullDescription> <UIPath>HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting</UIPath> <DefaultValue>Not Configured </DefaultValue> <Vulnerability>-- </Vulnerability> <Countermeasure>You can enable Azure Watson by setting the following registry entry: "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\Consent", REG_DWORD, DefaultConsent==1 </Countermeasure> <PotentialImpact>-- </PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="0"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">SOFTWARE\Microsoft\Windows\Windows Error Reporting</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">DefaultConsent</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment> </Comment> </Setting> <Setting Index="240" ID="{80de7581-89eb-4fe2-9c7b-cc69243494e6}" OriginalSettingID="{c3a43044-6ffb-4b54-b72b-61f5d1566d5b}" Name="Enable Command-line logging" LockdownDate="2016-02-28T02:01:10Z" GenerateDCM="false" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="AZID-00003"> <Description> </Description> </CCEID-50> <ShortDescription>Enable Command-line logging</ShortDescription> <FullDescription>This policy setting determines what information is logged in security audit events when a new process has been created. This setting only applies when the Audit Process Creation policy is enabled. If you enable this policy setting the command line information for every process will be logged in plain text in the security event log as part of the Audit Process Creation event 4688, "a new process has been created," on the workstations and servers on which this policy setting is applied. If you disable or do not configure this policy setting, the process's command line information will not be included in Audit Process Creation events. Note: When this policy setting is enabled, any user with access to read the security events will be able to read the command line arguments for any successfully created process. Command line arguments can contain sensitive or private information such as passwords or user data. </FullDescription> <UIPath>Computer Configuration\Administrative Templates\System\Audit Process Creation </UIPath> <DefaultValue>Not configured </DefaultValue> <Vulnerability>-- </Vulnerability> <Countermeasure>Command-line auditing isn't enabled by default. You can enable this setting in the local system registry by setting the HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\Audit\ ProcessCreationIncludeCmdLine_Enabled registry key value to 1. </Countermeasure> <PotentialImpact>-- </PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="0"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">Software\Microsoft\Windows\CurrentVersion\Policies\System\Audit</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">ProcessCreationIncludeCmdLine_Enabled</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment> </Comment> </Setting> <Setting Index="241" ID="{23b42fec-1e67-458c-89f1-0ee0e9e5224c}" OriginalSettingID="{d25b88d2-9b0d-4bcd-ac68-7e4bec504081}" Name="Ensure Microsoft Anti-malware is enabled:schedule scan day" LockdownDate="2016-02-28T02:01:10Z" GenerateDCM="false" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="AZID-00004-a"> <Description> </Description> </CCEID-50> <ShortDescription>Ensure Microsoft Anti-malware is enabled:schedule scan day</ShortDescription> <FullDescription>This policy setting ensures Microsoft Anti-malware quick scan is scheduled to run on weekly basis. The value indicates which day of the week it's scheduled to run.</FullDescription> <UIPath>HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Microsoft Antimalware\Scan\ScheduleDay </UIPath> <DefaultValue>Not configured </DefaultValue> <Vulnerability>-- </Vulnerability> <Countermeasure>You can set the following registry to enable Microsoft Antimalware quick scan. The value needs to be greater than 0 and lessorequal 7. The value indicates the day in the week. Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Microsoft Antimalware\Scan\ScheduleDay </Countermeasure> <PotentialImpact>-- </PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="0"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">SOFTWARE\Policies\Microsoft\Microsoft Antimalware\Scan</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">ScheduleDay</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment> </Comment> </Setting> <Setting Index="242" ID="{f1daa65d-03ba-48ac-9ca4-184740ef0794}" OriginalSettingID="{a2074b84-8606-4406-bd48-e4545006df8d}" Name="Ensure Microsoft Anti-malware is enabled:schedule scan time" LockdownDate="2016-02-28T02:01:10Z" GenerateDCM="false" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="AZID-00004-b"> <Description> </Description> </CCEID-50> <ShortDescription>Ensure Microsoft Anti-malware is enabled:schedule scan time</ShortDescription> <FullDescription>This policy setting ensures Microsoft Anti-malware quick scan is scheduled to run on weekly basis. The value indicates if scan time is configured for the machine. The value should be greater than 0 </FullDescription> <UIPath>HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Microsoft Antimalware\Scan\ScheduleTime </UIPath> <DefaultValue>Not configured </DefaultValue> <Vulnerability>-- </Vulnerability> <Countermeasure>You can set the following registry to enable Microsoft Antimalware quick scan. The value indicates if scan time is configured for the machine. The value should be greater than 0. Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Microsoft Antimalware\Scan\ScheduleTime </Countermeasure> <PotentialImpact>-- </PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="0"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">SOFTWARE\Policies\Microsoft\Microsoft Antimalware\Scan</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">ScheduleTime</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment> </Comment> </Setting> <Setting Index="243" ID="{7d6282bf-6678-4fa3-adb5-3e10297bb2f6}" OriginalSettingID="{cf7eeacd-033e-4f9f-aea8-b350f9c1118d}" Name="Microsoft Antimalware signature update should occur every 8 hours" LockdownDate="2016-02-28T02:01:10Z" GenerateDCM="false" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="AZID-00004-c"> <Description> </Description> </CCEID-50> <ShortDescription>Microsoft Antimalware signature update should occur every 8 hours</ShortDescription> <FullDescription>This policy setting ensures Microsoft Antimalware signature update occurs every 8 hours. The value should be less or equal 8 </FullDescription> <UIPath>HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Microsoft Antimalware\Signature Updates\SignatureUpdateInterval </UIPath> <DefaultValue> Not configured </DefaultValue> <Vulnerability>-- </Vulnerability> <Countermeasure>This policy setting ensures Microsoft Antimalware signature update occurs every 8 hours. The value should be less or equal 8. Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Microsoft Antimalware\Signature Updates\SignatureUpdateInterval </Countermeasure> <PotentialImpact>-- </PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="0"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">SOFTWARE\Policies\Microsoft\Microsoft Antimalware\Scan</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">ScheduleTime</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment> </Comment> </Setting> <Setting Index="244" ID="{b868f59b-8323-4bb7-ac3e-5c0aa96cf4b2}" OriginalSettingID="{2015bc22-961b-47a8-97fa-4972758e63a1}" Name="Enable SecureBoot" LockdownDate="2016-02-28T02:01:10Z" GenerateDCM="false" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="AZID-00005"> <Description> </Description> </CCEID-50> <ShortDescription>Ensure SecureBoot is eanbled for your service.</ShortDescription> <FullDescription>This registry value determines if secure boot is enabled or not. Secure Boot ensures that the machine boots using only software that is trusted by the PC manufacturer. </FullDescription> <UIPath>HKLM\System\CurrentControlSet\Control\SecureBoot\State </UIPath> <DefaultValue>Disabled </DefaultValue> <Vulnerability>If secureboot is not enabled, malware could persist on early boot components. </Vulnerability> <Countermeasure> Enable secure boot by setting the following registry to 1. Registry:HKLM\System\CurrentControlSet\Control\SecureBoot\State\UEFISecureBootEnabled </Countermeasure> <PotentialImpact>-- </PotentialImpact> <ManualTestProcedure> </ManualTestProcedure> <ValueRange Low="0" High="0"> <Exclude> <Value> </Value> </Exclude> <Include> <Value> </Value> </Include> </ValueRange> </ProductInfo> <ProductStartedFrom product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" /> </Content> <DiscoveryInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingDiscoveryInfo DiscoveryType="Registry" Scope="Machine"> <RegistryDiscoveryInfo> <mssasc-core:Hive xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">HKEY_LOCAL_MACHINE</mssasc-core:Hive> <mssasc-core:DataType xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">REG_DWORD</mssasc-core:DataType> <mssasc-core:KeyPath xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">System\CurrentControlSet\Control\SecureBoot\State</mssasc-core:KeyPath> <mssasc-core:ValueName xmlns:mssasc-core="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance/core">UEFISecureBootEnabled</mssasc-core:ValueName> </RegistryDiscoveryInfo> </SettingDiscoveryInfo> <DataType>Int64</DataType> </DiscoveryInfo> <ExportInfo xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance" GPOGenerateFormat="POL"> <Inf /> <OVAL> <Reference source="" ref_id="" ref_url="" /> </OVAL> </ExportInfo> <Comment> </Comment> </Setting> <Comment> </Comment> </SettingGroup> <SettingGroup ID="{95a7468b-4dbf-4626-aec8-5060b8326d67}" Name="Devices" OriginalSettingGroupID="{19e9c4ac-dfdf-442f-a5d6-eafdc2d44649}"> <mssasc-core:Description> </mssasc-core:Description> <mssasc-core:Version Major="1" Minor="0" /> <Author> </Author> <Setting Index="1" ID="{d81e699b-7e42-4f71-80e1-0c92b61a2d91}" OriginalSettingID="{71d6ee80-22f8-44e3-99ad-cbc707218ff8}" Name="Devices: Allowed to format and eject removable media" LockdownDate="2011-10-09T10:37:56Z" GenerateDCM="true" GenerateSCAP="true" GenerateGPO="true"> <mssasc-core:Version Major="1" Minor="0" /> <Publisher ID="{6c5767f4-983a-41ce-a964-962604dbb544}"> <DisplayName>Custom</DisplayName> </Publisher> <PMOwner>Microsoft</PMOwner> <DevOwner>Microsoft</DevOwner> <TestOwner>Microsoft</TestOwner> <ReviewedBy>Microsoft</ReviewedBy> <ReviewStatus>Complete</ReviewStatus> <Content> <ProductInfo> <ProductRef product_ref="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <CCEID-50 ID="CCE-10637-7"> <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>Administrators</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="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" /> <Unit> </Unit> <ValueMappingTable SelectedFriendlyName="Administrators"> <Mapping FriendlyName="Not Defined"> <BehaviorDescription /> <DCMValue ValueA="Not Defined" /> <SCAPValue ValueA="Not Defined" /> <GPOValue ValueA="Not Defined" /> </Mapping> <Mapping FriendlyName="Not Configured"> <BehaviorDescription /> <DCMValue ValueA="Not Configured" /> <SCAPValue ValueA="Not Configured" /> <GPOValue ValueA="Not Configured" /> </Mapping> <Mapping FriendlyName="Not Applicable"> <BehaviorDescription /> <DCMValue ValueA="Not Applicable" /> <SCAPValue ValueA="Not Applicable" /> <GPOValue ValueA="Not Applicable" /> </Mapping> <Mapping FriendlyName="Not Recommended"> <BehaviorDescription /> <DCMValue ValueA="Not 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> <Comment> </Comment> </SettingGroup> <SettingGroup ID="{e4e0f412-5fe8-457c-bf74-a5d87ad3243a}" Name="PlaceHolder1" OriginalSettingGroupID="{7587f0ed-9b04-492d-bab0-94517dc3ae0d}"> <mssasc-core:Description> </mssasc-core:Description> <mssasc-core:Version Major="1" Minor="0" /> <Author> </Author> <Comment> </Comment> </SettingGroup> <SettingGroup ID="{0116ebb7-1b32-4390-8cea-a5b6b8f32a7a}" Name="PlaceHolder2" OriginalSettingGroupID="{7b3f9294-576c-4c8b-98b8-78b1f360cfef}"> <mssasc-core:Description> </mssasc-core:Description> <mssasc-core:Version Major="1" Minor="0" /> <Author> </Author> <Comment> </Comment> </SettingGroup> <SettingGroup ID="{eec972a0-e197-4589-9bbf-b2a42e9cf935}" Name="PlaceHolder3" OriginalSettingGroupID="{30d2cb99-e767-42c0-adcf-3d278b77a0da}"> <mssasc-core:Description> </mssasc-core:Description> <mssasc-core:Version Major="1" Minor="0" /> <Author> </Author> <Comment> </Comment> </SettingGroup> <Check> <SettingRef setting_ref="{d81e699b-7e42-4f71-80e1-0c92b61a2d91}" 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="0" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{236aa795-e020-4b72-8d40-9502567f8561}" 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="{fe995933-3583-43ab-8932-168850b077a0}" 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 /> <Value ValueA="1" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{7b14fd19-eadf-42da-960a-e02c5a49cfb5}" Severity="Important" /> <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="Warning" id="AlwaysInstallElevated_2"> <Description /> <Value ValueA="Disabled" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{a40ce73c-ee67-4b10-afcc-70e2c9fb784f}" 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 /> <Value ValueA="Enabled" /> </SettingRule> <OptionRule Name="Turn off Autoplay on:" Operator="Equals" Severity="Informational" id="Autorun_Box"> <Description /> <Value ValueA="$(string.d97da86453d5448fbe2cbc4ff0b031cc)" /> </OptionRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{13d86ad6-83cc-4092-9e58-50a54d1aecce}" 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="{162f9d7c-7d0d-4e46-9a18-43d165b07e85}" 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="{581f0698-c134-4949-a648-267e5e61c5c8}" 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="0" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{e0e9ab4c-e39c-4251-9ecc-1e8b88749eab}" 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="{124534b0-17b7-4944-9922-bbf6a5cc1569}" 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="1" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{85029100-6fe5-4f31-a457-7f20b99c5b48}" Severity="Important" /> <ExistentialRule Name="MSS: (AutoAdminLogon) Enable Automatic Logon (not recommended)" Operator="GreaterThan" Severity="Informational" 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="Warning" id="{c883c1c8-866f-46c5-8675-2bbe6309b782}"> <Description /> <Value ValueA="0" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{8f58e594-a4ba-43e8-bd78-5b03bc06297c}" 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="0" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{79b4e067-440a-497d-9a87-95188942a003}" Severity="Critical" /> <ExistentialRule Name="Microsoft network server: Disconnect clients when logon hours expire" Operator="GreaterThan" Severity="Informational" 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 /> <Value ValueA="1" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{8b7f3756-397b-49b6-b639-1023af377d3b}" 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 /> <Value ValueA="0" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{c007b836-5214-4b0b-b5fb-9a9b58b80f42}" 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="{b4264b5a-d5eb-4534-b514-3884840cc19f}" 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="{7556ff3b-976d-4105-97a6-558465627ffc}" 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="{94622cee-0b73-4007-a029-cd68273adecb}" 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="{a471355b-7f15-41db-b339-b384d0020cfd}" 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="{10a56b26-ac55-4ac8-9db7-2cca216d496b}" 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="{014038f2-2d49-4cb0-88b3-ae58b2140c6a}" 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="{4d5107c4-50ce-4625-bb8a-4589ff35b5a7}" 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 /> <Value ValueA="0" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{b97df99f-e32c-49c2-bed9-0213fa84e34b}" 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="{b7acd6e0-04b1-431e-b7fd-a673562ce721}" Severity="Critical" /> <ExistentialRule Name="Set client connection encryption level" Operator="GreaterThan" Severity="Informational" 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 /> <Value ValueA="Enabled" /> </SettingRule> <OptionRule Name="Encryption Level" Operator="Equals" Severity="Informational" id="TS_ENCRYPTION_LEVEL"> <Description /> <Value ValueA="$(string.c7c2c16080314e20b138a74cb1e8b1dd)" /> </OptionRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{c060464b-ce68-4df9-bff1-58d0fc1c7cea}" Severity="Important" /> <ExistentialRule Name="SSL Cipher Suite Order" Operator="GreaterThan" Severity="None" ValueA="0"> <Description>SSL Cipher Suite Order</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="SSL Cipher Suite Order" Operator="Equals" Severity="Warning" id="SSLCipherSuiteOrder"> <Description /> <Value ValueA="Enabled" /> </SettingRule> <OptionRule Name="SSL Cipher Suites" Operator="Equals" Severity="None" id="Pol_SSLCipherSuiteOrder"> <Description /> <Value ValueA="TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256,TLS_RSA_WITH_AES_256_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_RC4_128_SHA,TLS_RSA_WITH_RC4_128_MD5" /> </OptionRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{3cfdfcda-1c9f-4a63-8761-6efbaaff1cf4}" Severity="Critical" /> <ExistentialRule Name="Enforce user logon restrictions" Operator="GreaterThan" Severity="None" ValueA="0"> <Description>Enforce user logon restrictions</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Enforce user logon restrictions" Operator="Equals" Severity="Critical" id="{6557c718-f185-496e-b0d0-7f40374bb173}"> <Description /> <Value ValueA="True" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{b1c37fde-5315-4563-9b08-3bbb1ac55233}" 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 /> <Value ValueA="14" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{f5e55156-eb42-421e-a8f4-faa939998db9}" 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="0" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{6782d755-bfb1-482c-b720-e8e4d03d3800}" Severity="Critical" /> <ExistentialRule Name="Accounts: Limit local account use of blank passwords to console logon only" Operator="GreaterThan" Severity="Informational" 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 /> <Value ValueA="1" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{610fb9bb-0d5e-4388-a265-866afeff6660}" 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="{8e2a40ed-2bf7-42ec-8c40-b6d712496fd7}" 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="{d5af2ea2-c4ad-49d8-af55-b0a6c1bde041}" Severity="Critical" /> <ExistentialRule Name="Windows Firewall: Private: Inbound connections" Operator="GreaterThan" Severity="Informational" 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 /> <Value ValueA="Enabled" /> </SettingRule> <OptionRule Name="Inbound connections" Operator="Equals" Severity="Informational" id="DefaultInboundActions"> <Description /> <Value ValueA="$(string.43bcf2ef7f9e4f21a3222e0b58894de8)" /> </OptionRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{5270f303-206a-45df-b7a4-1d98e0ba3b0e}" Severity="Important" /> <ExistentialRule Name="MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)" Operator="GreaterThan" Severity="Informational" 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 /> <Value ValueA="Not Defined" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{d0401a2f-a8b9-486d-8aed-204deb32ef39}" 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="{245d1612-ea25-42e9-97c8-02ea2a8b059c}" 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 /> <Value ValueA="1" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{0ad79564-2846-45e3-9d1b-c95768004097}" 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="{36a80eb5-d25e-464e-ab5e-a70e2c96b305}" Severity="Important" /> <ExistentialRule Name="MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)" Operator="GreaterThan" Severity="Informational" 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 /> <Value ValueA="Not Defined" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{7ab49e87-2ab9-4f7b-b1d2-7be32e06d958}" Severity="Critical" /> <ExistentialRule Name="Windows Firewall: Public: Inbound connections" Operator="GreaterThan" Severity="Informational" 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 /> <Value ValueA="Enabled" /> </SettingRule> <OptionRule Name="Inbound connections" Operator="Equals" Severity="Informational" id="DefaultInboundActions"> <Description /> <Value ValueA="$(string.ac1a7471dc154e72b11333ca4d0ba7fd)" /> </OptionRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{1b5f0e1b-aa17-4dab-9c97-ac788ae5af2c}" 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="{9b95cd26-50b9-456f-8e98-5723f5a2c0d4}" 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="{0507a6c8-0219-40f6-86be-d6f948e32e47}" 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="{6442ff6f-d388-42c2-a804-26a00036b127}" 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="{33c89fd1-1cd4-461c-8008-17e2efc277fe}" 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="{1c2e1a4b-2980-42f5-bc39-1d2f79a4971c}" Severity="Critical" /> <ExistentialRule Name="Windows Firewall: Public: Firewall state" Operator="GreaterThan" Severity="Informational" 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 /> <Value ValueA="1" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{351866dd-ce4d-4f13-8e17-f72d2381aeda}" 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="0" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{e1d6ad24-8993-4879-9121-d58c3777c7a5}" 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="{11a69901-de1c-4599-96de-e323e7017e0c}" Severity="Critical" /> <ExistentialRule Name="Windows Firewall: Domain: Inbound connections" Operator="GreaterThan" Severity="Informational" 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 /> <Value ValueA="Enabled" /> </SettingRule> <OptionRule Name="Inbound connections" Operator="Equals" Severity="Informational" id="DefaultInboundActions"> <Description /> <Value ValueA="$(string.3dc8e9cfabac4a4d9dc4e289fdf262da)" /> </OptionRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{ec3aaedb-8cb5-45c9-82ec-e50a18d9f734}" 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="{b04263ca-fc10-4d89-aaa1-cb388ea13dea}" 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="1" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{eb9e605c-74bd-433d-bd48-a20b616b243d}" 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 /> <Value ValueA="1" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{2b627347-5932-4a63-9458-3c3be03012cd}" 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="{2010d729-2830-4578-aa5c-e9bc99f44f66}" 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="GreaterEquals" 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="{6387c003-9ed7-4207-98b5-4596732345f6}" 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="GreaterEquals" 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="{831fc482-1d5e-4918-87c8-b7adb1728591}" 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="GreaterEquals" 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="{31817c74-55a8-473c-965d-5b8748c5b0de}" 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="GreaterEquals" 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="{864fd407-4b0f-474d-9a2a-940668525875}" 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="GreaterEquals" 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="{3bb15d3e-d350-4ccc-893a-a2f582427254}" 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="GreaterEquals" 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="{a45dc25d-4adb-4da6-ad67-3ba82c3d110b}" 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="GreaterEquals" Severity="Critical" id="{e812bde9-b47f-4b44-95b5-02651d66d65a}"> <Description /> <Value ValueA="No Auditing" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{9b5cef05-0c38-4137-a951-1ec03812703c}" 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="GreaterEquals" Severity="Critical" id="{669a6cac-099c-40c0-a868-633341528f6d}"> <Description /> <Value ValueA="No Auditing" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{752b5794-5a8c-44ae-b048-2f0c65a1e30f}" 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="GreaterEquals" 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="{1deb0360-7dbb-411b-970f-b4c0d3695cee}" 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="GreaterEquals" 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="{5a73f721-6f43-4bb0-bc02-32c01efd2439}" 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="GreaterEquals" 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="{29ebd2b0-b6bf-49b8-93d6-36017b2a1d83}" 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="GreaterEquals" 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="{32e2c032-1461-489f-9566-3288cc3a468f}" 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="GreaterEquals" 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="{ff52c0bb-aea1-498f-94fe-fbb33375bb61}" 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="GreaterEquals" 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="{c2c411ee-2744-46b9-bf81-1713f8e56e25}" 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="GreaterEquals" 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="{bac5ad93-64c2-422a-a7b8-5c9da6174397}" 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="GreaterEquals" Severity="Critical" id="{c7511b1b-9972-42ef-8915-ccfc913f9187}"> <Description /> <Value ValueA="Success and Failure" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{5ebe0373-a273-4c2c-ad2f-4d42409598bc}" 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="GreaterEquals" Severity="Critical" id="{2863d620-9040-4078-aa09-4304140e7887}"> <Description /> <Value ValueA="No Auditing" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{6f2ea732-6efe-4c42-9086-f30a6363a0f3}" 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="GreaterEquals" 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="{76f567b9-07c9-4aef-8a58-4c41db0327ce}" 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="GreaterEquals" 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="{d13987f3-a86c-43e9-a934-6d2583b06201}" 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="GreaterEquals" Severity="Critical" id="{ae06de0b-8e6b-476a-b34f-18f22edb6720}"> <Description /> <Value ValueA="No Auditing" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{b721fbbe-86df-4baf-9ea4-2c7554d1e042}" 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="GreaterEquals" Severity="Critical" id="{ceb584ec-5985-437b-8e74-9f6f4c10bd2c}"> <Description /> <Value ValueA="No Auditing" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{4fd2a029-547e-490d-8c37-9fc1ea7d9cf9}" 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="GreaterEquals" 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="{30147e6d-0078-4086-ba10-0ad9b3990e08}" 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="GreaterEquals" 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="{1a2564bc-8cf4-40e1-9a43-733a753629e7}" 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="GreaterEquals" 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="{16e6b535-93b8-44d6-ac52-4edd98f80260}" 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="GreaterEquals" Severity="Critical" id="{586da9b8-787b-4492-87a2-c0e6777a378f}"> <Description /> <Value ValueA="No Auditing" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{6550cbe2-10e6-442d-87c2-97b7ec891ad3}" 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="GreaterEquals" 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="{2b1ced96-3a71-46e1-8cb1-f50f612357a5}" 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="GreaterEquals" Severity="Critical" id="{41aed31a-6b83-42ed-bc28-e4b37a266a10}"> <Description /> <Value ValueA="No Auditing" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{82e7501d-04fd-433c-bb42-f6d53907fce1}" 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="GreaterEquals" Severity="Critical" id="{5ef932dd-d326-4a24-914f-b090f58db753}"> <Description /> <Value ValueA="Success and Failure" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{e167d977-870f-4ef4-b146-af0f0fa1bb43}" 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="GreaterEquals" 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="{8baffdc0-9a5c-4376-a54a-c403c9eb5f4e}" 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="GreaterEquals" 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="{1be1f452-745f-4b80-bb41-243eb322da22}" 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="GreaterEquals" Severity="Critical" id="{e7a3f2b0-d710-4df6-af2a-944c8d3764de}"> <Description /> <Value ValueA="No Auditing" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{8e63e8b4-74ee-4a03-bde1-2fd4fb31a90f}" 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="GreaterEquals" Severity="Critical" id="{9461f7af-40e3-43e6-83b9-2135fa4edbcd}"> <Description /> <Value ValueA="No Auditing" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{49bfcc2d-29ea-4b7b-9957-c7cad20e8643}" 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="GreaterEquals" Severity="Critical" id="{1d24c5bd-ff69-4485-ac83-7c9d38c632ab}"> <Description /> <Value ValueA="No Auditing" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{83584dcf-369d-4175-a8a2-d830838482eb}" 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="GreaterEquals" Severity="Critical" id="{6f1d8062-bc12-4f3f-89fa-bdb228ceb8b2}"> <Description /> <Value ValueA="Success and Failure" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{f999aa39-ba73-48a7-9492-5f50a31f04f5}" 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="GreaterEquals" 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="{d483785a-4e9b-4b42-8ce5-fda2cd396324}" 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="GreaterEquals" 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="{27311858-1d89-4cc3-b374-0a4bb1e370b2}" 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="GreaterEquals" 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="{5494b66f-2664-4c73-873f-600330559866}" 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="GreaterEquals" 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="{e9f25f6e-e27e-4d24-9bdd-7fff0613609d}" 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="GreaterEquals" Severity="Critical" id="{64f21b25-d5f9-4757-b4d3-782cce864765}"> <Description /> <Value ValueA="No Auditing" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{fb56d7a0-d1f6-457a-8d6b-7c8008807d86}" Severity="Critical" /> <ExistentialRule Name="Audit Policy: Object Access: Audit Detailed File Share" Operator="GreaterThan" Severity="Informational" ValueA="0"> <Description>Audit Policy: Object Access: Audit Detailed File Share</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Audit Policy: Object Access: Audit Detailed File Share" Operator="GreaterEquals" Severity="Critical" id="{23e9ba4c-089c-470e-b4fb-2079ab9a5c7f}"> <Description /> <Value ValueA="No Auditing" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{ffeffad3-0568-45d2-a51b-5976fffdd201}" 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="GreaterEquals" 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="{d842cfc6-45f7-4220-b637-f2a3d62f18bc}" 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="GreaterEquals" Severity="Critical" id="{be2080be-dd72-4059-ba13-10d6f98bbcb1}"> <Description /> <Value ValueA="Success" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{c4c4d35d-6e34-4565-99fd-10dc89be3d9f}" 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="GreaterEquals" 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="{836dc8c5-6844-432f-a1d6-5bcb43043a66}" 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="GreaterEquals" 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="{45c5dc4f-f872-4c11-94bc-d88964148db1}" 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="GreaterEquals" 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="{a543572f-2f65-421c-97bf-f0710d0787fe}" 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="GreaterEquals" 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="{a867bdd2-5fa3-4f96-9838-ef4522450b51}" 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="GreaterEquals" Severity="Critical" id="{fb018357-5c57-4900-af95-fd3fb8e395e3}"> <Description /> <Value ValueA="No Auditing" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{c234429b-7d46-437c-b3ae-f6bfaf70c567}" 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="GreaterEquals" 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="{175aa1cf-26f8-4d24-a39d-f241f55e1c22}" 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="GreaterEquals" 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="{9497d4f9-d805-459b-9531-d053ce704891}" 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="GreaterEquals" Severity="Critical" id="{88219aa9-f6b1-471e-9a70-a78ffec9186c}"> <Description /> <Value ValueA="No Auditing" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{8d9ccb64-cca3-4f66-9d90-2fa0873f62d4}" 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="GreaterEquals" 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="{4098e6f2-4e6f-405d-bbfe-fcf0ea22b835}" 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="GreaterEquals" 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="{31541f5d-3c65-48e3-b50b-23793cc9a5c0}" 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="GreaterEquals" 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="{14fa680f-80c2-4046-95b8-e66630e86cd9}" Severity="Critical" /> <ExistentialRule Name="Maximum Application Log Size (KB)" Operator="GreaterThan" Severity="Informational" ValueA="0"> <Description>Maximum Log Size (KB)</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Maximum Application Log Size (KB)" Operator="Equals" Severity="Critical" id="Channel_LogMaxSize_1"> <Description /> <Value ValueA="Enabled" /> </SettingRule> <OptionRule Name="Maximum Application Log Size (KB)" Operator="Equals" Severity="Informational" id="Channel_LogMaxSize"> <Description /> <Value ValueA="32768" /> </OptionRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{51a9d10d-f947-4101-a3b7-686df36aa4df}" Severity="Critical" /> <ExistentialRule Name="Retain old Application events" Operator="GreaterThan" Severity="Informational" ValueA="0"> <Description>Retain old events</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Retain old Application 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="{954fc693-9491-4d0e-b76e-624e3ce0096f}" 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 /> <Value ValueA="90" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{600f3971-db99-4491-8ffb-6dacb64f7ff4}" Severity="Critical" /> <ExistentialRule Name="Retain old System events" Operator="GreaterThan" Severity="Informational" ValueA="0"> <Description>Retain old events</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Retain old System events" Operator="Equals" Severity="Critical" id="Channel_Log_Retention_4"> <Description /> <Value ValueA="Disabled" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{b25d9b50-7b04-411d-b4be-dce09389821b}" Severity="Critical" /> <ExistentialRule Name="Maximum Security Log Size (KB)" Operator="GreaterThan" Severity="Informational" ValueA="0"> <Description>Maximum Log Size (KB)</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Maximum Security Log Size (KB)" Operator="Equals" Severity="Critical" id="Channel_LogMaxSize_2"> <Description /> <Value ValueA="Enabled" /> </SettingRule> <OptionRule Name="Maximum Security Log Size (KB)" Operator="Equals" Severity="Informational" id="Channel_LogMaxSize"> <Description /> <Value ValueA="196608" /> </OptionRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{81ed1680-2a32-479f-9deb-9f19b6655a4f}" Severity="Critical" /> <ExistentialRule Name="Maximum System Log Size (KB)" Operator="GreaterThan" Severity="Informational" ValueA="0"> <Description>Maximum Log Size (KB)</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Maximum System Log Size (KB)" Operator="Equals" Severity="Critical" id="Channel_LogMaxSize_4"> <Description /> <Value ValueA="Enabled" /> </SettingRule> <OptionRule Name="Maximum System Log Size (KB)" Operator="Equals" Severity="Informational" id="Channel_LogMaxSize"> <Description /> <Value ValueA="32768" /> </OptionRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{1e31b25c-6e25-4816-aaa7-6fb2173bbeca}" 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 /> <Value ValueA="0" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{c110c874-a0db-4c24-90b9-58ea0e38a02c}" Severity="Critical" /> <ExistentialRule Name="Retain old Security events" Operator="GreaterThan" Severity="Informational" ValueA="0"> <Description>Retain old events</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Retain old Security events" Operator="Equals" Severity="Critical" id="Channel_Log_Retention_2"> <Description /> <Value ValueA="Disabled" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{87b67dfd-0050-46be-b059-7a5bc27450d6}" 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="{dd870988-2b4c-4893-8121-8107e23ce62a}" 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="{0dbf2d2a-8241-4651-ba0e-fa44f21c205a}" 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 /> <Value ValueA="1" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{37a7c6aa-cec8-48e8-8696-ad205278c119}" 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="{8ea9ed06-2613-4007-b957-bc45ef84c196}" 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 /> <Value ValueA="0" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{c131f351-2c48-4368-87be-c6d02782f531}" 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 /> <Value ValueA="1" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{a0b0d923-27e7-4a27-9eb2-f5816e408983}" 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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{9879927b-0fed-44e0-bef6-b356c96c23b2}" Severity="Optional" /> <ExistentialRule Name="Require user authentication for remote connections by using Network Level Authentication" Operator="GreaterThan" Severity="None" ValueA="0"> <Description>Require user authentication for remote connections by using Network Level Authentication</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Require user authentication for remote connections by using Network Level Authentication" Operator="Equals" Severity="Informational" id="TS_USER_AUTHENTICATION_POLICY"> <Description /> <Value ValueA="Enabled" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{f819013e-bb1d-4b2f-a412-605d023d03af}" 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="{1ff9acbd-9502-449e-8190-abe5600525f1}" 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 /> <Value ValueA="False" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{b149d65d-ab8e-4978-aa97-098e23f8141e}" 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="{0b0f3e44-3c02-49f9-8dc9-b928c67ceaeb}" 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="{be75df5a-acf5-4dcc-846f-b59887b9d7ed}" 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="{842b8a87-dfd5-4fb5-afac-5ce6535cde3e}" 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="{ac1cb4ab-0043-434e-ac04-6113670e316b}" 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="{0239af2e-7bef-4f73-ba18-1c879e8f5607}" 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="{c8539e2a-518c-439d-9fbe-52e47f4d7605}" 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="{1d73fbc4-ddc3-46e2-b89d-1683fd35be82}" Severity="Important" /> <ExistentialRule Name="Network access: Remotely accessible registry paths and sub-paths" Operator="GreaterThan" Severity="Informational" 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 /> <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="{18a13c8c-6e88-4fe8-8a59-76ce952283c1}" 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="{ac06599d-73de-4e84-a7f9-b6ad81d13276}" Severity="Important" /> <ExistentialRule Name="Network access: Remotely accessible registry paths" Operator="GreaterThan" Severity="Informational" 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 /> <Value ValueA="System\CurrentControlSet\Control\ProductOptions
System\CurrentControlSet\Control\Server Applications
Software\Microsoft\Windows NT\CurrentVersion
" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{029d0857-80ca-44f5-a4b6-f739f0221aa9}" 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="{22e26ced-34e2-42ce-ba97-4e7d967c33bb}" 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="{35830c81-b6b8-4b14-9907-3761b7e139ab}" 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 /> <Value ValueA="Administrators" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{d7ec0317-708c-4274-809f-224fe2f06d45}" 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="{a67b797e-c129-4a25-ba26-cf34e33a558f}" 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 /> <Value ValueA="Administrators" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{b3c78a52-a565-4d52-9944-52b07cc2455f}" 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="{a17804d8-98a5-4300-98dd-1ff45c32e442}" 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="{ba25b6e3-16fc-46a9-a5b2-18e71080c4b2}" 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" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{745eceb6-02c1-421c-a901-19bb8f7e58e5}" 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="{b727fae4-1c3d-4df4-b3a9-af2f56594b97}" 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="{df236122-5bec-4d70-9779-01af4e3fab2c}" 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" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{ee2f7f2a-7c63-4738-84f6-80adca85d2b1}" 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="LessOrEqual" 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, IIS APPPOOL\DefaultAppPool" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{ba4498d2-9c57-437a-987d-e23715f89aba}" 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="LessOrEqual" 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, IIS APPPOOL\DefaultAppPool" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{3846e648-ac41-4a1a-8eee-fd5b5f32307d}" 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="{a6847356-7858-4a2f-88c9-1bd2e51d9b3b}" 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="{a32e24bf-093e-47ca-be50-54863b467b46}" Severity="Important" /> <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="Warning" 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" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{4466f092-301f-4c80-8933-ab479ccadfbb}" 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="Administrators" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{257c4081-0278-4785-a6a6-8c44653cfdb7}" 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="{da248703-5c1d-4c9f-8294-3b86b2222425}" 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="{42c34fe5-f793-4ceb-91c8-1a614fe2acd1}" 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="LessOrEqual" 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, IIS_IUSRS" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{b74c8d46-e23c-47b3-9f5a-1f37890b905f}" 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="{5830a178-7a84-48f1-8bba-df5535aaee50}" 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="Administrators, Authenticated Users" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{a6cfe6c4-2949-4e30-a2d7-335baf9c9721}" 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="{f588029b-66bd-40d8-bd0a-29a579aadc30}" 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="Administrators, Authenticated Users, Backup Operators, Local Service, Network Service" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{c69f490d-63ba-4475-b3fc-27083773f07f}" 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="{d87bc7fb-eb43-4485-8611-38a6846627c8}" 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 /> <Value ValueA="0" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{055bbc50-4de1-4e78-80fd-321a607174ee}" 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 /> <Value ValueA="1" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{86bf6fd4-7fe8-4c18-a74f-817a28f86d6b}" Severity="Critical" /> <ExistentialRule Name="User Account Control: Only elevate UIAccess applications that are installed in secure locations" Operator="GreaterThan" Severity="Informational" 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 /> <Value ValueA="1" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{28313a00-0b64-49c0-a199-7301c8887941}" 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="{a0e9a455-1625-4a8a-831f-9f0bcf5614cf}" 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 /> <Value ValueA="0" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{4eb8bad7-0e87-483c-905f-f0cae5323360}" Severity="Critical" /> <ExistentialRule Name="User Account Control: Virtualize file and registry write failures to per-user locations" Operator="GreaterThan" Severity="Informational" 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 /> <Value ValueA="1" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{f688e052-605c-48b5-9600-9ed46a34fe14}" Severity="Critical" /> <ExistentialRule Name="User Account Control: Only elevate executables that are signed and validated" Operator="GreaterThan" Severity="Informational" 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 /> <Value ValueA="0" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{a3596a1f-1ecb-4800-8750-6b2088657bc4}" 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 /> <Value ValueA="3" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{b2825c9d-9d7b-4dd7-b4e2-22a9d6d2999a}" 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 /> <Value ValueA="1" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{1ee1c8ec-d5bd-4f15-b9ed-31c95bed7f28}" Severity="Critical" /> <ExistentialRule Name="User Account Control: Run all administrators in Admin Approval Mode" Operator="GreaterThan" Severity="Informational" 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 /> <Value ValueA="1" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{a37311b1-65b5-435c-9122-32137c99168f}" Severity="Critical" /> <ExistentialRule Name="User Account Control: Switch to the secure desktop when prompting for elevation" Operator="GreaterThan" Severity="Informational" 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 /> <Value ValueA="1" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{9777622a-3415-4141-b3c3-6b739db9c40c}" 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 /> <Value ValueA="5" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{8ee4bb8c-ad79-48ec-99ae-98a2c54c6105}" Severity="Critical" /> <ExistentialRule Name="Require trusted path for credential entry" Operator="GreaterThan" Severity="None" 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 /> <Value ValueA="Enabled" /> </SettingRule> </ValidationRules> </Check> <Check> <SettingRef setting_ref="{fcbb701f-88ab-4618-be42-55d2be230218}" 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 xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{25c149ae-0822-4f8c-885b-6d6a9a03963b}" Severity="Critical" /> <ExistentialRule Name="Always prompt for password upon connection" Operator="GreaterThan" Severity="None" 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 /> <Value ValueA="Enabled" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{f37ec02b-1925-4cc5-997c-c72912af268c}" Severity="Critical" /> <ExistentialRule Name="Do not allow passwords to be saved" Operator="GreaterThan" Severity="None" 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 /> <Value ValueA="Enabled" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{a1d0e16e-e734-4790-b8ca-204b20d5b89c}" Severity="Critical" /> <ExistentialRule Name="Enforce password history" Operator="GreaterThan" Severity="None" ValueA="0"> <Description>Enforce password history</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Enforce password history" Operator="Equals" Severity="Critical" id="{af0d2d51-8fa9-4015-a59f-44f18c777f3d}"> <Description /> <Value ValueA="24" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{d3c1e430-62b3-4e94-8aff-84db4abc82e6}" Severity="Critical" /> <ExistentialRule Name="Store passwords using reversible encryption" Operator="GreaterThan" Severity="None" ValueA="0"> <Description>Store passwords using reversible encryption</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Store passwords using reversible encryption" Operator="Equals" Severity="Critical" id="{f165f25c-446b-43c4-979a-53c86d894218}"> <Description /> <Value ValueA="False" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{61b3f0bd-4106-464f-9ffb-39255ff9cd58}" Severity="Critical" /> <ExistentialRule Name="Minimum password age" Operator="GreaterThan" Severity="None" ValueA="0"> <Description>Minimum password age</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Minimum password age" Operator="Equals" Severity="Critical" id="{5ded6573-fb98-48ba-be4c-50e572690666}"> <Description /> <Value ValueA="1" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{7ac8fbc8-eecc-4e14-b68c-498df8dcf697}" Severity="Optional" /> <ExistentialRule Name="Devices: Allow undock without having to log on" Operator="GreaterThan" Severity="None" 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 /> <Value ValueA="0" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{abf4270e-5b23-4602-aaa4-fe02ef0cb0b0}" Severity="Optional" /> <ExistentialRule Name="MSS: (NtfsDisable8dot3NameCreation) Enable the computer to stop generating 8.3 style filenames" Operator="GreaterThan" Severity="None" ValueA="0"> <Description>MSS: (NtfsDisable8dot3NameCreation) Enable the computer to stop generating 8.3 style filenames</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="MSS: (NtfsDisable8dot3NameCreation) Enable the computer to stop generating 8.3 style filenames" Operator="Equals" Severity="Informational" id="{132e1b76-6a75-4d53-9c1f-ecead7636975}"> <Description /> <Value ValueA="Not Defined" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{3db85b27-a930-4714-b0bd-be050b063580}" Severity="Critical" /> <ExistentialRule Name="Registry policy processing" Operator="GreaterThan" Severity="None" ValueA="0"> <Description>Registry policy processing</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Registry policy processing" Operator="Equals" Severity="Critical" id="CSE_Registry"> <Description /> <Value ValueA="Enabled" /> </SettingRule> <OptionRule Name="Do not apply during periodic background processing" Operator="Equals" Severity="None" id="CSE_NOBACKGROUND10"> <Description /> <Value ValueA="False" /> </OptionRule> <OptionRule Name="Process even if the Group Policy objects have not changed" Operator="Equals" Severity="None" id="CSE_NOCHANGES10"> <Description /> <Value ValueA="True" /> </OptionRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{b97ea12f-9ee5-4abe-9928-98fa9f8b9b4d}" Severity="Critical" /> <ExistentialRule Name="Minimum password length" Operator="GreaterThan" Severity="None" ValueA="0"> <Description>Minimum password length</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Minimum password length" Operator="GreaterEquals" Severity="Critical" id="{3aac62ae-89a5-4615-892a-0487867a6fc3}"> <Description /> <Value ValueA="12" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{6f6a3805-b798-4d65-a61c-89f07554e7e3}" Severity="Critical" /> <ExistentialRule Name="Password must meet complexity requirements" Operator="GreaterThan" Severity="None" ValueA="0"> <Description>Password must meet complexity requirements</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Password must meet complexity requirements" Operator="Equals" Severity="Critical" id="{02eecc8f-c965-4459-9456-fc1fba6800cd}"> <Description /> <Value ValueA="True" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{e5b84241-75e1-4578-8b76-9c070095a456}" Severity="Critical" /> <ExistentialRule Name="Turn off downloading of print drivers over HTTP" Operator="GreaterThan" Severity="None" 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 /> <Value ValueA="Enabled" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{ad5e8cf0-e1ac-4667-b101-21bf0de845bb}" Severity="Critical" /> <ExistentialRule Name="Turn off Internet download for Web publishing and online ordering wizards" Operator="GreaterThan" Severity="None" 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 /> <Value ValueA="Enabled" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{0e750f63-94f3-4ee5-8956-191af9aefd4d}" Severity="Critical" /> <ExistentialRule Name="Turn off printing over HTTP" Operator="GreaterThan" Severity="None" 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 /> <Value ValueA="Enabled" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{f56ab036-9c85-4fe6-96f9-9d4d328bfc88}" Severity="Critical" /> <ExistentialRule Name="Turn off Search Companion content file updates" Operator="GreaterThan" Severity="None" 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 /> <Value ValueA="Enabled" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{ce2e90b0-2305-4169-8fa1-eadd8942570d}" Severity="Critical" /> <ExistentialRule Name="Turn off the "Publish to Web" task for files and folders" Operator="GreaterThan" Severity="None" 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 /> <Value ValueA="Enabled" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{2999c1ca-bed4-4b51-8ea5-8bf025fccf92}" Severity="Critical" /> <ExistentialRule Name="Turn off the Windows Messenger Customer Experience Improvement Program" Operator="GreaterThan" Severity="None" 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 /> <Value ValueA="Enabled" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{df07738d-5931-419d-8235-6f5e7c593126}" Severity="Critical" /> <ExistentialRule Name="Maximum password age" Operator="GreaterThan" Severity="None" ValueA="0"> <Description>Maximum password age</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Maximum password age" Operator="LessEquals" Severity="Critical" id="{9147edfc-62b3-45ad-aa7c-64ec50eb2969}"> <Description /> <Value ValueA="70" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{b2a24f45-fab7-4aab-8dc7-ea4321a14784}" Severity="Critical" /> <ExistentialRule Name="Reset account lockout counter after" Operator="GreaterThan" Severity="None" ValueA="0"> <Description>Reset account lockout counter after</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Reset account lockout counter after" Operator="Equals" Severity="Critical" id="{9f7c56fb-c689-4f35-a322-b1dd6fd88a26}"> <Description /> <Value ValueA="15" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{ed1a9aa2-5058-40fb-93d2-2e305be45afd}" Severity="Critical" /> <ExistentialRule Name="Account lockout threshold" Operator="GreaterThan" Severity="None" ValueA="0"> <Description>Account lockout threshold</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Account lockout threshold" Operator="Equals" Severity="Critical" id="{6b1d3868-82dd-4f75-932f-f81be9b6b798}"> <Description /> <Value ValueA="50" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{7079d671-dace-4f56-8652-e3a9448f371c}" Severity="Critical" /> <ExistentialRule Name="Account lockout duration" Operator="GreaterThan" Severity="None" ValueA="0"> <Description>Account lockout duration</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Account lockout duration" Operator="Equals" Severity="Critical" id="{0b61dc30-21ee-438a-b437-ff6faf6c477f}"> <Description /> <Value ValueA="15" /> </SettingRule> </ValidationRules> </Check> <!--TO DO: Check why we need the id field--> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{825abafe-20d8-4520-af63-6bfa1adf8d3b}" Severity="Important" /> <ExistentialRule Name="Enable Windows Error Reporting (Policy Check)" Operator="Equals" Severity="Important" ValueA="0"> <Description>Enable Windows Error Reporting (Policy Check)</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Enable Windows Error Reporting (Policy Check)" Operator="Equals" Severity="Important" id="WerDisable_1"> <Description /> <Value ValueA="0" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{3a0fdd4a-e4c3-4788-9240-fd86f6df2225}" Severity="Important" /> <ExistentialRule Name="Enable Windows Error Reporting (Registry Check)" Operator="Equals" Severity="Important" ValueA="0"> <Description>Enable Windows Error Reporting (Registry Check)</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Enable Windows Error Reporting (Registry Check)" Operator="Equals" Severity="Important" id="WerDisable_1"> <Description /> <Value ValueA="0" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{d8081a87-a751-4fe3-bb1f-5dc27f0a6d9f}" Severity="Important" /> <ExistentialRule Name="Ensure Azure Watson is configured correctly (Registry Check:ForceQueue)" Operator="Equals" Severity="Important" ValueA="2"> <Description>Ensure Azure Watson is configured correctly (Registry Check:ForceQueue)</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Ensure Azure Watson is configured correctly (Registry Check:ForceQueue)" Operator="Equals" Severity="Important" id="WerDisable_1"> <Description /> <Value ValueA="2" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{6798451d-438b-498d-8d7c-1249802b1530}" Severity="Important" /> <ExistentialRule Name="Ensure Azure Watson is configured correctly (Registry Check:DefaultConsent)" Operator="Equals" Severity="Important" ValueA="1"> <Description>Ensure Azure Watson is configured correctly (Registry Check:DefaultConsent)</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Ensure Azure Watson is configured correctly (Registry Check:DefaultConsent)" Operator="Equals" Severity="Important" id="WerDisable_1"> <Description /> <Value ValueA="1" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{80de7581-89eb-4fe2-9c7b-cc69243494e6}" Severity="Important" /> <ExistentialRule Name="Enable Command-line logging" Operator="Equals" Severity="Important" ValueA="1"> <Description>Enable Command-line logging</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Enable Command-line logging" Operator="Equals" Severity="Important" id="{111d3868-82dd-4f75-932f-f81be9b6b798}"> <Description /> <Value ValueA="1" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{23b42fec-1e67-458c-89f1-0ee0e9e5224c}" Severity="Important" /> <ExistentialRule Name="Ensure Microsoft Anti-malware is enabled:schedule scan day" Operator="LessOrEqual" Severity="Important" ValueA="7"> <Description>Ensure Microsoft Anti-malware is enabled:schedule scan day</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Ensure Microsoft Anti-malware is enabled:schedule scan day" Operator="LessOrEqual" Severity="Important" id="{222d3868-82dd-4f75-932f-f81be9b6b798}"> <Description /> <Value ValueA="7" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{f1daa65d-03ba-48ac-9ca4-184740ef0794}" Severity="Important" /> <ExistentialRule Name="Ensure Microsoft Anti-malware is enabled:schedule scan time" Operator="GreaterThan" Severity="Important" ValueA="0"> <Description>Ensure Microsoft Anti-malware is enabled:schedule scan time</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Ensure Microsoft Anti-malware is enabled:schedule scan time" Operator="GreaterThan" Severity="Important" id="{333d3868-82dd-4f75-932f-f81be9b6b798}"> <Description /> <Value ValueA="0" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{7d6282bf-6678-4fa3-adb5-3e10297bb2f6}" Severity="Important" /> <ExistentialRule Name="Microsoft Antimalware signature update should occur every 8 hours" Operator="LessOrEqual" Severity="Important" ValueA="8"> <Description>Microsoft Antimalware signature update should occur every 8 hours</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Microsoft Antimalware signature update should occur every 8 hours" Operator="LessOrEqual" Severity="Important" id="{444d3868-82dd-4f75-932f-f81be9b6b798}"> <Description /> <Value ValueA="8" /> </SettingRule> </ValidationRules> </Check> <Check xmlns="http://schemas.microsoft.com/SolutionAccelerator/SecurityCompliance"> <SettingRef setting_ref="{b868f59b-8323-4bb7-ac3e-5c0aa96cf4b2}" Severity="Important" /> <ExistentialRule Name="Enable SecureBoot" Operator="Equals" Severity="Important" ValueA="1"> <Description>Enable SecureBoot</Description> </ExistentialRule> <ValidationRules> <SettingRule Name="Enable SecureBoot" Operator="Equals" Severity="Important" id="{555d3868-82dd-4f75-932f-f81be9b6b798}"> <Description /> <Value ValueA="1" /> </SettingRule> </ValidationRules> </Check> <Comment> </Comment> </Baseline> <Product ID="{eb659f7b-1271-460e-9bbf-0809b4a90d60}" DisplayName="Windows Server 2008 R2 SP1"> <OperatingSystemInfo MajorVersion="6" MinorVersion="1" BuildVersion="7601" /> <ProductFamilyRef productfamily_ref="{5cea53d1-8a08-4804-8886-1ddea5899aea}" /> <CPE> <CPE-Dictionary>Windows Server 2008 R2 SP1-CPE-Dictionary.xml</CPE-Dictionary> <CPE-Oval>Windows Server 2008 R2 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> |