acceptedWindows 8 / 8.1 Security Technical Implementation GuideThe Windows 8 / 8.1 Security Technical Implementation Guide (STIG) is published as a tool to improve the security of Department of Defense (DoD) information systems. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.stig_spt@mail.mil.Developed_by_DISA_for_the_DoDDISASTIG.DOD.MILRelease: 16 Benchmark Date: 27 Jan 20171I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>Physical security<GroupDescription></GroupDescription>WN08-00-000001Systems must be physically secured.<VulnDiscussion>Inadequate physical protection can undermine all other security precautions utilized to protect the system. This can jeopardize the confidentiality, availability, and integrity of the system. Physical security is the first line of protection of any system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Establish site policy that ensures workstations containing sensitive data are located inside a controlled access area. Establish a policy on protecting mobile systems outside of controlled areas.Verify user workstations containing sensitive data are in access-controlled areas. Users must maintain control of, and protect, mobile systems. If systems are not adequately protected, this is a finding.Shared User Accounts<GroupDescription></GroupDescription>WN08-00-000002Shared user accounts must not be permitted on the system.<VulnDiscussion>Shared accounts (accounts where two or more people log on with the same user identification) do not provide adequate identification and authentication. There is no way to provide for non-repudiation or individual accountability for system access and resource usage. Documentation must include a list of personnel that have access to each shared account.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000764Create or update shared accounts documentation that minimally contains the name of the shared account(s), the system(s) on which the accounts exist, and the individuals who have access to the accounts. Remove any shared accounts that do not meet the requirements.Determine if any shared accounts exist. If no shared accounts exist, this is NA.
Any shared account must be documented with the ISSO. Documentation must include the reason for the account, who has access to this account, and how the risk of using a shared account (which provides no individual identification and accountability) is mitigated. If such documentation does not exist, or is not current, this is a finding.
Note: As an example, a shared account may be permitted for a help desk or a site security personnel machine, if that machine is standalone and has no access to the network.Unsupported Service Packs<GroupDescription></GroupDescription>WN08-GE-000001Systems must be maintained at a supported version of an operating system.<VulnDiscussion>Systems at unsupported versions or releases of an operating system will not receive security updates for new vulnerabilities which leaves them subject to exploitation. Systems must be maintained at a version of the operating system supported by the vendor with new security updates.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Update the system to a version of the operating system supported by the vendor.
Support for the initial release of Windows 8 ended 12 January 2016. After this date, systems must have Windows 8.1 installed.Support for the initial release of Windows 8 ended 12 January 2016. After this date, systems must have Windows 8.1 installed.
Run "winver.exe".
If the "About Windows" dialog box does not display:
"Microsoft Windows
Version 6.3 (Build 9600)"
or greater this is a finding.Approved DoD Virus Scan Program<GroupDescription></GroupDescription>WN08-GE-000002An approved, up-to-date, DoD antivirus program must be installed and used.<VulnDiscussion>Antivirus programs are a primary line of defense against the introduction of viruses and malicious code that can destroy data and even render a computer inoperable. Utilizing an antivirus program provides the ability to detect malicious code before extensive damage occurs. Updated virus scan data files help to protect a system, since new malware are identified by the software vendors on a continual basis.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance>If another recognized antivirus product is installed and has a current signature, this would still be a finding; however, the severity may be reduced to a Category III.</SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Install McAfee VirusScan Enterprise 8.8 or later on the system. Update the signature file at least every 7 days.If V-19910 from an antivirus STIG has been applied to the system, the signature verification portion of this requirement is NA.
Verify a supported DoD antivirus product has been installed on the system.
If McAfee VirusScan Enterprise 8.8 Patch 3 or later is not installed on the system, this is a finding.
And
If a product other than McAfee VirusScan Enterprise is used and V-19910 from an antivirus STIG has not been applied to the system, verify the date of the antivirus signature.
If the antivirus program signature has not been updated within the past 7 days, this is a finding.
The version numbers and the date of the signature can generally be checked by starting the antivirus program. The information may appear in the antivirus window or be available in the Help >> About window. The location varies from product to product.Display Shutdown Button<GroupDescription></GroupDescription>WN08-SO-000073The shutdown option must be available from the logon dialog box.<VulnDiscussion>Preventing display of the shutdown button in the logon dialog box may encourage a hard shut down with the power button. (However, displaying the shutdown button may allow individuals to shut down a system anonymously.)</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Shutdown: Allow system to be shutdown without having to log on" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Shutdown: Allow system to be shutdown without having to log on" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\System\
Value Name: ShutdownWithoutLogon
Value Type: REG_DWORD
Value: 1System Recovery Backups<GroupDescription></GroupDescription>WN08-00-000003System information backups must be created, updated, and protected.<VulnDiscussion>Recovery of a damaged or compromised system in a timely manner is difficult without a system information backup. A system backup will usually include sensitive information such as user accounts that could be used in an attack. As a valuable system resource, the system backup must be protected and stored in a physically secure location.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Implement system recovery procedures that include maintaining emergency system recovery data, protecting that data from destruction and storing it in a locked storage container, and updating it following each and every system modification.Determine if system recovery backup procedures are in place that comply with DoD requirements.
Any of the following would be a finding:
-The site does not maintain emergency system recovery data.
-The emergency system recovery data is not protected from destruction and stored in a locked storage container.
-The emergency system recovery data has not been updated following the last system modification.NTFS Requirement<GroupDescription></GroupDescription>WN08-GE-000005Local volumes must be formatted using NTFS.<VulnDiscussion>The ability to set access permissions and auditing is critical to maintaining the security and proper access controls of a system. To support this, volumes must be formatted using the NTFS file system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000213Format all local partitions/drives to use NTFS.Open the Computer Management Console.
Expand the "Storage" object in the left pane.
Select the "Disk Management" object.
If the file system column does not indicate "NTFS" as the file system for each local hard drive, this is a finding.
Some hardware vendors create a small FAT partition to store troubleshooting and recovery data. No other files must be stored here. This must be documented with the ISSO.Legal Notice Display<GroupDescription></GroupDescription>WN08-SO-000022The required legal notice must be configured to display before console logon.<VulnDiscussion>Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000048CCI-000050CCI-001384CCI-001385CCI-001386CCI-001387CCI-001388Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Interactive Logon: Message text for users attempting to log on" to the following.
You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.
By using this IS (which includes any device attached to this IS), you consent to the following conditions:
-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.
-At any time, the USG may inspect and seize data stored on this IS.
-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.
-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.
-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Interactive Logon: Message text for users attempting to log on" is not set to the following, this is a finding:
You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.
By using this IS (which includes any device attached to this IS), you consent to the following conditions:
-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.
-At any time, the USG may inspect and seize data stored on this IS.
-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.
-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.
-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.
Any OS versions that do not support the full text version must state the following:
"I've read & consent to terms in IS user agreem't."
Deviations are not permitted except as authorized by the Deputy Assistant Secretary of Defense for Information and Identity Assurance.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\System\
Value Name: LegalNoticeText
Value Type: REG_SZ
Value: See message text aboveCaching of logon credentials<GroupDescription></GroupDescription>WN08-SO-000024Caching of logon credentials must be limited.<VulnDiscussion>The default Windows configuration caches the last logon credentials for users who log on interactively to a system. This feature is provided for system availability reasons, such as the user's machine being disconnected from the network or domain controllers being unavailable. Even though the credential cache is well-protected, if a system is attacked, an unauthorized individual may isolate the password to a domain user account using a password-cracking program and gain access to the domain.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366If the system is not a member of a domain, this is NA.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Interactive Logon: Number of previous logons to cache (in case Domain Controller is not available)" to "4" logons or less.If the system is not a member of a domain, this is NA.
Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Interactive Logon: Number of previous logons to cache (in case Domain Controller is unavailable)" is not set to "4" logons or less, this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\
Value Name: CachedLogonsCount
Value Type: REG_SZ
Value: 4 (or less)Anonymous shares are not restricted<GroupDescription></GroupDescription>WN08-SO-000052Anonymous enumeration of shares must be restricted.<VulnDiscussion>Allowing anonymous logon users (null session connections) to list all account names and enumerate all shared resources can provide a map of potential points to attack the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1, PRNK-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001090Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network access: Do not allow anonymous enumeration of SAM accounts and shares" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Network access: Do not allow anonymous enumeration of SAM accounts and shares" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Control\Lsa\
Value Name: RestrictAnonymous
Value Type: REG_DWORD
Value: 1Bad Logon Attempts<GroupDescription></GroupDescription>WN08-AC-000002The number of allowed bad logon attempts must meet minimum requirements.<VulnDiscussion>The account lockout feature, when enabled, prevents brute-force password attacks on the system. The higher this value is, the less effective the account lockout feature will be in protecting the local system. The number of bad logon attempts must be reasonably small to minimize the possibility of a successful password attack, while allowing for honest errors made during a normal user logon.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000044Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Account Policies -> Account Lockout Policy -> "Account lockout threshold" to "3" or less invalid logon attempts (excluding "0" which is unacceptable).Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Account Policies -> Account Lockout Policy.
If the "Account lockout threshold" is "0" or more than 3 attempts, this is a finding.Bad Logon Counter Reset<GroupDescription></GroupDescription>WN08-AC-000003The period of time before the bad logon counter is reset must meet minimum requirements.<VulnDiscussion>The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the period of time that must pass after failed logon attempts before the counter is reset to 0. The smaller this value is, the less effective the account lockout feature will be in protecting the local system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000044CCI-002238Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Account Policies -> Account Lockout Policy -> "Reset account lockout counter after" to at least "60" minutes.Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Account Policies -> Account Lockout Policy.
If the "Reset account lockout counter after" value is less than 60 minutes, this is a finding.Lockout Duration<GroupDescription></GroupDescription>WN08-AC-000001The lockout duration must be configured to require an administrator to unlock an account.<VulnDiscussion>The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the amount of time that an account will remain locked after the specified number of failed logon attempts. A value of 0 will require an administrator to unlock the account.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002238Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Account Policies -> Account Lockout Policy -> "Account lockout duration" to "0" minutes, "Account is locked out until administrator unlocks it".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Account Policies -> Account Lockout Policy.
If the "Account lockout duration" is not set to "0", requiring an administrator to unlock the account, this is a finding.User Right - Act as part of OS<GroupDescription></GroupDescription>WN08-UR-000003No accounts must be granted the Act as part of the operating system user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Act as part of the operating system" user right can assume the identity of any user and gain access to resources that user is authorized to access. Any accounts with this right can take complete control of a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Act as part of the operating system" to be defined but containing no entries (blank).Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups (to include administrators), are granted the "Act as part of the operating system" user right, this is a finding.Maximum Password Age <GroupDescription></GroupDescription>WN08-AC-000005The maximum password age must meet requirements.<VulnDiscussion>The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the passwords. Scheduled changing of passwords hinders the ability of unauthorized system users to crack passwords and gain access to a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000199Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Account Policies -> Password Policy -> "Maximum Password Age" to "60" days or less (excluding "0" which is unacceptable).Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Account Policies -> Password Policy.
If the value for the "Maximum password age" is greater than 60 days, this is a finding. If the value is set to 0 (never expires), this is a finding.Minimum Password Age<GroupDescription></GroupDescription>WN08-AC-000006The minimum password age must meet requirements.<VulnDiscussion>Permitting passwords to be changed in immediate succession within the same day allows users to cycle passwords through their history database. This enables users to effectively negate the purpose of mandating periodic password changes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000198Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Account Policies -> Password Policy -> "Minimum Password Age" to at least "1" day.Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Account Policies -> Password Policy.
If the value for the "Minimum password age" is less than one day, this is a finding.Password Uniqueness<GroupDescription></GroupDescription>WN08-AC-000004The password history must be configured to 24 passwords remembered.<VulnDiscussion>A system is more vulnerable to unauthorized access when system users recycle the same password several times without being required to change a password to a unique password on a regularly scheduled basis. This enables users to effectively negate the purpose of mandating periodic password changes. The default value is 24 for Windows domain systems. DoD has decided this is the appropriate value for all Windows systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000200Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Enforce password history" to "24" passwords remembered.Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Account Policies >> Password Policy.
If the value for "Enforce password history" is less than "24" passwords remembered, this is a finding.Dormant Accounts<GroupDescription></GroupDescription>WN08-GE-000007Outdated or unused accounts must be removed from the system.<VulnDiscussion>Outdated or unused accounts provide penetration points that may go undetected. Inactive accounts must be deleted if no longer necessary or, if still required, disable until needed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000795Regularly review accounts to determine if they are still active. Accounts that have not been used in the last 35 days must be removed or disabled.Run the DUMPSEC utility.
Select "Dump Users as Table" from the "Report" menu.
Select the following fields, and click "Add" for each entry:
UserName
SID
LastLogonTime
AcctDisabled
Review the "LastLogonTime".
If any enabled accounts have not been logged on to within the past 35 days, this is a finding.
The following accounts are exempt:
Built-in administrator account (SID ending in 500)
Built-in guest account (SID ending in 501)
Application accounts
Disabled accounts
Review the list to determine the finding validity for each account reported.
If the organization has a need for special purpose local user accounts such as a backup administrator account (see V-14224), this must be documented with the ISSO. This would not be a finding.
Dormant accounts that have been reviewed and deemed to be required must be documented with the ISSO.Disable Guest Account<GroupDescription></GroupDescription>WN08-SO-000003The built-in guest account must be disabled.<VulnDiscussion>A system faces an increased vulnerability threat if the built-in guest account is not disabled. This account is a known account that exists on all Windows systems and cannot be deleted. This account is initialized during the installation of the operating system with no password assigned.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000804Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Accounts: Guest account status" to "Disabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Accounts: Guest account status" is not set to "Disabled", this is a finding.Rename Built-in Guest Account<GroupDescription></GroupDescription>WN08-SO-000006The built-in guest account must be renamed.<VulnDiscussion>The built-in guest account is a well known user account on all Windows systems and, as initially installed, does not require a password. This can allow access to system resources by unauthorized users. Renaming this account to an unidentified name improves the protection of this account and the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Accounts: Rename guest account" to a name other than "Guest".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Accounts: Rename guest account" is not set to a value other than "Guest", this is a finding.Rename Built-in Administrator Account<GroupDescription></GroupDescription>WN08-SO-000005The built-in administrator account must be renamed.<VulnDiscussion>The built-in administrator account is a well-known account subject to attack. Renaming this account to an unidentified name improves the protection of this account and the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Accounts: Rename administrator account" to a name other than "Administrator".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Accounts: Rename administrator account" is not set to a value other than "Administrator", this is a finding.Booting into Multiple Operating Systems<GroupDescription></GroupDescription>WN08-GE-000008Alternate operating systems must not be permitted on the same system.<VulnDiscussion>Allowing other operating systems to run on a secure system may allow security to be circumvented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Ensure Windows 8 is the only operating system on a device. Remove alternate operating systems.Verify the local system boots directly into Windows.
Open Control Panel.
Select "System".
Select the "Advanced System Settings" link.
Select the "Advanced" tab.
Click the Startup and Recovery "Settings" button.
If the drop-down list box "Default operating system:" shows any operating system other than Windows 8, this is a finding.Restricted Administrator Group Membership<GroupDescription></GroupDescription>WN08-GE-000009Only accounts responsible for the administration of a system must have Administrator rights on the system.<VulnDiscussion>An account that does not have Administrator duties must not have Administrator rights. Such rights would allow the account to bypass or modify required security restrictions on that machine and make it vulnerable to attack.
System administrators must log on to systems only using accounts with the minimum level of authority necessary.
For domain-joined workstations, the Domain Admins group must be replaced by a domain workstation administrator group (see V-36434 in the Active Directory Domain STIG). Restricting highly privileged accounts from the local Administrators group helps mitigate the risk of privilege escalation resulting from credential theft attacks.
Systems dedicated to the management of Active Directory (AD admin platforms, see V-36436 in the Active Directory Domain STIG) are exempt from this. AD admin platforms may use the Domain Admins group or a domain administrative group created specifically for AD admin platforms (see V-43711 in the Active Directory Domain STIG).
Standard user accounts must not be members of the local administrators group.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the system to include only administrator groups or accounts that are responsible for the system in the local Administrators group.
For domain-joined workstations, the Domain Admins group must be replaced by a domain workstation administrator group.
Systems dedicated to the management of Active Directory (AD admin platforms, see V-36436 in the Active Directory Domain STIG) are exempt from this. AD admin platforms may use the Domain Admins group or a domain administrative group created specifically for AD admin platforms (see V-43711 in the Active Directory Domain STIG).
Remove any standard user accounts.Review the local Administrators group. Only the appropriate administrator groups or accounts responsible for administration of the system may be members of the group.
For domain-joined workstations, the Domain Admins group must be replaced by a domain workstation administrator group.
Systems dedicated to the management of Active Directory (AD admin platforms, see V-36436 in the Active Directory Domain STIG) are exempt from this. AD admin platforms may use the Domain Admins group or a domain administrative group created specifically for AD admin platforms (see V-43711 in the Active Directory Domain STIG).
Standard user accounts must not be members of the local administrator group.
If prohibited accounts are members of the local administrators group, this is a finding.
The built-in Administrator account or other required administrative accounts would not be a finding.Security Configuration Tools<GroupDescription></GroupDescription>WN08-00-000004Security configuration tools or equivalent processes must be used to configure and maintain platforms for security compliance.<VulnDiscussion>Security configuration tools such as Group Policies and Security Templates allow system administrators to consolidate security-related system settings into a single configuration file. These settings can then be applied consistently to any number of Windows machines. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Implement a process using security configuration tools or the equivalent to configure Windows systems to meet security requirements.Verify security configuration tools, or an equivalent process, are being used to configure Windows systems to meet security requirements. Security configuration tools that are integrated into Windows, such as Group Policies and Security Templates, may be used to configure platforms for security compliance.
If an alternate method is used to configure a system (e.g., manually using the DISA Windows Security STIGs, etc.) that achieves the same configured result, this is acceptable.System File ACLs<GroupDescription></GroupDescription>WN08-GE-000010Permissions for system files and directories must conform to minimum requirements.<VulnDiscussion>Changing the system's file and directory permissions allows the possibility of unauthorized and anonymous modification to the operating system and installed applications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002165Maintain the default file ACLs and configure the Security Option: "Network access: Let everyone permissions apply to anonymous users" to "Disabled" (V-3377).The default ACL settings are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (V-3377). If the default ACLs are maintained and the referenced option is set to "Disabled", this is not a finding.
Verify the default permissions for the sample directories below. Non-privileged groups such as Users or Authenticated Users must not have greater than Read & execute permissions except where noted as defaults. (Individual accounts must not be used to assign permissions.)
Viewing in File Explorer:
Select the "Security" tab, and the "Advanced" button.
C:\
Type - "Allow" for all
Inherited from - "None" for all
Principal - Access - Applies to
Administrators - Full control - This folder, subfolders and files
SYSTEM - Full control - This folder, subfolders and files
Users - Read & execute - This folder, subfolders and files
Authenticated Users - Modify - Subfolders and files only
Authenticated Users - Create folders / append data - This folder only
\Program Files
Type - "Allow" for all
Inherited from - "None" for all
Principal - Access - Applies to
TrustedInstaller - Full control - This folder and subfolders
SYSTEM - Modify - This folder only
SYSTEM - Full control - Subfolders and files only
Administrators - Modify - This folder only
Administrators - Full control - Subfolders and files only
Users - Read & execute - This folder, subfolders and files
CREATOR OWNER - Full control - Subfolders and files only
ALL APPLICATION PACKAGES - Read & execute - This folder, subfolders and files
\Windows
Type - "Allow" for all
Inherited from - "None" for all
Principal Access Applies to
TrustedInstaller - Full control - This folder and subfolders
SYSTEM - Modify - This folder only
SYSTEM - Full control - Subfolders and files only
Administrators - Modify - This folder only
Administrators - Full control - Subfolders and files only
Users - Read & execute - This folder, subfolders and files
CREATOR OWNER - Full control - Subfolders and files only
ALL APPLICATION PACKAGES - Read & execute - This folder, subfolders and files
Alternately use Icacls.
In a Command prompt (admin)
Enter icacls followed by the directory.
icacls c:\
icacls "c:\program files"
icacls c:\windows
The following results will be displayed as each is entered:
c:\
BUILTIN\Administrators:(OI)(CI)(F)
NT AUTHORITY\SYSTEM:(OI)(CI)(F)
BUILTIN\Users:(OI)(CI)(RX)
NT AUTHORITY\Authenticated Users:(OI)(CI)(IO)(M)
NT AUTHORITY\Authenticated Users:(AD)
Mandatory Label\High Mandatory Level:(OI)(NP)(IO)(NW)
Successfully processed 1 files; Failed processing 0 files
c:\program files
NT SERVICE\TrustedInstaller:(F)
NT SERVICE\TrustedInstaller:(CI)(IO)(F)
NT AUTHORITY\SYSTEM:(M)
NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F)
BUILTIN\Administrators:(M)
BUILTIN\Administrators:(OI)(CI)(IO)(F)
BUILTIN\Users:(RX)
BUILTIN\Users:(OI)(CI)(IO)(GR,GE)
CREATOR OWNER:(OI)(CI)(IO)(F)
APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(RX)
APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE)
Successfully processed 1 files; Failed processing 0 files
c:\windows
NT SERVICE\TrustedInstaller:(F)
NT SERVICE\TrustedInstaller:(CI)(IO)(F)
NT AUTHORITY\SYSTEM:(M)
NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F)
BUILTIN\Administrators:(M)
BUILTIN\Administrators:(OI)(CI)(IO)(F)
BUILTIN\Users:(RX)
BUILTIN\Users:(OI)(CI)(IO)(GR,GE)
CREATOR OWNER:(OI)(CI)(IO)(F)
APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(RX)
APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE)
Successfully processed 1 files; Failed processing 0 files
If an ACL setting prevents a site's applications from performing properly, settings must only be changed to the minimum necessary for the application to function. Each exception must be documented with the ISSO.Forcibly Disconnect when Logon Hours Expire<GroupDescription></GroupDescription>WN08-SO-000034Users must be forcibly disconnected when their logon hours expire.<VulnDiscussion>Users must not be permitted to remain logged on to the network after they have exceeded their permitted logon hours. In many cases, this indicates that a user forgot to log off before leaving for the day. However, it may also indicate that a user is attempting unauthorized access at a time when the system may be less closely monitored. Forcibly disconnecting users when logon hours expire protects critical and sensitive network data from exposure to unauthorized personnel with physical access to the computer.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001133Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Microsoft Network Server: Disconnect Clients When Logon Hours Expire" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Microsoft Network Server: Disconnect Clients When Logon Hours Expire" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Services\LanManServer\Parameters\
Value Name: EnableForcedLogoff
Value Type: REG_DWORD
Value: 1Unencrypted Password is Sent to SMB Server.<GroupDescription></GroupDescription>WN08-SO-000030Unencrypted passwords must not be sent to third-party SMB Servers.<VulnDiscussion>Some non-Microsoft SMB servers only support unencrypted (plain text) password authentication. Sending plain text passwords across the network, when authenticating to an SMB server, reduces the overall security of the environment. Check with the vendor of the SMB server to see if there is a way to support encrypted password authentication.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000197Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Microsoft Network Client: Send unencrypted password to third-party SMB servers" to "Disabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies >> Security Options.
If the value for "Microsoft Network Client: Send unencrypted password to third-party SMB servers" is not set to "Disabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\
Value Name: EnablePlainTextPassword
Value Type: REG_DWORD
Value: 0Disable Automatic Logon<GroupDescription></GroupDescription>WN08-SO-000036Automatic logons must be disabled.<VulnDiscussion>Allowing a system to automatically log on when the machine is booted could give access to any unauthorized individual who restarts the computer. Automatic logon with administrator privileges would give full access to an unauthorized individual.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance>If the DefaultName or DefaultDomainName in the same registry path contain an administrator account name and the DefaultPassword contains a value, this is a CAT I finding.</SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (AutoAdminLogon) Enable Automatic Logon (not recommended)" to "Disabled".
Ensure no passwords are stored in the "DefaultPassword" registry value noted below.
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Microsoft\Windows NT\CurrentVersion\Winlogon\
Value Name: DefaultPasswordAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
(See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)
If the value for "MSS: (AutoAdminLogon) Enable Automatic Logon (not recommended)" is not set to "Disabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Microsoft\Windows NT\CurrentVersion\Winlogon\
Value Name: AutoAdminLogon
Type: REG_SZ
Value: 0
Severity Override: If the "DefaultName" or "DefaultDomainName" in the same registry path contain an administrator account name and the "DefaultPassword" contains a value, this is a CAT I finding.Local Users Exist on a Workstation<GroupDescription></GroupDescription>WN08-GE-000013Local users must not exist on a system in a domain.<VulnDiscussion>To minimize potential points of attack, local users, other than built-in accounts such as Administrator and Guest accounts, must not exist on a workstation in a domain. Users must log onto workstations in a domain with their domain accounts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Limit local user accounts on domain-joined systems. Remove any unauthorized local accounts.Run the DUMPSEC utility.
Select "Dump Users as Table" from the "Report" menu.
Select the following fields, and click "Add" for each entry:
UserName
SID
AcctDisabled
Groups
If local users other than the built-in accounts listed below exist on a workstation in a domain, this is a finding:
Built-in administrator account (SID ending in 500)
Built-in guest account (SID ending in 501)
If the organization has a need for special purpose local user accounts such as a backup administrator account (see V-14224), this must be documented with the ISSO. This would not be a finding.Microsoft Strong Password Filtering<GroupDescription></GroupDescription>WN08-AC-000008The built-in Windows password complexity policy must be enabled.<VulnDiscussion>The use of complex passwords increases their strength against attack. The built-in Windows password complexity policy requires passwords to contain at least 3 of the 4 types of characters (numbers, upper- and lower-case letters, and special characters), as well as preventing the inclusion of user names or parts of.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000192CCI-000193CCI-000194CCI-001619Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Password must meet complexity requirements" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Account Policies >> Password Policy.
If the value for "Password must meet complexity requirements" is not set to "Enabled", this is a finding.
Note: If an external password filter is in use that enforces all 4 character types and requires this setting be set to "Disabled", this would not be considered a finding. If this setting does not affect the use of an external password filter, it must be enabled for fallback purposes.Anonymous Access to the Registry<GroupDescription></GroupDescription>WN08-GE-000014Anonymous access to the registry must be restricted.<VulnDiscussion>The registry is integral to the function, security, and stability of the Windows system. Some processes may require anonymous access to the registry. This must be limited to properly protect the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Maintain the default permissions of the following registry key as noted below:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\Winreg\
Administrators - Full Control
Backup Operators - Read (This key only)
LOCAL SERVICE - ReadRun "Regedit".
Navigate to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\Winreg\
If the key does not exist, this is a finding.
Review the permissions.
If the default permissions listed below have been changed, this is a finding.
Administrators - Full Control
Backup Operators - Read (This key only)
LOCAL SERVICE - ReadLanMan Authentication Level<GroupDescription></GroupDescription>WN08-SO-000067The LanMan authentication level must be set to send NTLMv2 response only, and to refuse LM and NTLM.<VulnDiscussion>The Kerberos v5 authentication protocol is the default for authentication of users who are logging on to domain accounts. NTLM which is less secure, is retained in later Windows versions for compatibility with clients and servers that are running earlier versions of Windows or applications that still use it. It is also used to authenticate logons to stand-alone computers that are running later versions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>IAIA-1, IAIA-2</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network security: LAN Manager authentication level" to "Send NTLMv2 response only. Refuse LM & NTLM".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Network security: LAN Manager authentication level" is not set to "Send NTLMv2 response only. Refuse LM & NTLM" (Level 5), this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Control\Lsa\
Value Name: LmCompatibilityLevel
Value Type: REG_DWORD
Value: 5Ctrl+Alt+Del Security Attention Sequence<GroupDescription></GroupDescription>WN08-SO-000019The Ctrl+Alt+Del security attention sequence for logons must be enabled.<VulnDiscussion>Disabling the Ctrl+Alt+Del security attention sequence can compromise system security. Because only Windows responds to the Ctrl+Alt+Del security sequence, you can be assured that any passwords you enter following that sequence are sent only to Windows. If you eliminate the sequence requirement, malicious programs can request and receive your Windows password. Disabling this sequence also suppresses a custom logon banner.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Interactive Logon: Do not require CTRL+ALT+DEL" to "Disabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Interactive Logon: Do not require CTRL+ALT+DEL" is not set to "Disabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\System\
Value Name: DisableCAD
Value Type: REG_DWORD
Value: 0Deny Access from the Network<GroupDescription></GroupDescription>WN08-UR-000017The Deny access to this computer from the network user right on workstations must be configured to prevent access from highly privileged domain accounts and local accounts on domain systems and unauthenticated access on all systems. <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
The "Deny access to this computer from the network" right defines the accounts that are prevented from logging on from the network.
In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower trust systems helps mitigate the risk of privilege escalation from credential theft attacks which could lead to the compromise of an entire domain.
Local accounts on domain-joined systems must also be assigned this right to decrease the risk of lateral movement resulting from credential theft attacks.
The Guests group must be assigned this right to prevent unauthenticated access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000213Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Deny access to this computer from the network" to include the following.
Domain Systems Only:
Enterprise Admins group
Domain Admins group
Local account (see Note below)
All Systems:
Guests group
Systems dedicated to the management of Active Directory (AD admin platforms, see V-36436 in the Active Directory Domain STIG) are exempt from denying the Enterprise Admins and Domain Admins groups.
Note: "Local account" is a built-in security group used to assign user rights and permissions to all local accounts.Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If the following accounts or groups are not defined for the "Deny access to this computer from the network" right, this is a finding:
Domain Systems Only:
Enterprise Admins group
Domain Admins group
Local account (see Note below)
All Systems:
Guests group
Systems dedicated to the management of Active Directory (AD admin platforms, see V-36436 in the Active Directory Domain STIG) are exempt from denying the Enterprise Admins and Domain Admins groups.
Note: "Local account" is a built-in security group used to assign user rights and permissions to all local accounts.Smart Card Removal Option <GroupDescription></GroupDescription>WN08-SO-000027The Smart Card removal option must be configured to Force Logoff or Lock Workstation.<VulnDiscussion>Unattended systems are susceptible to unauthorized use and must be locked. Configuring a system to lock when a smart card is removed will ensure the system is inaccessible when unattended.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Interactive logon: Smart card removal behavior" to "Lock Workstation" or "Force Logoff".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies >> Security Options.
If the value for "Interactive logon: Smart card removal behavior" is not set to "Lock Workstation" or "Force Logoff", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\
Value Name: SCRemoveOption
Value Type: REG_SZ
Value: 1 (Lock Workstation) or 2 (Force Logoff)
This can be left not configured or set to "No action" on workstations with the following conditions. This must be documented with the ISSO.
-The setting cannot be configured due to mission needs, or because it interferes with applications.
-Policy must be in place that users manually lock workstations when leaving them unattended.
-The screen saver is properly configured to lock as required.SMB Server Packet Signing (if client agrees)<GroupDescription></GroupDescription>WN08-SO-000033The Windows SMB server must perform SMB packet signing when possible.<VulnDiscussion>The server message block (SMB) protocol provides the basis for many network operations. Digitally signed SMB packets aid in preventing man-in-the-middle attacks. If this policy is enabled, the SMB server will negotiate SMB packet signing as requested by the client.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002418CCI-002421Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Microsoft Network Server: Digitally sign communications (if Client agrees)" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Microsoft Network Server: Digitally sign communications (if client agrees)" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Services\LanManServer\Parameters\
Value Name: EnableSecuritySignature
Value Type: REG_DWORD
Value: 1Encryption of Secure Channel Traffic<GroupDescription></GroupDescription>WN08-SO-000013Outgoing secure channel traffic must be encrypted when possible.<VulnDiscussion>Requests sent on the secure channel are authenticated, and sensitive information (such as passwords) is encrypted, but not all information is encrypted. If this policy is enabled, outgoing secure channel traffic will be encrypted.</VulnDiscussion><FalsePositives>If the value for Domain Member: Digitally encrypt or sign secure channel data (always) is set to Enabled, this would not be a finding.</FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002418CCI-002421Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Domain Member: Digitally encrypt secure channel data (when possible)" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Domain Member: Digitally encrypt secure channel data (when possible)" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Services\Netlogon\Parameters\
Value Name: SealSecureChannel
Value Type: REG_DWORD
Value: 1
Note: If the value for "Domain Member: Digitally encrypt or sign secure channel data (always)" is set to "Enabled", this would not be a finding.Signing of Secure Channel Traffic<GroupDescription></GroupDescription>WN08-SO-000014Outgoing secure channel traffic must be signed when possible.<VulnDiscussion>Requests sent on the secure channel are authenticated, and sensitive information (such as passwords) is encrypted, but the channel is not integrity checked. If this policy is enabled, outgoing secure channel traffic will be signed.</VulnDiscussion><FalsePositives>If the value for Domain Member: Digitally encrypt or sign secure channel data (always) is set to Enabled, this would not be a finding.</FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002418CCI-002421Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Domain Member: Digitally sign secure channel data (when possible)" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Domain Member: Digitally sign secure channel data (when possible)" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Services\Netlogon\Parameters\
Value Name: SignSecureChannel
Value Type: REG_DWORD
Value: 1
Note: If the value for "Domain Member: Digitally encrypt or sign secure channel data (always)" is set to "Enabled", this would not be a finding.Computer Account Password Reset<GroupDescription></GroupDescription>WN08-SO-000015The computer account password must not be prevented from being reset.<VulnDiscussion>Computer account passwords are changed automatically on a regular basis. Disabling automatic password changes can make the system more vulnerable to malicious access. Frequent password changes can be a significant safeguard for your system. A new password for the computer account will be generated every 30 days.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Domain Member: Disable Machine Account Password Changes" to "Disabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Domain Member: Disable Machine Account Password Changes" is not set to "Disabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Services\Netlogon\Parameters\
Value Name: DisablePasswordChange
Value Type: REG_DWORD
Value: 0SMB Client Packet Signing (if server agrees)<GroupDescription></GroupDescription>WN08-SO-000029The Windows SMB client must be enabled to perform SMB packet signing when possible.<VulnDiscussion>The server message block (SMB) protocol provides the basis for many network operations. If this policy is enabled, the SMB client will request packet signing when communicating with an SMB server that is enabled or required to perform SMB packet signing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002418CCI-002421Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Microsoft Network Client: Digitally sign communications (if server agrees)" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Microsoft Network Client: Digitally sign communications (if server agrees)" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Services\LanmanWorkstation\Parameters\
Value Name: EnableSecuritySignature
Value Type: REG_DWORD
Value: 1Members of the Backup Operators Group<GroupDescription></GroupDescription>WN08-00-000006Members of the Backup Operators group must have separate accounts for backup duties and normal operational tasks.<VulnDiscussion>Backup Operators are able to read and write to any file in the system, regardless of the rights assigned to it. Backup and restore rights permit users to circumvent the file access restrictions present on NTFS disk drives for backup and restore purposes. Members of the Backup Operators group must have separate logon accounts for performing backup duties.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Create the necessary documentation that identifies the members of the Backup Operators group, to be maintained with the ISSO.
Create separate accounts for backup operations for users with this privilege.
Create separate accounts for normal user functions for users with this privilege.Review the Backup Operators group in Computer Management.
If the group contains any accounts, this must be documented with the ISSO.
Any accounts that are members of the Backup Operators group must be documented, including application accounts. Users with accounts in the Backup Operators group will have a separate user account for backup functions and for performing normal user tasks.
If the group contains no accounts, this is not a finding.
If any of the following conditions are true, this is a finding:
-Each Backup Operator does not have a unique userid dedicated to the backup function.
-Each Backup Operator does not have a separate account for normal user tasks.
-The ISSO does not maintain a list of users belonging to the Backup Operators group.Format and Eject Removable Media<GroupDescription></GroupDescription>WN08-SO-000011Ejection of removable NTFS media must be restricted to Administrators.<VulnDiscussion>Removable hard drives can be formatted and ejected by others who are not members of the Administrators Group, if they are not properly configured. Formatting and ejecting removable NTFS media must only be done by administrators.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Devices: Allowed to Format and Eject Removable Media" to "Administrators".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Devices: Allowed to Format and Eject Removable Media" is not set to " Administrators", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \Software\Microsoft\Windows NT\CurrentVersion\Winlogon
Value Name: AllocateDASD
Value Type: REG_SZ
Value: 0Password Expiration Warning<GroupDescription></GroupDescription>WN08-SO-000025Users must be warned in advance of their passwords expiring.<VulnDiscussion>Creating strong passwords that can be remembered by users requires some thought. By giving the user advance warning, the user has time to construct a sufficiently strong password. This setting configures the system to display a warning to users telling them how many days are left before their password expires.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Interactive Logon: Prompt user to change password before expiration" to "14" days or more.Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Interactive Logon: Prompt user to change password before expiration" is not set to "14" days or more, this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \Software\Microsoft\Windows NT\CurrentVersion\Winlogon\
Value Name: PasswordExpiryWarning
Value Type: REG_DWORD
Value: 14Global System Objects Permission Strength<GroupDescription></GroupDescription>WN08-SO-000076The default permissions of global system objects must be increased.<VulnDiscussion>Windows systems maintain a global list of shared system resources such as DOS device names, mutexes, and semaphores. Each type of object is created with a default DACL that specifies who can access the objects with what permissions. If this policy is enabled, the default DACL is stronger, allowing non-admin users to read shared objects, but not modify shared objects that they did not create.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "System Objects: Strengthen default permissions of internal system objects (e.g. Symbolic links)" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "System Objects: Strengthen default permissions of internal system objects (e.g. Symbolic links)" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Control\Session Manager\
Value Name: ProtectionMode
Value Type: REG_DWORD
Value: 1Idle Time Before Suspending a Session.<GroupDescription></GroupDescription>WN08-SO-000031The amount of idle time required before suspending a session must be properly set.<VulnDiscussion>Open sessions can increase the avenues of attack on a system. This setting is used to control when a computer disconnects an inactive SMB session. If client activity resumes, the session is automatically re-established. This protects critical and sensitive network data from exposure to unauthorized personnel with physical access to the computer.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001133CCI-002361Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Microsoft Network Server: Amount of idle time required before suspending session" to "15" minutes or less.Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies >> Security Options.
If the value for "Microsoft Network Server: Amount of idle time required before suspending session" is not set to "15" minutes or less, this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\
Value Name: autodisconnect
Value Type: REG_DWORD
Value: 0x0000000f (15) (or less)Reversible Password Encryption<GroupDescription></GroupDescription>WN08-AC-000009Reversible password encryption must be disabled.<VulnDiscussion>Storing passwords using reversible encryption is essentially the same as storing clear-text versions of the passwords. For this reason, this policy must never be enabled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>IAIA-1, IAIA-2</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000196Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Account Policies -> Password Policy -> "Store password using reversible encryption" to "Disabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Account Policies -> Password Policy.
If the value for "Store password using reversible encryption" is not set to "Disabled", this is a finding.Disable Media Autoplay<GroupDescription></GroupDescription>WN08-CC-000074Autoplay must be disabled for all drives.<VulnDiscussion>Allowing autoplay to execute may introduce malicious code to a system. Autoplay begins reading from a drive as soon as you insert media in the drive. As a result, the setup file of programs or music on audio media may start. By default, autoplay is disabled on removable drives, such as the floppy disk drive (but not the CD-ROM drive) and on network drives. If you enable this policy, you can also disable autoplay on all drives.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001764Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> AutoPlay Policies -> "Turn off AutoPlay" to "Enabled:All Drives".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\
Value Name: NoDriveTypeAutoRun
Type: REG_DWORD
Value: 0x000000ff (255)
Note: If the value for NoDriveTypeAutorun is entered manually, it must be entered as "ff" when Hexadecimal is selected, or "255" with Decimal selected. Using the policy value specified in the Fix section will enter it correctly.Unencrypted Remote Access <GroupDescription></GroupDescription>WN08-00-000007Unencrypted remote access to system services must not be permitted.<VulnDiscussion>Unencrypted access to system services may permit user identification and passwords that are being transmitted in clear text to be intercepted. This could provide an intruder access to the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000068Require encryption for remote access.
Encryption of userid and password information is always required.
Encryption of administrator data is always required.
Encryption of user data coming from or going outside the network firewall is required.
Encryption of the user data inside the network firewall is also highly recommended.Verify encryption is required for remote access.
If userid and password information are not encrypted, this is a finding.
If administrator data is not encrypted, this is a finding.
If user data coming from or going outside the enclave is not encrypted, this is a finding.File share ACLs<GroupDescription></GroupDescription>WN08-GE-000015File shares must be limited on a system.<VulnDiscussion>Shares on a system can provide network access, exposing sensitive information. If a share is necessary, share permissions, as well as NTFS permissions, must be reconfigured to give the minimum access to those accounts that require it.</VulnDiscussion><FalsePositives>System created shares should be excluded from the check.</FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001090If a share is required on a system, configure the share and NTFS permissions to limit access to the specific groups or accounts that require it.
Remove any unnecessary non-system created shares.Open the Computer Management Console.
Expand the "System Tools" object in the Tree window.
Expand the "Shared Folders" object.
Select the "Shares" object.
Right click any non-system-created shares (the system will prompt you if Properties are selected for system-created shares).
Select Properties.
Select the Share Permissions tab.
Verify the necessity of any shares found. If the file shares have not been reconfigured to restrict permissions to the specific groups or accounts that require access, this is a finding.
Select the Security tab.
If the NTFS permissions have not been reconfigured to restrict permissions to the specific groups or accounts that require access, this is a finding.Anonymous SID/Name Translation<GroupDescription></GroupDescription>WN08-SO-000050Anonymous SID/Name translation must not be allowed.<VulnDiscussion>Allowing anonymous SID/Name translation can provide sensitive information for accessing a system. Only authorized users must be able to perform such translations.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network access: Allow anonymous SID/Name translation" to "Disabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Network access: Allow anonymous SID/Name translation" is not set to "Disabled", this is a finding.Anonymous Access to Named Pipes<GroupDescription></GroupDescription>WN08-SO-000055Named pipes that can be accessed anonymously must be configured to contain no values.<VulnDiscussion>Named pipes that can be accessed anonymously provide the potential for gaining unauthorized system access. Pipes are internal system communications processes. They are identified internally by ID numbers that vary between systems. To make access to these processes easier, these pipes are given names that do not vary between systems. This setting controls which of these pipes anonymous users may access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001090Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network access: Named pipes that can be accessed anonymously" to be defined but containing no entries (blank).Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies >> Security Options.
If the value for "Network access: Named pipes that can be accessed anonymously" contains any entries, this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\
Value Name: NullSessionPipes
Value Type: REG_MULTI_SZ
Value: (blank)
Legitimate applications may add entries to this registry value. If an application requires these entries to function properly and is documented with the ISSO, this would not be a finding. Documentation must contain supporting information from the vendor's instructions.Remotely Accessible Registry Paths<GroupDescription></GroupDescription>WN08-SO-000056Unauthorized remotely accessible registry paths must not be configured.<VulnDiscussion>The registry is integral to the function, security, and stability of the Windows system. Some processes may require remote access to the registry. This setting controls which registry paths are accessible from a remote computer. These registry paths must be limited, as they could give unauthorized individuals access to the registry.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001090Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network access: Remotely accessible registry paths" with the following entries:
System\CurrentControlSet\Control\ProductOptions
System\CurrentControlSet\Control\Server Applications
Software\Microsoft\Windows NT\CurrentVersionAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies >> Security Options.
If the value for "Network access: Remotely accessible registry paths" contains entries besides the following, this is a finding:
System\CurrentControlSet\Control\ProductOptions
System\CurrentControlSet\Control\Server Applications
Software\Microsoft\Windows NT\CurrentVersion
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Control\SecurePipeServers\Winreg\AllowedExactPaths\
Value Name: Machine
Value Type: REG_MULTI_SZ
Value: As defined in policy above
Legitimate applications may add entries to this registry value. If an application requires these entries to function properly and is documented with the ISSO, this would not be a finding. Documentation must contain supporting information from the vendor's instructions.Anonymous Access to Network Shares<GroupDescription></GroupDescription>WN08-SO-000059Network shares that can be accessed anonymously must not be allowed.<VulnDiscussion>Anonymous access to network shares provides the potential for gaining unauthorized system access by network users. This could lead to the exposure or corruption of sensitive data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001090Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network access: Shares that can be accessed anonymously" to be defined but containing no entries (blank).Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Network access: Shares that can be accessed anonymously" includes any entries, this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Services\LanManServer\Parameters\
Value Name: NullSessionShares
Value Type: REG_MULTI_SZ
Value: (Blank)Remote Assistance - Solicit Remote Assistance<GroupDescription></GroupDescription>WN08-CC-000059Solicited Remote Assistance must not be allowed.<VulnDiscussion>Remote assistance allows another user to view or take control of the local session of a user. Solicited assistance is help that is specifically requested by the local user. This may allow unauthorized parties access to the resources on the computer.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001090Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Remote Assistance -> "Configure Solicited Remote Assistance" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\
Value Name: fAllowToGetHelp
Type: REG_DWORD
Value: 0Limit Blank Passwords<GroupDescription></GroupDescription>WN08-SO-000004Local accounts with blank passwords must be restricted to prevent access from the network.<VulnDiscussion>An account without a password can allow unauthorized access to a system as only the username would be required. Password policies should prevent accounts with blank passwords from existing on a system. However, if a local account with a blank password did exist, enabling this setting will prevent network access, limiting the account to local console logon only.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Accounts: Limit local account use of blank passwords to console logon only" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Accounts: Limit local account use of blank passwords to console logon only" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Control\Lsa
Value Name: LimitBlankPasswordUse
Value Type: REG_DWORD
Value: 1Internet Information System (IIS)<GroupDescription></GroupDescription>WN08-GE-000016Internet Information System (IIS) or its subcomponents must not be installed on a workstation.<VulnDiscussion>Installation of Internet Information System (IIS) may allow unauthorized internet services to be hosted. Websites must only be hosted on servers that have been designed for that purpose and can be adequately secured.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Remove "Internet Information Services" or "Internet Information Services Hostable Web Core" from the system.Verify IIS is not installed by performing the following:
Search for "Features".
Select "Turn Windows features on or off".
If the entries for "Internet Information Services" or "Internet Information Services Hostable Web Core" are selected, this is a finding.
If an application requires IIS or a subset to be installed to function, this needs be documented with the ISSO. In addition, any applicable requirements from the IIS STIG must be addressed.Maximum Machine Account Password Age<GroupDescription></GroupDescription>WN08-SO-000016The maximum age for machine account passwords must be set to requirements.<VulnDiscussion>Computer account passwords are changed automatically on a regular basis. This setting controls the maximum password age that a machine account may have. This setting must be set to no more than 30 days, ensuring the machine changes its password monthly.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Domain Member: Maximum Machine Account Password Age" to "30" or less (excluding 0 which is unacceptable).Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Domain Member: Maximum Machine Account Password Age" is "0" or greater than 30 (30 is the default), this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Services\Netlogon\Parameters\
Value Name: MaximumPasswordAge
Value Type: REG_DWORD
Value: 30Strong Session Key<GroupDescription></GroupDescription>WN08-SO-000017The system must be configured to require a strong session key.<VulnDiscussion>A computer connecting to a domain controller will establish a secure channel. Requiring strong session keys enforces 128-bit encryption between systems. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002418CCI-002421Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Domain Member: Require Strong (Windows 2000 or Later) Session Key" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Domain Member: Require Strong (Windows 2000 or Later) Session Key" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Services\Netlogon\Parameters\
Value Name: RequireStrongKey
Value Type: REG_DWORD
Value: 1
Warning: This setting may prevent a system from being joined to a domain if not configured consistently between systems.Domain Controller authentication for unlock<GroupDescription></GroupDescription>WN08-SO-000026Domain Controller authentication must not be required to unlock the workstation.<VulnDiscussion>This setting controls the behavior of the system when there is an attempt to unlock the workstation. If this setting is enabled, the system will pass the credentials to the domain controller (if in a domain) for authentication before allowing the system to be unlocked. This may cause a denial of service if the workstation loses connectivity to the domain controller.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Interactive logon: Require domain controller authentication to unlock workstation" to "Disabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Interactive logon: Require domain controller authentication to unlock workstation" is not set to "Disabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \Software\Microsoft\Windows NT\CurrentVersion\Winlogon\
Value Name: ForceUnlockLogon
Value Type: REG_DWORD
Value: 0Storage of Passwords and Credentials<GroupDescription></GroupDescription>WN08-SO-000053The system must be configured to prevent the storage of passwords and credentials.<VulnDiscussion>This setting controls the storage of passwords and credentials for network authentication on the local system. Such credentials must not be stored on the local machine as that may lead to account compromise.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002038Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network access: Do not allow storage of passwords and credentials for network authentication" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Network access: Do not allow storage of passwords and credentials for network authentication" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Control\Lsa\
Value Name: DisableDomainCreds
Value Type: REG_DWORD
Value: 1Everyone Anonymous rights<GroupDescription></GroupDescription>WN08-SO-000054The system must be configured to prevent anonymous users from having the same rights as the Everyone group.<VulnDiscussion>Access by anonymous users must be restricted. If this setting is enabled, then anonymous users have the same rights and permissions as the built-in Everyone group. Anonymous users must not have these permissions or rights.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1, ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network access: Let everyone permissions apply to anonymous users" to "Disabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Network access: Let everyone permissions apply to anonymous users" is not set to "Disabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Control\Lsa\
Value Name: EveryoneIncludesAnonymous
Value Type: REG_DWORD
Value: 0Sharing and Security Model for Local Accounts<GroupDescription></GroupDescription>WN08-SO-000060The system must be configured to use the Classic security model.<VulnDiscussion>Windows includes two network-sharing security models - Classic and Guest only. With the Classic model, local accounts must be password protected; otherwise, anyone can use guest user accounts to access shared system resources.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001090Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network access: Sharing and security model for local accounts" to "Classic - local users authenticate as themselves".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Network access: Sharing and security model for local accounts" is not set to "Classic - local users authenticate as themselves", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Control\Lsa\
Value Name: ForceGuest
Value Type: REG_DWORD
Value: 0LAN Manager Hash stored<GroupDescription></GroupDescription>WN08-SO-000065The system must be configured to prevent the storage of the LAN Manager hash of passwords.<VulnDiscussion>The LAN Manager hash uses a weak encryption algorithm and there are several tools available that use this hash to retrieve account passwords. This setting controls whether or not a LAN Manager hash of the password is stored in the SAM the next time the password is changed. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000196Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network security: Do not store LAN Manager hash value on next password change" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Network security: Do not store LAN Manager hash value on next password change" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Control\Lsa\
Value Name: NoLMHash
Value Type: REG_DWORD
Value: 1Force Logoff When Logon Hours Expire<GroupDescription></GroupDescription>WN08-SO-000066The system must be configured to force users to log off when their allowed logon hours expire.<VulnDiscussion>Limiting logon hours can help protect data by only allowing access during specified times. This setting controls whether or not users are forced to log off when their allowed logon hours expire. If logon hours are set for users, then this must be enforced.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001133Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network security: Force logoff when logon hours expire" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Network security: Force logoff when logon hours expire" is not set to "Enabled", this is a finding.LDAP Client Signing<GroupDescription></GroupDescription>WN08-SO-000068The system must be configured to the required LDAP client signing level.<VulnDiscussion>This setting controls the signing requirements for LDAP clients. This setting must be set to Negotiate signing or Require signing, depending on the environment and type of LDAP server in use.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network security: LDAP client signing requirements" to "Negotiate signing" at a minimum.Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Network security: LDAP client signing requirements" is not set to at least "Negotiate signing", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Services\LDAP\
Value Name: LDAPClientIntegrity
Value Type: REG_DWORD
Value: 1Session Security for NTLM SSP Based Clients<GroupDescription></GroupDescription>WN08-SO-000069The system must be configured to meet the minimum session security requirement for NTLM SSP based clients.<VulnDiscussion>Microsoft has implemented a variety of security support providers for use with RPC sessions. All of the options must be enabled to ensure the maximum security level.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network security: Minimum session security for NTLM SSP based (including secure RPC) clients" to "Require NTLMv2 session security" and "Require 128-bit encryption" (all options selected).Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Network security: Minimum session security for NTLM SSP based (including secure RPC) clients" is not set to "Require NTLMv2 session security" and "Require 128-bit encryption", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Control\Lsa\MSV1_0\
Value Name: NTLMMinClientSec
Value Type: REG_DWORD
Value: 0x20080000 (537395200)
"Require NTLMv2 session security" will prevent authentication, if the "Network security: LAN Manager Authentication level" is set to permit NTLM or LM authentication. FIPS Compliant Algorithms <GroupDescription></GroupDescription>WN08-SO-000074The system must be configured to use FIPS-compliant algorithms for encryption, hashing, and signing.<VulnDiscussion>This setting ensures that the system uses algorithms that are FIPS-compliant for encryption, hashing, and signing. FIPS-compliant algorithms meet specific standards established by the U.S. Government and must be the algorithms used for all OS encryption functions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts>Clients with this setting enabled will not be able to communicate via digitally encrypted or signed protocols with servers that do not support these algorithms. Both the browser and web server must be configured to use TLS, or the browser will not be able to connect to a secure site.</PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002450Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\
Value Name: Enabled
Value Type: REG_DWORD
Value: 1
Warning: Clients with this setting enabled will not be able to communicate via digitally encrypted or signed protocols with servers that do not support these algorithms. Both the browser and web server must be configured to use TLS, or the browser will not be able to connect to a secure site.Case Insensitivity for Non-Windows<GroupDescription></GroupDescription>WN08-SO-000075The system must be configured to require case insensitivity for non-Windows subsystems.<VulnDiscussion>This setting controls the behavior of non-Windows subsystems when dealing with the case of arguments or commands. Case sensitivity could lead to the access of files or commands that must be restricted. To prevent this from happening, case insensitivity restrictions must be required.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "System Objects: Require case insensitivity for non-Windows subsystems" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies >> Security Options.
If the value for "System Objects: Require case insensitivity for non-Windows subsystems" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Control\Session Manager\Kernel\
Value Name: ObCaseInsensitive
Value Type: REG_DWORD
Value: 1TS/RDS - Password Prompting<GroupDescription></GroupDescription>WN08-CC-000099Remote Desktop Services must always prompt a client for passwords upon connection.<VulnDiscussion>This setting controls the ability of users to supply passwords automatically as part of their remote desktop connection. Disabling this setting would allow anyone to use the stored credentials in a connection item to connect to the terminal server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002038Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Security -> "Always prompt for password upon connection" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\
Value Name: fPromptForPassword
Type: REG_DWORD
Value: 1TS/RDS - Set Encryption Level<GroupDescription></GroupDescription>WN08-CC-000100Remote Desktop Services must be configured with the client connection encryption set to the required level.<VulnDiscussion>Remote connections must be encrypted to prevent interception of data or sensitive information. Selecting "High Level" will ensure encryption of Remote Desktop Services sessions in both directions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000068CCI-002890Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Security -> "Set client connection encryption level" to "Enabled" and "High Level".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\
Value Name: MinEncryptionLevel
Type: REG_DWORD
Value: 3TS/RDS - Do Not Use Temp Folders<GroupDescription></GroupDescription>WN08-CC-000104Remote Desktop Services must be configured to use session-specific temporary folders.<VulnDiscussion>If a communal temporary folder is used for remote desktop sessions, it might be possible for users to access other users' temporary folders. If this setting is enabled, only one temporary folder is used for all remote desktop sessions. Per session temporary folders must be established.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Temporary Folders -> "Do not use temporary folders per session" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\
Value Name: PerSessionTempDir
Type: REG_DWORD
Value: 1TS/RDS - Delete Temp Folders<GroupDescription></GroupDescription>WN08-CC-000103Remote Desktop Services must delete temporary folders when a session is terminated.<VulnDiscussion>Remote desktop session temporary folders must always be deleted after a session is over to prevent hard disk clutter and potential leakage of information. This setting controls the deletion of the temporary folders when the session is terminated.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Temporary Folders -> "Do not delete temp folder upon exit" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\
Value Name: DeleteTempDirsOnExit
Type: REG_DWORD
Value: 1Group Policy - Do Not Turn off Background Refresh<GroupDescription></GroupDescription>WN08-CC-000029Group Policies must be refreshed in the background if the user is logged on.<VulnDiscussion>If this setting is enabled, then Group Policy settings are not refreshed while a user is currently logged on. This could lead to instances when a user does not have the latest changes to a policy applied and is therefore operating in an insecure context.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Group Policy -> "Turn off background refresh of Group Policy" to "Disabled".Review the registry.
If the following registry value does not exist, this is not a finding (This is the expected result from configuring the policy as outlined in the Fix section).
If the following registry value exists but is not configured as specified, this is a finding.
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Microsoft\Windows\CurrentVersion\Policies\system\
Value Name: DisableBkGndGroupPolicy
Type: REG_DWORD
Value: 0Remote Assistance - Offer Remote Assistance<GroupDescription></GroupDescription>WN08-CC-000058The system must be configured to prevent unsolicited remote assistance offers.<VulnDiscussion>Remote assistance allows another user to view or take control of the local session of a user. Unsolicited remote assistance is help that is offered by the remote user. This may allow unauthorized parties access to the resources on the computer.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations>WN08-CC-000058</Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl>-Users must be trained to include the following:
-Users must know who they can accept a remote assistance offer from. The remote assistance offer must be in response to a help desk request or confirmed with the help desk if an unsolicited remote assistance offer comes through.
-Users must know how to accept a request, allow view or control, and disconnect a remote assistance session.
-Users must monitor the remote assistance activity at the workstation while it is occurring.
-The support personnel allowed to offer remote assistance (helpers) must be limited and documented.
-Port 3389 must be blocked at the perimeter to prevent other access.
Accounts and groups authorized to offer remote assistance (helpers) are identified in the following registry key:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\RAUnsolicit\
Each Account or group will be listed under a separate value name, with the value equaling the value name as in the following examples:
Value Name: Administrators
Type: REG_SZ
Value: Administrators
Value Name: TestUser
Type: REG_SZ
Value: TestUser</MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001090Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Remote Assistance >> "Configure Offer Remote Assistance" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\
Value Name: fAllowUnsolicited
Type: REG_DWORD
Value: 0
Offer remote assistance may be enabled on workstations if mitigations are in place. This must be documented with the ISSO.Windows Time Service - Configure NTP Client<GroupDescription></GroupDescription>WN08-CC-000069If the time service is configured, it must use an authorized time server.<VulnDiscussion>The Windows Time Service controls time synchronization settings. Time synchronization is essential for authentication and auditing purposes. If the Windows Time Service is used, it must synchronize with a secure, authorized time source. Domain-joined systems are automatically configured to synchronize with domain controllers. If an NTP server is configured, it must synchronize with a secure, authorized time source.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001891If the system needs to be configured to an NTP server, configure the system to point to an authorized time server by setting the policy value for Computer Configuration -> Administrative Templates -> System -> Windows Time Service -> Time Providers -> "Configure Windows NTP Client" to "Enabled", and configure the "NtpServer" field to point to an authorized time server.Review the following registry values:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\W32time\Parameters\
Value Name: Type
Type: REG_SZ
Value: Possible values are NoSync, NTP, NT5DS, AllSync
and
Value Name: NTPServer
Type: REG_SZ
Value: "address of the time server"
The following would be a finding:
"Type" has a value of "NTP" or "Allsync" AND the "NTPServer" value is set to "time.windows.com" or other unauthorized server.
The following would not be a finding:
The referenced registry values do not exist.
"Type" has a value of "NoSync" or "NT5DS".
"Type" has a value of "NTP" or "Allsync" AND the "NTPServer" is blank or configured to an authorized time server.
For DoD organizations, the US Naval Observatory operates stratum 1 time servers, identified at http://tycho.usno.navy.mil/ntp.html. Time synchronization will occur through a hierarchy of time servers down to the local level. Clients and lower level servers will synchronize with an authorized time server in the hierarchy.
Domain-joined systems are automatically configured to synchronize with domain controllers, and it would not be a finding unless this is changed.Safe DLL Search Mode<GroupDescription></GroupDescription>WN08-SO-000045The system must be configured to use Safe DLL Search Mode.<VulnDiscussion>The default search behavior, when an application calls a function in a Dynamic Link Library (DLL), is to search the current directory, followed by the directories contained in the system's path environment variable. An unauthorized DLL, inserted into an application's working directory, could allow malicious code to be run on the system. Setting this policy value forces the system to search the %Systemroot% for the DLL before searching the current directory or the rest of the path.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (SafeDllSearchMode) Enable Safe DLL search mode (recommended)" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
(See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)
If the value for "MSS: (SafeDllSearchMode) Enable Safe DLL search mode (recommended)" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Control\Session Manager\
Value Name: SafeDllSearchMode
Value Type: REG_DWORD
Value: 1Media Player - Disable Automatic Updates<GroupDescription></GroupDescription>WN08-CC-000122Media Player must be configured to prevent automatic checking for updates.<VulnDiscussion>Uncontrolled system updates can introduce issues to a system. The automatic check for updates performed by Windows Media Player must be disabled to ensure a constant platform and to prevent the introduction of unknown\untested software on the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001812Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Media Player -> "Prevent Automatic Updates" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\WindowsMediaPlayer\
Value Name: DisableAutoupdate
Type: REG_DWORD
Value: 1Media Player - Prevent Codec Download<GroupDescription></GroupDescription>WN08-UC-000013Media Player must be configured to prevent automatic Codec downloads.<VulnDiscussion>The Windows Media Player uses software components, referred to as Codecs, to play back media files. By default, when an unknown file type is opened with the Media Player, it will search the Internet for the appropriate Codec and automatically download it. To ensure platform consistency and to protect against new vulnerabilities associated with media types, all Codecs must be installed by the System Administrator.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001812Configure the policy value for User Configuration -> Administrative Templates -> Windows Components -> Windows Media Player -> Playback -> "Prevent Codec Download" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_CURRENT_USER
Subkey: \Software\Policies\Microsoft\WindowsMediaPlayer\
Value Name: PreventCodecDownload
Type: REG_DWORD
Value: 1Session Security for NTLM SSP based Servers<GroupDescription></GroupDescription>WN08-SO-000070The system must be configured to meet the minimum session security requirement for NTLM SSP based servers.<VulnDiscussion>Microsoft has implemented a variety of security support providers for use with RPC sessions. All of the options must be enabled to ensure the maximum security level.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network security: Minimum session security for NTLM SSP based (including secure RPC) servers" to "Require NTLMv2 session security" and "Require 128-bit encryption" (all options selected).Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Network security: Minimum session security for NTLM SSP based (including secure RPC) servers" is not set to "Require NTLMv2 session security" and "Require 128-bit encryption", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Control\Lsa\MSV1_0\
Value Name: NTLMMinServerSec
Value Type: REG_DWORD
Value: 0x20080000 (537395200)
"Require NTLMv2 session security" will prevent authentication if "Network security: LAN Manager Authentication level" is set to permit NTLM or LM authentication. Audit Log Warning Level<GroupDescription></GroupDescription>WN08-SO-000049The system must generate an audit event when the audit log reaches a percentage of full threshold.<VulnDiscussion>Audit records may be lost if the security log becomes full. When the audit log reaches a given percent full, an audit event is written to the security log. An event is recorded as a success audit under the category of System. This option may be especially useful if the audit logs are set to be cleared manually.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECRR-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000139CCI-001855CCI-001858If the system is configured to send audit records directly to an audit server, or automatically archive full logs, this is NA. This must be documented with the ISSO.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (WarningLevel) Percentage threshold for the security event log at which the system will generate a warning" to "90%" or less.If the system is configured to send audit records directly to an audit server, or automatically archive full logs, this is NA. This must be documented with the ISSO.
Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
(See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)
If the value for "MSS: (WarningLevel) Percentage threshold for the security event log at which the system will generate a warning" is not set to "90%" or less, this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\Eventlog\Security\
Value Name: WarningLevel
Value Type: REG_DWORD
Value: 0x0000005a (90) (or less)Disable IP Source Routing<GroupDescription></GroupDescription>WN08-SO-000038The system must be configured to prevent IP source routing.<VulnDiscussion>Configuring the system to disable IP source routing protects against spoofing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)" to "Highest protection, source routing is completely disabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
(See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)
If the value for "MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)" is not set to "Highest protection, source routing is completely disabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Services\Tcpip\Parameters\
Value Name: DisableIPSourceRouting
Value Type: REG_DWORD
Value: 2Disable ICMP Redirect<GroupDescription></GroupDescription>WN08-SO-000039The system must be configured to prevent Internet Control Message Protocol (ICMP) redirects from overriding Open Shortest Path First (OSPF) generated routes.<VulnDiscussion>Allowing ICMP redirect of routes can lead to traffic not being routed properly. When disabled, this forces ICMP to be routed via shortest path first.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes" to "Disabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
(See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)
If the value for "MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes" is not set to "Disabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Services\Tcpip\Parameters\
Value Name: EnableICMPRedirect
Value Type: REG_DWORD
Value: 0Disable Router Discovery<GroupDescription></GroupDescription>WN08-SO-000044The system must be configured to disable the Internet Router Discovery Protocol (IRDP).<VulnDiscussion>The Internet Router Discovery Protocol (IRDP) is used to detect and configure default gateway addresses on the computer. If a router is impersonated on a network, traffic could be routed through the compromised system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002385Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (PerformRouterDiscovery) Allow IRDP to detect and configure Default Gateway addresses (could lead to DoS)" to "Disabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
(See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)
If the value for "MSS: (PerformRouterDiscovery) Allow IRDP to detect and configure Default Gateway addresses (could lead to DoS)" is not set to "Disabled", this is a finding.
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \System\CurrentControlSet\Services\Tcpip\Parameters\
Value Name: PerformRouterDiscovery
Value Type: REG_DWORD
Value: 0TCP Connection Keep-Alive Time<GroupDescription></GroupDescription>WN08-SO-000041The system must be configured to limit how often keep-alive packets are sent.<VulnDiscussion>This setting controls how often TCP sends a keep-alive packet in attempting to verify that an idle connection is still intact. A higher value could allow an attacker to cause a denial of service with numerous connections.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002385Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (KeepAliveTime) How often keep-alive packets are sent in milliseconds" to "300000 or 5 minutes (recommended)" or less.Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
(See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)
If the value for "MSS: (KeepAliveTime) How often keep-alive packets are sent in milliseconds" is not set to "300000 or 5 minutes (recommended)" or less, this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \System\CurrentControlSet\Services\Tcpip\Parameters\
Value Name: KeepAliveTime
Value Type: REG_DWORD
Value: 300000Name-Release Attacks<GroupDescription></GroupDescription>WN08-SO-000043The system must be configured to ignore NetBIOS name release requests except from WINS servers.<VulnDiscussion>Configuring the system to ignore name release requests, except from WINS servers, prevents a denial of service (DoS) attack. The DoS consists of sending a NetBIOS name release request to the server for each entry in the server's cache, causing a response delay in the normal operation of the servers WINS resolution capability.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002385Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers" to "Enabled". Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies >> Security Options.
(See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)
If the value for "MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\Netbt\Parameters\
Value Name: NoNameReleaseOnDemand
Value Type: REG_DWORD
Value: 1TCP Data Retransmissions<GroupDescription></GroupDescription>WN08-SO-000048The system must limit how many times unacknowledged TCP data is retransmitted.<VulnDiscussion>In a SYN flood attack, the attacker sends a continuous stream of SYN packets to a server, and the server leaves the half-open connections open until it is overwhelmed and is no longer able to respond to legitimate requests.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002385Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "MSS: (TcpMaxDataRetransmissions) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)" to "3" or less.Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies >> Security Options.
(See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)
If the value for "MSS: (TcpMaxDataRetransmissions) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)" is not set to "3" or less, this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\
Value Name: TcpMaxDataRetransmissions
Value Type: REG_DWORD
Value: 3 (or less)Screen Saver Grace Period<GroupDescription></GroupDescription>WN08-SO-000046The system must be configured to have password protection take effect within a limited time frame when the screen saver becomes active.<VulnDiscussion>Allowing more than several seconds makes the computer vulnerable to a potential attack from someone walking up to the console to attempt to log onto the system before the lock takes effect.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (ScreenSaverGracePeriod) The time in seconds before the screen saver grace period expires (0 recommended)" to "5" or less.Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
(See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)
If the value for "MSS: (ScreenSaverGracePeriod) The time in seconds before the screen saver grace period expires (0 recommended)" is not set to "5" or less, this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \Software\Microsoft\Windows NT\CurrentVersion\Winlogon\
Value Name: ScreenSaverGracePeriod
Value Type: REG_SZ
Value: 5 (or less)Remotely Accessible Registry Paths and Sub-Paths<GroupDescription></GroupDescription>WN08-SO-000057Unauthorized remotely accessible registry paths and sub-paths must not be configured.<VulnDiscussion>The registry is integral to the function, security, and stability of the Windows system. Some processes may require remote access to the registry. This setting controls which registry paths and sub-paths are accessible from a remote computer. These registry paths must be limited, as they could give unauthorized individuals access to the registry.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001090Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network access: Remotely accessible registry paths and sub-paths" with the following entries:
Software\Microsoft\OLAP Server
Software\Microsoft\Windows NT\CurrentVersion\Perflib
Software\Microsoft\Windows NT\CurrentVersion\Print
Software\Microsoft\Windows NT\CurrentVersion\Windows
System\CurrentControlSet\Control\ContentIndex
System\CurrentControlSet\Control\Print\Printers
System\CurrentControlSet\Control\Terminal Server
System\CurrentControlSet\Control\Terminal Server\UserConfig
System\CurrentControlSet\Control\Terminal Server\DefaultUserConfiguration
System\CurrentControlSet\Services\Eventlog
System\CurrentControlSet\Services\SysmonlogAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies >> Security Options.
If the value for "Network access: Remotely accessible registry paths and sub-paths" contains entries besides the following, this is a finding:
Software\Microsoft\OLAP Server
Software\Microsoft\Windows NT\CurrentVersion\Perflib
Software\Microsoft\Windows NT\CurrentVersion\Print
Software\Microsoft\Windows NT\CurrentVersion\Windows
System\CurrentControlSet\Control\ContentIndex
System\CurrentControlSet\Control\Print\Printers
System\CurrentControlSet\Control\Terminal Server
System\CurrentControlSet\Control\Terminal Server\UserConfig
System\CurrentControlSet\Control\TerminalServer\DefaultUserConfiguration
System\CurrentControlSet\Services\Eventlog
System\CurrentControlSet\Services\Sysmonlog
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Control\SecurePipeServers\Winreg\AllowedPaths\
Value Name: Machine
Value Type: REG_MULTI_SZ
Value: As defined in policy above
Legitimate applications may add entries to this registry value. If an application requires these entries to function properly and is documented with the ISSO, this would not be a finding. Documentation must contain supporting information from the vendor's instructions.TS/RDS - Secure RPC Connection.<GroupDescription></GroupDescription>WN08-CC-000130The Remote Desktop Session Host must require secure RPC communications.<VulnDiscussion>Allowing unsecure RPC communication exposes the system to man in the middle attacks and data disclosure attacks. A man in the middle attack occurs when an intruder captures packets between a client and server and modifies them before allowing the packets to be exchanged. Usually the attacker will modify the information in the packets in an attempt to cause either the client or server to reveal sensitive information.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001453Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Security "Require secure RPC communication" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\
Value Name: fEncryptRPCTraffic
Type: REG_DWORD
Value: 1Group Policy - Registry Policy Processing<GroupDescription></GroupDescription>WN08-CC-000028Group Policy objects must be reprocessed even if they have not changed.<VulnDiscussion>Enabling this setting and then selecting the "Process even if the Group Policy objects have not changed" option ensures that the policies will be reprocessed even if none have been changed. This way, any unauthorized changes are forced to match the domain-based group policy settings again.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Group Policy -> "Configure registry policy processing" to "Enabled" and select the option "Process even if the Group Policy objects have not changed".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}
Value Name: NoGPOListChanges
Type: REG_DWORD
Value: 0Encrypting and Signing of Secure Channel Traffic<GroupDescription></GroupDescription>WN08-SO-000012Outgoing secure channel traffic must be encrypted or signed.<VulnDiscussion>Requests sent on the secure channel are authenticated, and sensitive information (such as passwords) is encrypted, but not all information is encrypted. If this policy is enabled, outgoing secure channel traffic will be encrypted and signed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002418CCI-002421Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Domain Member: Digitally encrypt or sign secure channel data (always)" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Domain Member: Digitally encrypt or sign secure channel data (always)" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Services\Netlogon\Parameters\
Value Name: RequireSignOrSeal
Value Type: REG_DWORD
Value: 1SMB Client Packet Signing (Always)<GroupDescription></GroupDescription>WN08-SO-000028The Windows SMB client must be configured to always perform SMB packet signing.<VulnDiscussion>The server message block (SMB) protocol provides the basis for many network operations. Digitally signed SMB packets aid in preventing man-in-the-middle attacks. If this policy is enabled, the SMB client will only communicate with an SMB server that performs SMB packet signing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002418CCI-002421Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Microsoft Network Client: Digitally sign communications (always)" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Microsoft Network Client: Digitally sign communications (always)" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Services\LanmanWorkstation\Parameters\
Value Name: RequireSecuritySignature
Value Type: REG_DWORD
Value: 1SMB Server Packet Signing (Always)<GroupDescription></GroupDescription>WN08-SO-000032The Windows SMB server must be configured to always perform SMB packet signing.<VulnDiscussion>The server message block (SMB) protocol provides the basis for many network operations. Digitally signed SMB packets aid in preventing man-in-the-middle attacks. If this policy is enabled, the SMB server will only communicate with an SMB client that performs SMB packet signing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002418CCI-002421Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Microsoft Network Server: Digitally sign communications (always)" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Microsoft Network Server: Digitally sign communications (always)" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Services\LanManServer\Parameters\
Value Name: RequireSecuritySignature
Value Type: REG_DWORD
Value: 1Anonymous Access to Named Pipes and Shares<GroupDescription></GroupDescription>WN08-SO-000058Anonymous access to Named Pipes and Shares must be restricted.<VulnDiscussion>Allowing anonymous access to named pipes or shares provides the potential for unauthorized system access. This setting restricts access to those defined in "Network access: Named Pipes that can be accessed anonymously" and "Network access: Shares that can be accessed anonymously", both of which must be blank under other requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001090Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network access: Restrict anonymous access to Named Pipes and Shares" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Network access: Restrict anonymous access to Named Pipes and Shares" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Services\LanManServer\Parameters\
Value Name: RestrictNullSessAccess
Value Type: REG_DWORD
Value: 1Minimum Password Length<GroupDescription></GroupDescription>WN08-AC-000007Passwords must, at a minimum, be 14 characters.<VulnDiscussion>Information systems not protected with strong password schemes (including passwords of minimum length) provide the opportunity for anyone to crack the password, thus gaining access to the system and compromising the device, information, or the local network. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000205Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Account Policies -> Password Policy -> "Minimum password length" to at least "14" characters.Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Account Policies -> Password Policy.
If the value for the "Minimum password length," is less than 14 characters, this is a finding.Password Expiration<GroupDescription></GroupDescription>WN08-GE-000017System mechanisms must be implemented to enforce automatic expiration of passwords.<VulnDiscussion>Passwords that do not expire increase exposure with a greater probability of being discovered or cracked.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000199Configure all passwords to expire. Ensure "Password never expires" is not checked on all accounts in Computer Management, Local Users and Groups. Document any exceptions with the ISSO.Run the DUMPSEC utility.
Select "Dump Users as Table" from the "Report" menu.
Select the following fields, and click "Add" for each entry.
UserName
SID
PswdExpires
AcctDisabled
Groups
If any accounts have "No" in the "PswdExpires" column, this is a finding.
The following are exempt from this requirement:
Application Accounts
Accounts that meet the requirements for allowable exceptions must be documented with the ISSO.Password Requirement<GroupDescription></GroupDescription>WN08-GE-000018Local accounts must require passwords.<VulnDiscussion>The lack of password protection enables anyone to gain access to the information system, which opens a backdoor opportunity for intruders to compromise the system as well as other resources. Local accounts on a system must require passwords.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000764Ensure all local accounts are configured to require passwords to gain access.
The password required flag can be set by entering the following on a command line: "Net user <account_name> /passwordreq:yes".Verify all local accounts require passwords.
Run the DUMPSEC utility.
Select "Dump Users as Table" from the "Report" menu.
Select the following fields, and click "Add" for each entry.
UserName
SID
PswdRequired
AcctDisabled
Groups
If any accounts have "No" in the "PswdRequired" column, this is a finding.
Some built-in or application-generated accounts (e.g., Guest, IWAM_, IUSR, etc.) may not have this flag set, even though there are passwords present. It can be set by entering the following on a command line: "Net user <account_name> /passwordreq:yes".Display of Last User Name<GroupDescription></GroupDescription>WN08-SO-000018The system must be configured to prevent the display of the last username on the logon screen.<VulnDiscussion>Displaying the username of the last logged on user provides half of the userid/password equation that an unauthorized person would need to gain access. The username of the last user to log onto a system must not be displayed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Interactive logon: Do not display last user name" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Interactive logon: Do not display last user name" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\System\
Value Name: DontDisplayLastUserName
Value Type: REG_DWORD
Value: 1Backup Administrator Account<GroupDescription></GroupDescription>WN08-00-000008The site must have a contingency for emergency administration of the system.<VulnDiscussion>The built-in administrator account, as a well known account subject to attack, is disabled by default and per STIG requirements. Domain administrative accounts on domain-joined systems should provide sufficient availability for administering a system. A site with limited administrators must ensure they have a contingency for administering a non-domain system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Create a contingency plan for administering a system. Document any emergency administrator account with the ISSO and store the account information in a secure location.Determine if there is a contingency for administering a non-domain system with limited administrators. An emergency administrator account must be documented with the ISSO, and it must be stored with its password in a secure location.
If there is no contingency for administering a system in an emergency, this is a finding.Administrator Account Password Changes<GroupDescription></GroupDescription>WN08-00-000009Administrator passwords must be changed as required.<VulnDiscussion>The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the passwords. Passwords for the default and emergency administrator accounts must be changed at least annually or when any member of the administrative team leaves the organization.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Define a policy that requires the default and emergency administrator passwords to be changed at least annually or when any member of the administrative team leaves the organization. Ensure the policy is implemented.Determine if the site has a policy that requires the default and emergency admin passwords to be changed at least annually or when any member of the administrative team leaves the organization. If there is no policy, this is a finding.Audit Access of Global System Objects<GroupDescription></GroupDescription>WN08-SO-000007Auditing Access of Global System Objects must be turned off.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
This setting prevents the system from setting up a default system access control list for certain system objects, which could create a very large number of security events, filling the security log in Windows and making it difficult to identify actual issues.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001095Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Audit: Audit the access of global system objects" to "Disabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Audit: Audit the access of global system objects" is not set to "Disabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Control\Lsa
Value Name: AuditBaseObjects
Value Type: REG_DWORD
Value: 0Audit Backup and Restore Privileges<GroupDescription></GroupDescription>WN08-SO-000008Auditing of Backup and Restore Privileges must be turned off.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
This setting prevents the system from generating audit events for every file backed up or restored which could fill the security log in Windows, making it difficult to identify actual issues.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001095Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Audit: Audit the use of Backup and Restore privilege" to "Disabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Audit: Audit the use of Backup and Restore privilege" is not set to "Disabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Control\Lsa
Value Name: FullPrivilegeAuditing
Value Type: REG_BINARY
Value: 0Audit Policy Subcategory Setting<GroupDescription></GroupDescription>WN08-SO-000009Audit policy using subcategories must be enabled.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
This setting allows administrators to enable more precise auditing capabilities.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000169Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Control\Lsa\
Value Name: SCENoApplyLegacyAuditPolicy
Value Type: REG_DWORD
Value: 1Hide Computer<GroupDescription></GroupDescription>WN08-SO-000040The system must be configured to hide the computer from the browse list.<VulnDiscussion>Identifying the computer name on a network could provide an attacker with information useful in gaining access. This setting prevents the computer name from displaying in the browse list.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (Hidden) Hide Computer From the Browse List (not recommended except for highly secure environments)" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
(See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)
If the value for "MSS: (Hidden) Hide Computer From the Browse List (not recommended except for highly secure environments)" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \System\CurrentControlSet\Services\Lanmanserver\Parameters\
Value Name: Hidden
Value Type: REG_DWORD
Value: 1IPSec Exemptions<GroupDescription></GroupDescription>WN08-SO-000042IPSec Exemptions must be limited.<VulnDiscussion>IPSec exemption filters allow specific traffic that may be needed by the system for such things as Kerberos authentication. This setting configures Windows for specific IPSec exemptions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (NoDefaultExempt) Configure IPSec exemptions for various types of network traffic" to "Multicast, broadcast and ISAKMP exempt (best for Windows XP)".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
(See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)
If the value for "MSS: (NoDefaultExempt) Configure IPSec exemptions for various types of network traffic" is not set to "Multicast, broadcast and ISAKMP exempt (best for Windows XP)", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Services\IPSEC\
Value Name: NoDefaultExempt
Value Type: REG_DWORD
Value: 1UAC - Admin Approval Mode<GroupDescription></GroupDescription>WN08-SO-000077User Account Control approval mode for the built-in Administrator must be enabled.<VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures the built-in Administrator account so that it runs in Admin Approval Mode.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECCD-1, ECCD-2</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002038Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "User Account Control: Admin Approval Mode for the Built-in Administrator account" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "User Account Control: Admin Approval Mode for the Built-in Administrator account" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\System\
Value Name: FilterAdministratorToken
Value Type: REG_DWORD
Value: 1UAC - Admin Elevation Prompt<GroupDescription></GroupDescription>WN08-SO-000078User Account Control must, at minimum, prompt administrators for consent on the secure desktop.<VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures the elevation requirements for logged on administrators to complete a task that requires raised privileges.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECCD-1, ECCD-2</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001084Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode" to "Prompt for consent on the secure desktop".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode" is not set to "Prompt for consent on the secure desktop", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\System\
Value Name: ConsentPromptBehaviorAdmin
Value Type: REG_DWORD
Value: 2 (Prompt for consent on the secure desktop)UAC - User Elevation Prompt<GroupDescription></GroupDescription>WN08-SO-000079User Account Control must automatically deny elevation requests for standard users.<VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. Denying elevation requests from standard user accounts requires tasks that need elevation to be initiated by accounts with administrative privileges. This prevents privileged account credentials from being cached with standard user profile information to help mitigate credential theft.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002038Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "User Account Control: Behavior of the elevation prompt for standard users" to "Automatically deny elevation requests".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies >> Security Options.
If the value for "User Account Control: Behavior of the elevation prompt for standard users" is not set to "Automatically deny elevation requests", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\
Value Name: ConsentPromptBehaviorUser
Value Type: REG_DWORD
Value: 0x00000000 (0)UAC - Application Installations<GroupDescription></GroupDescription>WN08-SO-000080User Account Control must be configured to detect application installations and prompt for elevation.<VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting requires Windows to respond to application installation requests by prompting for credentials.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECCD-1, ECCD-2</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001084Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "User Account Control: Detect application installations and prompt for elevation" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "User Account Control: Detect application installations and prompt for elevation" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\System\
Value Name: EnableInstallerDetection
Value Type: REG_DWORD
Value: 1UAC - UIAccess Application Elevation<GroupDescription></GroupDescription>WN08-SO-000082User Account Control must only elevate UIAccess applications that are installed in secure locations.<VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures Windows to only allow applications installed in a secure location on the file system, such as the Program Files or the Windows\System32 folders, to run with elevated privileges.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001084Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "User Account Control: Only elevate UIAccess applications that are installed in secure locations" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "User Account Control: Only elevate UIAccess applications that are installed in secure locations" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\System\
Value Name: EnableSecureUIAPaths
Value Type: REG_DWORD
Value: 1UAC - All Admin Approval Mode<GroupDescription></GroupDescription>WN08-SO-000083User Account Control must run all administrators in Admin Approval Mode, enabling UAC.<VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting enables UAC.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECCD-1, ECCD-2</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002038Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "User Account Control: Run all administrators in Admin Approval Mode" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "User Account Control: Run all administrators in Admin Approval Mode" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\System\
Value Name: EnableLUA
Value Type: REG_DWORD
Value: 1UAC - Secure Desktop Mode<GroupDescription></GroupDescription>WN08-SO-000084User Account Control must switch to the secure desktop when prompting for elevation.<VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting ensures that the elevation prompt is only used in secure desktop mode.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECCD-1, ECCD-2</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001084Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "User Account Control: Switch to the secure desktop when prompting for elevation" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "User Account Control: Switch to the secure desktop when prompting for elevation" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\System\
Value Name: PromptOnSecureDesktop
Value Type: REG_DWORD
Value: 1UAC - Non UAC Compliant Application Virtualization<GroupDescription></GroupDescription>WN08-SO-000085User Account Control must virtualize file and registry write failures to per-user locations.<VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures non-UAC compliant applications to run in virtualized file and registry entries in per-user locations, allowing them to run.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECCD-1, ECCD-2</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001084Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "User Account Control: Virtualize file and registry write failures to per-user locations" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "User Account Control: Virtualize file and registry write failures to per-user locations" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\System\
Value Name: EnableVirtualization
Value Type: REG_DWORD
Value: 1Enumerate Administrator Accounts on Elevation<GroupDescription></GroupDescription>WN08-CC-000077The system must require username and password to elevate a running application.<VulnDiscussion>Enumeration of administrator accounts when elevating can provide part of the logon information to an unauthorized user. This setting configures the system to always require users to type in a username and password to elevate a running application.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001084Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Credential User Interface -> "Enumerate administrator accounts on elevation" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Microsoft\Windows\CurrentVersion\Policies\CredUI
Value Name: EnumerateAdministrators
Type: REG_DWORD
Value: 0TS/RDS - Prevent Password Saving<GroupDescription></GroupDescription>WN08-CC-000096Passwords must not be saved in the Remote Desktop Client.<VulnDiscussion>Saving passwords in the Remote Desktop Client could allow an unauthorized user to establish a remote desktop session to another system. The system must be configured to prevent users from saving passwords in the Remote Desktop Client.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002038Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Connection Client -> "Do not allow passwords to be saved" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\
Value Name: DisablePasswordSaving
Type: REG_DWORD
Value: 1TS/RDS - Remote User Connections<GroupDescription></GroupDescription>WN08-CC-000097Users must be prevented from connecting using Remote Desktop Services.<VulnDiscussion>Allowing a remote desktop session to a workstation enables another avenue of access that could be exploited. The system must be configured to prevent users from connecting to a computer using Remote Desktop Services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002314Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Remote Desktop Services >> Remote Desktop Session Host >> Connections >> "Allow users to connect remotely by using Remote Desktop Services" to "Disabled".
If Remote Desktop Services for remote administration is necessary, enabling this would not be a finding. Restricted Admin mode must be used. This must be document with the ISSO.
See Microsoft article KB2871997 for patches required to add this function to systems prior to Windows 8.1.
Restricted Admin mode for Remote Desktop Connections can be implemented for each session using a command line switch to start the Remote Desktop Client or through a group policy to enable it for all sessions.
The command line to do this is "mstsc /restrictedadmin".
To enable this with group policy, configure the policy value for Computer Configuration >> Administrative Templates >> System >> Credentials Delegation >> "Restrict delegation of credentials to remote servers" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\
Value Name: fDenyTSConnections
Value Type: REG_DWORD
Value: 1
If Remote Desktop Services for remote administration is necessary, enabling this would not be a finding. Restricted Admin mode must be used. This must be document with the ISSO.
See Microsoft article KB2871997 for patches required to add this function to systems prior to Windows 8.1.
Restricted Admin mode for Remote Desktop Connections can be implemented for each session using a command line switch to start the Remote Desktop Client or through a group policy to enable it for all sessions.
The command line to do this is "mstsc /restrictedadmin".
To enable this with group policy, configure the policy value for Computer Configuration >> Administrative Templates >> System >> Credentials Delegation >> "Restrict delegation of credentials to remote servers" to "Enabled".TS/RDS - Drive Redirection<GroupDescription></GroupDescription>WN08-CC-000098Local drives must be prevented from sharing with Remote Desktop Session Hosts.<VulnDiscussion>Preventing users from sharing the local drives on their client computers to Remote Session Hosts that they access helps reduce possible exposure of sensitive data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001090Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Device and Resource Redirection -> "Do not allow drive redirection" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\
Value Name: fDisableCdm
Type: REG_DWORD
Value: 1RPC - Unauthenticated RPC Clients<GroupDescription></GroupDescription>WN08-CC-000064Unauthenticated RPC clients must be restricted from connecting to the RPC server.<VulnDiscussion>Configuring RPC to restrict unauthenticated RPC clients from connecting to the RPC server will prevent anonymous connections.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001967Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Remote Procedure Call -> "Restrict Unauthenticated RPC clients" to "Enabled" and "Authenticated".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows NT\Rpc\
Value Name: RestrictRemoteClients
Type: REG_DWORD
Value: 1Internet Download / Online Ordering<GroupDescription></GroupDescription>WN08-CC-000037Web publishing and online ordering wizards must be prevented from downloading a list of providers.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting prevents Windows from downloading a list of providers for the Web publishing and online ordering wizards.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication settings -> "Turn off Internet download for Web publishing and online ordering wizards" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\
Value Name: NoWebServices
Type: REG_DWORD
Value: 1Printing Over HTTP<GroupDescription></GroupDescription>WN08-CC-000039Printing over HTTP must be prevented.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting prevents the client computer from printing over HTTP, which allows the computer to print to printers on the intranet as well as the Internet.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication settings -> "Turn off printing over HTTP" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows NT\Printers\
Value Name: DisableHTTPPrinting
Type: REG_DWORD
Value: 1HTTP Printer Drivers<GroupDescription></GroupDescription>WN08-CC-000032Downloading print driver packages over HTTP must be prevented.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting prevents the computer from downloading print driver packages over HTTP.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication settings -> "Turn off downloading of print drivers over HTTP" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows NT\Printers\
Value Name: DisableWebPnPDownload
Type: REG_DWORD
Value: 1Windows Update Device Drive Searching<GroupDescription></GroupDescription>WN08-CC-000047Windows must be prevented from using Windows Update to search for drivers.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting prevents Windows from searching Windows Update for device drivers when no local drivers for a device are present.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001812Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication settings -> "Turn off Windows Update device driver searching" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\DriverSearching\
Value Name: DontSearchWindowsUpdate
Type: REG_DWORD
Value: 1Attachment Mgr - Preserve Zone Info<GroupDescription></GroupDescription>WN08-UC-000009Zone information must be preserved when saving attachments.<VulnDiscussion>Preserving zone of origin (internet, intranet, local, restricted) information on file attachments allows Windows to determine risk.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for User Configuration -> Administrative Templates -> Windows Components -> Attachment Manager -> "Do not preserve zone information in file attachments" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_CURRENT_USER
Subkey: \Software\Microsoft\Windows\CurrentVersion\Policies\Attachments\
Value Name: SaveZoneInformation
Type: REG_DWORD
Value: 2Attachment Mgr - Hide Mech to Remove Zone Info<GroupDescription></GroupDescription>WN08-UC-000010Mechanisms for removing zone information from file attachments must be hidden.<VulnDiscussion>Preserving zone of origin (internet, intranet, local, restricted) information on file attachments allows Windows to determine risk. This setting prevents users from manually removing zone information from saved file attachments.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for User Configuration -> Administrative Templates -> Windows Components -> Attachment Manager -> "Hide mechanisms to remove zone information" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_CURRENT_USER
Subkey: \Software\Microsoft\Windows\CurrentVersion\Policies\Attachments\
Value Name: HideZoneInfoOnProperties
Type: REG_DWORD
Value: 1Attachment Mgr - Scan with Antivirus<GroupDescription></GroupDescription>WN08-UC-000011The system must notify antivirus when file attachments are opened.<VulnDiscussion>Attaching malicious files is a known avenue of attack. This setting configures the system to notify antivirus programs when a user opens a file attachment.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for User Configuration -> Administrative Templates -> Windows Components -> Attachment Manager -> "Notify antivirus programs when opening attachments" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_CURRENT_USER
Subkey: \Software\Microsoft\Windows\CurrentVersion\Policies\Attachments\
Value Name: ScanWithAntiVirus
Type: REG_DWORD
Value: 3HBSS McAfee Agent<GroupDescription></GroupDescription>WN08-GE-000019The HBSS McAfee Agent must be installed.<VulnDiscussion></VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Deploy the McAfee Agent as detailed in accordance with the DoD HBSS STIG.Verify the following file is installed and at a version listed or above:
McAfee Agent v5.x - masvc.exe
McAfee Agent v4.x - FrameworkService.exe
The default location is C:\Program Files (x86)\McAfee\Common Framework\
If the McAfee Agent file is not found or at a version specified or above, this is a finding.
Run "Services.msc".
Verify the corresponding service is running.
McAfee Agent v5.x - McAfee Agent Service
McAfee Agent v4.x - McAfee Framework Service
If the service does not have a Status of "Started", this is a finding.Windows Peer to Peer Networking <GroupDescription></GroupDescription>WN08-CC-000003Windows Peer-to-Peer networking services must be turned off.<VulnDiscussion>Peer-to-Peer applications can allow unauthorized access to a system and exposure of sensitive data. This setting will turn off the Microsoft Peer-to-Peer Networking Service.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> Microsoft Peer-to-Peer Networking Services -> "Turn Off Microsoft Peer-to-Peer Networking Services" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Peernet\
Value Name: Disabled
Type: REG_DWORD
Value: 1Prohibit Network Bridge<GroupDescription></GroupDescription>WN08-CC-000004Network Bridges must be prohibited in Windows.<VulnDiscussion>A Network Bridge can connect two or more network segments allowing unauthorized access or exposure of sensitive data. This setting prevents a Network Bridge from being installed and configured. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> Network Connections -> "Prohibit installation and configuration of Network Bridge on your DNS domain network" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\Network Connections\
Value Name: NC_AllowNetBridge_NLA
Type: REG_DWORD
Value: 0Event Viewer Events.asp Links<GroupDescription></GroupDescription>WN08-CC-000033Event Viewer Events.asp links must be turned off.<VulnDiscussion>Viewing events is a function of administrators, who must not access the internet with privileged accounts. This setting will disable Events.asp hyperlinks in Event Viewer to prevent links to the internet from within events.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication settings -> "Turn off Event Viewer "Events.asp" links" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\EventViewer\
Value Name: MicrosoftEventVwrDisableLinks
Type: REG_DWORD
Value: 1Internet File Association Service <GroupDescription></GroupDescription>WN08-CC-000038The Internet File Association service must be turned off.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting prevents unhandled file associations from using the Microsoft Web service to find an application.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication settings -> "Turn off Internet File Association service" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\
Value Name: NoInternetOpenWith
Type: REG_DWORD
Value: 1Order Prints Online<GroupDescription></GroupDescription>WN08-CC-000042The Order Prints Online wizard must be turned off.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting ensures the "Order Prints Online" task is not available in File Explorer.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication settings -> "Turn off the "Order Prints" picture task" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\
Value Name: NoOnlinePrintsWizard
Type: REG_DWORD
Value: 1Classic Logon<GroupDescription></GroupDescription>WN08-CC-000049The classic logon screen must be required for user logons.<VulnDiscussion>The classic logon screen requires users to enter a logon name and password to access a system. The simple logon screen or Welcome screen displays usernames for selection, providing part of the necessary logon information.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366If the system is a member of a domain, this is NA.
Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Logon -> "Always use classic logon" to "Enabled".If the system is a member of a domain, this is NA.
If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\
Value Name: LogonType
Type: REG_DWORD
Value: 0RSS Attachment Downloads<GroupDescription></GroupDescription>WN08-CC-000105Attachments must be prevented from being downloaded from RSS feeds.<VulnDiscussion>Attachments from RSS feeds may not be secure. This setting will prevent attachments from being downloaded from RSS feeds.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> RSS Feeds -> "Prevent downloading of enclosures" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Internet Explorer\Feeds\
Value Name: DisableEnclosureDownload
Type: REG_DWORD
Value: 1Windows Explorer – Shell Protocol Protected Mode <GroupDescription></GroupDescription>WN08-CC-000091File Explorer shell protocol must run in protected mode.<VulnDiscussion>The shell protocol will limit the set of folders applications can open when run in protected mode. Restricting files an application can open, to a limited set of folders, increases the security of Windows.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> File Explorer -> "Turn off shell protocol protected mode" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\
Value Name: PreXPSP2ShellProtocolBehavior
Type: REG_DWORD
Value: 0Windows Installer – IE Security Prompt<GroupDescription></GroupDescription>WN08-CC-000117Users must be notified if a web-based program attempts to install software.<VulnDiscussion>Users must be aware of attempted program installations. This setting ensures users are notified if a web-based program attempts to install software. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Installer -> "Prevent Internet Explorer security prompt for Windows Installer scripts" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\Installer\
Value Name: SafeForScripting
Type: REG_DWORD
Value: 0Windows Installer – User Control <GroupDescription></GroupDescription>WN08-CC-000115Users must be prevented from changing installation options.<VulnDiscussion>Installation options for applications are typically controlled by administrators. This setting prevents users from changing installation options that may bypass security features.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001812Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Installer -> "Allow user control over installs" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\Installer\
Value Name: EnableUserControl
Type: REG_DWORD
Value: 0Windows Installer – Vendor Signed Updates<GroupDescription></GroupDescription>WN08-CC-000118Non-administrators must be prevented from applying vendor-signed updates.<VulnDiscussion>Uncontrolled system updates can introduce issues to a system. This setting will prevent users from applying vendor-signed updates (though they may be from a trusted source).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001812Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Installer -> "Prohibit non-administrators from applying vendor signed updates" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\Installer\
Value Name: DisableLUAPatching
Type: REG_DWORD
Value: 1Media Player – First Use Dialog Boxes <GroupDescription></GroupDescription>WN08-CC-000121Users must not be presented with Privacy and Installation options on first use of Windows Media Player.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting prevents users from being presented with Privacy and Installation options on first use of Windows Media Player which could enable some communication with the vendor.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Media Player -> "Do Not Show First Use Dialog Boxes" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\WindowsMediaPlayer\
Value Name: GroupPrivacyAcceptance
Type: REG_DWORD
Value: 1Network – Mapper I/O Driver <GroupDescription></GroupDescription>WN08-CC-000001The Mapper I/O network protocol (LLTDIO) driver must be disabled.<VulnDiscussion>The Mapper I/O network protocol (LLTDIO) driver allows the discovery of the connected network and allows various options to be enabled. Disabling this helps protect the system from potentially discovering and connecting to unauthorized devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> Link-Layer Topology Discovery -> "Turn on Mapper I/O (LLTDIO) driver" to "Disabled".If the following registry values do not exist or are not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\LLTD\
Value Name: AllowLLTDIOOndomain
Value Name: AllowLLTDIOOnPublicNet
Value Name: EnableLLTDIO
Value Name: ProhibitLLTDIOOnPrivateNet
Type: REG_DWORD
Value: 0Network – Responder Driver <GroupDescription></GroupDescription>WN08-CC-000002The Responder network protocol driver must be disabled.<VulnDiscussion>The Responder network protocol driver allows a computer to be discovered and located on a network. Disabling this helps protect the system from potentially being discovered and connected to by unauthorized devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> Link-Layer Topology Discovery -> "Turn on Responder (RSPNDR) driver" to "Disabled".If the following registry values do not exist or are not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\LLTD\
Value Name: AllowRspndrOndomain
Value Name: AllowRspndrOnPublicNet
Value Name: EnableRspndr
Value Name: ProhibitRspndrOnPrivateNet
Type: REG_DWORD
Value: 0Network – WCN Wireless Configuration <GroupDescription></GroupDescription>WN08-CC-000012The configuration of wireless devices using Windows Connect Now must be disabled.<VulnDiscussion>Windows Connect Now allows the discovery and configuration of devices over wireless. Wireless devices must be managed. If a rogue device is connected to a system, there is potential for sensitive information to be compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> Windows Connect Now -> "Configuration of wireless settings using Windows Connect Now" to "Disabled".If the following registry values do not exist or are not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\WCN\Registrars\
Value Name: DisableFlashConfigRegistrar
Value Name: DisableInBand802DOT11Registrar
Value Name: DisableUPnPRegistrar
Value Name: DisableWPDRegistrar
Value Name: EnableRegistrars
Type: REG_DWORD
Value: 0Network – Windows Connect Now Wizards <GroupDescription></GroupDescription>WN08-CC-000013The Windows Connect Now wizards must be disabled.<VulnDiscussion>Windows Connect Now provides wizards for tasks such as "Set up a wireless router or access point" and must not be available to users. Functions such as these may allow unauthorized connections to a system and the potential for sensitive information to be compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> Windows Connect Now -> "Prohibit Access of the Windows Connect Now wizards" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\WCN\UI\
Value Name: DisableWcnUi
Type: REG_DWORD
Value: 1Device Install – PnP Interface Remote Access <GroupDescription></GroupDescription>WN08-CC-000019Remote access to the Plug and Play interface must be disabled for device installation.<VulnDiscussion>Remote access to the Plug and Play interface could potentially allow connections by unauthorized devices. This setting configures remote access to the Plug and Play interface and must be disabled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Device Installation -> "Allow remote access to the Plug and Play interface" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\DeviceInstall\Settings\
Value Name: AllowRemoteRPC
Type: REG_DWORD
Value: 0Device Install – Drivers System Restore Point<GroupDescription></GroupDescription>WN08-CC-000021A system restore point must be created when a new device driver is installed.<VulnDiscussion>A system restore point allows a rollback if an issue is encountered when a new device driver is installed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Device Installation -> "Prevent creation of a system restore point during device activity that would normally prompt creation of a restore point" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\DeviceInstall\Settings\
Value Name: DisableSystemRestore
Type: REG_DWORD
Value: 0Device Install – Generic Driver Error Report<GroupDescription></GroupDescription>WN08-CC-000020An Error Report must not be sent when a generic device driver is installed.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting prevents an error report from being sent when a generic device driver is installed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Device Installation -> "Do not send a Windows Error Report when a generic driver is installed on a device" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\DeviceInstall\Settings\
Value Name: DisableSendGenericDriverNotFoundToWER
Type: REG_DWORD
Value: 1Driver Install – Device Driver Search Prompt<GroupDescription></GroupDescription>WN08-CC-000026Users must not be prompted to search Windows Update for device drivers.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting prevents users from being prompted to search Windows Update for device drivers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001812Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Driver Installation -> "Turn off Windows Update device driver search prompt" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\DriverSearching\
Value Name: DontPromptForWindowsUpdate
Type: REG_DWORD
Value: 1Handwriting Recognition Error Reporting<GroupDescription></GroupDescription>WN08-CC-000035Errors in handwriting recognition on tablet PCs must not be reported to Microsoft.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting prevents errors in handwriting recognition on tablet PCs from being reported to Microsoft.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication settings -> "Turn off handwriting recognition error reporting" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\HandwritingErrorReports\
Value Name: PreventHandwritingErrorReports
Type: REG_DWORD
Value: 1Power Mgmt – Password Wake on Battery<GroupDescription></GroupDescription>WN08-CC-000054Users must be prompted for a password on resume from sleep (on battery).<VulnDiscussion>Authentication must always be required when accessing a system. This setting ensures the user is prompted for a password on resume from sleep (on battery).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002038Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Power Management -> Sleep Settings -> "Require a password when a computer wakes (on battery)" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\
Value Name: DCSettingIndex
Type: REG_DWORD
Value: 1Power Mgmt – Password Wake When Plugged In<GroupDescription></GroupDescription>WN08-CC-000055The user must be prompted for a password on resume from sleep (plugged in). <VulnDiscussion>Authentication must always be required when accessing a system. This setting ensures the user is prompted for a password on resume from sleep (plugged in).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002038Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Power Management -> Sleep Settings -> "Require a password when a computer wakes (plugged in)" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\
Value Name: ACSettingIndex
Type: REG_DWORD
Value: 1Remote Assistance – Session Logging<GroupDescription></GroupDescription>WN08-CC-000062Remote Assistance log files must be generated.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. This setting will turn on session logging for Remote Assistance connections.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Remote Assistance -> "Turn on session logging" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\
Value Name: LoggingEnabled
Type: REG_DWORD
Value: 1Game Explorer Information Downloads<GroupDescription></GroupDescription>WN08-CC-000092Game explorer information must not be downloaded from Windows Metadata Services.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting prevents game information from being downloaded from Windows Metadata Services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Game Explorer -> "Turn off downloading of game information" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\GameUX\
Value Name: DownloadGameInfo
Type: REG_DWORD
Value: 0Search – Encrypted Files Indexing<GroupDescription></GroupDescription>WN08-CC-000107Indexing of encrypted files must be turned off.<VulnDiscussion>Indexing of encrypted files may expose sensitive data. This setting prevents encrypted files from being indexed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Search -> "Allow indexing of encrypted files" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\Windows Search\
Value Name: AllowIndexingEncryptedStoresOrItems
Type: REG_DWORD
Value: 0Search – Exchange Folder Indexing <GroupDescription></GroupDescription>WN08-CC-000108Indexing of mail items in Exchange folders when Outlook is running in uncached mode must be turned off.<VulnDiscussion>Indexing of encrypted items may expose sensitive data. This setting prevents mail items in a Microsoft Exchange folder from being indexed when Outlook is running in uncached mode.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381If Outlook is not installed on the system, this is NA.
If Outlook is installed on the system, configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Search -> "Enable indexing uncached Exchange folders" to "Disabled".If Outlook is not installed on the system, this is NA.
If Outlook is installed on the system and the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Windows Search\
Value Name: PreventIndexingUncachedExchangeFolders
Type: REG_DWORD
Value: 1Defender – SpyNet Reporting<GroupDescription></GroupDescription>WN08-CC-000111Microsoft Active Protection Service membership must be disabled.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting disables Microsoft Active Protection Service membership and reporting.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Defender >> MAPS >> "Join Microsoft MAPS" to "Disabled".If the following registry value exists and is set to "1" (Basic) or "2" (Advanced), this is a finding.
If the following registry value does not exist, this is not a finding.
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\Windows Defender\Spynet\
Value Name: SpyNetReporting
Type: REG_DWORD
Value: 1 or 2 = a FindingWindows Explorer – Heap Termination<GroupDescription></GroupDescription>WN08-CC-000090Turning off File Explorer heap termination on corruption must be disabled.<VulnDiscussion>Legacy plug-in applications may continue to function when a File Explorer session has become corrupt. Disabling this feature will prevent this.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002385Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> File Explorer -> "Turn off heap termination on corruption" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\Explorer\
Value Name: NoHeapTerminationOnCorruption
Type: REG_DWORD
Value: 0Media DRM – Internet Access<GroupDescription></GroupDescription>WN08-CC-000120Windows Media Digital Rights Management must be prevented from accessing the Internet.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This check verifies that Windows Media DRM will be prevented from accessing the Internet.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Media Digital Rights Management -> "Prevent Windows Media DRM Internet Access" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\WMDRM\
Value Name: DisableOnline
Type: REG_DWORD
Value: 1User Network Sharing<GroupDescription></GroupDescription>WN08-UC-000012Users must be prevented from sharing files in their profiles.<VulnDiscussion>Allowing users to share files in their profiles may provide unauthorized access or result in the exposure of sensitive data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for User Configuration -> Administrative Templates -> Windows Components -> Network Sharing -> "Prevent users from sharing files within their profile" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_CURRENT_USER
Subkey: \Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\
Value Name: NoInPlaceSharing
Type: REG_DWORD
Value: 1Software Certificate Installation Files<GroupDescription></GroupDescription>WN08-GE-000020Software certificate installation files must be removed from a system.<VulnDiscussion>Use of software certificates and their accompanying installation files for end users to access resources is less secure than the use of hardware-based certificates.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Remove any certificate installation files (*.p12 and *.pfx) found on a system.
Note: This does not apply to server-based applications that have a requirement for .p12 certificate files (e.g., Oracle Wallet Manager).Search all drives for *.p12 and *.pfx files.
If any files with these extensions exist, this is a finding.
This does not apply to server-based applications that have a requirement for .p12 certificate files (e.g., Oracle Wallet Manager). Some applications create files with extensions of .p12 that are NOT certificate installation files. Removal of non-certificate installation files from systems is not required. These must be documented with the ISSO.UAC - Application Elevations<GroupDescription></GroupDescription>WN08-SO-000081Windows must elevate all applications in User Account Control, not just signed ones.<VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures whether Windows elevates all applications, not just signed ones.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECCD-1, ECCD-2</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001084Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "User Account Control: Only elevate executables that are signed and validated" to "Disabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "User Account Control: Only elevate executables that are signed and validated" is not set to "Disabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\System\
Value Name: ValidateAdminCodeSignatures
Value Type: REG_DWORD
Value: 0Windows Customer Experience Improvement Program <GroupDescription></GroupDescription>WN08-CC-000045The Windows Customer Experience Improvement Program must be disabled.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting ensures the Windows Customer Experience Improvement Program is disabled so information is not passed to the vendor.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication Settings -> "Turn off Windows Customer Experience Improvement Program" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\SQMClient\Windows\
Value Name: CEIPEnable
Type: REG_DWORD
Value: 0Help Experience Improvement Program <GroupDescription></GroupDescription>WN08-UC-000007The Windows Help Experience Improvement Program must be disabled.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting ensures the Windows Help Experience Improvement Program is disabled to prevent information from being passed to the vendor.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for User Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication Settings -> "Turn off Help Experience Improvement Program" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_CURRENT_USER
Subkey: \Software\Policies\Microsoft\Assistance\Client\1.0\
Value Name: NoImplicitFeedback
Type: REG_DWORD
Value: 1Built-in Admin Account Status<GroupDescription></GroupDescription>WN08-SO-000001The built-in administrator account must be disabled.<VulnDiscussion>The built-in administrator account is a well-known account subject to attack. It also provides no accountability to individual administrators on a system. It must be disabled to prevent its use.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000764Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Accounts: Administrator account status" to "Disabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Accounts: Administrator account status" is not set to "Disabled", this is a finding.Help Ratings<GroupDescription></GroupDescription>WN08-UC-000008Windows Help Ratings feedback must be turned off.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting ensures users cannot provide ratings feedback to Microsoft for Help content.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for User Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication Settings -> "Turn off Help Ratings" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_CURRENT_USER
Subkey: \Software\Policies\Microsoft\Assistance\Client\1.0\
Value Name: NoExplicitFeedback
Type: REG_DWORD
Value: 1User Right - Debug Programs<GroupDescription></GroupDescription>WN08-UR-000016Unauthorized accounts must not have the Debug programs user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Debug Programs" user right can attach a debugger to any process or to the kernel, providing complete access to sensitive and critical operating system components. This right is given to Administrators in the default configuration.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Debug Programs" to only include the following accounts or groups:
AdministratorsAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Debug Programs" user right, this is a finding:
AdministratorsSPN Target Name Validation Level<GroupDescription></GroupDescription>WN08-SO-000035The service principal name (SPN) target name validation level must be configured to Accept if provided by client.<VulnDiscussion>If a service principle name (SPN) is provided by the client, it is validated against the server's list of SPNs, aiding in the prevention of spoofing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Microsoft network server: Server SPN target name validation level" to "Accept if provided by client".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Microsoft network server: Server SPN target name validation level" is not set to "Accept if provided by client", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \System\CurrentControlSet\Services\LanmanServer\Parameters\
Value Name: SmbServerNameHardeningLevel
Type: REG_DWORD
Value: 1Computer Identity Authentication for NTLM<GroupDescription></GroupDescription>WN08-SO-000061Services using Local System that use Negotiate when reverting to NTLM authentication must use the computer identity vs. authenticating anonymously.<VulnDiscussion>Services using Local System that use Negotiate when reverting to NTLM authentication may gain unauthorized access if allowed to authenticate anonymously vs. using the computer identity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000778Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network Security: Allow Local System to use computer identity for NTLM" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Network Security: Allow Local System to use computer identity for NTLM" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \System\CurrentControlSet\Control\LSA\
Value Name: UseMachineId
Type: REG_DWORD
Value: 1NTLM NULL Session Fallback<GroupDescription></GroupDescription>WN08-SO-000062NTLM must be prevented from falling back to a Null session.<VulnDiscussion>NTLM sessions that are allowed to fall back to Null (unauthenticated) sessions may gain unauthorized access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network Security: Allow LocalSystem NULL session fallback" to "Disabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Network Security: Allow LocalSystem NULL session fallback" is not set to "Disabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \System\CurrentControlSet\Control\LSA\MSV1_0\
Value Name: allownullsessionfallback
Type: REG_DWORD
Value: 0PKU2U Online Identities Authentication<GroupDescription></GroupDescription>WN08-SO-000063PKU2U authentication using online identities must be prevented.<VulnDiscussion>PKU2U is a peer-to-peer authentication protocol. This setting prevents online identities from authenticating to domain-joined systems. Authentication will be centrally managed with Windows user accounts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network Security: Allow PKU2U authentication requests to this computer to use online identities" to "Disabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Network Security: Allow PKU2U authentication requests to this computer to use online identities" is not set to "Disabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \System\CurrentControlSet\Control\LSA\pku2u\
Value Name: AllowOnlineID
Type: REG_DWORD
Value: 0Kerberos Encryption Types<GroupDescription></GroupDescription>WN08-SO-000064Kerberos encryption types must be configured to prevent the use of DES encryption suites.<VulnDiscussion>Certain encryption types are no longer considered secure. This setting configures a minimum encryption type for Kerberos, preventing the use of the DES encryption suites.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000803Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network Security: Configure encryption types allowed for Kerberos" to "Enabled" with only the following selected:
RC4_HMAC_MD5
AES128_HMAC_SHA1
AES256_HMAC_SHA1
Future encryption typesAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Network Security: Configure encryption types allowed for Kerberos" is not set to "Enabled" with only the following selected, this is a finding:
RC4_HMAC_MD5
AES128_HMAC_SHA1
AES256_HMAC_SHA1
Future encryption types
(If DES_CBC_CRC and DES_CBC_MD5 are selected, this is a finding)
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\
Value Name: SupportedEncryptionTypes
Type: REG_DWORD
Value: 0x7ffffffc (2147483644)IPv6 Source Routing<GroupDescription></GroupDescription>WN08-SO-000037IPv6 source routing must be configured to highest protection.<VulnDiscussion>Configuring the system to disable IPv6 source routing protects against spoofing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)" to "Highest protection, source routing is completely disabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
(See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)
If the value for "MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)" is not set to "Highest protection, source routing is completely disabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \System\CurrentControlSet\Services\Tcpip6\Parameters\
Value Name: DisableIpSourceRouting
Type: REG_DWORD
Value: 2IPv6 TCP Data Retransmissions<GroupDescription></GroupDescription>WN08-SO-000047IPv6 TCP data retransmissions must be configured to prevent resources from becoming exhausted.<VulnDiscussion>Configuring Windows to limit the number of times that IPv6 TCP retransmits unacknowledged data segments before aborting the attempt helps prevent resources from becoming exhausted.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002385Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "MSS: (TcpMaxDataRetransmissions IPv6) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)" to "3" or less.Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies >> Security Options.
(See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)
If the value for "MSS: (TcpMaxDataRetransmissions IPv6) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)" is not set to "3" or less, this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\
Value Name: TcpMaxDataRetransmissions
Type: REG_DWORD
Value: 3 (or less)Elevate when setting a network’s location<GroupDescription></GroupDescription>WN08-CC-000005Domain users must be required to elevate when setting a networks location.<VulnDiscussion>Selecting an incorrect network location may allow greater exposure of a system. Elevation is required by default on non-domain systems to change network location. This setting configures elevation to also be required on domain-joined systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001084Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> Network Connections -> "Require domain users to elevate when setting a network's location" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\Network Connections\
Value Name: NC_StdDomainUserSetLocation
Type: REG_DWORD
Value: 1Direct Access – Route Through Internal Network<GroupDescription></GroupDescription>WN08-CC-000006All Direct Access traffic must be routed through the internal network.<VulnDiscussion>Routing all Direct Access traffic through the internal network allows monitoring and prevents split tunneling.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> Network Connections -> "Route all traffic through the internal network" to "Enabled: Enabled State".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\TCPIP\v6Transition\
Value Name: Force_Tunneling
Type: REG_SZ
Value: EnabledWindows Update Point and Print Driver Search<GroupDescription></GroupDescription>WN08-CC-000016Windows Update must be prevented from searching for point and print drivers.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting will prevent Windows from searching Windows Update for point and print drivers. Only the local driver store and server driver cache will be searched.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001812Configure the policy value for Computer Configuration -> Administrative Templates -> Printers -> "Extend Point and Print connection to search Windows Update" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows NT\Printers\
Value Name: DoNotInstallCompatibleDriverFromWindowsUpdate
Type: REG_DWORD
Value: 1Prevent device metadata retrieval from Internet<GroupDescription></GroupDescription>WN08-CC-000022Device metadata retrieval from the Internet must be prevented.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting will prevent Windows from retrieving device metadata from the Internet.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Device Installation >> "Prevent device metadata retrieval from the Internet" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Device Metadata\
Value Name: PreventDeviceMetadataFromNetwork
Type: REG_DWORD
Value: 1Prevent Windows Update for device driver search<GroupDescription></GroupDescription>WN08-CC-000024Device driver searches using Windows Update must be prevented.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting will prevent the system from searching Windows Update for device drivers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001812Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Device Installation -> "Specify Search Order for device driver source locations" to "Enabled: Do not search Windows Update".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\DriverSearching\
Value Name: SearchOrderConfig
Type: REG_DWORD
Value: 0Handwriting personalization data sharing<GroupDescription></GroupDescription>WN08-CC-000034Handwriting personalization data sharing with Microsoft must be prevented.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting prevents data from the handwriting recognition personalization tool being shared with Microsoft.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication settings -> "Turn off handwriting personalization data sharing" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\TabletPC\
Value Name: PreventHandwritingDataSharing
Type: REG_DWORD
Value: 1MSDT Interactive Communication<GroupDescription></GroupDescription>WN08-CC-000066Microsoft Support Diagnostic Tool (MSDT) interactive communication with Microsoft must be prevented.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting prevents the MSDT from communicating with and sending collected data to Microsoft, the default support provider.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Troubleshooting and Diagnostics -> Microsoft Support Diagnostic Tool -> "Microsoft Support Diagnostic Tool: Turn on MSDT interactive communication with Support Provider" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\ScriptedDiagnosticsProvider\Policy\
Value Name: DisableQueryRemoteServer
Type: REG_DWORD
Value: 0Windows Online Troubleshooting Service<GroupDescription></GroupDescription>WN08-CC-000067Access to Windows Online Troubleshooting Service (WOTS) must be prevented.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting prevents users from searching troubleshooting content on Microsoft servers. Only local content will be available.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Troubleshooting and Diagnostics -> Scripted Diagnostics -> "Troubleshooting: Allow users to access online troubleshooting content on Microsoft servers from the Troubleshooting Control Panel (via Windows Online Troubleshooting Service - WOTS)" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\ScriptedDiagnosticsProvider\Policy\
Value Name: EnableQueryRemoteServer
Type: REG_DWORD
Value: 0Disable PerfTrack<GroupDescription></GroupDescription>WN08-CC-000068Responsiveness events must be prevented from being aggregated and sent to Microsoft.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting prevents responsiveness events from being aggregated and sent to Microsoft.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Troubleshooting and Diagnostics -> Windows Performance PerfTrack -> "Enable/Disable PerfTrack" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\WDI\{9c5a40da-b965-4fc3-8781-88dd50a6299d}\
Value Name: ScenarioExecutionEnabled
Type: REG_DWORD
Value: 0Application Compatibility Program Inventory<GroupDescription></GroupDescription>WN08-CC-000071The Application Compatibility Program Inventory must be prevented from collecting data and sending the information to Microsoft.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting will prevent the Program Inventory from collecting data about a system and sending the information to Microsoft.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Application Compatibility -> "Turn off Inventory Collector" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\AppCompat\
Value Name: DisableInventory
Type: REG_DWORD
Value: 1Autoplay for non-volume devices<GroupDescription></GroupDescription>WN08-CC-000072Autoplay must be turned off for non-volume devices.<VulnDiscussion>Allowing autoplay to execute may introduce malicious code to a system. Autoplay begins reading from a drive as soon as you insert media in the drive. As a result, the setup file of programs or music on audio media may start. This setting will disable autoplay for non-volume devices (such as Media Transfer Protocol (MTP) devices).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001764Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> AutoPlay Policies -> "Disallow Autoplay for non-volume devices" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\Explorer\
Value Name: NoAutoplayfornonVolume
Type: REG_DWORD
Value: 1Turn Off Game Updates<GroupDescription></GroupDescription>WN08-CC-000093Downloading of game update information must be turned off.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting will prevent the system from downloading game update information from Windows Metadata Services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001812Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Game Explorer -> "Turn off game updates" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\GameUX\
Value Name: GameUpdateOptions
Type: REG_DWORD
Value: 0Prevent Joining Homegroup<GroupDescription></GroupDescription>WN08-CC-000094The system must be prevented from joining a homegroup.<VulnDiscussion>Homegroups are a method of sharing data and printers on a home network. This setting will prevent a system from being joined to a homegroup. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> HomeGroup -> "Prevent the computer from joining a homegroup" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\Homegroup\
Value Name: DisableHomeGroup
Type: REG_DWORD
Value: 1Explorer Data Execution Prevention<GroupDescription></GroupDescription>WN08-CC-000089Explorer Data Execution Prevention must be enabled.<VulnDiscussion>Data Execution Prevention (DEP) provides additional protection by performing checks on memory to help prevent malicious code from running. This setting will prevent Data Execution Prevention from being turned off for File Explorer.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002824Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> File Explorer -> "Turn off Data Execution Prevention for Explorer" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\Explorer\
Value Name: NoDataExecutionPrevention
Type: REG_DWORD
Value: 0Default Autorun Behavior<GroupDescription></GroupDescription>WN08-CC-000073The default autorun behavior must be configured to prevent autorun commands.<VulnDiscussion>Allowing autorun commands to execute may introduce malicious code to a system. Configuring this setting prevents autorun commands from executing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001764Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> AutoPlay Policies -> "Set the default behavior for AutoRun" to "Enabled:Do not execute any autorun commands".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\
Value Name: NoAutorun
Type: REG_DWORD
Value: 1Winlogon Registry Permissions<GroupDescription></GroupDescription>WN08-RG-000001Standard user accounts must only have Read permissions to the Winlogon registry key.<VulnDiscussion>Permissions on the Winlogon registry key must only allow privileged accounts to change registry values. If standard users have this capability, there is a potential for programs to run with elevated privileges when a privileged user logs on to the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Maintain the default permissions of the following registry key as noted below:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\
TrustedInstaller - Full Control
SYSTEM - Full Control
Administrators - Full Control
Users - Read
ALL APPLICATION PACKAGES - ReadRun "Regedit".
Navigate to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\
Review the permissions.
If the default permissions listed below have been changed, this is a finding.
TrustedInstaller - Full Control
SYSTEM - Full Control
Administrators - Full Control
Users - Read
ALL APPLICATION PACKAGES - ReadRestrict Anonymous SAM Enumeration<GroupDescription></GroupDescription>WN08-SO-000051Anonymous enumeration of SAM accounts must not be allowed.<VulnDiscussion>Anonymous enumeration of SAM accounts allows anonymous log on users (null session connections) to list all accounts names, thus providing a list of potential points to attack the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network access: Do not allow anonymous enumeration of SAM accounts" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Network access: Do not allow anonymous enumeration of SAM accounts" is not set to "Enabled", this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \System\CurrentControlSet\Control\Lsa\
Value Name: RestrictAnonymousSAM
Value Type: REG_DWORD
Value: 1Legal Banner Dialog Box Title<GroupDescription></GroupDescription>WN08-SO-000023The Windows dialog box title for the legal banner must be configured.<VulnDiscussion>Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000048CCI-001384CCI-001385CCI-001386CCI-001387CCI-001388Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Interactive Logon: Message title for users attempting to log on" to "DoD Notice and Consent Banner", "US Department of Defense Warning Statement", or a site-defined equivalent.
If a site-defined title is used, it can in no case contravene or modify the language of the banner text required in V-1089.Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Interactive Logon: Message title for users attempting to log on" is not set to "DoD Notice and Consent Banner", "US Department of Defense Warning Statement" or a site-defined equivalent, this is a finding.
If a site-defined title is used, it can in no case contravene or modify the language of the banner text required in V-1089.
Automated tools may only search for the titles defined above. If a site-defined title is used, a manual review will be required.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\System\
Value Name: LegalNoticeCaption
Value Type: REG_SZ
Value: See message title aboveAccess Credential Manager as a trusted caller<GroupDescription></GroupDescription>WN08-UR-000001Unauthorized accounts must not have the Access Credential Manager as a trusted caller user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Access Credential Manager as a trusted caller" user right may be able to retrieve the credentials of other accounts from Credential Manager.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Access Credential Manager as a trusted caller" to be defined but containing no entries (blank).Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups are granted the "Access Credential Manager as a trusted caller" user right, this is a finding.Access this computer from the network<GroupDescription></GroupDescription>WN08-UR-000002Unauthorized accounts must not have the Access this computer from the network user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Access this computer from the network" user right may access resources on the system, and must be limited to those that require it.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000213Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Access this computer from the network" to only include the following accounts or groups:
AdministratorsAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Access this computer from the network" user right, this is a finding:
AdministratorsAllow log on locally<GroupDescription></GroupDescription>WN08-UR-000005Unauthorized accounts must not have the Allow log on locally user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Allow log on locally" user right can log on interactively to a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000213Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Allow log on locally" to only include the following accounts or groups:
Administrators
Users
Systems dedicated to managing Active Directory (AD admin platforms), must only allow Administrators, removing the Users group.Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Allow log on locally" user right, this is a finding:
Administrators
Users
Systems dedicated to managing Active Directory (AD admin platforms), must only allow Administrators, removing the Users group.Allow log on through Remote Desktop Services<GroupDescription></GroupDescription>WN08-UR-000006Unauthorized accounts must not have the Allow log on through Remote Desktop Services user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Allow log on through Remote Desktop Services" user right can access a system through Remote Desktop.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000213Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Allow log on through Remote Desktop Services" to be defined but containing no entries (blank).
Administrators may be granted this user right if Remote Desktop Services is necessary for remote administration. Restricted Admin mode must be used. This must be document with the ISSO.
See Microsoft article KB2871997 for patches required to add this function to systems prior to Windows 8.1.
Restricted Admin mode for Remote Desktop Connections can be implemented for each session using a command line switch to start the Remote Desktop Client or through a group policy to enable it for all sessions.
The command line to do this is "mstsc /restrictedadmin".
To enable this with group policy, configure the policy value for Computer Configuration >> Administrative Templates >> System >> Credentials Delegation >> "Restrict delegation of credentials to remote servers" to "Enabled".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies >> User Rights Assignment.
If any accounts or groups are granted the "Allow log on through Remote Desktop Services" user right, this is a finding.
Administrators may be granted this user right if Remote Desktop Services is necessary for remote administration. Restricted Admin mode must be used. This must be document with the ISSO.
See Microsoft article KB2871997 for patches required to add this function to systems prior to Windows 8.1.
Restricted Admin mode for Remote Desktop Connections can be implemented for each session using a command line switch to start the Remote Desktop Client or through a group policy to enable it for all sessions.
The command line to do this is "mstsc /restrictedadmin".
To enable this with group policy, configure the policy value for Computer Configuration >> Administrative Templates >> System >> Credentials Delegation >> "Restrict delegation of credentials to remote servers" to "Enabled".Back up files and directories<GroupDescription></GroupDescription>WN08-UR-000007Unauthorized accounts must not have the Back up files and directories user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Back up files and directories" user right can circumvent file and directory permissions and could allow access to sensitive data."</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Back up files and directories" to only include the following accounts or groups:
AdministratorsAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Back up files and directories" user right, this is a finding:
AdministratorsBypass traverse checking<GroupDescription></GroupDescription>WN08-UR-000008Unauthorized accounts must not have the Bypass traverse checking user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Bypass traverse checking" user right can pass through folders when browsing even if they do not have the "Traverse Folder" access permission. They could potentially view sensitive file and folder names. They would not have additional access to the files and folders unless it is granted through permissions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Bypass traverse checking" to only include the following accounts or groups:
Administrators
Users
Local Service
Network Service
Window Manager\Window Manager GroupAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Bypass traverse checking" user right, this is a finding:
Administrators
Users
Local Service
Network Service
Window Manager\Window Manager GroupChange the system time<GroupDescription></GroupDescription>WN08-UR-000009Unauthorized accounts must not have the Change the system time user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Change the system time" user right can change the system time, which can impact authentication, as well as affect time stamps on event log entries.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Change the system time" to only include the following accounts or groups:
Administrators
Local ServiceAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Change the system time" user right, this is a finding:
Administrators
Local ServiceChange the time zone<GroupDescription></GroupDescription>WN08-UR-000010Unauthorized accounts must not have the Change the time zone user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Change the time zone" user right can change the time zone of a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Change the time zone" to only include the following accounts or groups:
Administrators
Users
Local ServiceAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Change the time zone" user right, this is a finding:
Administrators
Users
Local ServiceCreate a pagefile<GroupDescription></GroupDescription>WN08-UR-000011Unauthorized accounts must not have the Create a pagefile user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Create a pagefile" user right can change the size of a pagefile, which could affect system performance.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Create a pagefile" to only include the following accounts or groups:
AdministratorsAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Create a pagefile" user right, this is a finding:
AdministratorsCreate a token object<GroupDescription></GroupDescription>WN08-UR-000012No accounts must have the Create a token object user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
The "Create a token object" user right allows a process to create an access token. This could be used to provide elevated rights and compromise a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Create a token object" to be defined but containing no entries (blank).Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups are granted the "Create a token object" user right, this is a finding.Create global objects<GroupDescription></GroupDescription>WN08-UR-000013Unauthorized accounts must not have the Create global objects user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Create global objects" user right can create objects that are available to all sessions, which could affect processes in other users' sessions. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Create global objects" to only include the following accounts or groups:
Administrators
Service
Local Service
Network ServiceAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Create global objects" user right, this is a finding:
Administrators
Service
Local Service
Network ServiceCreate permanent shared objects<GroupDescription></GroupDescription>WN08-UR-000014Unauthorized accounts must not have the Create permanent shared objects user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Create permanent shared objects" user right could expose sensitive data by creating shared objects.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Create permanent shared objects" to be defined but containing no entries (blank).Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups are granted the "Create permanent shared objects" user right, this is a finding.Create symbolic links<GroupDescription></GroupDescription>WN08-UR-000015Unauthorized accounts must not have the Create symbolic links user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Create symbolic links" user right can create pointers to other objects, which could potentially expose the system to attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Create symbolic links" to only include the following accounts or groups:
AdministratorsAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Create symbolic links" user right, this is a finding:
AdministratorsDeny log on as a batch job<GroupDescription></GroupDescription>WN08-UR-000018The Deny log on as a batch job user right on workstations must be configured to prevent access from highly privileged domain accounts on domain systems and unauthenticated access on all systems.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
The "Deny log on as a batch job" right defines accounts that are prevented from logging on to the system as a batch job, such as Task Scheduler.
In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower trust systems helps mitigate the risk of privilege escalation from credential theft attacks which could lead to the compromise of an entire domain.
The Guests group must be assigned to prevent unauthenticated access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000213Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Deny log on as a batch job" to include the following.
Domain Systems Only:
Enterprise Admin Group
Domain Admin Group
All Systems:
Guests GroupAnalyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If the following accounts or groups are not defined for the "Deny log on as a batch job" right, this is a finding:
Domain Systems Only:
Enterprise Admin Group
Domain Admin Group
All Systems:
Guests GroupDeny log on as service <GroupDescription></GroupDescription>WN08-UR-000019The Deny log on as a service user right on workstations must be configured to prevent access from highly privileged domain accounts on domain systems and unauthenticated access on all systems. <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
The "Deny log on as a service" right defines accounts that are denied log on as a service.
In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower trust systems helps mitigate the risk of privilege escalation from credential theft attacks which could lead to the compromise of an entire domain.
Incorrect configurations could prevent services from starting and result in a DoS.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000213Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Deny log on as a service" to include the following for domain joined systems.
Enterprise Admin Group
Domain Admin Group
Configure the "Deny log on as a service" for non-domain systems to include no entries (blank).Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If the following accounts or groups are not defined for the "Deny log on as a service" right on domain joined systems, this is a finding:
Enterprise Admin Group
Domain Admin Group
If any accounts or groups are defined for the "Deny log on as a service" right on non-domain joined systems, this is a finding.Deny log on locally<GroupDescription></GroupDescription>WN08-UR-000020The Deny log on locally user right on workstations must be configured to prevent access from highly privileged domain accounts on domain systems and unauthenticated access on all systems.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
The "Deny log on locally" right defines accounts that are prevented from logging on interactively.
In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower trust systems helps mitigate the risk of privilege escalation from credential theft attacks which could lead to the compromise of an entire domain.
The Guests group must be assigned this right to prevent unauthenticated access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000213Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Deny log on locally" to include the following.
Domain Systems Only:
Enterprise Admins Group
Domain Admins Group
Workstations dedicated to the management of Active Directory (see V-36436 in the Active Directory Domain STIG) are exempt from this.
All Systems:
Guests GroupAnalyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If the following accounts or groups are not defined for the "Deny log on locally" right, this is a finding.
Domain Systems Only:
Enterprise Admins Group
Domain Admins Group
Workstations dedicated to the management of Active Directory (see V-36436 in the Active Directory Domain STIG) are exempt from this.
All Systems:
Guests GroupDeny log on through Remote Desktop \ Terminal Services<GroupDescription></GroupDescription>WN08-UR-000021The Deny log on through Remote Desktop Services user right on workstations must at a minimum be configured to prevent access from highly privileged domain accounts and local accounts on domain systems and unauthenticated access on all systems. <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
The "Deny log on through Remote Desktop Services" right defines the accounts that are prevented from logging on using Remote Desktop Services.
If Remote Desktop Services is not used by the organization, the Everyone group must be assigned this right to prevent all access.
In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower trust systems helps mitigate the risk of privilege escalation from credential theft attacks which could lead to the compromise of an entire domain.
Local accounts on domain-joined systems must also be assigned this right to decrease the risk of lateral movement resulting from credential theft attacks.
The Guests group must be assigned this right to prevent unauthenticated access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000213Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Deny log on through Remote Desktop" to include the following.
If Remote Desktop Services is not used by the organization, assign the Everyone group this right to prevent all access.
Domain Systems Only:
Enterprise Admins group
Domain Admins group
Local account (see Note below)
All Systems:
Guests group
Systems dedicated to the management of Active Directory (AD admin platforms, see V-36436 in the Active Directory Domain STIG) are exempt from denying the Enterprise Admins and Domain Admins groups.
Note: "Local account" is a built-in security group used to assign user rights and permissions to all local accounts.Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If the following accounts or groups are not defined for the "Deny log on through Remote Desktop Services" right, this is a finding:
If Remote Desktop Services is not used by the organization, the Everyone group can replace all of the groups listed below.
Domain Systems Only:
Enterprise Admin group
Domain Admin group
Local account (see Note below)
All Systems:
Guests group
Systems dedicated to the management of Active Directory (AD admin platforms, see V-36436 in the Active Directory Domain STIG) are exempt from denying the Enterprise Admins and Domain Admins groups.
Note: "Local account" is a built-in security group used to assign user rights and permissions to all local accounts.Enable accounts to be trusted for delegation<GroupDescription></GroupDescription>WN08-UR-000022Unauthorized accounts must not have the Enable computer and user accounts to be trusted for delegation user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
The "Enable computer and user accounts to be trusted for delegation" user right allows the "Trusted for Delegation" setting to be changed. This could potentially allow unauthorized users to impersonate other users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Enable computer and user accounts to be trusted for delegation" to be defined but containing no entries (blank).Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups are granted the "Enable computer and user accounts to be trusted for delegation" user right, this is a finding.Force shutdown from a remote system<GroupDescription></GroupDescription>WN08-UR-000023Unauthorized accounts must not have the Force shutdown from a remote system user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Force shutdown from a remote system" user right can remotely shut down a system which could result in a DoS.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Force shutdown from a remote system" to only include the following accounts or groups:
AdministratorsAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Force shutdown from a remote system" user right, this is a finding:
AdministratorsGenerate security audits<GroupDescription></GroupDescription>WN08-UR-000024Unauthorized accounts must not have the Generate security audits user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
The "Generate security audits" user right specifies users and processes that can generate Security Log audit records, which must only be the system service accounts defined.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Generate security audits" to only include the following accounts or groups:
Local Service
Network ServiceAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Generate security audits" user right, this is a finding:
Local Service
Network ServiceImpersonate a client after authentication<GroupDescription></GroupDescription>WN08-UR-000025Unauthorized accounts must not have the Impersonate a client after authentication user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
The "Impersonate a client after authentication" user right allows a program to impersonate another user or account to run on their behalf. An attacker could potentially use this to elevate privileges.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Impersonate a client after authentication" to only include the following accounts or groups:
Administrators
Service
Local Service
Network ServiceAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Impersonate a client after authentication" user right, this is a finding:
Administrators
Service
Local Service
Network ServiceIncrease scheduling priority<GroupDescription></GroupDescription>WN08-UR-000027Unauthorized accounts must not have the Increase scheduling priority user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Increase scheduling priority" user right can change a scheduling priority causing performance issues or a DoS.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Increase scheduling priority" to only include the following accounts or groups:
AdministratorsAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Increase scheduling priority" user right, this is a finding:
AdministratorsLoad and unload device drivers<GroupDescription></GroupDescription>WN08-UR-000028Unauthorized accounts must not have the Load and unload device drivers user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
The "Load and unload device drivers" user right allows device drivers to dynamically be loaded on a system by a user. This could potentially be used to install malicious code by an attacker.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Load and unload device drivers" to only include the following accounts or groups:
AdministratorsAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Load and unload device drivers" user right, this is a finding:
AdministratorsLock pages in memory<GroupDescription></GroupDescription>WN08-UR-000029Unauthorized accounts must not have the Lock pages in memory user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
The "Lock pages in memory" user right allows physical memory to be assigned to processes, which could cause performance issues or a DoS.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Lock pages in memory" to be defined but containing no entries (blank).Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups are granted the "Lock pages in memory" user right, this is a finding.Manage auditing and security log<GroupDescription></GroupDescription>WN08-UR-000032Unauthorized accounts must not have the Manage auditing and security log user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Manage auditing and security log" user right can manage the security log and change auditing configurations. This could be used to clear evidence of tampering. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000162CCI-000163CCI-000164CCI-000171CCI-001914Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Manage auditing and security log" to only include the following accounts or groups:
AdministratorsAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Manage auditing and security log" user right, this is a finding:
AdministratorsModify an object label<GroupDescription></GroupDescription>WN08-UR-000033Unauthorized accounts must not have the Modify an object label user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Modify an object label" user right can change the integrity label of an object. This could potentially be used to execute code at a higher privilege.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Modify an object label" to be defined but containing no entries (blank).Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups are granted the "Modify an object label" user right, this is a finding.Modify firmware environment values<GroupDescription></GroupDescription>WN08-UR-000034Unauthorized accounts must not have the Modify firmware environment values user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Modify firmware environment values" user right can change hardware configuration environment variables. This could result in hardware failures or a DoS.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Modify firmware environment values" to only include the following accounts or groups:
AdministratorsAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Modify firmware environment values" user right, this is a finding:
AdministratorsPerform volume maintenance tasks<GroupDescription></GroupDescription>WN08-UR-000035Unauthorized accounts must not have the Perform volume maintenance tasks user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Perform volume maintenance tasks" user right can manage volume and disk configurations. They could potentially delete volumes, resulting in, data loss or a DoS.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Perform volume maintenance tasks" to only include the following accounts or groups:
AdministratorsAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Perform volume maintenance tasks" user right, this is a finding:
AdministratorsProfile single process<GroupDescription></GroupDescription>WN08-UR-000036Unauthorized accounts must not have the Profile single process user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Profile single process" user right can monitor non-system processes performance. An attacker could potentially use this to identify processes to attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Profile single process" to only include the following accounts or groups:
AdministratorsAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Profile single process" user right, this is a finding:
AdministratorsProfile system performance<GroupDescription></GroupDescription>WN08-UR-000037Unauthorized accounts must not have the Profile system performance user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Profile system performance" user right can monitor system processes performance. An attacker could potentially use this to identify processes to attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Profile system performance" to only include the following accounts or groups:
Administrators
NT Service\WdiServiceHostAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Profile system performance" user right, this is a finding:
Administrators
NT Service\WdiServiceHostRemove computer from docking station<GroupDescription></GroupDescription>WN08-UR-000038Unauthorized accounts must not have the Remove computer from docking station user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
The "Remove computer from docking station" user right defines accounts that can undock a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Remove computer from docking station" to only include the following accounts or groups:
Administrators
UsersAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Remove computer from docking station" user right, this is a finding:
Administrators
UsersReplace a process level token<GroupDescription></GroupDescription>WN08-UR-000039Unauthorized accounts must not have the Replace a process level token user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
The "Replace a process level token" user right allows one process or service to start another process or service with a different security access token. A user with this right could use this to impersonate another account.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Replace a process level token" to only include the following accounts or groups:
Local Service
Network ServiceAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Replace a process level token" user right, this is a finding:
Local Service
Network ServiceRestore files and directories<GroupDescription></GroupDescription>WN08-UR-000040Unauthorized accounts must not have the Restore files and directories user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Restore files and directories" user right can circumvent file and directory permissions and could allow access to sensitive data. It could also be used to over-write more current data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Restore files and directories" to only include the following accounts or groups:
AdministratorsAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Restore files and directories" user right, this is a finding:
AdministratorsShut down the system<GroupDescription></GroupDescription>WN08-UR-000041Unauthorized accounts must not have the Shut down the system user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Shut down the system" user right can interactively shut down a system, which could result in a DoS.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Shut down the system" to only include the following accounts or groups:
Administrators
UsersAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Shut down the system" user right, this is a finding:
Administrators
UsersTake ownership of files or other objects<GroupDescription></GroupDescription>WN08-UR-000042Unauthorized accounts must not have the Take ownership of files or other objects user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Take ownership of files or other objects" user right can take ownership of objects and make changes.
</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Take ownership of files or other objects" to only include the following accounts or groups:
AdministratorsAnalyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups other than the following are granted the "Take ownership of files or other objects" user right, this is a finding:
AdministratorsAudit - Credential Validation - Success<GroupDescription></GroupDescription>WN08-AU-000002The system must be configured to audit Account Logon - Credential Validation successes.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Credential validation records events related to validation tests on credentials for a user account logon. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Account Logon -> "Audit Credential Validation" with "Success" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Account Logon -> Credential Validation - SuccessAudit - Credential Validation - Failure<GroupDescription></GroupDescription>WN08-AU-000001The system must be configured to audit Account Logon - Credential Validation failures.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Credential validation records events related to validation tests on credentials for a user account logon. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Account Logon -> "Audit Credential Validation" with "Failure" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Account Logon -> Credential Validation - FailureAudit - Other Account Management Events - Success<GroupDescription></GroupDescription>WN08-AU-000004The system must be configured to audit Account Management - Other Account Management Events successes.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Other Account Management records events such as the access of a password hash or the Password Policy Checking API being called.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172CCI-002234Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Account Management -> "Audit Other Account Management Events" with "Success" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Account Management -> Other Account Management Events - SuccessAudit - Other Account Management Events - Failure<GroupDescription></GroupDescription>WN08-AU-000003The system must be configured to audit Account Management - Other Account Management Events failures.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Other Account Management records events such as the access of a password hash or the Password Policy Checking API being called.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172CCI-002234Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Account Management -> "Audit Other Account Management Events" with "Failure" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Account Management -> Other Account Management Events - FailureAudit - Security Group Management - Success<GroupDescription></GroupDescription>WN08-AU-000006The system must be configured to audit Account Management - Security Group Management successes.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Security Group Management records events such as creating, deleting or changing of security groups, including changes in group members.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000018CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130CCI-002234Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Account Management -> "Audit Security Group Management" with "Success" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Account Management -> Security Group Management - SuccessAudit - Security Group Management - Failure<GroupDescription></GroupDescription>WN08-AU-000005The system must be configured to audit Account Management - Security Group Management failures.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Security Group Management records events such as creating, deleting or changing of security groups, including changes in group members.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000018CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130CCI-002234Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Account Management -> "Audit Security Group Management" with "Failure" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Account Management -> Security Group Management - FailureAudit - User Account Management - Success<GroupDescription></GroupDescription>WN08-AU-000008The system must be configured to audit Account Management - User Account Management successes.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
User Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000018CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130CCI-002234Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Account Management -> "Audit User Account Management" with "Success" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Account Management -> User Account Management - SuccessAudit - User Account Management - Failure<GroupDescription></GroupDescription>WN08-AU-000007The system must be configured to audit Account Management - User Account Management failures.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
User Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000018CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130CCI-002234Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Account Management -> "Audit User Account Management" with "Failure" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Account Management -> User Account Management - FailureAudit - Process Creation - Success<GroupDescription></GroupDescription>WN08-AU-000009The system must be configured to audit Detailed Tracking - Process Creation successes.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Process creation records events related to the creation of a process and the source.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Detailed Tracking -> "Audit Process Creation" with "Success" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Detailed Tracking -> Process Creation - SuccessAudit - Logoff - Success<GroupDescription></GroupDescription>WN08-AU-000010The system must be configured to audit Logon/Logoff - Logoff successes.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Logoff records user logoffs. If this is an interactive logoff, it is recorded on the local system. If it is to a network share, it is recorded on the system accessed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000067CCI-000172Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Logon/Logoff -> "Audit Logoff" with "Success" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Logon/Logoff -> Logoff - SuccessAudit - Logon - Success<GroupDescription></GroupDescription>WN08-AU-000012The system must be configured to audit Logon/Logoff - Logon successes.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Logon records user logons. If this is an interactive logon, it is recorded on the local system. If it is to a network share, it is recorded on the system accessed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000067CCI-000172Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Logon/Logoff -> "Audit Logon" with "Success" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Logon/Logoff -> Logon - SuccessAudit - Logon - Failure<GroupDescription></GroupDescription>WN08-AU-000011The system must be configured to audit Logon/Logoff - Logon failures.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Logon records user logons. If this is an interactive logon, it is recorded on the local system. If it is to a network share, it is recorded on the system accessed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000067CCI-000172Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Logon/Logoff -> "Audit Logon" with "Failure" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Logon/Logoff -> Logon - FailureAudit - Special Logon - Success<GroupDescription></GroupDescription>WN08-AU-000013The system must be configured to audit Logon/Logoff - Special Logon successes.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Special Logon records special logons which have administrative privileges and can be used to elevate processes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Logon/Logoff -> "Audit Special Logon" with "Success" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Logon/Logoff -> Special Logon - SuccessAudit - Audit Policy Change - Success<GroupDescription></GroupDescription>WN08-AU-000019The system must be configured to audit Policy Change - Audit Policy Change successes.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Audit Policy Change records events related to changes in audit policy.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Policy Change -> "Audit Audit Policy Change" with "Success" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Policy Change -> Audit Policy Change - SuccessAudit - Audit Policy Change - Failure<GroupDescription></GroupDescription>WN08-AU-000018The system must be configured to audit Policy Change - Audit Policy Change failures.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Audit Policy Change records events related to changes in audit policy.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172CCI-002234Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Policy Change -> "Audit Audit Policy Change" with "Failure" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Policy Change -> Audit Policy Change - FailureAudit - Authentication Policy Change - Success<GroupDescription></GroupDescription>WN08-AU-000020The system must be configured to audit Policy Change - Authentication Policy Change successes.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Authentication Policy Change records events related to changes in authentication policy including Kerberos policy and Trust changes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172CCI-002234Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Policy Change -> "Audit Authentication Policy Change" with "Success" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Policy Change -> Authentication Policy Change - SuccessAudit - Sensitive Privilege Use - Success<GroupDescription></GroupDescription>WN08-AU-000022The system must be configured to audit Privilege Use - Sensitive Privilege Use successes.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Sensitive Privilege Use records events related to use of sensitive privileges, such as "Act as part of the operating system" or "Debug programs".</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172CCI-002234Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Privilege Use -> "Audit Sensitive Privilege Use" with "Success" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Privilege Use -> Sensitive Privilege Use - SuccessAudit - Sensitive Privilege Use - Failure<GroupDescription></GroupDescription>WN08-AU-000021The system must be configured to audit Privilege Use - Sensitive Privilege Use failures.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Sensitive Privilege Use records events related to use of sensitive privileges, such as "Act as part of the operating system" or "Debug programs".</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172CCI-002234Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Privilege Use -> "Audit Sensitive Privilege Use" with "Failure" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Privilege Use -> Sensitive Privilege Use - FailureAudit - IPSec Driver - Success<GroupDescription></GroupDescription>WN08-AU-000024The system must be configured to audit System - IPSec Driver successes.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
IPSec Driver records events related to the IPSec Driver such as dropped packets.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> System -> "Audit IPSec Driver" with "Success" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:"
System -> IPSec Driver - SuccessAudit - IPSec Driver - Failure<GroupDescription></GroupDescription>WN08-AU-000023The system must be configured to audit System - IPSec Driver failures.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
IPSec Driver records events related to the IPSec Driver such as dropped packets.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> System -> "Audit IPSec Driver" with "Failure" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
System -> IPSec Driver - FailureAudit - Security State Change - Success<GroupDescription></GroupDescription>WN08-AU-000026The system must be configured to audit System - Security State Change successes.<VulnDiscussion>"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Security State Change records events related to changes in the security state, such as startup and shutdown of the system."</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172CCI-002234Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> System -> "Audit Security State Change" with "Success" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
System -> Security State Change - SuccessAudit - Security State Change - Failure<GroupDescription></GroupDescription>WN08-AU-000025The system must be configured to audit System - Security State Change failures.<VulnDiscussion>"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Security State Change records events related to changes in the security state such as startup and shutdown of the system."</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172CCI-002234Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> System -> "Audit Security State Change" with "Failure" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
System -> Security State Change - FailureAudit - Security System Extension - Success<GroupDescription></GroupDescription>WN08-AU-000028The system must be configured to audit System - Security System Extension successes.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Security System Extension records events related to extension code being loaded by the security subsystem.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172CCI-002234Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> System -> "Audit Security System Extension" with "Success" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
System -> Security System Extension - SuccessAudit - Security System Extension - Failure<GroupDescription></GroupDescription>WN08-AU-000027The system must be configured to audit System - Security System Extension failures.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Security System Extension records events related to extension code being loaded by the security subsystem.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172CCI-002234Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> System -> "Audit Security System Extension" with "Failure" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
System -> Security System Extension - FailureAudit - System Integrity - Success<GroupDescription></GroupDescription>WN08-AU-000030The system must be configured to audit System - System Integrity successes.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
System Integrity records events related to violations of integrity to the security subsystem.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172CCI-002234Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> System -> "Audit System Integrity" with "Success" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
System -> System Integrity - SuccessAudit - System Integrity - Failure<GroupDescription></GroupDescription>WN08-AU-000029The system must be configured to audit System - System Integrity failures.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
System Integrity records events related to violations of integrity to the security subsystem.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172CCI-002234Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> System -> "Audit System Integrity" with "Failure" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*".
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
System -> System Integrity - Failure6to4 State<GroupDescription></GroupDescription>WN08-CC-000007The 6to4 IPv6 transition technology must be disabled.<VulnDiscussion>IPv6 transition technologies, which tunnel packets through other protocols, do not provide visibility.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> TCPIP Settings -> IPv6 Transition Technologies -> "Set 6to4 State" to "Enabled: Disabled State".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\TCPIP\v6Transition\
Value Name: 6to4_State
Type: REG_SZ
Value: DisabledIP-HTTPS State<GroupDescription></GroupDescription>WN08-CC-000008The IP-HTTPS IPv6 transition technology must be disabled.<VulnDiscussion>IPv6 transition technologies, which tunnel packets through other protocols, do not provide visibility.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> TCPIP Settings -> IPv6 Transition Technologies -> "Set IP-HTTPS State" to "Enabled: Disabled State".
Note: "IPHTTPS URL:" must be entered in the policy even if set to Disabled State. Enter "about:blank".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\TCPIP\v6Transition\IPHTTPS\IPHTTPSInterface\
Value Name: IPHTTPS_ClientState
Type: REG_DWORD
Value: 3ISATAP State<GroupDescription></GroupDescription>WN08-CC-000009The ISATAP IPv6 transition technology must be disabled.<VulnDiscussion>IPv6 transition technologies, which tunnel packets through other protocols, do not provide visibility.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> TCPIP Settings -> IPv6 Transition Technologies -> "Set ISATAP State" to "Enabled: Disabled State".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\TCPIP\v6Transition\
Value Name: ISATAP_State
Type: REG_SZ
Value: DisabledTeredo State<GroupDescription></GroupDescription>WN08-CC-000010The Teredo IPv6 transition technology must be disabled.<VulnDiscussion>IPv6 transition technologies, which tunnel packets through other protocols, do not provide visibility.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000382Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> TCPIP Settings -> IPv6 Transition Technologies -> "Set Teredo State" to "Enabled: Disabled State".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\TCPIP\v6Transition\
Value Name: Teredo_State
Type: REG_SZ
Value: DisabledMaximum Log Size - Application<GroupDescription></GroupDescription>WN08-CC-000084The Application event log size must be configured to 32768 KB or greater.<VulnDiscussion>Inadequate log size will cause the log to fill up quickly. This may prevent audit events from being recorded properly and require frequent attention by administrative personnel.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001849Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Event Log Service >> Application >> "Specify the maximum log file size (KB)" to "Enabled" with a "Maximum Log Size (KB)" of "32768" or greater.If the system is configured to send audit records directly to an audit server, this is NA. This must be documented with the ISSO.
If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Application\
Value Name: MaxSize
Type: REG_DWORD
Value: 0x00008000 (32768) (or greater)Maximum Log Size - Security<GroupDescription></GroupDescription>WN08-CC-000085The Security event log size must be configured to 196608 KB or greater.<VulnDiscussion>Inadequate log size will cause the log to fill up quickly. This may prevent audit events from being recorded properly and require frequent attention by administrative personnel.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001849Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Event Log Service >> Security >> "Specify the maximum log file size (KB)" to "Enabled" with a "Maximum Log Size (KB)" of "196608" or greater.If the system is configured to send audit records directly to an audit server, this is NA. This must be documented with the ISSO.
If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Security\
Value Name: MaxSize
Type: REG_DWORD
Value: 0x00030000 (196608) (or greater)Maximum Log Size - Setup<GroupDescription></GroupDescription>WN08-CC-000086The Setup event log size must be configured to 32768 KB or greater.<VulnDiscussion>Inadequate log size will cause the log to fill up quickly. This may prevent audit events from being recorded properly and require frequent attention by administrative personnel.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001849Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Event Log Service >> Setup >> "Specify the maximum log file size (KB)" to "Enabled" with a "Maximum Log Size (KB)" of "32768" or greater.If the system is configured to send audit records directly to an audit server, this is NA. This must be documented with the ISSO.
If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Setup\
Value Name: MaxSize
Type: REG_DWORD
Value: 0x00008000 (32768) (or greater)Maximum Log Size - System<GroupDescription></GroupDescription>WN08-CC-000087The System event log size must be configured to 32768 KB or greater.<VulnDiscussion>Inadequate log size will cause the log to fill up quickly. This may prevent audit events from being recorded properly and require frequent attention by administrative personnel.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001849Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Event Log Service >> System >> "Specify the maximum log file size (KB)" to "Enabled" with a "Maximum Log Size (KB)" of "32768" or greater.If the system is configured to send audit records directly to an audit server, this is NA. This must be documented with the ISSO.
If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\System\
Value Name: MaxSize
Type: REG_DWORD
Value: 0x00008000 (32768) (or greater)Log on as a service<GroupDescription></GroupDescription>WN08-UR-000031Unauthorized users must not have the Log on as a service user right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high level capabilities.
Accounts with the "Log on as a service" user right are able to launch network services or register a process as a service on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000213Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Log on as a service" to be defined but containing no entries (blank).Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> User Rights Assignment.
If any accounts or groups are granted the "Log on as a service" user right, this is a finding.Device Install Software Request Error Report<GroupDescription></GroupDescription>WN08-CC-000023Windows must be prevented from sending an error report when a device driver requests additional software during installation.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.
This setting will prevent Windows from sending an error report to Microsoft when a device driver requests additional software during installation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Device Installation -> "Prevent Windows from sending an error report when a device driver requests additional software during installation" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\DeviceInstall\Settings\
Value Name: DisableSendRequestAdditionalSoftwareToWER
Type: REG_DWORD
Value: 1WINPK-000001<GroupDescription></GroupDescription>WN08-PK-000001The DoD Root CA certificates must be installed in the Trusted Root Store.<VulnDiscussion>To ensure secure DoD websites and DoD-signed code are properly validated, the system must trust the DoD Root Certificate Authorities (CAs). The DoD root certificates will ensure that the trust chain is established for server certificates issued from the DoD CAs.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000185CCI-002470Install the DoD Root CA certificates.
DoD Root CA 2
DoD Root CA 3
DoD Root CA 4
The InstallRoot tool is available on IASE at http://iase.disa.mil/pki-pke/Pages/tools.aspx.Verify the DoD Root CA certificates are installed as Trusted Root Certification Authorities.
Run "PowerShell" as an administrator.
Execute the following command:
Get-ChildItem -Path Cert:Localmachine\root | Where Subject -Like "*DoD*" | FL Subject, Thumbprint
If the following information is not displayed, this is finding.
Subject: CN=DoD Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US
Thumbprint: 8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561
Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US
Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB
Subject: CN=DoD Root CA 4, OU=PKI, OU=DoD, O=U.S. Government, C=US
Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026
Alternately use the Certificates MMC snap-in:
Run "MMC".
Select "File", "Add/Remove Snap-in".
Select "Certificates", click "Add".
Select "Computer account", click "Next".
Select "Local computer: (the computer this console is running on)", click "Finish".
Click "OK".
Expand "Certificates" and navigate to "Trusted Root Certification Authorities >> Certificates".
If there are no entries for "DoD Root CA 2", "DoD Root CA 3", and "DoD Root CA 4", this is a finding.
For each of the DoD Root CA certificates noted above:
Right click on the certificate and select "Open".
Select the "Details" Tab.
Scroll to the bottom and select "Thumbprint".
If the value for the "Thumbprint" field is not as noted below, this is a finding.
DoD Root CA 2 - 8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561
DoD Root CA 3 - D73CA91102A2204A36459ED32213B467D7CE97FB
DoD Root CA 4 - B8269F25DBD937ECAFD4C35A9838571723F2D026
The thumbprints referenced apply to unclassified systems; see PKE documentation for other networks.WINPK-000002<GroupDescription></GroupDescription>WN08-PK-000002The External Root CA certificates must be installed in the Trusted Root Store on unclassified systems.<VulnDiscussion>To ensure secure websites protected with External Certificate Authority (ECA) server certificates are properly validated, the system must trust the ECA Root CAs. The ECA root certificates will ensure the trust chain is established for server certificates issued from the External CAs. This requirement only applies to unclassified systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000185Install the ECA Root CA certificates on unclassified systems.
ECA Root CA 2
ECA Root CA 4
The InstallRoot tool is available on IASE at http://iase.disa.mil/pki-pke/Pages/tools.aspx.Verify the ECA Root CA certificates are installed on unclassified systems as Trusted Root Certification Authorities.
Run "PowerShell" as an administrator.
Execute the following command:
Get-ChildItem -Path Cert:Localmachine\root | Where Subject -Like "*ECA*" | FL Subject, Thumbprint
If the following information is not displayed, this is finding.
Subject: CN=ECA Root CA 2, OU=ECA, O=U.S. Government, C=US
Thumbprint: C313F919A6ED4E0E8451AFA930FB419A20F181E4
Subject: CN=ECA Root CA 4, OU=ECA, O=U.S. Government, C=US
Thumbprint: 73E8BB08E337D6A5A6AEF90CFFDD97D9176CB582
Alternately use the Certificates MMC snap-in:
Run "MMC".
Select "File", "Add/Remove Snap-in".
Select "Certificates", click "Add".
Select "Computer account", click "Next".
Select "Local computer: (the computer this console is running on)", click "Finish".
Click "OK".
Expand "Certificates" and navigate to "Trusted Root Certification Authorities >> Certificates".
If there are no entries for "ECA Root CA 2", and "ECA Root CA 4", this is a finding.
For each of the ECA Root CA certificates noted above:
Right click on the certificate and select "Open".
Select the "Details" Tab.
Scroll to the bottom and select "Thumbprint".
If the value for the "Thumbprint" field is not as noted below, this is a finding.
ECA Root CA 2 - C313F919A6ED4E0E8451AFA930FB419A20F181E4
ECA Root CA 4 - 73E8BB08E337D6A5A6AEF90CFFDD97D9176CB582WINPK-000003<GroupDescription></GroupDescription>WN08-PK-000003The DoD Interoperability Root CA cross-certificates must be installed in the Untrusted Certificates Store on unclassified systems.<VulnDiscussion>To ensure users do not experience denial of service when performing certificate-based authentication to DoD websites due to the system chaining to a root other than DoD Root CAs, the DoD Interoperability Root CA cross-certificates must be installed in the Untrusted Certificate Store. This requirement only applies to unclassified systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000185CCI-002470Install the DoD Interoperability Root CA cross-certificates on unclassified systems.
Issued To - Issued By - Thumbprint
DoD Root CA 2 - DoD Interoperability Root CA 1 - 22BBE981F0694D246CC1472ED2B021DC8540A22F
DoD Root CA 3 - DoD Interoperability Root CA 2 - FFAD03329B9E527A43EEC66A56F9CBB5393E6E13
DoD Root CA 3 - DoD Interoperability Root CA 2 - FCE1B1E25374DD94F5935BEB86CA643D8C8D1FF4
Administrators should run the Federal Bridge Certification Authority (FBCA) Cross-Certificate Removal Tool once as an administrator and once as the current user.
The FBCA Cross-Certificate Remover tool and user guide is available on IASE at http://iase.disa.mil/pki-pke/Pages/tools.aspx.Verify the DoD Interoperability cross-certificates are installed on unclassified systems as Untrusted Certificates.
Run "PowerShell" as an administrator.
Execute the following command:
Get-ChildItem -Path Cert:Localmachine\disallowed | Where {$_.Issuer -Like "*DoD Interoperability*" -and $_.Subject -Like "*DoD*"} | FL Subject, Issuer, Thumbprint
If the following information is not displayed, this is finding.
Subject: CN=DoD Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US
Issuer: CN=DoD Interoperability Root CA 1, OU=PKI, OU=DoD, O=U.S. Government, C=US
Thumbprint: 22BBE981F0694D246CC1472ED2B021DC8540A22F
Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US
Issuer: CN=DoD Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US
Thumbprint: FFAD03329B9E527A43EEC66A56F9CBB5393E6E13
Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US
Issuer: CN=DoD Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US
Thumbprint: FCE1B1E25374DD94F5935BEB86CA643D8C8D1FF4
Alternately use the Certificates MMC snap-in:
Run "MMC".
Select "File", "Add/Remove Snap-in".
Select "Certificates", click "Add".
Select "Computer account", click "Next".
Select "Local computer: (the computer this console is running on)", click "Finish".
Click "OK".
Expand "Certificates" and navigate to "Untrusted Certificates >> Certificates".
For each certificate with "DoD Root CA…" under "Issued To" and "DoD Interoperability Root CA…" under "Issued By":
Right click on the certificate and select "Open".
Select the "Details" Tab.
Scroll to the bottom and select "Thumbprint".
If the certificates below are not listed or the value for the "Thumbprint" field is not as noted, this is a finding.
Issued To - Issued By - Thumbprint
DoD Root CA 2 - DoD Interoperability Root CA 1 - 22BBE981F0694D246CC1472ED2B021DC8540A22F
DoD Root CA 3 - DoD Interoperability Root CA 2 - FFAD03329B9E527A43EEC66A56F9CBB5393E6E13
DoD Root CA 3 - DoD Interoperability Root CA 2 - FCE1B1E25374DD94F5935BEB86CA643D8C8D1FF4WINRG-000001 Active Setup\Installed Components Registry Permissions<GroupDescription></GroupDescription>WN08-RG-000002Standard user accounts must only have Read permissions to the Active Setup\Installed Components registry key.<VulnDiscussion>Permissions on the Active Setup\Installed Components registry key must only allow privileged accounts to add or change registry values. If standard user accounts have this capability, there is a potential for programs to run with elevated privileges when a privileged user logs on to the system. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002235Maintain the default permissions of the following registry keys as noted below:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Active Setup\Installed Components\ (64-bit systems only)
Users - Read
Administrators - Full Control
SYSTEM - Full Control
CREATOR OWNER - Full Control (Subkeys only)
ALL APPLICATION PACKAGES - ReadRun "Regedit".
Navigate to the following registry keys and review the permissions:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Active Setup\Installed Components\ (64-bit systems)
If the default permissions listed below have been changed, this is a finding.
Users - Read
Administrators - Full Control
SYSTEM - Full Control
CREATOR OWNER - Full Control (Subkeys only)
ALL APPLICATION PACKAGES - ReadAlways Install with Elevated Privileges Disabled<GroupDescription></GroupDescription>WN08-CC-000116The Windows Installer Always install with elevated privileges must be disabled.<VulnDiscussion>Standard user accounts must not be granted elevated privileges. Enabling Windows Installer to elevate privileges when installing applications can allow malicious persons and applications to gain full control of a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001812Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Installer -> "Always install with elevated privileges" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\Installer\
Value Name: AlwaysInstallElevated
Type: REG_DWORD
Value: 0Inbound Firewall Exception for Administration<GroupDescription></GroupDescription>WN08-FW-000100Inbound exceptions to the firewall on domain workstations must only allow authorized remote management hosts.<VulnDiscussion>Allowing inbound access to domain workstations from other systems may allow lateral movement across systems if credentials are compromised. Limiting inbound connections only from authorized remote management systems will help limit this exposure.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure firewall exceptions to inbound connections on domain workstations to include only authorized remote management hosts.
Configure only inbound connection exceptions for authorized remote management hosts.
Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Inbound Rules (this link will be in the right pane) ->
For any inbound rules that allow connections, configure the Scope for Remote IP address to those of authorized remote management hosts. This may be defined as an IP address, subnet or range. Apply the rule to all firewall profiles.
If a third-party firewall is used, configure inbound exceptions to only include authorized remote management hosts.Verify firewall exceptions to inbound connections on domain workstations include only authorized remote management hosts.
If allowed inbound exceptions are not limited to authorized remote management hosts, this is a finding.
Review inbound firewall exceptions.
Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Inbound Rules (this link will be in the right pane) ->
For any inbound rules that allow connections view the Scope for Remote IP address. This may be defined as an IP address, subnet, or range. The rule must apply to all firewall profiles.
If a third-party firewall is used, ensure comparable settings are in place.WINUC-000001<GroupDescription></GroupDescription>WN08-UC-000001A screen saver must be enabled on the system.<VulnDiscussion>Unattended systems are susceptible to unauthorized use and must be locked when unattended. Enabling a password-protected screen saver to engage after a specified period of time helps protects critical and sensitive data from exposure to unauthorized personnel with physical access to the computer.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000060Configure the policy value for User Configuration >> Administrative Templates >> Control Panel >> Personalization >> "Enable Screen Saver" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_CURRENT_USER
Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Control Panel\Desktop\
Value Name: ScreenSaveActive
Type: REG_SZ
Value: 1
Applications requiring continuous, real-time screen display (e.g., network management products) require the following and must be documented with the ISSO.
-The logon session does not have administrator rights.
-The display station (e.g., keyboard, monitor, etc.) is located in a controlled access area.WINUC-000003<GroupDescription></GroupDescription>WN08-UC-000003The screen saver must be password protected.<VulnDiscussion>Unattended systems are susceptible to unauthorized use and must be locked when unattended. Enabling a password protected screen saver to engage after a specified period of time helps protects critical and sensitive data from exposure to unauthorized personnel with physical access to the computer.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>PESL-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000056Configure the policy value for User Configuration -> Administrative Templates -> Control Panel -> Personalization -> "Password protect the screen saver" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_CURRENT_USER
Subkey: \Software\Policies\Microsoft\Windows\Control Panel\Desktop\
Value Name: ScreenSaverIsSecure
Type: REG_SZ
Value: 1WIN00-000005-01<GroupDescription></GroupDescription>WN08-00-000005-01Users with Administrative privilege must be documented.<VulnDiscussion>Administrative accounts may perform any action on a system. Users with administrative accounts must be documented to ensure those with this level of access are clearly identified.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Create the necessary documentation that identifies the members of the Administrators group.Review the necessary documentation that identifies the members of the Administrators group. If a list of all users belonging to the Administrators group is not maintained with the ISSO, this is a finding.WIN00-000005-02<GroupDescription></GroupDescription>WN08-00-000005-02Users with Administrative privilege must have separate accounts for administrative duties and normal operational tasks.<VulnDiscussion>Using a privileged account to perform routine functions makes the computer vulnerable to malicious software inadvertently introduced during a session that has been granted full privileges.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Ensure each user with administrative privilege has a separate account for user duties and one for privileged duties.Verify each user with administrative privileges has been assigned a unique administrative account separate from their standard user account.
The ISSO will maintain a list of all users belonging to the Administrators group.
If any of the following conditions are true, this is a finding:
-Each SA does not have a unique userid dedicated for administering the system.
-Each SA does not have a separate account for normal user tasks.WN08-00-000005-03<GroupDescription></GroupDescription>WN08-00-000005-03Policy must require that administrative user accounts not be used with applications that access the internet, such as web browsers, or with potential internet sources, such as email.<VulnDiscussion>Using applications that access the internet, or have potential internet sources using administrative privileges, exposes a system to compromise. If a flaw in an application is exploited while running as a privileged user, the entire system could be compromised. Web browsers and email are common attack vectors for introducing malicious code and must not be run with an administrative user account.
Since administrative user accounts may generally change or work around technical restrictions for running a web browser or other applications, it is essential that policy requires administrative users not access the internet or use applications, such as email.
The policy should define specific exceptions for local service administration. These exceptions may include HTTP(S)-based tools that are used for the administration of the local system, services, or attached devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Establish a site policy to prohibit the use applications that access the internet, such as web browsers, or with potential internet sources, such as email, by administrative user accounts. Ensure the policy is enforced.Determine if site policy prohibits the use of applications that access the internet, such as web browsers, or with potential internet sources, such as email, by administrative user accounts, except as necessary for local service administration. If it does not, this is a finding.WIN00-000010-01<GroupDescription></GroupDescription>WN08-00-000010-01Application account passwords must be at least 15 characters in length.<VulnDiscussion>Application/service account passwords must be of sufficient length to prevent being easily cracked. Application/service accounts that are manually managed must have passwords at least 15 characters in length.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>IAIA-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000205Establish a site policy that defines the requirements for application/service account length. Create application/service account passwords that are at least 15 characters in length.The site must have a policy to ensure passwords for manually managed application/service accounts are at least 15 characters in length. If such a policy does not exist or has not been implemented, this is a finding.WIN00-000010-02<GroupDescription></GroupDescription>WN08-00-000010-02Application account passwords must be changed at least annually or when a system administrator with knowledge of the password leaves the organization.<VulnDiscussion>Setting application accounts to expire may cause applications to stop functioning. The site will have a policy that application account passwords are changed at least annually or when a system administrator with knowledge of the password leaves the organization.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>IAIA-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Establish a site policy that defines the requirements for application/service account password changes.
Change application/service account passwords that are manually managed and entered by a system administrator at least annually or whenever an administrator with knowledge of the password leaves the organization.The site must have a policy to ensure passwords for manually managed application/service accounts are changed at least annually or whenever a system administrator that has knowledge of the password leaves the organization. If such a policy does not exist or has not been implemented, this is a finding.
Run the DUMPSEC utility.
Select "Dump Users as Table" from the "Report" menu.
Select the following fields, and click "Add" for each entry.
UserName
SID
PwsdLastSetTime
AcctDisabled
If any application accounts listed have a date older than one year in the "PwsdLastSetTime" column, this is a finding.WN08-00-000013<GroupDescription></GroupDescription>WN08-00-000013Mobile systems must encrypt all data per the DoD Data at Rest policy.<VulnDiscussion>If data at rest is unencrypted, it is vulnerable to disclosure. Even if the operating system enforces permissions on data access, an adversary can remove non-volatile memory and read it directly, thereby circumventing operating system controls. Encrypting the data ensures that confidentiality is protected even when the operating system is not running.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECCR-1, ECCR-2</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001199CCI-002475CCI-002476Install an approved DoD encryption package and enable full disk encryption.Verify the system employs DoD-approved full disk encryption. If full disk encryption is not implemented, this is a finding.WIN00-000014<GroupDescription></GroupDescription>WN08-00-000014Policy must require that system administrators (SAs) be trained for the operating systems used by systems under their control.<VulnDiscussion>If system administrators (SAs) are assigned to systems running operating systems for which they have no training, these systems are at additional risk of unintentional misconfiguration that may result in vulnerabilities or decreased availability of the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Establish site policy that requires SAs be trained for all operating systems running on systems under their control.Review the list of SAs assigned to each system and compare this information to SA training records. If SAs are assigned to systems running operating systems for which there is no record of training, this is a finding.WINAU-000016<GroupDescription></GroupDescription>WN08-AU-000016The system must be configured to audit Object Access - Removable Storage failures.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Auditing object access for removable media records events related to access attempts on file system objects on removable storage devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Object Access -> "Audit Removable Storage" with "Failure" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*"
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Object Access -> Removable Storage - FailureWINAU-000017<GroupDescription></GroupDescription>WN08-AU-000017The system must be configured to audit Object Access - Removable Storage successes.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Auditing object access for removable media records events related to access attempts on file system objects on removable storage devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECAR-2, ECAR-3</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000172Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Object Access -> "Audit Removable Storage" with ""Success" selected.Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective.
Use the AuditPol tool to review the current Audit Policy configuration:
-Open a Command Prompt with elevated privileges ("Run as Administrator").
-Enter "AuditPol /get /category:*"
Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding:
Object Access -> Removable Storage - SuccessWINCC-000011<GroupDescription></GroupDescription>WN08-CC-000011IP stateless autoconfiguration limits state must be enabled.<VulnDiscussion>IP stateless autoconfiguration could configure routes that circumvent preferred routes if not limited.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> TCPIP Settings -> Parameters -> "Set IP Stateless Autoconfiguration Limits State" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \System\CurrentControlSet\Services\Tcpip\Parameters\
Value Name: EnableIPAutoConfigurationLimits
Type: REG_DWORD
Value: 1WN08-CC-000014<GroupDescription></GroupDescription>WN08-CC-000014Simultaneous connections to the Internet or a Windows domain must be limited.<VulnDiscussion>Multiple network connections can provide additional attack vectors to a system and must be limited.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> Windows Connection Manager -> "Minimize the number of simultaneous connections to the Internet or a Windows Domain" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\WcmSvc\GroupPolicy\
Value Name: fMinimizeConnections
Type: REG_DWORD
Value: 1WN08-CC-000015<GroupDescription></GroupDescription>WN08-CC-000015Connections to non-domain networks when connected to a domain authenticated network must be blocked.<VulnDiscussion>Multiple network connections can provide additional attack vectors to a system and should be limited. When connected to a domain, communication must go through the domain connection.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> Windows Connection Manager -> "Prohibit connection to non-domain networks when connected to domain authenticated network" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\WcmSvc\GroupPolicy\
Value Name: fBlockNonDomain
Type: REG_DWORD
Value: 1WN08-CC-000017<GroupDescription></GroupDescription>WN08-CC-000017Users must only be allowed to point and print to machines in their forest.<VulnDiscussion>Uncontrolled system updates can introduce issues to a system. Obtaining update components from an outside source may also potentially provide sensitive information outside of the enterprise. Configuring this setting will restrict, but allow users to obtain print drivers for printers in their forest.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> Printers -> "Point and Print Restrictions" to "Enabled" with "Users can only point and print to machines in their forest" selected and the following Security Prompts:
When installing Drivers for a new connection:
Do not show warning or elevation prompt.
When updating drivers for an existing connection:
Do not show warning or elevation prompt.
If the following registry values do not exist or are not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows NT\Printers\PointAndPrint \
Value Name: InForest
Type: REG_DWORD
Value: 1
Value Name: NoWarningNoElevationOnInstall
Type: REG_DWORD
Value: 1
Value Name: UpdatePromptSettings
Type: REG_DWORD
Value: 2WINCC-000018<GroupDescription></GroupDescription>WN08-CC-000018Optional component installation and component repair must be prevented from using Windows Update.<VulnDiscussion>Uncontrolled system updates can introduce issues to a system. Obtaining update components from an outside source may also potentially provide sensitive information outside of the enterprise. Optional component installation or repair must be obtained from an internal source.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001812Configure the policy value for Computer Configuration -> Administrative Templates -> System -> "Specify settings for optional component installation and component repair" to "Enabled" and with "Never attempt to download payload from Windows Update" selected.If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Microsoft\Windows\CurrentVersion\Policies\Servicing \
Value Name: UseWindowsUpdate
Type: REG_DWORD
Value: 2WINCC-000025<GroupDescription></GroupDescription>WN08-CC-000025Device driver updates must only search managed servers, not Windows Update.<VulnDiscussion>Uncontrolled system updates can introduce issues to a system. Obtaining update components from an outside source may also potentially provide sensitive information outside of the enterprise. Device driver updates must be obtained from an internal source.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001812Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Device Installation -> "Specify the search server for device driver updates" to "Enabled" with "Search Managed Server" selected.If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\DriverSearching\
Value Name: DriverServerSelection
Type: REG_DWORD
Value: 1WINCC-000027<GroupDescription></GroupDescription>WN08-CC-000027Early Launch Antimalware, Boot-Start Driver Initialization Policy must be enabled and configured to only Good and Unknown.<VulnDiscussion>Compromised boot drivers can introduce malware prior to some protection mechanisms that load after initialization. The Early Launch Antimalware driver can limit allowed drivers based on classifications determined by the malware protection application. At a minimum, drivers determined to be bad must not be allowed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECVP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Early Launch Antimalware -> "Boot-Start Driver Initialization Policy" to "Enabled" with "Good and Unknown" selected.If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \System\CurrentControlSet\Policies\EarlyLaunch\
Value Name: DriverLoadPolicy
Type: REG_DWORD
Value: 1WINCC-000030<GroupDescription></GroupDescription>WN08-CC-000030Access to the Windows Store must be turned off.<VulnDiscussion>Uncontrolled installation of applications can introduce various issues, including system instability and allow access to sensitive information. Installation of applications must be controlled by the enterprise. Turning off access to the Windows Store will limit access to publicly available applications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication settings -> "Turn off access to the Store" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\Explorer\
Value Name: NoUseStoreOpenWith
Type: REG_DWORD
Value: 1WINCC-000048<GroupDescription></GroupDescription>WN08-CC-000048Copying of user input methods to the system account for sign-in must be prevented.<VulnDiscussion>Allowing different input methods for sign-in could open different avenues of attack. User input methods must be restricted to those enabled for the system account at sign-in.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Locale Services -> "Disallow copying of user input methods to the system account for sign-in" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Control Panel\International\
Value Name: BlockUserInputMethodsForSignIn
Type: REG_DWORD
Value: 1WN08-CC-000050<GroupDescription></GroupDescription>WN08-CC-000050Connected users on domain-joined computers must not be enumerated.<VulnDiscussion>The username is one part of logon credentials that could be used to gain access to a system. Preventing the enumeration of users limits this information to unauthorized personnel.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Logon -> "Do not enumerate connected users on domain-joined computers" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\System\
Value Name: DontEnumerateConnectedUsers
Type: REG_DWORD
Value: 1WINCC-000051<GroupDescription></GroupDescription>WN08-CC-000051Local users on domain-joined computers must not be enumerated.<VulnDiscussion>The username is one part of logon credentials that could be used to gain access to a system. Preventing the enumeration of users limits this information to authorized personnel.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Logon -> "Enumerate local users on domain-joined computers" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\System\
Value Name: EnumerateLocalUsers
Type: REG_DWORD
Value: 0WINCC-000052<GroupDescription></GroupDescription>WN08-CC-000052App notifications on the lock screen must be turned off.<VulnDiscussion>App notifications that are displayed on the lock screen could display sensitive information to unauthorized personnel. Turning off this feature will limit access to the information to a logged on user.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Logon -> "Turn off app notifications on the lock screen" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\System\
Value Name: DisableLockScreenAppNotifications
Type: REG_DWORD
Value: 1WN08-CC-000053<GroupDescription></GroupDescription>WN08-CC-000053Signing in using a PIN must be turned off.<VulnDiscussion>Strong sign-on must be used to protect a system. The PIN feature is limited to 4 numbers and caches the domain password in the system vault.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>IAIA-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Logon -> "Turn on PIN sign-in" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\System\
Value Name: AllowDomainPINLogon
Type: REG_DWORD
Value: 0WN08-CC-000060<GroupDescription></GroupDescription>WN08-CC-000060Remote assistance must display a warning message when allowing helpdesk personnel to control a system.<VulnDiscussion>Requiring warning text to display when allowing helpdesk personnel to control remote assistance sessions ensures personnel of the activity and enforces the need to monitor the activity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECWM-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Remote Assistance -> "Customize warning messages" to "Enabled" with "You are about to allow other personnel to remotely control your system. You must monitor the activity until the session is closed." entered in the "Display warning message before sharing control:" field.If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\
Value Name: ShareControlMessage
Type: REG_SZ
Value: You are about to allow other personnel to remotely control your system. You must monitor the activity until the session is closed.WN08-CC-000061<GroupDescription></GroupDescription>WN08-CC-000061Remote assistance must display a warning message when allowing helpdesk personnel to connect to a system.<VulnDiscussion>Requiring warning text to display when allowing helpdesk personnel to connect to a system with remote assistance ensures personnel are aware of the activity and enforces the need to monitor the activity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECWM-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Remote Assistance -> "Customize warning messages" to "Enabled" with "You are about to allow other personnel to remotely connect to your system. Sensitive data should not be displayed during this session." entered in the "Display warning message before connecting:" field.If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\
Value Name: ViewMessage
Type: REG_SZ
Value: You are about to allow other personnel to remotely connect to your system. Sensitive data should not be displayed during this session.
WINCC-000065<GroupDescription></GroupDescription>WN08-CC-000065The detection of compatibility issues for applications and drivers must be turned off.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Troubleshooting and Diagnostics -> Application Compatibility Diagnostics -> "Detect compatibility issues for applications and drivers" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\AppCompat\
Value Name: DisablePcaUI
Type: REG_DWORD
Value: 0WINCC-000070<GroupDescription></GroupDescription>WN08-CC-000070Trusted app installation must be enabled to allow for signed enterprise line of business apps.<VulnDiscussion>Enabling trusted app installation allows for enterprise line of business Windows 8 type apps. A trusted app package is one that is signed with a certificate chain that can be successfully validated in the enterprise. Configuring this ensures enterprise line of business apps are accessible.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> App Package Deployment -> " Allow all trusted apps to install " to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\Appx\
Value Name: AllowAllTrustedApps
Type: REG_DWORD
Value: 1WINCC-000075<GroupDescription></GroupDescription>WN08-CC-000075The use of biometrics must be disabled.<VulnDiscussion>Allowing biometrics may bypass required authentication methods. Biometrics may only be used as an additional authentication factor where an enhanced strength of identity credential is necessary or desirable. Additional factors must be met per DoD policy.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>IAIA-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Biometrics -> "Allow the use of biometrics" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \SOFTWARE\Policies\Microsoft\Biometrics\
Value Name: Enabled
Type: REG_DWORD
Value: 0WINCC-000076<GroupDescription></GroupDescription>WN08-CC-000076The password reveal button must not be displayed.<VulnDiscussion>Visible passwords may be seen by nearby persons, compromising them. The password reveal button can be used to display an entered password and must not be allowed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>IAIA-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000206Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Credential User Interface -> "Do not display the password reveal button" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\CredUI\
Value Name: DisablePasswordReveal
Type: REG_DWORD
Value: 1WINCC-000078<GroupDescription></GroupDescription>WN08-CC-000078The Enhanced Mitigation Experience Toolkit (EMET) system-wide Address Space Layout Randomization (ASLR) must be enabled and configured to Application Opt In.<VulnDiscussion>Attackers are constantly looking for vulnerabilities in systems and applications. The Enhanced Mitigation Experience Toolkit can enable several mechanisms, such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), and Structured Exception Handler Overwrite Protection (SEHOP) on the system and applications adding additional levels of protection.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002824This is applicable to unclassified systems, for other systems this is NA.
Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> EMET -> "System ASLR" to "Enabled" with "Application Opt In" selected.
The Enhanced Mitigation Experience Toolkit must be installed on the system and the administrative template files added to make this setting available.This is applicable to unclassified systems, for other systems this is NA.
If EMET has not been installed and DEP and SEHOP are configured as required in V-68843 and V-68847, this is NA.
If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\EMET\SysSettings\
Value Name: ASLR
Type: REG_DWORD
Value: 3WINCC-000079<GroupDescription></GroupDescription>WN08-CC-000079The Enhanced Mitigation Experience Toolkit (EMET) Default Protections for Internet Explorer must be enabled.<VulnDiscussion>Attackers are constantly looking for vulnerabilities in systems and applications. The Enhanced Mitigation Experience Toolkit can enable several mechanisms, such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), and Structured Exception Handler Overwrite Protection (SEHOP) on the system and applications adding additional levels of protection.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002824Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> EMET >> "Default Protections for Internet Explorer" to "Enabled".
Note: The Enhanced Mitigation Experience Toolkit must be installed on the system and the administrative template files added to make this setting available.
Due to a change in the registry structure for EMET 5.5, if the system has a previous version of EMET installed and configured, this setting needs to be set to "Not Configured" prior to the upgrade to EMET 5.5, and the new administrative template files copied to the appropriate area. The setting can then be re-enabled.This is applicable to unclassified systems, for other systems this is NA.
If EMET has not been installed and DEP and SEHOP are configured as required in V-68843 and V-68847, this is NA.
If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\EMET\Defaults\
Value Name: *\Internet Explorer\iexplore.exe
Value Type: REG_SZ
Value: +EAF+ eaf_modules:mshtml.dll;flash*.ocx;jscript*.dll;vbscript.dll;vgx.dll +ASR asr_modules:npjpi*.dll;jp2iexp.dll;vgx.dll;msxml4*.dll;wshom.ocx;scrrun.dll;vbscript.dll asr_zones:1;2
Due to a change in the registry structure for EMET 5.5, if the system has a previous version of EMET installed and configured, this setting needs to be set to "Not Configured" prior to the upgrade to EMET 5.5, and the new administrative template files copied to the appropriate area. The setting can then be re-enabled.WINCC-000080<GroupDescription></GroupDescription>WN08-CC-000080The Enhanced Mitigation Experience Toolkit (EMET) Default Protections for Recommended Software must be enabled.<VulnDiscussion>Attackers are constantly looking for vulnerabilities in systems and applications. The Enhanced Mitigation Experience Toolkit can enable several mechanisms, such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), and Structured Exception Handler Overwrite Protection (SEHOP) on the system and applications adding additional levels of protection.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002824Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> EMET >> "Default Protections for Recommended Software" to "Enabled".
Note: The Enhanced Mitigation Experience Toolkit must be installed on the system and the administrative template files added to make this setting available.
Due to a change in the registry structure for EMET 5.5, if the system has a previous version of EMET installed and configured, this setting needs to be set to "Not Configured" prior to the upgrade to EMET 5.5, and the new administrative template files copied to the appropriate area. The setting can then be re-enabled.This is applicable to unclassified systems, for other systems this is NA.
If EMET has not been installed and DEP and SEHOP are configured as required in V-68843 and V-68847, this is NA.
If the following registry values do not exist or are not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\EMET\Defaults\
Value Type: REG_SZ (for each Value below)
Values noted as "Blank" are empty in the registry.
Value Name: *\Adobe\*\Reader\AcroRd32.exe
Value: +EAF+ eaf_modules:AcroRd32.dll;Acrofx32.dll;AcroForm.api
Value Name: *\Adobe\Acrobat*\Acrobat\Acrobat.exe
Value: +EAF+ eaf_modules:AcroRd32.dll;Acrofx32.dll;AcroForm.api
Value Name: *\Java\jre*\bin\java.exe
Value: -HeapSpray
Value Name: *\Java\jre*\bin\javaw.exe
Value: -HeapSpray
Value Name: *\Java\jre*\bin\javaws.exe
Value: -HeapSpray
Value Name: *\OFFICE1*\EXCEL.EXE
Value: +ASR asr_modules:flash*.ocx
Value Name: *\OFFICE1*\INFOPATH.EXE
Value: "Blank"
Value Name: *\OFFICE1*\LYNC.EXE
Value: "Blank"
Value Name: *\OFFICE1*\MSACCESS.EXE
Value: "Blank"
Value Name: *\OFFICE1*\MSPUB.EXE
Value: "Blank"
Value Name: *\OFFICE1*\OIS.EXE
Value: "Blank"
Value Name: *\OFFICE1*\OUTLOOK.EXE
Value: "Blank"
Value Name: *\OFFICE1*\POWERPNT.EXE
Value: +ASR asr_modules:flash*.ocx
Value Name: *\OFFICE1*\PPTVIEW.EXE
Value: "Blank"
Value Name: *\OFFICE1*\VISIO.EXE
Value: "Blank"
Value Name: *\OFFICE1*\VPREVIEW.EXE
Value: "Blank"
Value Name: *\OFFICE1*\WINWORD.EXE
Value: +ASR asr_modules:flash*.ocx
Value Name: *\Windows NT\Accessories\wordpad.exe
Value: "Blank"
Due to a change in the registry structure for EMET 5.5, if the system has a previous version of EMET installed and configured, this setting needs to be set to "Not Configured" prior to the upgrade to EMET 5.5, and the new administrative template files copied to the appropriate area. The setting can then be re-enabled.WINCC-000081<GroupDescription></GroupDescription>WN08-CC-000081The Enhanced Mitigation Experience Toolkit (EMET) Default Protections for Popular Software must be enabled.<VulnDiscussion>Attackers are constantly looking for vulnerabilities in systems and applications. The Enhanced Mitigation Experience Toolkit can enable several mechanisms, such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), and Structured Exception Handler Overwrite Protection (SEHOP) on the system and applications adding additional levels of protection.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002824Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> EMET >> "Default Protections for Popular Software" to "Enabled".
Note: The Enhanced Mitigation Experience Toolkit must be installed on the system and the administrative template files added to make this setting available.
Due to a change in the registry structure for EMET 5.5, if the system has a previous version of EMET installed and configured, this setting needs to be set to "Not Configured" prior to the upgrade to EMET 5.5, and the new administrative template files copied to the appropriate area. The setting can then be re-enabled.This is applicable to unclassified systems, for other systems this is NA.
If EMET has not been installed and DEP and SEHOP are configured as required in V-68843 and V-68847, this is NA.
If the following registry values do not exist or are not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\EMET\Defaults\
Value Type: REG_SZ (for each Value below)
Values noted as "Blank" are empty in the registry.
Value Name: *\7-Zip\7z.exe
Value: -EAF
Value Name: *\7-Zip\7zG.exe
Value: -EAF
Value Name: *\7-Zip\7zFM.exe
Value: -EAF
Value Name: *\Adobe\Adobe Photoshop CS*\Photoshop.exe
Value: "Blank"
Value Name: *\Foxit Reader\Foxit Reader.exe
Value: "Blank"
Value Name: *\Google\Chrome\Application\chrome.exe
Value: +EAF+ eaf_modules:chrome_child.dll
Value Name: *\Google\Google Talk\googletalk.exe
Value: -DEP
Value Name: *\iTunes\iTunes.exe
Value: "Blank"
Value Name: *\Microsoft Lync\communicator.exe
Value: "Blank"
Value Name: *\mIRC\mirc.exe
Value: "Blank"
Value Name: *\Mozilla Firefox\firefox.exe
Value: +EAF+ eaf_modules:mozjs.dll;xul.dll
Value Name: *\Mozilla Firefox\plugin-container.exe
Value: "Blank"
Value Name: *\Mozilla Thunderbird\plugin-container.exe
Value: "Blank"
Value Name: *\Mozilla Thunderbird\thunderbird.exe
Value: "Blank"
Value Name: *\Opera\*\opera.exe
Value: "Blank"
Value Name: *\Opera\opera.exe
Value: "Blank"
Value Name: *\Pidgin\pidgin.exe
Value: "Blank"
Value Name: *\QuickTime\QuickTimePlayer.exe
Value: "Blank"
Value Name: *\Real\RealPlayer\realconverter.exe
Value: "Blank"
Value Name: *\Real\RealPlayer\realplay.exe
Value: "Blank"
Value Name: *\Safari\Safari.exe
Value: "Blank"
Value Name: *\SkyDrive\SkyDrive.exe
Value: "Blank"
Value Name: *\Skype\Phone\Skype.exe
Value: -EAF
Value Name: *\VideoLAN\VLC\vlc.exe
Value: "Blank"
Value Name: *\Winamp\winamp.exe
Value: "Blank"
Value Name: *\Windows Live\Mail\wlmail.exe
Value: "Blank"
Value Name: *\Windows Live\Photo Gallery\WLXPhotoGallery.exe
Value: "Blank"
Value Name: *\Windows Live\Writer\WindowsLiveWriter.exe
Value: "Blank"
Value Name: *\Windows Media Player\wmplayer.exe
Value: -EAF -MandatoryASLR
Value Name: *\WinRAR\rar.exe
Value: "Blank"
Value Name: *\WinRAR\unrar.exe
Value: "Blank"
Value Name: *\WinRAR\winrar.exe
Value: "Blank"
Value Name: *\WinZip\winzip32.exe
Value: "Blank"
Value Name: *\WinZip\winzip64.exe
Value: "Blank"
Due to a change in the registry structure for EMET 5.5, if the system has a previous version of EMET installed and configured, this setting needs to be set to "Not Configured" prior to the upgrade to EMET 5.5, and the new administrative template files copied to the appropriate area. The setting can then be re-enabled.WINCC-000082<GroupDescription></GroupDescription>WN08-CC-000082The Enhanced Mitigation Experience Toolkit (EMET) system-wide Data Execution Prevention (DEP) must be enabled and configured to at least Application Opt Out.<VulnDiscussion>Attackers are constantly looking for vulnerabilities in systems and applications. The Enhanced Mitigation Experience Toolkit can enable several mechanisms, such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), and Structured Exception Handler Overwrite Protection (SEHOP) on the system and applications adding additional levels of protection.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002824This is applicable to unclassified systems, for other systems this is NA.
Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> EMET -> "System DEP" to "Enabled" with at least "Application Opt Out" selected.
The Enhanced Mitigation Experience Toolkit must be installed on the system and the administrative template files added to make this setting available.
Document applications that do not function properly due to this setting, and are opted out, with the ISSO.
Opted out exceptions can be configured with the following command.
EMET_Conf --Set "application path\executable name" -DEP
Alternately, configured exceptions in System Properties.
Select "System" in Control Panel.
Select "Advanced system settings".
Click "Settings" in the "Performance" section.
Select the "Data Execution Prevention" tab.
Select "Turn on DEP for all programs and services except those I select:".
Applications that are opted out are configured in the window below this selection.This is applicable to unclassified systems, for other systems this is NA.
If EMET has not been installed and DEP and SEHOP are configured as required in V-68843 and V-68847, this is NA.
If the following registry value does not exist or is not configured as specified, this is a finding.
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\EMET\SysSettings\
Value Name: DEP
Type: REG_DWORD
Value: 2 (Application Opt Out)
Applications that do not function properly due to this setting, and are opted out, must be documented with the ISSO.WINCC-000083<GroupDescription></GroupDescription>WN08-CC-000083The Enhanced Mitigation Experience Toolkit (EMET) system-wide Structured Exception Handler Overwrite Protection (SEHOP) must be configured to Application Opt Out.<VulnDiscussion>Attackers are constantly looking for vulnerabilities in systems and applications. The Enhanced Mitigation Experience Toolkit can enable several mechanisms, such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), and Structured Exception Handler Overwrite Protection (SEHOP) on the system and applications adding additional levels of protection.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002824This is applicable to unclassified systems, for other systems this is NA.
Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> EMET -> "System SEHOP" to "Enabled" with "Application Opt Out" selected.
The Enhanced Mitigation Experience Toolkit must be installed on the system and the administrative template files added to make this setting available.
Document applications that do not function properly due to this setting, and are opted out, with the ISSO.
Opted out exceptions can be configured with the following command.
EMET_Conf --Set "application path\executable name" -SEHOPThis is applicable to unclassified systems, for other systems this is NA.
If EMET has not been installed and DEP and SEHOP are configured as required in V-68843 and V-68847, this is NA.
If the following registry value does not exist or is not configured as specified, this is a finding.
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\EMET\SysSettings\
Value Name: SEHOP
Type: REG_DWORD
Value: 2
Applications that do not function properly due to this setting, and are opted out, must be documented with the ISSO.WINCC-000088<GroupDescription></GroupDescription>WN08-CC-000088The Windows SmartScreen must be configured to require approval from an administrator before running downloaded unknown software.<VulnDiscussion>Windows SmartScreen helps protect systems from programs downloaded from the Internet that may be malicious. Requiring administrator approval before running unknown software will prevent users from executing potentially malicious programs.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Configure Windows SmartScreen" to "Enabled" with "Require approval from an administrator before running downloaded unknown software" selected.If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\
Value Name: EnableSmartScreen
Type: REG_DWORD
Value: 2WINCC-000095<GroupDescription></GroupDescription>WN08-CC-000095The location feature must be turned off.<VulnDiscussion>The location service on mobile devices may allow sensitive data to be used by applications on the system. This should be turned off unless explicitly allowed for approved systems/applications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Location and Sensors >> "Turn off location" to "Enabled".
If location services are approved by the organization for a device, this must be documented.If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\Windows\LocationAndSensors\
Value Name: DisableLocation
Type: REG_DWORD
Value: 1 (Enabled)
If location services are approved for the device by the organization, this may be set to "Disabled" (0). This must be documented with the ISSO.WINCC-000106<GroupDescription></GroupDescription>WN08-CC-000106Basic authentication for RSS feeds over HTTP must be turned off.<VulnDiscussion>Basic authentication uses plain text passwords that could be used to compromise a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> RSS Feeds -> "Turn on Basic feed authentication over HTTP" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Internet Explorer\Feeds\
Value Name: AllowBasicAuthInClear
Type: REG_DWORD
Value: 0WINCC-000109<GroupDescription></GroupDescription>WN08-CC-000109Automatic download of updates from the Windows Store must be turned off.<VulnDiscussion>Uncontrolled system updates can introduce issues to a system. Obtaining update components from an outside source may also potentially allow sensitive information outside of the enterprise. Application updates must be obtained from an internal source.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Windows 8.1 split the original policy that configures this setting into two separate ones. Configuring either one to "Enabled" will update the registry value as identified in the Check section.
Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Store >> "Turn off Automatic Download of updates on Win8 machines" or "Turn off Automatic Download and install of updates" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsStore\
Value Name: AutoDownload
Type: REG_DWORD
Value: 0x00000002 (2)WINCC-000110<GroupDescription></GroupDescription>WN08-CC-000110The Windows Store application must be turned off.<VulnDiscussion>Uncontrolled installation of applications can introduce various issues including system instability, and provide access to sensitive information. Installation of applications must be controlled by the enterprise. Turning off access to the Windows Store will limit access to publicly available applications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Store -> "Turn off the Store application" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\WindowsStore\
Value Name: RemoveWindowsStore
Type: REG_DWORD
Value: 1WINCC-000123<GroupDescription></GroupDescription>WN08-CC-000123The Windows Remote Management (WinRM) client must not use Basic authentication.<VulnDiscussion>Basic authentication uses plain text passwords that could be used to compromise a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>IAIA-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000877Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Remote Management (WinRM) -> WinRM Client -> "Allow Basic authentication" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\WinRM\Client\
Value Name: AllowBasic
Type: REG_DWORD
Value: 0WINCC-000124<GroupDescription></GroupDescription>WN08-CC-000124The Windows Remote Management (WinRM) client must not allow unencrypted traffic.<VulnDiscussion>Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECCT-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002890CCI-003123Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Remote Management (WinRM) -> WinRM Client -> "Allow unencrypted traffic" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\WinRM\Client\
Value Name: AllowUnencryptedTraffic
Type: REG_DWORD
Value: 0WINCC-000125<GroupDescription></GroupDescription>WN08-CC-000125The Windows Remote Management (WinRM) client must not use Digest authentication.<VulnDiscussion>Digest authentication is not as strong as other options and may be subject to man-in-the-middle attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>IAIA-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000877Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Remote Management (WinRM) -> WinRM Client -> "Disallow Digest authentication" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\WinRM\Client\
Value Name: AllowDigest
Type: REG_DWORD
Value: 0WINCC-000126<GroupDescription></GroupDescription>WN08-CC-000126The Windows Remote Management (WinRM) service must not use Basic authentication.<VulnDiscussion>Basic authentication uses plain text passwords that could be used to compromise a system. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000877Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Remote Management (WinRM) -> WinRM Service -> "Allow Basic authentication" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\WinRM\Service\
Value Name: AllowBasic
Type: REG_DWORD
Value: 0WINCC-000127<GroupDescription></GroupDescription>WN08-CC-000127The Windows Remote Management (WinRM) service must not allow unencrypted traffic.<VulnDiscussion>Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECCT-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002890CCI-003123Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Remote Management (WinRM) -> WinRM Service -> "Allow unencrypted traffic" to "Disabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\WinRM\Service\
Value Name: AllowUnencryptedTraffic
Type: REG_DWORD
Value: 0WINCC-000128<GroupDescription></GroupDescription>WN08-CC-000128The Windows Remote Management (WinRM) service must not store RunAs credentials.<VulnDiscussion>Storage of administrative credentials could allow unauthorized access. Disallowing the storage of RunAs credentials for Windows Remote Management will prevent them from being used with plug-ins.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECLP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002038Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Remote Management (WinRM) -> WinRM Service -> "Disallow WinRM from storing RunAs credentials" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows\WinRM\Service\
Value Name: DisableRunAs
Type: REG_DWORD
Value: 1WINAU-000204<GroupDescription></GroupDescription>WN08-GE-000003-01Permissions for the Application event log must prevent access by non-privileged accounts.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. The Application event log may be susceptible to tampering if proper permissions are not applied.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECTP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000162CCI-000163CCI-000164Ensure the permissions on the Application event log (Application.evtx) are configured to prevent standard user accounts or groups from having access. The default permissions listed below satisfy this requirement.
Eventlog - Full Control
SYSTEM - Full Control
Administrators - Full Control
The default location is the "%SystemRoot%\SYSTEM32\WINEVT\LOGS" directory.
If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog".Verify the permissions on the Application event log (Application.evtx). Standard user accounts or groups must not have access. The default permissions listed below satisfy this requirement.
Eventlog - Full Control
SYSTEM - Full Control
Administrators - Full Control
The default location is the "%SystemRoot%\SYSTEM32\WINEVT\LOGS" directory. They may have been moved to another folder.
If the permissions for these files are not as restrictive as the ACLs listed, this is a finding.WINAU-000205<GroupDescription></GroupDescription>WN08-GE-000003-02Permissions for the Security event log must prevent access by non-privileged accounts.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. The Security event log may disclose sensitive information or be susceptible to tampering if proper permissions are not applied.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECTP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000162CCI-000163CCI-000164Ensure the permissions on the Security event log (Security.evtx) are configured to prevent standard user accounts or groups from having access. The default permissions listed below satisfy this requirement.
Eventlog - Full Control
SYSTEM - Full Control
Administrators - Full Control
The default location is the "%SystemRoot%\SYSTEM32\WINEVT\LOGS" directory.
If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog".Verify the permissions on the Security event log (Security.evtx). Standard user accounts or groups must not have access. The default permissions listed below satisfy this requirement.
Eventlog - Full Control
SYSTEM - Full Control
Administrators - Full Control
The default location is the "%SystemRoot%\SYSTEM32\WINEVT\LOGS" directory. They may have been moved to another folder.
If the permissions for these files are not as restrictive as the ACLs listed, this is a finding.WINAU-000206<GroupDescription></GroupDescription>WN08-GE-000003-03Permissions for the System event log must prevent access by non-privileged accounts.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. The System event log may be susceptible to tampering if proper permissions are not applied.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECTP-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000162CCI-000163CCI-000164Ensure the permissions on the System event log (System.evtx) are configured to prevent standard user accounts or groups from having access. The default permissions listed below satisfy this requirement.
Eventlog - Full Control
SYSTEM - Full Control
Administrators - Full Control
The default location is the "%SystemRoot%\SYSTEM32\WINEVT\LOGS" directory.
If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog".Verify the permissions on the System event log (System.evtx). Standard user accounts or groups must not have access. The default permissions listed below satisfy this requirement.
Eventlog - Full Control
SYSTEM - Full Control
Administrators - Full Control
The default location is the "%SystemRoot%\SYSTEM32\WINEVT\LOGS" directory. They may have been moved to another folder.
If the permissions for these files are not as restrictive as the ACLs listed, this is a finding.WN08-GE-000021<GroupDescription></GroupDescription>WN08-GE-000021Hyper-V must not be installed on a workstation.<VulnDiscussion>Allowing other operating systems to run on a secure system may allow users to circumvent security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Uninstall the Hyper-V platform through "Turn Windows Features on or off".Verify the Hyper-V platform has not been installed on the system.
Open Control Panel.
Select "Programs and Features".
Select "Turn Windows features on or off".
If "Hyper-V Platform" is selected, this is a finding. (Hyper-V Platform is a subcategory under Hyper-V)
If Hyper-V is installed on a workstation, the organization must have an approved use case for it. Any virtual OS's must be secured. This would not be a finding.WN08-GE-000022<GroupDescription></GroupDescription>WN08-GE-000022Simple Network Management Protocol (SNMP) must not be installed on the system.<VulnDiscussion>Some protocols and services do not support required security features, such as encrypting passwords or traffic.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000382Uninstall "Simple Network Management Protocol (SNMP)" from the system through "Turn Windows Features on or off".Verify SNMP has not been installed. If snmp.exe exists in the \system32 directory, this is a finding.WN08-GE-000023<GroupDescription></GroupDescription>WN08-GE-000023Simple TCP/IP Services must not be installed on the system.<VulnDiscussion>Some protocols and services do not support required security features, such as encrypting passwords or traffic.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Uninstall "Simple TCPIP Services (i.e. echo, daytime etc)" from the system through "Turn Windows features on or off".Verify "Simple TCP/IP Services" has not been installed on the system.
Run "Services.msc".
If "Simple TCP/IP Services" is listed, this is a finding.WN08-GE-000024<GroupDescription></GroupDescription>WN08-GE-000024The Telnet Client must not be installed on the system.<VulnDiscussion>Some protocols and services do not support required security features, such as encrypting passwords or traffic.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000382Uninstall "Telnet Client" from the system through "Turn Windows Features on or off".Verify the Telnet Client has not been installed. If Telnet.exe exists in the \system32 directory, this is a finding.WN08-GE-000025<GroupDescription></GroupDescription>WN08-GE-000025Telnet Server must not be installed on the system.<VulnDiscussion>Some protocols and services do not support required security features, such as encrypting passwords or traffic.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000382Uninstall "Telnet Server" from the system through "Turn Windows Features on or off".Verify Telnet Server has not been installed. If TlntSvr.exe exists in the \system32 directory, this is a finding.WN08-GE-000026<GroupDescription></GroupDescription>WN08-GE-000026The TFTP Client must not be installed on the system.<VulnDiscussion>Some protocols and services do not support required security features, such as encrypting passwords or traffic.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000382Uninstall "TFTP Client" from the system through "Turn Windows Features on or off".Verify the TFTP Client has not been installed. If TFTP.exe exists in the \system32 directory, this is a finding.WINGE-000027<GroupDescription></GroupDescription>WN08-GE-000027User-level information must be backed up per organization defined frequency consistent with recovery time and recovery point objectives.<VulnDiscussion>Operating system backup is a critical step in maintaining data assurance and availability. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>CODB-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Establish a process for backing up user-level information.Verify the organization has a process to backup user-level information to support recovery. If it does not, this is a finding.WINGE-000028<GroupDescription></GroupDescription>WN08-GE-000028The system must employ automated mechanisms or must have an application installed that, on an organization defined frequency determines the state of information system components with regard to flaw remediation.<VulnDiscussion>Organizations are required to identify information systems containing software affected by recently announced software flaws (and potential vulnerabilities resulting from those flaws) and report this information to designated organizational officials with information security responsibilities (e.g., senior information security officers, information system security managers, information systems security officers). To support this requirement, an automated process or mechanism is required. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>VIVM-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001233Establish an automated process to scan systems for identified software flaws and vulnerabilities.Verify the organization has an automated process to scan systems for identified software flaws and vulnerabilities. If it does not, this is a finding.WINGE-000029<GroupDescription></GroupDescription>WN08-GE-000029The system must support automated patch management tools to facilitate flaw remediation to organization defined information system components.<VulnDiscussion>The organization (including any contractor to the organization) must promptly install security-relevant software updates (e.g., patches, service packs, hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>VIVM-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Establish a process to automatically install security-related software updates.Verify the organization has an automated process to install security-related software updates. If it does not, this is a finding.WINGE-000030<GroupDescription></GroupDescription>WN08-GE-000030The system must query the certification authority to determine whether a public key certificate has been revoked before accepting the certificate for authentication purposes.<VulnDiscussion>Failure to verify a certificate's revocation status can result in the system accepting a revoked and therefore unauthorized, certificate. This could result in the installation of unauthorized software or a connection for rogue networks, depending on the use for which the certificate is intended. Querying for certificate revocation mitigates the risk that the system will accept an unauthorized certificate.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>IATS-1, IATS-2</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Install software that provides certificate validation and revocation checking.Verify the system has software installed and running that provides certificate validation and revocation checking. If it does not, this is a finding.WN08-GE-000033<GroupDescription></GroupDescription>WN08-GE-000033The Windows 8 Games app must be removed from the system.<VulnDiscussion>Some Windows 8 default apps provide links to external services and must be removed from the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Remove the Games app from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., Microsoft.XboxLIVEGames_1.0.927.0_x64__8wekyb3d8bbwe)
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename" substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the Games app has been removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : Microsoft.XboxLIVEGames" is listed, this is a finding.WN08-GE-000034<GroupDescription></GroupDescription>WN08-GE-000034The Windows 8 Music app must be removed from the system.<VulnDiscussion>Some Windows 8 default apps provide links to external services and must be removed from the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Remove the Music app from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., Microsoft.ZuneMusic_1.0.927.0_x64__8wekyb3d8bbwe)
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename" substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the Music app has been removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : Microsoft.ZuneMusic" is listed, this is a finding.WN08-GE-000035<GroupDescription></GroupDescription>WN08-GE-000035The Windows 8 Video app must be removed from the system.<VulnDiscussion>Some Windows 8 default apps provide links to external services and must be removed from the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Remove the Video app from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., Microsoft.ZuneVideo_1.0.927.0_x64__8wekyb3d8bbwe)
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename" substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the Video app has been removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : Microsoft.ZuneVideo" is listed this, is a finding.WN08-GE-000037<GroupDescription></GroupDescription>WN08-GE-000037The Windows 8 default Finance app must be updated with the latest security patches or removed from the system.<VulnDiscussion>Applications must be updated as flaws are identified and remediations are made available. The default method for updating Windows 8 apps is through the Windows Store, which is required to be blocked. An alternate method must be used to maintain the default Windows 8 apps with the latest security updates if they are allowed on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Maintain the Finance app with the latest security related updates or remove it from the system. Microsoft provides security related updates to default provisioned apps through the Microsoft Update Catalog for WSUS or as MSI files, as an alternate method to the Windows Store for updating.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128
To remove the Finance app from the system:
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., Microsoft.BingFinance_1.2.0.135_x64__8wekyb3d8bbwe).
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename", substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the default Finance app has been patched with the latest security related updates or removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : Microsoft.BingFinance" is listed and has not been updated with the latest security related updates, this is a finding.
The "PackageName" field will identify the version installed.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128WN08-GE-000038<GroupDescription></GroupDescription>WN08-GE-000038The Windows 8 default Maps app must be updated with the latest security patches or removed from the system.<VulnDiscussion>Applications must be updated as flaws are identified and remediations are made available. The default method for updating Windows 8 apps is through the Windows Store, which is required to be blocked. An alternate method must be used to maintain the default Windows 8 apps with the latest security updates if they are allowed on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Maintain the Maps app with the latest security related updates or remove it from the system. Microsoft provides security related updates to default provisioned apps through the Microsoft Update Catalog for WSUS or as MSI files, as an alternate method to the Windows Store for updating.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128
To remove the Maps app from the system:
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., Microsoft.BingMaps_1.2.0.135_x64__8wekyb3d8bbwe).
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename", substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the default Maps app has been patched with the latest security related updates or removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : Microsoft.BingMaps" is listed and has not been updated with the latest security related updates, this is a finding.
The "PackageName" field will identify the version installed.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128WN08-GE-000039<GroupDescription></GroupDescription>WN08-GE-000039The Windows 8 default News app must be updated with the latest security patches or removed from the system.<VulnDiscussion>Applications must be updated as flaws are identified and remediations are made available. The default method for updating Windows 8 apps is through the Windows Store, which is required to be blocked. An alternate method must be used to maintain the default Windows 8 apps with the latest security updates if they are allowed on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Maintain the News app with the latest security related updates or remove it from the system. Microsoft provides security related updates to default provisioned apps through the Microsoft Update Catalog for WSUS or as MSI files, as an alternate method to the Windows Store for updating.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128
To remove the News app from the system:
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., Microsoft.BingNews_1.2.0.135_x64__8wekyb3d8bbwe).
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename", substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the default News app has been patched with the latest security related updates or removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : Microsoft.BingNews" is listed and has not been updated with the latest security related updates, this is a finding.
The "PackageName" field will identify the version installed.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128WN08-GE-000040<GroupDescription></GroupDescription>WN08-GE-000040The Windows 8 default Sports app must be updated with the latest security patches or removed from the system.<VulnDiscussion>Applications must be updated as flaws are identified and remediations are made available. The default method for updating Windows 8 apps is through the Windows Store, which is required to be blocked. An alternate method must be used to maintain the default Windows 8 apps with the latest security updates if they are allowed on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Maintain the Sports app with the latest security related updates or remove it from the system. Microsoft provides security related updates to default provisioned apps through the Microsoft Update Catalog for WSUS or as MSI files, as an alternate method to the Windows Store for updating.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128
To remove the Sports app from the system:
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., Microsoft.BingSports_1.2.0.135_x64__8wekyb3d8bbwe).
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename", substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the default Sports app has been patched with the latest security related updates or removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : Microsoft.BingSports" is listed and has not been updated with the latest security related updates, this is a finding.
The "PackageName" field will identify the version installed.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128WN08-GE-000041<GroupDescription></GroupDescription>WN08-GE-000041The Windows 8 default Travel app must be updated with the latest security patches or removed from the system.<VulnDiscussion>Applications must be updated as flaws are identified and remediations are made available. The default method for updating Windows 8 apps is through the Windows Store, which is required to be blocked. An alternate method must be used to maintain the default Windows 8 apps with the latest security updates if they are allowed on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Maintain the Travel app with the latest security related updates or remove it from the system. Microsoft provides security related updates to default provisioned apps through the Microsoft Update Catalog for WSUS or as MSI files, as an alternate method to the Windows Store for updating.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128
To remove the Travel app from the system:
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., Microsoft.BingTravel_1.2.0.135_x64__8wekyb3d8bbwe).
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename", substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the default Travel app has been patched with the latest security related updates or removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : Microsoft.BingTravel" is listed and has not been updated with the latest security related updates, this is a finding.
The "PackageName" field will identify the version installed.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128WN08-GE-000042<GroupDescription></GroupDescription>WN08-GE-000042The Windows 8 default Weather app must be updated with the latest security patches or removed from the system.<VulnDiscussion>Applications must be updated as flaws are identified and remediations are made available. The default method for updating Windows 8 apps is through the Windows Store, which is required to be blocked. An alternate method must be used to maintain the default Windows 8 apps with the latest security updates if they are allowed on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Maintain the Weather app with the latest security related updates or remove it from the system. Microsoft provides security related updates to default provisioned apps through the Microsoft Update Catalog for WSUS or as MSI files, as an alternate method to the Windows Store for updating.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128
To remove the Weather app from the system:
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., Microsoft.BingWeather_1.2.0.135_x64__8wekyb3d8bbwe).
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename", substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the default Weather app has been patched with the latest security related updates or removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : Microsoft.BingWeather" is listed and has not been updated with the latest security related updates, this is a finding.
The "PackageName" field will identify the version installed.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128WN08-GE-000044<GroupDescription></GroupDescription>WN08-GE-000044The Windows 8 default Reader app must be updated with the latest security patches or removed from the system.<VulnDiscussion>Applications must be updated as flaws are identified and remediations are made available. The default method for updating Windows 8 apps is through the Windows Store, which is required to be blocked. An alternate method must be used to maintain the default Windows 8 apps with the latest security updates if they are allowed on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Maintain the Reader app with the latest security related updates or remove it from the system. Microsoft provides security related updates to default provisioned apps through the Microsoft Update Catalog for WSUS or as MSI files, as an alternate method to the Windows Store for updating.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128
To remove the Reader app from the system:
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., Microsoft.Reader_6.2.8514.0_x64__8wekyb3d8bbwe).
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename", substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the default Reader app has been patched with the latest security related updates or removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : Microsoft.Reader" is listed and has not been updated with the latest security related updates, this is a finding.
The "PackageName" field will identify the version installed.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128WN08-GE-000045<GroupDescription></GroupDescription>WN08-GE-000045The Windows 8 default Communications apps (Mail, People, Messaging, and Calendar) must be updated with the latest security patches or removed from the system.<VulnDiscussion>Applications must be updated as flaws are identified and remediations are made available. The default method for updating Windows 8 apps is through the Windows Store, which is required to be blocked. An alternate method must be used to maintain the default Windows 8 apps with the latest security updates if they are allowed on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Maintain the Communications apps with the latest security related updates or remove them from the system. Microsoft provides security related updates to default provisioned apps through the Microsoft Update Catalog for WSUS or as MSI files, as an alternate method to the Windows Store for updating.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128
To remove the Communications apps from the system:
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., microsoft.windowscommunicationsapps_16.4.4206.722_x64__8wekyb3d8bbwe).
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename", substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the default Communications apps have been patched with the latest security related updates or removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : microsoft.windowscommunicationsapps" is listed and has not been updated with the latest security related updates, this is a finding.
The "PackageName" field will identify the version installed.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128WN08-MO-000001<GroupDescription></GroupDescription>WN08-MO-000001The VPN client on mobile devices must use DoD approved multi-factor authentication tokens (e.g., Common Access Card (CAC) for unclassified systems) when connecting to DoD networks.<VulnDiscussion>VPNs are vulnerable to attack if they are not supported by strong authentication. An adversary may be able gain access to network resources and sensitive information if they can compromise the authentication process. DoD approved multi-factor authentication tokens (e.g., Common Access Card (CAC) for unclassified systems) is strong cryptographic two-factor authentication that greatly mitigates the risk of VPN authentication breaches.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001967Configure the VPN client on mobile devices to use DoD approved multi-factor authentication tokens (e.g., Common Access Card (CAC) for unclassified systems) when connecting to DoD networks.
Procedures will vary depending on the VPN client used.Verify the VPN client on mobile devices is configured to use DoD approved multi-factor authentication tokens (e.g., Common Access Card (CAC) for unclassified systems) for connections to DoD networks. If it is not, this is a finding.
Procedures will vary depending on the VPN client used.WN08-MO-000002<GroupDescription></GroupDescription>WN08-MO-000002The VPN client on mobile devices must disable split tunneling.<VulnDiscussion>When split tunneling is enabled, device peripherals and other computers communicating with the mobile device may be able to connect to a DoD network and obtain sensitive information or otherwise compromise DoD information resources. Disabling split tunneling eliminates the risk associated with this vulnerability.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the VPN client on mobile devices to prevent split tunneling when connecting to DoD networks.
Procedures will vary depending on the VPN client used.Verify the VPN client on mobile devices is configured to prevent split tunneling for connections to DoD networks. If it is not, this is a finding.
Procedures will vary depending on the VPN client used.WN08-MO-000003<GroupDescription></GroupDescription>WN08-MO-000003The VPN client on mobile devices must use either IPSec or SSL/TLS when connecting to DoD networks.<VulnDiscussion>Use of non-standard communications protocols can affect both the availability and confidentiality of communications. IPSec and SSL/TLS are both well-known and tested protocols that provide strong assurance with respect to both IA and interoperability.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002418Configure the VPN client on mobile devices to use IPSec or SSL/TLS when connecting to DoD networks.
Procedures will vary depending on the VPN client used.Verify the VPN client on mobile devices is configured to use IPSec or SSL/TLS for connections to DoD networks. If it does not, this is a finding.
Procedures will vary depending on the VPN client used.WN08-MO-000005<GroupDescription></GroupDescription>WN08-MO-000005Bluetooth must be turned off unless approved by the organization.<VulnDiscussion>If not configured properly, Bluetooth may allow rogue devices to communicate with a system. If a rogue device is paired with a system, there is potential for sensitive information to be compromised. DoD policy and Wireless STIG guidance must be implemented with the use of Bluetooth.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Turn off Bluetooth radios not organizationally approved. Establish an organizational policy for the use of Bluetooth.Verify the Bluetooth radio is turned off unless approved by the organization. If it is not, this is a finding.
Approval must be documented with the ISSO.
If the system does not have Bluetooth, this is not applicable.WN08-MO-000006<GroupDescription></GroupDescription>WN08-MO-000006Bluetooth must be turned off when not in use.<VulnDiscussion>If not configured properly, Bluetooth may allow rogue devices to communicate with a system. If a rogue device is paired with a system, there is potential for sensitive information to be compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Turn off Bluetooth radios when not in use. Establish an organizational policy for the use of Bluetooth to include training of personnel.Verify the organization has a policy to turn off Bluetooth when not in use and personnel are trained. If it does not, this is a finding.
If the system does not have Bluetooth or it is disabled, this is not applicable.WN08-MO-000007<GroupDescription></GroupDescription>WN08-MO-000007The system must notify the user when a Bluetooth device attempts to connect.<VulnDiscussion>If not configured properly, Bluetooth may allow rogue devices to communicate with a system. If a rogue device is paired with a system, there is potential for sensitive information to be compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure Bluetooth to notify users if devices attempt to connect.
View Bluetooth Settings.
Ensure "Alert me when a new Bluetooth device wants to connect" is checked.Verify Bluetooth notifies users if devices attempt to connect.
Search for "Bluetooth".
Select "Devices and Printers".
View Bluetooth Settings.
If "Alert me when a new Bluetooth device wants to connect" is not checked, this is a finding.
If the system does not have Bluetooth, this is not applicable.WN08-MO-000009<GroupDescription></GroupDescription>WN08-MO-000009Built-in cameras must be disabled unless allowed by physical security policies.<VulnDiscussion>Cameras can capture still pictures and video of sensitive information. There is also a potential for remote access, and cameras must be turned off unless approved by local policy.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Disable built-in cameras in device manager unless allowed by physical security policies.Verify built-in cameras are turned off unless allowed by physical security policies. View status in device manager.
If cameras have not been disabled per physical security policies, this is a finding.
If the system does not have cameras, this is not applicable.WN08-MO-000010<GroupDescription></GroupDescription>WN08-MO-000010Built-in microphones must be disabled on mobile devices unless required and approved by the organization.<VulnDiscussion>Microphones can capture audio of sensitive information. There is also a potential for remote access, and microphones must be turned off unless approved by local policy.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Disable microphones in device manager if not organizationally approved.Verify microphones are turned off unless approved by the organization. View status in device manager.
If built-in microphones are not approved by local policy or disabled, this is a finding.
If the system does not have built-in microphones, this is not applicable.WN08-MO-000011<GroupDescription></GroupDescription>WN08-MO-000011Global Positioning System (GPS) must be disabled unless required and approved by the organization.<VulnDiscussion>GPS may provide sensitive location information through various applications and embedded meta-data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Disable GPS in device manager if not organizationally approved.Verify GPS is turned off unless approved by the organization. View status in device manager or GPS management application.
If GPS is not approved or disabled, this is a finding.
If the system does not have GPS, this is not applicable.WN08-MO-000012<GroupDescription></GroupDescription>WN08-MO-000012Near Field Communications (NFC) chips must be disabled.<VulnDiscussion>Various connection ports can provide additional attack vectors to a system or expose sensitive information and should be limited.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Disable NFC in device manager.Verify NFC is turned off. View status in device manager or NFC management application.
IF NFC is not disabled, this is a finding.
If the system does not have NFC, this is not applicable.WN08-MO-000013<GroupDescription></GroupDescription>WN08-MO-000013Infrared (IR) ports must be disabled.<VulnDiscussion>Various connection ports can provide additional attack vectors to a system or expose sensitive information and should be limited.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Disable IR ports in device manager.Verify IR ports are disabled. View status in device manager.
If IR ports are not disabled, this is a finding.
If the system does not have IR ports, this is not applicable.WN08-RG-000003<GroupDescription></GroupDescription>WN08-RG-000003Local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain systems.<VulnDiscussion>A compromised local administrator account can provide means for an attacker to move laterally between domain systems.
With User Account Control enabled, filtering the privileged token for built-in administrator accounts will prevent the elevated privileges of these accounts from being used over the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECCD-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001084Configure the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
Value Name: LocalAccountTokenFilterPolicy
Type: REG_DWORD
Value: 0If the system is not a member of a domain, this is NA.
If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Subkey: SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
Value Name: LocalAccountTokenFilterPolicy
Type: REG_DWORD
Value: 0
This setting may cause issues with some network scanning tools if local administrative accounts are used remotely. Scans should use domain accounts where possible. If a local administrative account must be used, temporarily enabling the privileged token by configuring the registry value to 1 may be required.WN08-SO-000002<GroupDescription></GroupDescription>WN08-SO-000002Use of Microsoft accounts to log on must be blocked.<VulnDiscussion>Control of logon credentials and the system must be maintained within the enterprise. Linking an account to an outside vendor could provide an opening if the account is compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>IAIA-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Accounts: Block Microsoft accounts" to "Users can't add or log on with Microsoft accounts".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Accounts: Block Microsoft accounts" is not set to "Users can't add or log on with Microsoft accounts", this is a finding.WINSO-000021<GroupDescription></GroupDescription>WN08-SO-000021The machine inactivity limit must be set to 15 minutes, locking the system with the screensaver.<VulnDiscussion>Unattended systems are susceptible to unauthorized use and should be locked when unattended. The screen saver should be set at a maximum of 15 minutes and be password protected. This protects critical and sensitive data from exposure to unauthorized personnel with physical access to the computer.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>PESL-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000057Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Interactive logon: Machine inactivity limit" to "900" seconds".Analyze the system using the Security Configuration and Analysis snap-in. (See "Performing Analysis with the Security Configuration and Analysis Snap-in" in the STIG Overview document.)
Expand the Security Configuration and Analysis tree view.
Navigate to Local Policies -> Security Options.
If the value for "Interactive logon: Machine inactivity limit" is not set to "900" seconds or less, this is a finding.
The policy referenced configures the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\System\
Value Name: InactivityTimeoutSecs
Value Type: REG_DWORD
Value: 0x00000384 (900)WINUC-000002<GroupDescription></GroupDescription>WN08-UC-000002A screen saver must be defined.<VulnDiscussion>Unattended systems are susceptible to unauthorized use and must be locked. Specifying a screen saver ensures the screen saver timeout lock is initiated properly. This protects critical and sensitive data from exposure to unauthorized personnel with physical access to the computer.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>PESL-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000060Configure the policy value for User Configuration -> Administrative Templates -> Control Panel -> Personalization -> "Force specific screen saver" to "Enabled" with "scrnsave.scr" specified as the Screen saver executable name.If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_CURRENT_USER
Subkey: \Software\Policies\Microsoft\Windows\Control Panel\Desktop\
Value Name: SCRNSAVE.EXE
Type: REG_SZ
Value: scrnsave.scrWINUC-000004<GroupDescription></GroupDescription>WN08-UC-000004Changing the screen saver must be prevented.<VulnDiscussion>Unattended systems are susceptible to unauthorized use and must be locked. Preventing users from changing the screen saver ensures an approved screen saver is used. This protects critical and sensitive data from exposure to unauthorized personnel with physical access to the computer.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>PESL-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000060Configure the policy value for User Configuration -> Administrative Templates -> Control Panel -> Personalization -> "Prevent changing screen saver" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_CURRENT_USER
Subkey: \Software\Microsoft\Windows\CurrentVersion\Policies\System\
Value Name: NoDispScrSavPage
Type: REG_DWORD
Value: 1WINUC-000005<GroupDescription></GroupDescription>WN08-UC-000005Notifications from Windows Push Network Service must be turned off.<VulnDiscussion>The Windows Push Notification Service (WNS) allows third-party vendors to send updates for toasts, tiles, and badges.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for User Configuration -> Administrative Templates -> Start Menu and Taskbar -> Notifications -> "Turn off notifications network usage" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_CURRENT_USER
Subkey: \SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\PushNotifications\
Value Name: NoCloudApplicationNotification
Type: REG_DWORD
Value: 1WINUC-000006<GroupDescription></GroupDescription>WN08-UC-000006Toast notifications to the lock screen must be turned off.<VulnDiscussion>Toast notifications that are displayed on the lock screen could display sensitive information to unauthorized personnel. Turning off this feature will limit access to the information to a logged on user.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for User Configuration -> Administrative Templates -> Start Menu and Taskbar -> Notifications -> "Turn off toast notifications on the lock screen" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_CURRENT_USER
Subkey: \SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\PushNotifications\
Value Name: NoToastApplicationNotificationOnLockScreen
Type: REG_DWORD
Value: 1WINGE-000100<GroupDescription></GroupDescription>WN08-GE-000100The Enhanced Mitigation Experience Toolkit (EMET) v5.5 or later must be installed on the system.<VulnDiscussion>Attackers are constantly looking for vulnerabilities in systems and applications. The Enhanced Mitigation Experience Toolkit can enable several mechanisms, such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), and Structured Exception Handler Overwrite Protection (SEHOP) on the system and applications adding additional levels of protection.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Install EMET v5.5 or later on the system. EMET is available for download from Microsoft.This is applicable to unclassified systems, for other systems this is NA.
If EMET has not been installed and DEP and SEHOP are configured as required in V-68843 and V-68847, this is NA.
Verify EMET v5.5 or later is installed on the system.
If EMET is not installed, or at the minimum required version, this is a finding.WINPK-000004<GroupDescription></GroupDescription>WN08-PK-000004The US DoD CCEB Interoperability Root CA cross-certificate must be installed in the Untrusted Certificates Store on unclassified systems.<VulnDiscussion>To ensure users do not experience denial of service when performing certificate-based authentication to DoD websites due to the system chaining to a root other than DoD Root CAs, the US DoD CCEB Interoperability Root CA cross-certificate must be installed in the Untrusted Certificate Store. This requirement only applies to unclassified systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000185CCI-002470Install the US DoD CCEB Interoperability Root CA cross-certificate on unclassified systems.
Issued To - Issued By - Thumbprint
DoD Root CA 2 - US DoD CCEB Interoperability Root CA 1 - DA36FAF56B2F6FBA1604F5BE46D864C9FA013BA3
Administrators should run the Federal Bridge Certification Authority (FBCA) Cross-Certificate Removal Tool once as an administrator and once as the current user.
The FBCA Cross-Certificate Remover tool and user guide is available on IASE at http://iase.disa.mil/pki-pke/Pages/tools.aspx.Verify the US DoD CCEB Interoperability Root CA cross-certificate is installed on unclassified systems as an Untrusted Certificate.
Run "PowerShell" as an administrator.
Execute the following command:
Get-ChildItem -Path Cert:Localmachine\disallowed | Where Issuer -Like "*CCEB Interoperability*" | FL Subject, Issuer, Thumbprint
If the following information is not displayed, this is finding.
Subject: CN=DoD Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US
Issuer: CN=US DoD CCEB Interoperability Root CA 1, OU=PKI, OU=DoD, O=U.S. Government, C=US
Thumbprint: DA36FAF56B2F6FBA1604F5BE46D864C9FA013BA3
Alternately use the Certificates MMC snap-in:
Run "MMC".
Select "File", "Add/Remove Snap-in".
Select "Certificates", click "Add".
Select "Computer account", click "Next".
Select "Local computer: (the computer this console is running on)", click "Finish".
Click "OK".
Expand "Certificates" and navigate to "Untrusted Certificates >> Certificates".
For each certificate with "US DoD CCEB Interoperability Root CA …" under "Issued By":
Right click on the certificate and select "Open".
Select the "Details" Tab.
Scroll to the bottom and select "Thumbprint".
If the certificate below is not listed or the value for the "Thumbprint" field is not as noted, this is a finding.
Issued To - Issued By - Thumbprint
DoD Root CA 2 - US DoD CCEB Interoperability Root CA 1 - DA36FAF56B2F6FBA1604F5BE46D864C9FA013BA3WINFW-000001<GroupDescription></GroupDescription>WN08-FW-000001A host-based firewall must be installed and enabled on the system.<VulnDiscussion>A firewall provides a line of defense against attack, allowing or blocking inbound and outbound connections based on a set of rules.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Install and enable a host-based firewall on the system.Determine if a host-based firewall is installed and enabled on the system. If a host-based firewall is not installed and enabled on the system, this is a finding.
The configuration requirements will be determined by the applicable firewall STIG.WINCC-000137<GroupDescription></GroupDescription>WN08-CC-000137Camera access from the lock screen must be disabled.<VulnDiscussion>Enabling camera access from the lock screen could allow for unauthorized use. Requiring logon will ensure the device is only used by authorized personnel.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration >> Administrative Templates >> Control Panel >> Personalization >> "Prevent enabling lock screen camera" to "Enabled".If the device does not have a camera, this is NA.
Verify the registry value below. If it does not exist or is not configured as specified, this is a finding.
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Personalization\
Value Name: NoLockScreenCamera
Value Type: REG_DWORD
Value: 1WINCC-000138<GroupDescription></GroupDescription>WN08-CC-000138The display of slide shows on the lock screen must be disabled.<VulnDiscussion>Slide shows that are displayed on the lock screen could display sensitive information to unauthorized personnel. Turning off this feature will limit access to the information to a logged on user.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration >> Administrative Templates >> Control Panel >> Personalization >> "Prevent enabling lock screen slide show" to "Enabled".Verify the registry value below. If it does not exist or is not configured as specified, this is a finding.
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Personalization\
Value Name: NoLockScreenSlideshow
Value Type: REG_DWORD
Value: 1WINCC-000139<GroupDescription></GroupDescription>WN08-CC-000139Command line data must be included in process creation events.<VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Enabling "Include command line data for process creation events" will record the command line information with the process creation events in the log. This can provide additional detail when malware has run on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000135Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Audit Process Creation >> "Include command line in process creation events" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit\
Value Name: ProcessCreationIncludeCmdLine_Enabled
Value Type: REG_DWORD
Value: 1WINCC-000140<GroupDescription></GroupDescription>WN08-CC-000140The network selection user interface (UI) must not be displayed on the logon screen.<VulnDiscussion>Enabling interaction with the network selection UI allows users to change connections to available networks without signing into Windows.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Logon >> "Do not display network selection UI" to "Enabled".Verify the registry value below. If it does not exist or is not configured as specified, this is a finding.
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\
Value Name: DontDisplayNetworkSelectionUI
Value Type: REG_DWORD
Value: 1WINCC-000141<GroupDescription></GroupDescription>WN08-CC-000141The setting to allow Microsoft accounts to be optional for modern style apps must be enabled.<VulnDiscussion>Control of credentials and the system must be maintained within the enterprise. Enabling this setting allows enterprise credentials to be used with modern style apps that support this, instead of Microsoft accounts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> App Runtime >> "Allow Microsoft accounts to be optional" to "Enabled".Verify the registry value below. If it does not exist or is not configured as specified, this is a finding.
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
Value Name: MSAOptional
Value Type: REG_DWORD
Value: 1WINCC-000142<GroupDescription></GroupDescription>WN08-CC-000142Information shared with Bing in Search must be configured to the most restrictive setting.<VulnDiscussion>Various levels of information can be shared with Bing in Search, to include user information and location. Configuring this setting prevents users from selecting the level of information shared and enables the most restrictive selection.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Search >> "Set what information is shared in Search" to "Enabled" with "Anonymous" selected in "Type of Information".Verify the registry value below. If it does not exist or is not configured as specified, this is a finding.
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Windows Search\
Value Name: ConnectedSearchPrivacy
Value Type: REG_DWORD
Value: 3WINCC-000143<GroupDescription></GroupDescription>WN08-CC-000143The use of OneDrive for storage must be disabled.<VulnDiscussion>OneDrive provides access to external services for data storage which must not be used. Enabling this setting will prevent such access from the OneDrive app, as well as from File Explorer.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> OneDrive >> "Prevent the usage of OneDrive for file storage" to "Enabled".If the following registry value does not exist or is not configured as specified, this is a finding.
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Skydrive\
Value Name: DisableFileSync
Value Type: REG_DWORD
Value: 1WINCC-000144<GroupDescription></GroupDescription>WN08-CC-000144The option to update to the latest version of Windows from the Store must be turned off.<VulnDiscussion>Uncontrolled system updates can introduce issues into the environment. Updates to the latest version of Windows must be done through proper change management. This setting will prevent the option to update to the latest version of Windows from being offered through the Store.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001812Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Store >> "Turn off the offer to update to the latest version of Windows" to "Enabled".Verify the registry value below. If it does not exist or is not configured as specified, this is a finding.
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsStore\
Value Name: DisableOSUpgrade
Value Type: REG_DWORD
Value: 1WINCC-000145<GroupDescription></GroupDescription>WN08-CC-000145Automatically signing in the last interactive user after a system-initiated restart must be disabled.<VulnDiscussion>Windows can be configured to automatically sign the user back in after a Windows Update restart. Some protections are in place to help ensure this is done in a secure fashion; however, disabling this will prevent the caching of credentials for this purpose and also ensure the user is aware of the restart.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Logon Options >> "Sign-in last interactive user automatically after a system-initiated restart" to "Disabled".Verify the registry value below. If it does not exist or is not configured as specified, this is a finding.
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\
Value Name: DisableAutomaticRestartSignOn
Value Type: REG_DWORD
Value: 1WN08-GE-000054<GroupDescription></GroupDescription>WN08-GE-000054The Windows 8 default Skype app must be removed from the system.<VulnDiscussion>Some Windows 8 default apps provide links to external services and must be removed from the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Remove the Skype app from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., Microsoft.SkypeApp_2013.805.1159.2246_neutral_~_kzf8qxf38zg5c).
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename", substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the Skype app has been removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : Microsoft.SkypeApp" is listed, this is a finding.WN08-GE-000047<GroupDescription></GroupDescription>WN08-GE-000047The Windows 8 default Alarms app must be updated with the latest security patches or removed from the system.<VulnDiscussion>Applications must be updated as flaws are identified and remediations are made available. The default method for updating Windows 8 apps is through the Windows Store, which is required to be blocked. An alternate method must be used to maintain the default Windows 8 apps with the latest security updates if they are allowed on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Maintain the Alarms app with the latest security related updates or remove it from the system. Microsoft provides security related updates to default provisioned apps through the Microsoft Update Catalog for WSUS or as MSI files, as an alternate method to the Windows Store for updating.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128
To remove the Alarms app from the system:
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., Microsoft.WindowsAlarms_2013.822.1841.1043_neutral_~_8wekyb3d8bbwe).
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename", substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the default Alarms app has been patched with the latest security related updates or removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : Microsoft.WindowsAlarms" is listed and has not been updated with the latest security related updates, this is a finding.
The "PackageName" field will identify the version installed.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128WN08-GE-000048<GroupDescription></GroupDescription>WN08-GE-000048The Windows 8 default Calculator app must be updated with the latest security patches or removed from the system.<VulnDiscussion>Applications must be updated as flaws are identified and remediations are made available. The default method for updating Windows 8 apps is through the Windows Store, which is required to be blocked. An alternate method must be used to maintain the default Windows 8 apps with the latest security updates if they are allowed on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Maintain the Calculator app with the latest security related updates or remove it from the system. Microsoft provides security related updates to default provisioned apps through the Microsoft Update Catalog for WSUS or as MSI files, as an alternate method to the Windows Store for updating.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128
To remove the Calculator app from the system:
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., Microsoft.WindowsCalculator_2013.822.1828.2633_neutral_~_8wekyb3d8bbwe).
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename", substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the default Calculator app has been patched with the latest security related updates or removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : Microsoft.WindowsCalculator" is listed and has not been updated with the latest security related updates, this is a finding.
The "PackageName" field will identify the version installed.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128WN08-GE-000049<GroupDescription></GroupDescription>WN08-GE-000049The Windows 8 default Food and Drink app must be updated with the latest security patches or removed from the system.<VulnDiscussion>Applications must be updated as flaws are identified and remediations are made available. The default method for updating Windows 8 apps is through the Windows Store, which is required to be blocked. An alternate method must be used to maintain the default Windows 8 apps with the latest security updates if they are allowed on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Maintain the Food & Drink app with the latest security related updates or remove it from the system. Microsoft provides security related updates to default provisioned apps through the Microsoft Update Catalog for WSUS or as MSI files, as an alternate method to the Windows Store for updating.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128
To remove the Food & Drink app from the system:
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., Microsoft.BingFoodAndDrink_2013.820.258.2561_neutral_~_8wekyb3d8bbwe).
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename", substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the default Food & Drink app has been patched with the latest security related updates or removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : Microsoft.BingFoodAndDrink" is listed and has not been updated with the latest security related updates, this is a finding.
The "PackageName" field will identify the version installed.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128WN08-GE-000050<GroupDescription></GroupDescription>WN08-GE-000050The Windows 8 default Health and Fitness app must be updated with the latest security patches or removed from the system.<VulnDiscussion>Applications must be updated as flaws are identified and remediations are made available. The default method for updating Windows 8 apps is through the Windows Store, which is required to be blocked. An alternate method must be used to maintain the default Windows 8 apps with the latest security updates if they are allowed on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Maintain the Health & Fitness app with the latest security related updates or remove it from the system. Microsoft provides security related updates to default provisioned apps through the Microsoft Update Catalog for WSUS or as MSI files, as an alternate method to the Windows Store for updating.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128
To remove the Health & Fitness app from the system:
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., Microsoft.BingHealthandFitness_2013.813.243.3760_neutral_~_8wekyb3d8bbwe).
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename", substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the default Health & Fitness app has been patched with the latest security related updates or removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : Microsoft.BingHealthAndFitness" is listed and has not been updated with the latest security related updates, this is a finding.
The "PackageName" field will identify the version installed.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128WN08-GE-000051<GroupDescription></GroupDescription>WN08-GE-000051The Windows 8 default Help + Tips app must be updated with the latest security patches or removed from the system.<VulnDiscussion>Applications must be updated as flaws are identified and remediations are made available. The default method for updating Windows 8 apps is through the Windows Store, which is required to be blocked. An alternate method must be used to maintain the default Windows 8 apps with the latest security updates if they are allowed on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Maintain the Help + Tips app with the latest security related updates or remove it from the system. Microsoft provides security related updates to default provisioned apps through the Microsoft Update Catalog for WSUS or as MSI files, as an alternate method to the Windows Store for updating.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128
To remove the Help + Tips app from the system:
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., Microsoft.HelpAndTips_2013.822.1812.1279_neutral_~_8wekyb3d8bbwe).
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename", substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the default Help + Tips app has been patched with the latest security related updates or removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : Microsoft.HelpAndTips" is listed and has not been updated with the latest security related updates, this is a finding.
The "PackageName" field will identify the version installed.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128WN08-GE-000052<GroupDescription></GroupDescription>WN08-GE-000052The Windows 8 default Reading List app must be updated with the latest security patches or removed from the system.<VulnDiscussion>Applications must be updated as flaws are identified and remediations are made available. The default method for updating Windows 8 apps is through the Windows Store, which is required to be blocked. An alternate method must be used to maintain the default Windows 8 apps with the latest security updates if they are allowed on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Maintain the Reading List app with the latest security related updates or remove it from the system. Microsoft provides security related updates to default provisioned apps through the Microsoft Update Catalog for WSUS or as MSI files, as an alternate method to the Windows Store for updating.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128
To remove the Reading List app from the system:
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., Microsoft.WindowsReadingList_2013.822.1837.5741_neutral_~_8wekyb3d8bbwe).
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename", substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the default Reading List app has been patched with the latest security related updates or removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : Microsoft.WindowsReadingList" is listed and has not been updated with the latest security related updates, this is a finding.
The "PackageName" field will identify the version installed.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128WN08-GE-000053<GroupDescription></GroupDescription>WN08-GE-000053The Windows 8 default Scan app must be updated with the latest security patches or removed from the system.<VulnDiscussion>Applications must be updated as flaws are identified and remediations are made available. The default method for updating Windows 8 apps is through the Windows Store, which is required to be blocked. An alternate method must be used to maintain the default Windows 8 apps with the latest security updates if they are allowed on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Maintain the Scan app with the latest security related updates or remove it from the system. Microsoft provides security related updates to default provisioned apps through the Microsoft Update Catalog for WSUS or as MSI files, as an alternate method to the Windows Store for updating.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128
To remove the Scan app from the system:
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., Microsoft.WindowsScan_2013.822.1832.4879_neutral_~_8wekyb3d8bbwe).
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename", substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the default Scan app has been patched with the latest security related updates or removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : Microsoft.WindowsScan" is listed and has not been updated with the latest security related updates, this is a finding.
The "PackageName" field will identify the version installed.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128WN08-GE-000055<GroupDescription></GroupDescription>WN08-GE-000055The Windows 8 default Sound Recorder app must be updated with the latest security patches or removed from the system.<VulnDiscussion>Applications must be updated as flaws are identified and remediations are made available. The default method for updating Windows 8 apps is through the Windows Store, which is required to be blocked. An alternate method must be used to maintain the default Windows 8 apps with the latest security updates if they are allowed on a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000366Maintain the Sound Recorder app with the latest security related updates or remove it from the system. Microsoft provides security related updates to default provisioned apps through the Microsoft Update Catalog for WSUS or as MSI files, as an alternate method to the Windows Store for updating.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128
To remove the Sound Recorder app from the system:
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
Make note of the PackageName (e.g., Microsoft.WindowsSoundRecorder_2013.822.1835.2133_neutral_~_8wekyb3d8bbwe).
Enter the following to remove the app package from the system: "dism /online /Remove-ProvisionedAppxPackage /PackageName:packagename", substituting "packagename" noted from the previous step.
Uninstall the application from any user profiles provisioned prior to this.Verify the default Sound Recorder app has been patched with the latest security related updates or removed from the system.
Open a command prompt as an administrator.
Enter "dism /online /Get-ProvisionedAppxPackages".
If "DisplayName : Microsoft.WindowsSoundRecorder" is listed and has not been updated with the latest security related updates, this is a finding.
The "PackageName" field will identify the version installed.
Microsoft Article 2971128 summarizes security related updates to the default apps, including versions and release dates. http://support.microsoft.com/kb/2971128WINCC-000147<GroupDescription></GroupDescription>WN08-CC-000147The touch keyboard or input panel must not highlight keys as passwords are entered.<VulnDiscussion>The touch keyboard or input panel may highlight keys as passwords are entered, providing visibility to nearby persons, and compromising them.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000206If the system does not have a touch screen, this is NA.
Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Tablet PC -> Input Panel -> "Turn off password security in Input Panel" to at least "Enabled: Medium High".If the system does not have a touch screen, this is NA.
If the system has a touch screen and the following registry values do not exist or are not configured as specified, this is a finding:
Registry Hive: HKEY_LOCAL_MACHINE
Registry path: \SOFTWARE\Policies\Microsoft\TabletTip\1.7\
Value Name: PasswordSecurityState
Type: REG_DWORD
Value: 1
Value Name: PasswordSecurity
Type: REG_DWORD
Value: 4 or 5
(1, 2, or 3 are a finding)WIN00-000018<GroupDescription></GroupDescription>WN08-00-000018The operating system must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.<VulnDiscussion>Utilizing a whitelist provides a configuration management method for allowing the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities.
The organization must identify authorized software programs and only permit execution of authorized software. The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as whitelisting.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-001774This is applicable to unclassified systems, for other systems this is NA.
Configure an application whitelisting program to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.
Configuration of whitelisting applications will vary by the program. AppLocker is a whitelisting application built into Windows 8 Enterprise.
If AppLocker is used, it is configured through group policy in Computer Configuration >> Windows Settings >> Security Settings >> Application Control Policies >> AppLocker.
Implementation guidance for AppLocker is available in the NSA paper "Application Whitelisting using Microsoft AppLocker" under the Microsoft Windows section of the following link:
https://www.nsa.gov/ia/mitigation_guidance/security_configuration_guides/operating_systems.shtmlThis is applicable to unclassified systems, for other systems this is NA.
Verify the operating system employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs. This must include packaged apps such as the Windows 8 modern/universal apps installed by default on systems.
If an application whitelisting program is not in use on the system, this is a finding.
Configuration of whitelisting applications will vary by the program.
AppLocker is a whitelisting application built into Windows 8 Enterprise. A deny-by-default implementation is initiated by enabling any AppLocker rules within a category, only allowing what is specified by defined rules.
If AppLocker is used, perform the following to view the configuration of AppLocker:
Open PowerShell.
If the AppLocker PowerShell module has not been previously imported, execute the following first:
Import-Module AppLocker
Execute the following command, substituting [c:\temp\file.xml] with a location and file name appropriate for the system:
Get-AppLockerPolicy -Effective -XML > c:\temp\file.xml
This will produce an xml file with the effective settings that can be viewed in a browser or opened in a program such as Excel for review.
Implementation guidance for AppLocker is available in the NSA paper "Application Whitelisting using Microsoft AppLocker" under the Microsoft Windows section of the following link:
https://www.nsa.gov/ia/mitigation_guidance/security_configuration_guides/operating_systems.shtmlWIN00-000145<GroupDescription></GroupDescription>WN08-00-000145Data Execution Prevention (DEP) must be configured to at least OptOut.<VulnDiscussion>Attackers are constantly looking for vulnerabilities in systems and applications. Data Execution Prevention (DEP) prevents harmful code from running in protected memory locations reserved for Windows and other programs.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002824Configure DEP to at least OptOut.
Open a command prompt (cmd.exe) or PowerShell with elevated privileges (Run as administrator).
Enter "BCDEDIT /set {current} nx OptOut". (If using PowerShell "{current}" must be enclosed in quotes.)
"AlwaysOn", a more restrictive selection, is also valid but does not allow applications that do not function properly to be opted out of DEP.
Note: Suspend BitLocker before making changes to the DEP configuration.
Opted out exceptions can be configured in the "System Properties".
Open "System" in Control Panel.
Select "Advanced system settings".
Click "Settings" in the "Performance" section.
Select the "Data Execution Prevention" tab.
Applications that are opted out are configured in the window below the selection "Turn on DEP for all programs and services except those I select:".If DEP is configured through the Enhanced Mitigation Experience Toolkit (EMET) (V-36705), this is NA.
Verify the DEP configuration.
Open a command prompt (cmd.exe) or PowerShell with elevated privileges (Run as administrator).
Enter "BCDEdit /enum {current}". (If using PowerShell "{current}" must be enclosed in quotes.)
If the value for "nx" is not "OptOut", this is a finding.
(The more restrictive configuration of "AlwaysOn" would not be a finding.)WIN00-000150<GroupDescription></GroupDescription>WN08-00-000150Structured Exception Handling Overwrite Protection (SEHOP) must be turned on.<VulnDiscussion>Attackers are constantly looking for vulnerabilities in systems and applications. Structured Exception Handling Overwrite Protection (SEHOP) blocks exploits that use the Structured Exception Handling overwrite technique, a common buffer overflow attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-002824Configure the following registry value:
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Control\Session Manager\kernel\
Value Name: DisableExceptionChainValidation
Value Type: REG_DWORD
Value: 0If SEHOP is configured through the Enhanced Mitigation Experience Toolkit (EMET) (V-36706), this is NA.
Verify SEHOP is turned on.
If the following registry value does not exist or is not configured as specified, this is a finding.
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Control\Session Manager\kernel\
Value Name: DisableExceptionChainValidation
Value Type: REG_DWORD
Value: 0WINCC-000150<GroupDescription></GroupDescription>WN08-CC-000150WDigest Authentication must be disabled.<VulnDiscussion>When the WDigest Authentication protocol is enabled, plain text passwords are stored in the Local Security Authority Subsystem Service (LSASS) exposing them to theft. This setting will prevent WDigest from storing credentials in memory.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 8DISADPMS TargetWindows 82348CCI-000381Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "WDigest Authentication (disabling may require KB2871997)" to "Disabled".
Note: Microsoft Security Advisory update 2871997 is not required for Windows 8.1. (Windows 8.0 is no longer supported.)
This policy setting requires the installation of the SecGuide custom templates included with the STIG package. "SecGuide.admx" and "SecGuide.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively.If the following registry value does not exist or is not configured as specified, this is a finding.
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Control\SecurityProviders\Wdigest\
Value Name: UseLogonCredential
Type: REG_DWORD
Value: 0x00000000 (0)
Note: Microsoft Security Advisory update 2871997 is not required for Windows 8.1. (Windows 8.0 is no longer supported.)